search

Leatherface75 / vtuner

Automatically exported from code.google.com/p/vtuner
0 stars 0 forks source link

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

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
-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 commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I would like to test....

vu+duo

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

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
I would like to test....

vu+ solo

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

Attachments:

GoogleCodeExporter commented 9 years ago 
I would like to test....

vu+ solo

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

Attachments:

GoogleCodeExporter commented 9 years ago 
> -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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
> 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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I created some thread on VU+ related forums to call help on this issue, but 
still couldn't find a guy with USB tuner that could help us :(

I just want to ask a question: I'm using VU+ Duo, a E2 STB with two tuners. I 
always start vtunerd without any additional parameter (except the -d that you 
asked above) . Do I need to use some advanced command line parameters to be 
sure that vtunerd connects to one of the tuners? I mean, may be I'm doing 
something wrong here? 

BTW, I can make some "blind" code modification trials in this weekend to find a 
way to make vtunerd work in VU+ . I said "blind", because I understand from 
your above comments that this requires a usb dvb card to find the root cause of 
the problem. Do you have any suggestions as a start point?

regards..

Original comment by buyukb...@gmail.com on 27 Jan 2012 at 6:48

GoogleCodeExporter commented 9 years ago 
Hello, I'am spanish and my inglish is very bad, sorry.

I have a Vu-duo whit openpli, and have if your need 2 usb-dtt tunners af9015 
and a sms-siano, is for dtt, not for dvb.

For my if your a serius person, for my don't have problem for test all your 
needed and if your need enter in my box, I open the ports in my router directed 
of my VU-duo for enter in my box and for test your directli in my box.

After this, I loock that your have controled the vtuner and I need your help 
for another box, I take help in open pli and another forums and don´t help my, 
like your with this virtual tuner, this box is a gigablue-Hd-800-solo, is not a 
clone is legal box, a only one team work whit this box is red-team and in this 
momment the aff-team, bud neither know or I don't know for what not work the 2 
teams for run the usb-dtt tuners, and ask a nothing question, 

This box is a mipsel like and same VU-solo the bcm-7325, have a one interior 
tuner dvb-s2 and one only usb exterior conexion, I start a usb-dtt tuner bad 
not work good, is inestable.

Your have control in question, I help your and your hel my?, I apreciate more 
if your help my for start de usb-dtt in this box, in spanish and in italy have 
many channels in dtt and is more needed this feature and nothing work in 
usb-dtt for this box, this box is economic and have many box in deutchland, 
spanish, Italy, etc., bud the countries need more the usb-dtt is spanish and 
Italy, I don`t know if in others countries not need the box with dtt.

I moderate the seccions Vu and gigablue and kathrein (VU is kathrein), in a 
important spanish forum tododream.your are welcom, my nick is javier3034 and my 
name is javier.

Your say my whats your need, my Vu-duo is at your disposition and my gigablue 
if your help my plis, have many users that have this problem whit gigablue and 
need work good the usb-dtt, he aren more agre if whit your help start and work 
good the usb-dtt in this box, like I say is same a VU-solo, but the images of 
vu-solo don't start in this box, I think is a problem of diferent blocks in 
flash or the base drivers, I don't know. the tuner dvbs2 is the same. 

Ok, your say my wats your need,

regars

Original comment by javierfa...@gmail.com on 28 Jan 2012 at 11:36

GoogleCodeExporter commented 9 years ago 
Sorry, 2 infos, in the last 2 weeks updates of openpli, don`t work good the 
usb-dtt is more inestable, freeze and stop the image after 1 houre, need 
restart the VU, I say this bug in openpli but don't have response, after this 
update the usb-dtt tuners worck very good.

In black hole, vti, vix, etc., the usb-dtt works good, nothing problems.

In the last black hole image 1.7.1 work good the virtual tuner, and your view 
the channels of first box in a econd device, like another e2 box, PC, ps3, 
smartphones, etc, whit dlna/upnp and djimount, but not work in a TVs whit dlna.

