by gfi » Mon Jul 08, 2013 7:06 pm
steven
I wrote to You about SAT>IP by email.
Simulation of rtsp protocol, used by Sat>IP devices, isn't a problem.
Device can working with other tools simultanously.
That's mean, if frontend is busy by other applcation, device send message about busy, etc.
But:
Sat>IP working with principe one user -> one tuner. I don't know it's better or not. For little devices like MOI maybe better, due to lover CPU usage is needed.
But, it's always possible to start 2x TVheadend (one user -> one tuner).
I don't know, but I still think, is better to have a clear m3u playlist (and using xmltv for other apps) in PC or XBMC frondend.
For support of CI slot.
I'm working about month on upgrade of TVheadend to be PROPERLY handling of CI slot. There's a big problems and I think, never be working as is needed as sure. Lost time.
Better way for TBS - contact author of dvblink server. He can adapt it to MOI as sure.... Users can select TVheadend or DVBlink at start on webif of moi. Or just adapt first tuner for DVBlink, second for TVHeadend.
Back to Sat>IP.
---------------------
What I know, devices using linux based on STapi, insted (much better solution for us) DVBApi.
Max. 4 users. Of course, theres also posibility of use multicast, but...
It's only my opinion, I always prefer clear http or udp link instead communication protocol and only some SW and HW players.
Url I can adapt to all devices, SW players and EPG I have for free (xmltv). If isn't public xmltv for some countries, parser of EIT is available... Again, It's only my opinion.
But, If is that priority for You (I mean Sat>IP), I can buy one in Germany and help You. Let me know.
Without real device and experience, how is this stable, what clients working properly, etc, we can do nothing.
If You want playing with SAT>IP protocol, You can adapt it with tools in attachment. Tune, sending pids array by tcp, etc.
I agree with linuxstb, I don't think, Sat>IP is any miracle. It's really only low level. Decoding (what I know, but I'm not sure), muxing, epg parsing begin on client side.
Practically Sat>IP only tune and resending pids array stream as begin.
----------------------------
What is more important - tune chipset to finally state.
In case of MOI also expanding of USB efficienty to max.
If will be possible to setting HW pid filtering in the future, partly problems can be solved (depending of tuner options).
I think, nobody need all channels from 1 TP, now is opened all TP, not important, If You need only 1 channel (of course I think load to USB and also CPU, not in dvr).
Max. efficiency of USB in MOI (8 devices connected!) for tuners is max. 15-20% (~90M).
So, If user opening TP with 8PSK modulation and 30M Symbol Rate, will be have problem with second adapter as sure. And there's no important, how is opened dvr and demux. Need to say, this is problem with all devices like that.
Next and finally: define timeout to be tuner going to sleep after close handle. Option in TVheadend for close handle in idle state don't working with MOI.
Also to DVR in MOI, I wrote about that 5x. For find a max. possibilities is need precompile driver with value of DVR_BUFFER *16 (!) and put upgraded kernel source into Your site. I've tool, what give me a real value of max. usage for both tuners (there's also CPU and USB high load...). Default value in dmxdev.h is for One tuner, also older kernel is used...
Or, maybe better solution, make kernel and rootfs in udev, instead mdev and compile dvbcore and other modules (also MOI tuner) with last media build of v4l. Higher value of DVR buffer is needed too.
I tried change kernel to be dynamically assigned device for create udev rootfs, but I'm ending with MISHMASH in compilation.
I've updated buffer to default value *4, software PID filtering and look at pictures for real CPU load. But there's still problem, tuner driver is preconpiled with default value, so I can adapt it with calculation, only. In this case, MTV Live HD on 13E with CI (11M bitrate), http stream (picture).
On other channels I have much higher CPU load, or I need change buffer values. So, we need to find a max. possibilities for create any basic FAQ for streaming and used tools in MOI. I'm still waiting for final kernel with upgraded values, now I can't do nothing.
Again, If You strictly need SAT>IP, let me know by PM and I buy one device.
Will see, how working. I think, that haven't future. I realy don't know, how it be working (decoding) on Android/Apple devices. But, some devices using STi7126, what have HW support of CSA decryption, oscam exist also for STAPI, other tools too... Missing detailed informations on internet.
Without real device and experience, how is this stable, which clients working properly, etc, we can do nothing.
- Attachments
-