Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vtunerd in VU+ Duo receiver does not transmit audio and video #13

Open
GoogleCodeExporter opened this issue Oct 31, 2015 · 69 comments
Open

vtunerd in VU+ Duo receiver does not transmit audio and video #13

GoogleCodeExporter opened this issue Oct 31, 2015 · 69 comments

Comments

@GoogleCodeExporter
Copy link
Contributor

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

What steps will reproduce the problem?
vtunerd in VU+ Duo receiver does not transmit audio and video to vtunerc in 
ubuntu (10 or 11)



What is the expected output? What do you see instead?
To get audio and video on my ubuntu by using VU+ Duo tuner.



What version of the product are you using? On what operating system?
I tried binaries given here in September and October, I also compiled with 
today's source codes and used vtunerd.mipsel (I had already mipsel compile 
enviroment on my ubuntu) and vtunerc.i686. All gave the same result.




Please provide any additional information below.
I can see signal amount and EPG data on client perfectly but no audio or video 
is transmitted. 

Just as a not, T can easily have audio and video with my external usb dvbs2 
card.

I think there should be some code modification needed for VU driver.

I would be more than happy to  test to help you and, provide  any logs needed.


Best regards...

Original issue reported on code.google.com by buyukb...@gmail.com on 13 Jan 2012 at 11:54

  • Blocking: #14
@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I never played with any VU+ receiver unfortunatelly. Do you know how is DVB API 
behave there? Is it same to Dreambox or more like normal linux DVB API? If it 
is not DMM variant, then you can try to change DRIVER=vtuner-dmm-3 to 
DRIVER=vtuner-dvb-3 in buidl/mipsel/Makefile.

Honza

Original comment by jpetrous on 13 Jan 2012 at 2:49

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Unfortunately I really don't have enough knowledge about the dvbapi, but VU 
made public all its source codes including drivers 2 month ago. I wish this 
could help you to identify implementation method. You can find the codes here: 
http://code.vuplus.com 

I'll test DRIVER=vtuner-dvb-3 then inform you with the results.

Best regards...

Original comment by buyukb...@gmail.com on 13 Jan 2012 at 7:36

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I changed mipsel make file (replaced all dmm occurences with dvb) an I got 
below segmentation fault, which I didn't see with the dmm version:

Best regards...

root@vuduo:/media/usb# ./vtunerd.mipsel
vtunerd: [1973 ../../vtunerd.c:87]  info: S2API tuning support.
vtunerd: [1973 ../../vtuner-dvb-3.c:57]  info: FE_GET_INFO dvb-type:0 
vtuner-type:1
vtunerd: [1973 ../../vtunerd.c:97]  info: adapter:0, frontend:0, demux,0, dvr:0 
is type:1
vtunerd: [1973 ../../vtunerd-service.c:263]  info: waiting for autodiscover 
packet (groups 0xFFFFFFFF) ...
vtunerd: [1973 ../../vtunerd.c:111]  info: received discover request proto2, 
vtuner_type:9 group:0xFFFFFFFF
vtunerd: [1973 ../../vtunerd-service.c:263]  info: waiting for autodiscover 
packet (groups 0xFFFFFFFF) ...
vtunerd: [1973 ../../vtuner-dvb-3.c:57]  info: FE_GET_INFO dvb-type:0 
vtuner-type:1
vtunerd: [1973 ../../vtunerd-service.c:57] error: failed to bind socket - 
Invalid argument
vtunerd: [1973 ../../vtunerd-service.c:313]  info: control socket bound to 0
vtunerd: [1973 ../../vtunerd-service.c:57] error: failed to bind socket - 
Invalid argument
vtunerd: [1973 ../../vtunerd-service.c:326]  info: session prepared control:0 
data:0
vtunerd: [1973 ../../vtunerd-service.c:146] error: accept failed on data socket 
- Socket operation on non-socket
vtunerd: [1973 ../../vtunerd-service.c:249]  info: TS data copy thread 
terminated.
vtunerd: [1973 ../../vtunerd-service.c:344]  info: no client connected. timeout
vtunerd: [1973 ../../vtunerd-service.c:496]  info: control thread terminated.
Segmentation fault
root@vuduo:/media/usb# 

