(deprecated) cross platform tuner sharing, friendly user test

liviurosioara · 8. Oktober 2009

Zitat

Original von rmie

yes I can, but can last a few days

It would be great indeed! Thanks a lot!

jonnydreambox · 8. Oktober 2009

Moin,

verfolge das ganze hier schon lange , sehr interressant!

ich hätte an der Konstellation

DM800 DVB-S Client D-Box2 DVB-C bzw andere DVB-C taugliche Box
interesse

geht das ?

Lese immer nur von DVB-S zu DVB-S

Möchte auf meiner DM800 DVB-S noch Programme vom Kabelnetz DVB-C sehen können(HD nicht nötig)!

Gruß
JonnyDreambox

Tweek · 8. Oktober 2009

Eine Frage noch, wie kann ich den vTuner Client auf der DM800 sauber vor dem Start von enigma2 starten?

Mfg

muffi_1 · 8. Oktober 2009

Zitat

Original von Tweek
Eine Frage noch, wie kann ich den vTuner Client auf der DM800 sauber vor dem Start von enigma2 starten?

Mfg

Hallo,

schau mal auf Seite 9 dort habe ich meine enigma2.sh gepostet.

mfg. muffi

rmie · 8. Oktober 2009

Zitat

Originally posted by jonnydreambox
DM800 DVB-S Client D-Box2 DVB-C bzw andere DVB-C taugliche Box
interesse
geht das ?

Möchte auf meiner DM800 DVB-S noch Programme vom Kabelnetz DVB-C sehen können(HD nicht nötig)!

ja machen einige hier schon, wird aber eine ziemliche fummelei, da Du mit DVB-C keinen Suchlauf machen kannst

Tweek · 8. Oktober 2009

Mir ist gerade eben aufgefallen das sich der vTuner daemon für i686 in unregelmässigen abständen selbst beendet. Gibts dafür einen Grund?

Gibts die Möglichkeit den vTuner auch für x64 Systeme zu kompilieren?

Mfg

liviurosioara · 8. Oktober 2009

I downloaded the version from 14.09 and I compiled vtunerd for Popcornhour A110 (nmt with linux). Everything was okay in loading the driver and I launched vtunerd 1 0 0 0 0 & on nmt.

the output is like this:

/opt/sybhttpd/localhost.drives/HARD_DISK/Apps # ./vtunerd.mips 1 0 0 0 0 &
[6546 vtunerd.c:38] debug: try to init 1 tuner(s)
[6546 vtunerd.c:44] debug: init hardware adapter 0, frontend 0, demux 0, dvr 0
/opt/sybhttpd/localhost.drives/HARD_DISK/Apps # [6546 vtuner-dvb-3.c:44] info: F
E_GET_INFO dvb-type:2 vtuner-type:4
[6549 vtunerd-service.c:88] info: anon stream socket prepared 40
[6549 vtunerd-service.c:240] info: control socket bound to 35890
[6549 vtunerd-service.c:88] info: anon stream socket prepared 41
[6549 vtunerd-service.c:255] info: waiting for connect control:35890 data:41940
listen:40
[6550 vtunerd-service.c:21] info: autodiscver thread started.
[6550 vtunerd-service.c:33] info: waiting for autodiscover packet ...
[6551 vtunerd-service.c:154] debug: tsdata_worker thread started.
[6550 vtunerd-service.c:37] info: received discover request
[6550 vtunerd-service.c:40] debug: Session 0 device type 4 is idle
[6550 vtunerd-service.c:52] info: Answered discover request with session 0
[6550 vtunerd-service.c:55] info: waiting for autodiscover packet ...
[6549 vtunerd-service.c:103] debug: setsockopt TCP_NODELAY 1 successful
[6549 vtunerd-service.c:109] debug: setsockopt SO_KEEPALIVE 1 successful
[6549 vtunerd-service.c:116] debug: setsockopt TCP_KEEPIDLE 15 successful
[6549 vtunerd-service.c:123] debug: setsockopt TCP_KEEPCNT 2 successful
[6549 vtunerd-service.c:130] debug: setsockopt TCP_KEEPINTVL 2 successful
[6551 vtunerd-service.c:103] debug: setsockopt TCP_NODELAY 1 successful
[6551 vtunerd-service.c:109] debug: setsockopt SO_KEEPALIVE 1 successful
[6551 vtunerd-service.c:116] debug: setsockopt TCP_KEEPIDLE 15 successful
[6551 vtunerd-service.c:123] debug: setsockopt TCP_KEEPCNT 2 successful
[6551 vtunerd-service.c:130] debug: setsockopt TCP_KEEPINTVL 2 successful
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 0
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 45879
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 33591
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 17207
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:302] debug: MSG_GET_FRONTEND
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor:
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43947
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 823
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:302] debug: MSG_GET_FRONTEND
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 211 561 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 211 561 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 211 561 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 561 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 561 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 561 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent:
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after:
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43947
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 21304