Whit a openpli in my box VU-duo I rebuild and work good in my Tv whit dlna, and 
view all of my contents, pictures, films record in the VU (ts)and mp3 in to the 
hdd of my VU in TVs with dlna protocol, If your finaly start the virtual tuner 
in a hdd of VU, I think he is possible view this channels for example in a 
devives, like another e2, box, pc-linux and windows, ps3, xbox? (I don`t have), 
TVs whit dlna, smartphones, etc., is a very good goal.

Becouse, openpli in this momment the usb-dtt is not stable and not work good, 
Is good for your test I install in my VU the black hole 1.7.1 image? is 
possible your loock in my box all your need or debugs, etc., say my this.

If your need I send your the files for that streaming.

Regards

Original comment by javierfa...@gmail.com on 28 Jan 2012 at 12:00

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Sorry I say, after last 2 weeks the openpli updates work good the usb-dtt and 
is not correct, after this updates don`t work good the usb-dtt and before this 
updates the usb-dtt work very good.

Uuuffff, 

Regards

Original comment by javierfa...@gmail.com on 28 Jan 2012 at 12:13

GoogleCodeExporter commented 9 years ago 
Hi,

I am currently doing some test on my Xtrend ET-9x00.
Can you please test the attached vtunerd.et9x00 (server) on your VU+ on a FTA 
channel and use for openpliPC has client.
With my Xtrend it is working on FTA channels but not on scrambled channels.

Thanks.

Original comment by mebep...@gmail.com on 31 Jan 2012 at 5:43

Attachments:

GoogleCodeExporter commented 9 years ago 
I tested the xtrend test file, but the result is the same for my VU+ Duo. No 
audio and video, and a BER value like 30+.

Original comment by buyukb...@gmail.com on 31 Jan 2012 at 6:49

GoogleCodeExporter commented 9 years ago 
Can you please show up the message when you start this version to see if there 
are errors reported?

Original comment by mebep...@gmail.com on 31 Jan 2012 at 8:13

GoogleCodeExporter commented 9 years ago 
Here is the log file:

root@vuduo:/media/usb# ./vtunerd.et9x00
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:3.2 allow:5.x NetProto:2 MsgSize:96, 
Debug:0x3
vtunerd: [8025 ../../vtuner-dvb-3.c:57]  info: FE_GET_INFO dvb-type:0 
vtuner-type:1
vtunerd: [8025 ../../vtunerd.c:158]  info: adapter:0, frontend:0, demux,0, 
dvr:0 is type:1
vtunerd: [8025 ../../vtunerd-service.c:276]  info: waiting for autodiscover 
packet (groups 0xFFFF) ...
vtunerd: [8025 ../../vtunerd.c:177]  info: received discover request proto2, 
vtuner_type:9 group:0xFFFF
vtunerd: [8025 ../../vtunerd-service.c:276]  info: waiting for autodiscover 
packet (groups 0xFFFF) ...
vtunerd: [8025 ../../vtuner-dvb-3.c:57]  info: FE_GET_INFO dvb-type:0 
vtuner-type:1
vtunerd: [8025 ../../vtunerd-service.c:85]  info: anon stream socket prepared 37
vtunerd: [8025 ../../vtunerd-service.c:326]  info: control socket bound to 54622
vtunerd: [8025 ../../vtunerd-service.c:85]  info: anon stream socket prepared 38
vtunerd: [8025 ../../vtunerd-service.c:339]  info: session prepared 
control:54622 data:51189
vtunerd: [8025 ../../vtunerd-service.c:369]  info: session running
vtunerd: [8025 ../../vtuner-dvb-3.c:151]  info: FE_SET_FRONTEND parameters: 
freq:1364000 inversion:2 SR:5925000 FEC:3
vtunerd: [8025 ../../vtuner-dvb-3.c:151]  info: FE_SET_FRONTEND parameters: 
freq:1364370 inversion:2 SR:5925000 FEC:3
vtunerd: [8025 ../../vtuner-dvb-3.c:151]  info: FE_SET_FRONTEND parameters: 
freq:1363630 inversion:2 SR:5925000 FEC:3
vtunerd: [8025 ../../vtuner-dvb-3.c:151]  info: FE_SET_FRONTEND parameters: 
freq:1364740 inversion:2 SR:5925000 FEC:3
vtunerd: [8025 ../../vtuner-dvb-3.c:151]  info: FE_SET_FRONTEND parameters: 
freq:1363260 inversion:2 SR:5925000 FEC:3
vtunerd: [8025 ../../vtunerd-service.c:266]  info: TS data copy thread 
terminated.
vtunerd: [8025 ../../vtunerd-service.c:509]  info: control thread terminated.

Original comment by buyukb...@gmail.com on 31 Jan 2012 at 10:01

GoogleCodeExporter commented 9 years ago 
@Honza,

Waiting your kind response for the comments #29 and #30.

Original comment by buyukb...@gmail.com on 2 Feb 2012 at 10:53

GoogleCodeExporter commented 9 years ago 
Hi,

Please test this file. Now it is running better on my ET9x00 just hope that it 
will be the same for your VU+.

Mebepi

Original comment by mebep...@gmail.com on 4 Feb 2012 at 11:04

Attachments:

GoogleCodeExporter commented 9 years ago 
I just tested the last file, but nothing is different :(

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

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
Hi,

Sorry attachement was missing here it is.

Mebepi

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

Attachments:

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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 commented 9 years ago 
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