Original comment by buyukb...@gmail.com on 14 Jan 2012 at 4:32

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

OK, can you check the following few steps?

1, show what is running currently: "ps" or "ps -ef" or "ps aux" (dunno which 
variant works on your box)
2, start vtunerc.mipsel: "./vtunerd.mipsel -v 4" and save debug output
3, again show what is running (same command lin in step 1.)

Show me all those 3 debugs. I will try to understand what is going there.

Honza

Original comment by jpetrous on 19 Jan 2012 at 10:13

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

ok, I'll test these. I just need a clarification:

1,3 - I always kill emu's (kill -9) and then kill enigma (init 4) before 
running vtunerd on my VU+. Do yo want me to do same , or test without killing 
these processes?

2- Do you need DRIVER=vtuner-dmm-3 logs or DRIVER=vtuner-dvb-3 or both ?


Regards...

Original comment by buyukb...@gmail.com on 20 Jan 2012 at 7:14

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

you have to kill enigma at least, otherwise vtunerd can't be able to connect to 
DVB device. So yes, kill enigma+emu. Would be simple for analysis

Honza

Original comment by jpetrous on 20 Jan 2012 at 8:05

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

-v 4 is not working for me:

root@vuduo:/media/usb# ./vtunerd.mipsel -v 4
vtunerd: [6071 ../../vtunerd.c:73] error: Parameter mismatch. 0 tuner(s) 
requires 1 arguments, but 2 given.


So instead, i tried these, however I don't know if it's true or not (most 
probably not): root@vuduo:/media/usb# /media/usb/vtunerd.mipsel 1 0 1 2 -v4

You can see the full log here:
http://pastebin.com/sRTjyMc2


Please not that I provided log for the "DRIVER=vtuner-dvb-3" version.


regards...

Original comment by buyukb...@gmail.com on 20 Jan 2012 at 11:06

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I would like to test....

vu+duo

Original comment by ufukun...@gmail.com on 21 Jan 2012 at 4:05

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I would like to test....

vu+ solo


Add a comment 

Original comment by erkan.ge...@gmail.com on 21 Jan 2012 at 10:48

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I would like to test....

vu+ solo

Original comment by erkan.ge...@gmail.com on 21 Jan 2012 at 10:48

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I would like to test....

vu+ solo

Original comment by erkan.ge...@gmail.com on 21 Jan 2012 at 10:48

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

> -v 4 is not working for me:
>
> root@vuduo:/media/usb# ./vtunerd.mipsel -v 4
> vtunerd: [6071 ../../vtunerd.c:73] error: Parameter mismatch. 0 tuner(s) 
requires 1 arguments, but 2 given.

Ah, so you are using OLD version of binaries!

Fresh binaries has changed command line option parsing and now you can easily 
check what parameters can be used (by using -h parameter). Like here:

# ./vtunerd.mipsel -h
vtunerd: vtuner server (vtunerd), part of vtuner project
Visit http://code.google.com/p/vtuner/ for more information
Copyright (C) 2009-11 Roland Mieslinger
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.
vtunerd: Revision:3a9233717687/tip DVB:5.3 allow:5.x NetProto:2 MsgSize:96, 
Debug:0x3
vtunerd: 
Command line options:
    -d devs_list             : adapter[:frontend[:demux[:dvr]]] (default is 0:0:0:0)
    -g group_mask            : listen for group members requests only
    -l ip_address            : listen on local ip address (default is on ALL)
    -p port_number           : listen on local port (default is 39305)
    -u ip_address:port_number: send message log to udp://ip_address:port_number
    -v level                 : verbosity level (1:err,2:warn,3:info,4:debug)