When I try to tune a dvb-t channel, the usb tuner led lights up (like tuning) but I have no image on dm800 and time to time I get the 'no data on transponder. timeout reading PAT' error message.

In lamedb I manually added correctly the frequency and parameters for the transponder and also the channel.

eDVB services /3/
transponders
eeee0000:012f:0003
t 738000000:0:1:1:2:1:1:0:2:0
/

0001:eeee0000:012f:0003:1:0
TVR1
p:TVR

Do you have any idea why I have no image on dm800? (on nmt, the tuner works perfect, see http://www.networkedmediatank.com/showthread.php?tid=26368 )

muffi_1 · 8. Oktober 2009

Zitat

Original von Tweek
Mir ist gerade eben aufgefallen das sich der vTuner daemon für i686 in unregelmässigen abständen selbst beendet. Gibts dafür einen Grund?

Gibts die Möglichkeit den vTuner auch für x64 Systeme zu kompilieren?

Mfg

Alles anzeigen

Ja, geht habe es gerade getestet.

mfg. muffi

SrbastianM · 8. Oktober 2009

sorry.. offtopic, but what do you want to do with your popcorn hour?
It does not have a tuner, does it?

Edit: just saw your link... nice

ciao

Basti

liviurosioara · 9. Oktober 2009

Zitat

Originally posted by SrbastianM
sorry.. offtopic, but what do you want to do with your popcorn hour?
It does not have a tuner, does it?

Edit: just saw your link... nice

ciao

Basti

Alles anzeigen

The popcornhour doesn't have a tuner but you can use one if you can compile drivers for 2.6.15 kernel. I would like to use vtunerd on popcorn, but as you see, I encounter some difficulties.

jonnydreambox · 9. Oktober 2009

rmie and all,

Zitat

Zitat: Originally posted by jonnydreambox DM800 DVB-S Client D-Box2 DVB-C bzw andere DVB-C taugliche Box interesse geht das ? Möchte auf meiner DM800 DVB-S noch Programme vom Kabelnetz DVB-C sehen können(HD nicht nötig)! ja machen einige hier schon, wird aber eine ziemliche fummelei, da Du mit DVB-C keinen Suchlauf machen kannst

Hab noch von der DM800 DVB-C eine Kanalliste damit sollte das dann ja gehen oder ?

Welche Box ist den in der Konstellation zu empf.

Auf der DM800 DVB-S noch Programme vom Kabelnetz DVB-C(D-box2 ,DM???....)

Gruß
JonnyDreambox

rmie · 9. Oktober 2009

Zitat

Originally posted by liviurosioara
I downloaded the version from 14.09 and I compiled vtunerd for Popcornhour A110 (nmt with linux). Everything was okay in loading the driver and I launched vtunerd 1 0 0 0 0 & on nmt.

...

When I try to tune a dvb-t channel, the usb tuner led lights up (like tuning) but I have no image on dm800 and time to time I get the 'no data on transponder. timeout reading PAT' error message.

This version is buggy somehow. Maybe you should try 2009-08-26 first (check first post).

The log you sent seems to be ok:
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
=> is a clear indication that tuning was successful
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20
=> enigma sets a pid filter (happens if tuning works)

Roland

rmie · 9. Oktober 2009

Zitat

Originally posted by jonnydreambox
rmie and all,

Hab noch von der DM800 DVB-C eine Kanalliste damit sollte das dann ja gehen oder ?

Ja wenn die List aktuell ist.

Zitat

Originally posted by jonnydreambox
Welche Box ist den in der Konstellation zu empf. Auf der DM800 DVB-S noch Programme vom Kabelnetz DVB-C(D-box2 ,DM???....)
Gruß
JonnyDreambox

hmm, da will ich mich mal besser raushalten Wenn Du eine dbox2 hast, würde ich mal damit anfangen, und dann entscheiden ob ich für diese Feature Geld ausgeben will oder nicht.

Roland

rmie · 9. Oktober 2009

Zitat

Originally posted by Tweek
Mir ist gerade eben aufgefallen das sich der vTuner daemon für i686 in unregelmässigen abständen selbst beendet. Gibts dafür einen Grund?
Gibts die Möglichkeit den vTuner auch für x64 Systeme zu kompilieren?

Should be no problem to build a 64bit version, all you have to do is to add -m64 to the CFLAGS in compile.sh and run it.

Do you have the last lines of the output before the crash happens?
You can try to execute "ulimit -c unlimited" in the shell, before vtunerd is started. But be careful each time vtunerd crashes, a huge (60 MB) core dump is created. If you get a core, we can try to analyse what happens.

Roland

rmie · 9. Oktober 2009

Zitat
I can only guess at the moment what#s wrong here. My best guess is that "DMX_SET_SOURCE" isn't implemented/available if only one frontend is available. Do you have the option to compile vtunerd yourself? If yes try the following change around line 64 in vtuner-dmm-3.c:
Code
dmx_source_t src = DMX_SOURCE_FRONT0 + frontend;
  if( ioctl(hw->demux_fd, DMX_SET_SOURCE, &src) ) {
    INFO("DMX_SET_SOURCE failed for %s - %m\n",devstr);
#    goto cleanup_demux;
  }
Background: problems with DMX_SET_SOURCE are considered fatal at the moment. MayBe this isn't true. With the change above vtunerd tries to cont. if this problem happens.

Hi, find below the patched version

Roland

rmie · 10. Oktober 2009

Hi @ll,

I've been a bit quiet in the last weeks, nevertheless I made some progress.

The source is now available as public SVN repository, if you want to access latest code please you can checkout from: https://opensvn.csie.org/vTuner/trunk/
Anyone who want's to contribute is invited, I'll grant write access on request by PM.

The build system changed dramatically. Instead of the simple compile.sh, a complex set of Makefiles is used now (I think there is room form improvement here ). I think it will work better if more people are willing to contribute (eg. new platforms as sh4 or popcorn).

Roland

**Seddi** · 10. Oktober 2009

Hmm my first test today and a trivial problem ... client and server doesnt find each other

DM800

Code

[3061 ../../vtuner-dmm-3.c:52] info: FE_GET_INFO dvb-type:0 vtuner-type:1
[3061 ../../vtunerd-service.c:88] info: anon stream socket prepared 5
[3061 ../../vtunerd-service.c:240] info: control socket bound to 32778
[3061 ../../vtunerd-service.c:88] info: anon stream socket prepared 6
[3061 ../../vtunerd-service.c:255] info: waiting for connect control:32778 data:32779 listen:5
[3061 ../../vtunerd-service.c:21] info: autodiscver thread started.
[3061 ../../vtunerd-service.c:33] info: waiting for autodiscover packet ...
[3061 ../../vtunerd-service.c:154] debug: tsdata_worker thread started.

DM8K

Code

[3791 ../../vtunerc.c:249] info: Simulating a DVB-S2 tuner
[3791 ../../vtunerc.c:279] debug: Start discover worker for device type 1
[3791 ../../vtunerc.c:92] info: starting discover thread
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1
[3791 ../../vtunerc.c:124] info: Sending discover message for device types 1

Alles anzeigen

Didnt look inside the code so far .. how do you autodiscover ? Its a normal switched network here, only one subnet and completly wired ... any ideas ?

**Seddi** · 10. Oktober 2009

Hmm ok .. forget it ... my switch did some silly things .. so the udp broadcasts had been blocked

Working like a charm now

liviurosioara · 10. Oktober 2009

Zitat

Originally posted by rmie

Hi, find below the patched version

Roland

Roland, thank you very much!

But now I know what the problem is... hope I'm not saying stupid things here...

When you compile the vtunerd.mipsel for dm800 you do it with 'have_dmm_tuner' (vtuner-dmm-3.c)... but what i want to share is the second tuner, that is usb dvb-t (vtuner-dvb-3.c) attached to dm800. Could you build the vtunerd.mipsel in this way?

liviurosioara · 10. Oktober 2009

rmie, thanks again, you were right, the version from 26.08 works fine, I use vtunerd on popcornhour nmt with attached usb dvb-t cinergy t2 and vtunerc on dm800.

What I would like to try next is to connect directly the usb tuner to dm800, and to run both vtunerd and vtunerc on the same dm800. But this would require a vtunerd version compiled for dvb tuner and dm800, like I said in the previous post. I suppose compile.sh should look like:

CC=/stuff/dm800/build/tmp/cross/bin/mipsel-linux-gcc
ARCH=mipsel
CFLAGS="-DHAVE_DVB_API_VERSION=3 "$DBGFLAGS
LDFLAGS="-lpthread -lrt"
$CC $CFLAGS -c -o vtuner-network.$ARCH.o vtuner-network.c
$CC $CFLAGS -c -o vtuner-dvb-3.$ARCH.o vtuner-dvb-3.c
$CC $CFLAGS $LDFLAGS -o vtunerd.$ARCH vtuner-network.$ARCH.o vtuner-dvb-3.$ARCH.o vtunerd.c
$CC $CFLAGS $LDFLAGS -o vtunerc-test.$ARCH vtuner-network.$ARCH.o vtuner-dvb-3.$ARCH.o vtunerc-test.c

(deprecated) cross platform tuner sharing, friendly user test

Wer ist / war online ?

Benutzer online 30

Wer war online 254