Tvheadend

Tvheadend can't receive data from dreamboxes.

Hi Andreas,

this was 10 Month ago, is this still true? Is there absolutely no way to use TVheadend with a dreambox (eighter install it on, or use it via the http streaming that the dreamboxes have, or some plugin for another protocol)...? I have a dozen of old DM800 laying around gathering dust...

Greetings,

Max

there are people that are compiling the tvheadend source code on ARM powered devices. The dreambox is using a PPC processor but you can always try to "just compile" the tvheadend source code using a code chain for the dreambox and see what is happening.

OR

check if there are tools that would create a RTP stream from the dreambox to tvheadend.

OR

run the dreambox HTTP stream through VLC to convert it to a RTP stream and load that into tvheadend

Be creative, think out of the box and hack away :-)

Hi,
actually I got dreambox (DM500HDse (gp5,1 image) also Xtrend5000 (Egami Image 2.1) same processor Broadcom 400 Mhz and same Enigma2, both STB tested OK) as source with pretty good result. Possible to stream whole transponder with oscam decrypting )
I used virtual drivers from project vtuner http://code.google.com/p/vtuner/
Kernel driver for PC Ubuntu 10.04 LTS 64bit compiled myself.
all features working, only one last thing that I can't setup multicast output from tvheadend to local LAN.
on the source code I see that multicast output presents ( meaning iptv_output.c ).
Question is how to configure it properly and where to enter settings?
Please someone help for that.
Of course http streaming working without any problems, but I really need multicast

Regards.

Igosr,

Is it possible for you to write a how to on compiling tvheadend for the dreambox?
And also some information about how to setup tunerc?

If you had to make changes to the tvheadend source to make it work then could we get a patch?

About the multicast streams ... I do not know exactly how to set it up, but it is not as good as it should be. Any help to improve this is always welcome.

Hein

Hi,
I doesn't compiled tvheadend for dreambox but using Dreambox and Xtrend like remote tuners for tvheadend instead.Vtuner drivers allow use even 3 STB's like remote DVB cards. Everything working like a sharm.
What I did.

Here is short explanation:

Dreambox part
_____

1. On dreambox I copied vtunerd.mipsel to /usr/bin
2. for launching vtunerd daemon I altered mgcamd script mgcamd_1.35a_cam.sh from /usr/script folder( coz decryption doing tvheadend with oscam), but it's not a big deal,you can use any script, so three simple lines

##########################################
mgcamd_1.35a_cam.sh #########################################
#!/bin/sh
init 4 # kill enigma
sleep 5
/usr/bin/vtunerd.mipsel & # start in background

3. start "mgcamd" from blue panel

PC part
___

4. On PC (mine one is x86_64 so if yours is 32bit you have to compile kernel driver yourself, I attached working driver for Ubuntu 10.04LTS Linux 2.6.32-37-generic #81-Ubuntu SMP Fri Dec 2 20:32:42 UTC 2011 x86_64 GNU/Linux)
with tvheadend compiled from git latest build I did:
(It's too important to launch tvheadend before vtunerc client like vtunerc.ko-> vtunerc -> tvheadend.)
4.1 mkdir /lib/modules/2.6.32-37-generic/misc, copy vtunerc.ko driver to this directory.
4.2 depmod -a, reboot.
after that you will able to insert driver to kernel : (from root :)) modprobe vtunerc
4.3 copy file vtunerc (vtunerc.x86_64 renamed to vtunerc ) to /bin directory
4.4 vtunerc -f s & (note: you don't need vtuner -f s2 command coz tvheadend found both DVB-s and DVB-s2 channels too, thats really good, coz in
vtuner manual appeared that for HD channels need -f s2 option)

4.5 launch tvheadend. Tvheadend think like dreambox is local DVB card for now

That's all :)
Sorry, duplicated attachment virtual drivers, how to remove one?
PS. Again, how to launch multicast output from tvheadend? In my vision this feature really need for serving
more clients, coz when doing http streaming of HD channels LAN is too heavy loaded.
Maybe someone can implement that functions from mumudvb and another getstream_a84 projects?
I'm not a skilled C developer

https://cesbo.com/projects/getstream_a84

Nice solution to the original problem. I realy like it.

About multicast streams ... I suspect that the logic from dvblast might be beter as a basis to add/improve the multicast streaming. If you like to code it... please do so :-)

Will try to do that, but I'm not so skilled . I think you can do it much faster.
( Sometimes I coded private cardless OSCAM with DRE emu (coz udating cards for this system is really pain :)) for a 8 months :(( )
Regards.

Is there any update on the private cardless OSCAM,,

Hi! I tried Igosr Petroff's solution above for the Dreambox, but on the Dreambox I always get

vtunerd: [899 ../../vtunerd.c:113] info: No idle device found

when I run the script on my Dreambox 800. Do you have any idea why? The enigma2 is killed by the script, but it looks something else is using the device.

Ivan

I fixed the issue by downloading a new vtunerd.mipsel, must have downloaded an older one before.

Now it looks like both ends connect to each other, vtunerc says

vtunerc: Revision:3a9233717687/tip DVB:5.3 allow:5.x NetProto:2 MsgSize:96, Debug:3
vtunerc: [2353 ../../vtunerc.c:452] info: added frontend mode DVB-S as mode 0, searching for tuner types 1
vtunerc: [2353 ../../vtunerc.c:533] info: Created pidfile /var/run/vtunerc0.pid
vtunerc: [2353 ../../vtunerc.c:586] info: no server connected. discover thread is 0 (DWS_IDLE:0, DWS_RUNNING:1)
vtunerc: [2353 ../../vtunerc.c:588] info: changing frontend mode to DVB-S
vtunerc: [2353 ../../vtunerc.c:617] info: Start discover worker for device type 1 groups ffff
vtunerc: [2353 ../../vtunerc.c:214] info: starting discover thread
vtunerc: [2353 ../../vtunerc.c:258] info: Sending discover message for device types 1
vtunerc: [2353 ../../vtunerc.c:272] info: Received discover message from 192.168.207.241 proto2 control 1777 data 2285
vtunerc: [2353 ../../vtunerc.c:637] info: connect control socket to 192.168.207.241:1777
vtunerc: [2353 ../../vtunerc.c:654] info: connected data socket to 192.168.207.241:2285

but I can not find the remote Dreambox in TVHeadend, shouldn't I have seen something under TV Adapters?

Ivan

Hi.
Please check here more detail info
_h**p://wiki.nessiedvb.org/wiki/doku.php?id=vtuner_mode

_**p://www.nessiedvb.org/wiki/doku.php?id=install_dreamtuner

and maybe nessydvb forum:
_h**p://forum.nessiedvb.org/forum/

One of important part is to give less restricted access to /dev/dvb
I told about that before but again:

If you want the more reasonable access rights for /dev/dvb devices, create the appropriate rule for udev. Find, where these rules are at your system, the standard position is /etc/udev/rules.d. Create here the file 15-dvb.rules, containing the line:

SUBSYSTEM=="dvb", ACTION=="add", MODE="0666"

The filename is not critical, only it has to have the extension 'rules' and it should not interfere with others rules, already present in your linux box.
After that tvheadend works much better ( at least for me).

Second note: tvheadend should be compiled with avahi enabled.

Regards.