I have attached two binaries: vtunerd.mipsel, which you can already download 
from Dowload section here on code.google.com and added another one, which 
should be port of standard linux DVB API (like it is for i686,x86_64, sh4 and 
arm) but for mipsel cpu. 

Please try vtunerd-dvb.mipsel. And don't forget to use debug paramer "-v 4".

Honza

Original comment by jpetrous on 22 Jan 2012 at 10:01

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

OK, I get it :/ This time I was be able to collect proper debug logs as you 
mentioned. You can find the logs and the screenshot that shows a valid SNR when 
using vtunerd. As you can see from the log, I changed the channel 10+ time and 
always see valid SNR. Just I ve no audio/video.

As a footer note:
I'm using OpenPLiPC project to test it. All OpenPLiPC guys having DMM are using 
vtuner which is a wonderful driver to test and develop the project ! All have 
audio/video with  vtunerd on DMM  + vtunerc/OpenPLiPC on Ubuntu configuration. 
You can find the project here:

GIT:
https://github.com/nobody9/openpliPC (if you are interested in compiling, see 
readme file. compiling is really very simple) -

Discussion thread:
http://openpli.org/forums/topic/20871-build-script-for-openpli-enigma2-on-ubuntu
-104-32-bit/ (project was started as a simple build script, but now have its 
own GIT. So discard first messages and see latest pages)

Original comment by buyukb...@gmail.com on 22 Jan 2012 at 11:37

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Interesting, it looks like some data come correctly.

Can you show me what says "cat /proc/vtunerc0" on client side?

There should be visible if data are receiving or not.

BTW, the easiest way of checking if vtuner sharing works is using command line 
tools. Something like that:

1, start vtunerd on server side

2, start vtunerc on client side (of course vtunerc.ko linux driver module has 
to be inserted already)

3, edit .szap/channels.conf with some well-known TV channel data

4, run "szap -r <your_favourite_channel>"

And when you get LOCK you can test if all is ok by using for example mplayer:

5, "mplayer /dev/dvb/adapter0/dvr0" (adapter0 in the case if you don't have any 
other real DVB hardware there, otherwise it will be first free bigger index)

Now you should see picture.

I like this way of testing because it is using as simple tools as possible.

Honza

Original comment by jpetrous on 22 Jan 2012 at 3:36

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I'm getting below log for vtunerc0:
ubuntu@ubuntu-VirtualBox:~$ cat /proc/vtunerc0
[ vtunerc driver, version 1.2p1 ]
  sessions: 1
  TS data : 0
  PID tab : 134 100 (len=2)
  FE type : vTuner DVB-S2
  msg xchg: -1/-1
ubuntu@ubuntu-VirtualBox:~$ 

I tried szap, i think below means its locked successfully?:
ubuntu@ubuntu-VirtualBox:~/.szap$ szap -r ShowTV
reading channels from file '/home/ubuntu/.szap/channels.conf'
zapping to 1 'ShowTV':
sat 0, frequency = 11964 MHz H, symbolrate 5925000, vpid = 0x0134, apid = 
0x0100 sid = 0x0111
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal c2c7 | snr 0000 | ber 00000000 | unc 00000000 | 
status 1f | signal 642b | snr a8f5 | ber 0000a8f5 | unc 0000a8f5 | FE_HAS_LOCK
status 1f | signal 5e9a | snr a6b7 | ber 0000a6b7 | unc 0000a6b7 | FE_HAS_LOCK
status 1f | signal 642b | snr a784 | ber 0000a784 | unc 0000a784 | FE_HAS_LOCK
status 1f | signal 642b | snr a91e | ber 0000a91e | unc 0000a91e | FE_HAS_LOCK
...


But mplayer playes nothing:
ubuntu@ubuntu-VirtualBox:~/.szap$ mplayer /dev/dvb/adapter0/dvr0 
mplayer: Symbol `ff_codec_bmp_tags' has different size in shared object, 
consider re-linking
Creating config file: /home/ubuntu/.mplayer/config
MPlayer SVN-r33713-4.6.1 (C) 2000-2011 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /dev/dvb/adapter0/dvr0.

Original comment by buyukb...@gmail.com on 22 Jan 2012 at 4:33

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

LOCK good ok, but "ber" value points to some weak signal or something like 
that. Usually BER should be zero also.

Anyway, if you see "TS data : 0" in your /proc/vtunerc0 status,
then no real data are comming for sure. 

Strange.

BTW, I have noticed you have runnung usbtunerhelper on the box before.
Is it working for you? If yes, then I can analyze usbtunerhelper source and 
check what is there different.

Honza

Original comment by jpetrous on 22 Jan 2012 at 4:50

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I noticed usbtunerhelper with your above message :) I think it is installed and 
executed automatically by VU+ Duo PLi image since I never did anything related 
with usbtunerhelper or never used a usb tuner on my VU+.

Original comment by buyukb...@gmail.com on 22 Jan 2012 at 8:53

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hehe, oki :)

Anyway, do you have any usb dvb device to make a test?
If you confirm that usbtunerhelper works then I can check why vtuner nope.

Honza

Original comment by jpetrous on 22 Jan 2012 at 9:39

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Unfortunately I don't have any dvb device at the moment :( But I know that VU+ 
supports some DVB-T/C tuners and there are some VU+ users that uses them. For 
example,  Blackhole image team is releasing images only for VU+ at the moment 
and they included some usb tuner drivers to support this.  But I'm not sure if 
this is what your are asking or if this is directly related with usbtunerhelper 
or not ?

Regards...

Original comment by buyukb...@gmail.com on 22 Jan 2012 at 10:57

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

It's pity :(

As I don't have access to any VU+ device (with SUB tuner plugged in) either I 
can't help more. 

IF I find somebody willing to provide me access to the required hardware, then 
I can continue on the bug evaluating.

Honza

Original comment by jpetrous on 22 Jan 2012 at 11:31

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I'll try to find somebody with a dvb usb tuner in VU+ community that can help 
you. BTW, are DVB-T or DVB-C usb tuners OK for this testing? AFAIK DVBS usb 
sticks is not working on enigma2 at the moment?

Original comment by buyukb...@gmail.com on 22 Jan 2012 at 11:46

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

> BTW, are DVB-T or DVB-C usb tuners OK for this testing?

T or C, no difference for me.

>  AFAIK DVBS usb sticks is not working on enigma2 at the moment?

Dunno, but I don't see any reason why it should not work other then bug in 
vtuner linux driver.

So using our open-source vtunerc.ko should work.

Honza

Original comment by jpetrous on 23 Jan 2012 at 2:57

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

With OpenpliPC you cannot get image and video on other adapter than 
/dev/dvb/adaptor0 even if you set it to unconfigured in OpenpliPC and that you 
set your setup on adaptor 1 for example this doesn't work.
So when you test it be sure that vtunerc is the only device in your openpliPC.
So my advice is that you disconnect your external USB DVB-S2 card on the PC on 
which you are running OpenpliPC to test vtunerc.

Mebepi

Original comment by mebep...@gmail.com on 24 Jan 2012 at 10:08

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Yes, I already exactly tested as you said. Additionally testing with 
szap+mplayer (see above messages) gave the same result. So vtunerd is not 
working with VU+ at the moment, for sure.

Original comment by buyukb...@gmail.com on 25 Jan 2012 at 12:40

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Original comment by jpetrous on 26 Jan 2012 at 9:11

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I just tested the last file, but nothing is different :(

Original comment by buyukb...@gmail.com on 5 Feb 2012 at 12:12

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

OK thanks for the test and the feedback.

Last night I build the environment for vuduo. So please find attached the 
specifically compiled version of vtuner for VU+ Duo

Can you please also run the test program and show me the result?

Mebepi

Original comment by mebep...@gmail.com on 5 Feb 2012 at 10:30

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi again,

I tested the files. You can find the logs attached. Still no audio and picture 
on my ubuntu, only EPG data and a meaningful signal value.

Thank you for your precious efforts !

Regards...

Original comment by buyukb...@gmail.com on 5 Feb 2012 at 5:39

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

You client side compilation is not correct (I think), it is compiled for 
DVB_API 3.x not 5.x.  So I attach mine, please test.

Please ensure that the VU+ is in standby when testing to be sure that the 
frontend is free.

vtunerd.vuplus 

On the PC start:  vtunerc.i686 -f s2 -n 192.168.2.13 
(with my provided version please don't specify :1 let vtuner handshake itself 
the right type).

And please test first on FTA channels (please test on different and let time to 
image to display).

I would also advice you to edit: /usr/local/e2/share/enigma2/xine.conf  
and change video.driver=auto to video.driver:opengl

I also compare md5 checksum between Vuplus and Xtrend and both are identitical 
and Vuplus version is compiled toward Vuplus kernel header, so I guess that it 
should also work for you and that we are close to the solution.

I saw that you use a virtual instance I should perhaps give a try in a virtual 
instance too.

Mebepi

Original comment by mebep...@gmail.com on 5 Feb 2012 at 6:31

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

Sorry attachement was missing here it is.

Mebepi

Original comment by mebep...@gmail.com on 5 Feb 2012 at 6:32

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Good news !!!

I got audio/video with the szap application !!! Still have no audio video with 
openPLi, but I think this should be related with my openPLi settings or 
compilation.  I'm now investigating this issue.

BTW, I noticed that even with the vtuner.i686 that I used previously, I can get 
video (without audio). I found the mistake in my previous tests: I tested first 
openPLi, test failed, then I tried to test szap. This way makes szap not 
working completely. I don't know whey but a restart of vtunerc is needed to 
test the second application.


Original comment by buyukb...@gmail.com on 6 Feb 2012 at 12:34

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Even channel scanning does not find any channel on PLiPC. I was able to get 
audio video with my usb dvbs2 tuner, but I cannot get with vtuner, there may be 
some defect ? Have you ever tested PLiPC ? Do you have any idea on that?

Original comment by buyukb...@gmail.com on 6 Feb 2012 at 12:43

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

Yes I am playing everyday with OpenpliPC and vtunerc and it is working really 
fine.
Already test vtunerc with DVB-S2 and DVB-C remote access.

Please use the osd branch of OpenpliPC it is the one that is working the best.
Even if you have an Nvidia card! Please change your xine.conf file to use 
video.driver=opengl instead of auto (this will use then vdpau if you have a 
Nvidia card).

Scanning is also working for me even if it is slower than on a real STB.

But be sure that vtunerc is mounted on /dev/dvb/adaptor0/frontend0 when you do 
test.
Playing with other configuration can leads to problems but this is OpenpliPC 
specific problem not vtunerc related. If you play also with scrambled channels 
the dvbsoftwareca provided with OpenpliPC needs to be "rmmod" after each use of 
OpenpliPC. Then launch vtunerc wait and then "modprobe dvbsoftwareca" doing 
this gives the better result, but I have got many problem to get unscrambled 
image with the vdpau driver so forcing it to opengl gives better result, but 
then you need a more powerfull CPU.

Mebepi

Original comment by mebep...@gmail.com on 6 Feb 2012 at 9:59

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I just noticed your comment in your previous post:  "I would also advice you to 
edit: /usr/local/e2/share/enigma2/xine.conf and change video.driver=auto to 
video.driver:opengl" So you're using opnePli :) 

I tried OpenGL, but unfortunately it is not working in Virtualbox. Instead I'm 
using it with XSHM in my Virtualbox image. XSHM is implemented in OSD brach 
like OpenGL and I can see OSD without any problem. I had a usb dvbs2 tuner (I 
don't have it anymore) and tested with XSHM and got audio / video. 

Original comment by buyukb...@gmail.com on 6 Feb 2012 at 10:07

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

I'm sure that vtunerc is mounted on /dev/dvb/adaptor0/frontend0 since I can see 
audio picture with szap + mplayer combination. It's just perfect for freeview 
channels. Could't tried scrambled channels since I could not have audio/picture 
on my OpenPLi. Did you have any chance to test XSHM ?

BTW, can I learn in PLi forum nick :)



Original comment by buyukb...@gmail.com on 6 Feb 2012 at 10:13

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Do you:  git pull

and recompile the OpenpliPC osd branch because it is often updated, and first 
version doesn't support OpenGL just XSHM but the latest version now support 
also OpenGL.


Original comment by mebep...@gmail.com on 6 Feb 2012 at 10:14

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Yes, I created openpli OSD branch from scratch last night. I both tried OpenGL 
and XSHM. OpenGL is not still working on VM, it's killed immediately This is 
completely a VM related issue. But XSHM works, I got OSD, I saw a logical 
signal value on the skin without audio or picture. Of course I can install and 
use directly to my PC instead of VM, but this is not the target. I want to 
prepare easily shareble VM images with working and ready to use OpenPLi 
installed for people witout any linux and compile knowledge. I'm sure there is 
something very small is overlooked since I got audio/picture with usb tuner 
with XSHM? BTW, audio/video is not the only problem, as I said before, channel 
scanning also cannot find no channels. I did nothing special:

1- compiled openPli from scracth.
2- started vtunerd and vtunerd.
3- I saw audio video with szap+mplayer
4- restarted vtunerd and vtunerd.
5- Copied my settings from VU+ to OpenPli.
6- Changed tuner setting to VTuner.
7- Changed xine.conf as XSHM
8- Started OpenPli

Is there any missing step or setting ?

Original comment by buyukb...@gmail.com on 6 Feb 2012 at 11:10

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

I think that the goal here is not to troubleshoot your OpenpliPC installation.
Please post your questions on Openpli forum where people can help you.

For me issue #13 on vtuner is now solved since I didn't change anything in the 
source code, I just compile properly the vtunerc and vtunerd towards VU+ 
include files for you.

Mebepi.

Original comment by mebep...@gmail.com on 6 Feb 2012 at 11:57

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Yes you're right. At this point I'll try other dvb applications to be sure 
about the vtuner since to verify channel scan and channel change. I just only 
one channel in my szap config file (since manually adding channels to this file 
is a bit difficult), then I'll try to make openpliPC work.

These are my last question, could you please kindly answer them as a final note 
:

1- BTW, you changed no code? I previously tested vtunerd.mipsel files given in 
this site, and you can find one in the above messages given by Honza. None of 
them worked with szap. So I assume only gcc that you used made the difference 
in my szap+mplayer tests? Right ? Is this the same for your XTrend ? 

2- I think you used vtuner-dmm-3, not vtuner-dvb-3?  So you did't changed make 
config ?

3- Should I do anything special to compile vtunerc for DVB API 5? I'm using 
ubuntu 11.10 and I assume that DVB API 5 exist on ubuntu 11.10. Isn't the one 
that Honza provides the same ?


Thank you very much for all you helps and precious efforts !!!

Original comment by buyukb...@gmail.com on 6 Feb 2012 at 12:23

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hi,

1-

What I did is:
- Create a full Openpli environment for Vuplus on my build PC.
- I have the crosscompiler installed on my build PC.
- I create a full new bunch of file to build vtunerc/vtunerd based on mipsel 
one.

To do so I duplicate the ./build/mipsel into ./build/vuplus

Edit file:  ./build/vuplus/Makefile and change:

CFLAGS=-fpic -DHAVE_DVB_API_VERSION=5 -DHAVE_DREAMBOX_HARDWARE 
$(INCLUDE-$(ARCH)) $(INCLUDE2-$(ARCH)) $(DBGFLAGS)

Edit file: Make.config

# define the CC for target vuplus
CC-vuplus=/home/mebepi/vuplus/mipsel-unknown-linux-gnu/bin/mipsel-unknown-linux-
gnu-gcc
CXX-vuplus=/home/mebepi/vuplus/mipsel-unknown-linux-gnu/bin/mipsel-unknown-linux
-gnu-g++
INCLUDE2-vuplus=-I/home/mebepi/vuplus/build-vuduo/tmp/sysroots/vuduo-oe-linux/ke
rnel/include
INCLUDE-vuplus=-I/home/mebepi/vuplus/build-vuduo/tmp/sysroots/vuduo-oe-linux/ker
nel/arch/mips/include

The main point here is that I pickup the kernel include and arch/mips include 
file form the folder where I compile an openpli image for Vuplus (I choose a 
vuduo image).
This is the goal of INCLUDE and INCLUDE2 parameters.

After having compile towards those include file everything is working fine, so 
yes I compile with vtuner-dmm-3 (answer to question 2), nothing is changed 
compared to mipsel standard compilatione except the include files.

I do the same operation for xtrend and compared both compiled vtunerc and 
vtunerd md5sum and they are the same, so the headers are the same both for VU+ 
Duo and Xtrend ET-9x00.  I should check with VU+ Ultimo to see if the result is 
the same.
But since I don't own VU+ hardware this is not really usefull for me.

3- On Unbuntu you need to change the include file location to: 

Follow the tuto:  http://wiki.nessiedvb.org/wiki/doku.php?id=install_vtunerc

But replace the KDIR command mentioned in the tuto with:

make KDIR=/usr/src/linux-headers-`uname -r`

I already provide to Honza all the informations to successfully build a version 
for VU+ and Xtrend.

Mebepi

P.S.: if you don't know how to build a full openpli image please check this:
http://users.telenet.be/spstefansp/openpliubuntu.html

But be careful you need to use Makefile-2.1 and not Makefile-2.0 like in the 
explanations.
The hardest part is to find all the required packages to successfully build the 
image, since some mirrors are temporarily down or sometimes no longer available.

Original comment by mebep...@gmail.com on 6 Feb 2012 at 1:23

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Thank you very much again for the complete answer ! I have already openpli 
compile environment, it seems as I just need to modify make and make config 
files as you suggested. I'll try to compile vtuner this evening.

Regards...

Original comment by buyukb...@gmail.com on 6 Feb 2012 at 2:05

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Oh, few days I'm out and so nice progress. Good job Mebepi!

In day or two I should be back and then we can commit all necessary changes for 
build system to get working binaries for VU+/ET boxes.

Honza

Original comment by jpetrous on 6 Feb 2012 at 8:42

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

@Mebepi

I compiled vtunerd for VU this evening, with the suggested Make/ Make Config 
modifications. My compiled binaries gives the same with the ones that you 
attached above. Here are the results:

1- szap+mplayer gives audio + video with a manually created channels.conf.
2- w_scan finds no channel, so I could not create a channels.conf.  It locks to 
the frequencie,s but cannot find any channel.
3- I get No audio/video on PliPC with imported settings. EPG is OK. Signal is 
OK. BER always shows numbers like 31 strangely.
4- PliPC cannot find any channels in channel scans. It locks to the 
frequencies, but cannot find any channel.
5- Finally scan with the Mythtv cannot find any channels in channel scans. It 
locks to the frequencies, but cannot find any channel.


@Honza,
You had suggested to me to use szap as the simplest test tool. What are the 
differences of other DVB apps when compared to szap? Do you have any 
explanation that my tests 2,3,4,5 fail while only 1 succeeds? Any suggestion 
for the further test cases to prove vtunerd is working with no problem or not.

As I said before, I'm using a Virtual Machine (ubuntu 11.10) on my Windows 7. 
Do you think this is cauesed by a VM usage? May be a second VU+ user should 
check the results ??

Regards...

Original comment by buyukb...@gmail.com on 7 Feb 2012 at 9:26

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Still no progress here :( I think there is something wrong for vu+ here which 
is not PLi specific.

I'm found following the error in PLiPC logs : "DMX_SET_SOURCE failed! - Invalid 
argument"

I included problematic part raising the error when tunning to a channel below, 
you can also find full logs attached.



---------------------------
OURSTATE: tuning

allocate Channel: res 0

[eDVBCIInterfaces] addPMTHandler 1:0:1:1:1:FFFF:1A42EBC:0:0:0:

allocate demux

DMX_SET_SOURCE failed! - Invalid argument

-----------------------------

Original comment by buyukb...@gmail.com on 12 Feb 2012 at 12:52

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Any comments?

Original comment by buyukb...@gmail.com on 21 Feb 2012 at 1:13

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Hey guys, first of all: what an awesome project. I'd just love to have 
tvheadend use my dreambox as a dvb tuner!

It seems like my setup is almost working, but I get the "no scan results" 
issue, apparently.

I have a: dm800se running OpenPLi that runs vtunerd.mipsel (20120104-r2) +
xbmc running on an arch linux machine (x64) running vtunerc.ko + vtunerc.x86_64 
which i compiled myself using the kernel 3.3 quick-patch found in issue 18.

Communication seems ok, i have tried "vtunerc -f s" and "vtunerc -f s2" (others 
(-f S or -f S2) do not connect successfully, as my tuner type = 9)

So the problem at this time is: i cannot scan for any channels (tried using 
w_scan, passing -D1u, -D2u, ... for diseqc switching, don't know it this is 
supported?). 

I tried manually adding channels to channels.conf and tuning with szap, but 
this does not seem to LOCK... (will try this again)

btw: is there a way to convert Enigma's channels to a channels.conf ?

Also, if there's know issues causing this behavior, on which I could help? I am 
an embedded C programmer, so I might be able to help a little.

Original comment by maxime.v...@gmail.com on 17 Apr 2012 at 6:52

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Ok, I just read the line "Original Dreambox API is supported, but only up to 
August's 2011 DVB drivers!". I suppose this explains my troubles. I someone 
could point me out where I should look for improvements, to get it work on the 
new Dreambox API? Is there any documentation about the dreambox-API?
Should I look in the vtunerd-part, in vtuner-dmm-3 ?
I know very little about linux-dvb, so I'll have to do some research first.

best regards

Original comment by maxime.v...@gmail.com on 17 Apr 2012 at 10:32

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Maxime, If you can test against some older kernel (non 3.3), please do it. As 
you could notice, I did 3.3 kernel patch blindly, so it is more then possible 
it consists of some bugs and this is a reason why it is not working for you.

Original comment by jpetrous on 17 Apr 2012 at 7:38

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

jpetrous, everyone,

I have tried using a 3.0.x kernel, and scanning works now. (so using a recent 
OpenPLi image on my dm800se. I still have to check which driver version this 
image is using, exactly)
I will look into the new 3.3.x kernel dvb interface, and hopefully come up with 
a fix.

Best regards

Original comment by maxime.v...@gmail.com on 19 Apr 2012 at 12:01

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015


I have also a lot of problems with getting vtunerd on my STB.

I'm using the stv090x driver. With the szap utility I got a lock but no tsdata. 
Now I'm trying the openpliPC project.

On some channels in e2 I see a PID list and on a lot of channels I see nothing. 
The ioctl(hw->demux_fd[j], DMX_SET_PES_FILTER, &flt); is failing also with 
"invalid argument". If I set the PID hardcoded to 0 the ioctl succeeds.

The attached log shows what's going wrong. The DEMUX FAILED logging is custom 
added.

Original comment by leonleij...@gmail.com on 30 Apr 2012 at 12:09

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

@GoogleCodeExporter GoogleCodeExporter commented Oct 31, 2015

Issue 34 has been merged into this issue.

Original comment by jpetrous on 18 Feb 2014 at 7:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant