I'm using Dbox Live Streaming as described in:
http://wiki.tuxbox-cvs.sourceforge.net/ ... _Streaming
Is there a tool which can automatically generate Description Files?
/JockyW
Is there a tool to generate Description Files?
-
- Einsteiger
- Beiträge: 358
- Registriert: Montag 21. Juli 2003, 23:52
-
- Erleuchteter
- Beiträge: 553
- Registriert: Freitag 27. Februar 2004, 14:30
Re: Is there a tool to generate Description Files?
no, there isn't...JOCKYW2001 hat geschrieben:I'm using Dbox Live Streaming as described in:
http://wiki.tuxbox-cvs.sourceforge.net/ ... _Streaming
Is there a tool which can automatically generate Description Files?
/JockyW
may be in the future i will create some coding for estreamers e live capability to get the parameter values (also used in description files) on demand.
At the moment i don et know the best way to get these (per web interface or whatever ?) ...
Obtaining the actual pids a channel switch is needed (i guess no other solution yet). in fact of dealing with a few channels using live mode of streamer there would be no problem, but to generate description files in one turn for a large list of channels this could be a little bit strange ...
Also if you ere using only a subset of your dbox channels, a generator to create the description files could produce only a snapshot from the channels actual pids. in case of channels like prem*e that doesn et matter - but some other channels will change pids from time to time ...
as long as using the unmodded movieplayer (without streamer support) it es not worth to implement an automatism to build description files (but in fact, it es a little bit crucial to collect all needed parameter values )
perhaps you ell get some more ideas ?
- GMo -
-
- Einsteiger
- Beiträge: 358
- Registriert: Montag 21. Juli 2003, 23:52
-
- Erleuchteter
- Beiträge: 553
- Registriert: Freitag 27. Februar 2004, 14:30
i would prefer a solution without the need to switch to each channel before obtaining the pids ...
i think, selecting the transponder only followed by a PMT scan would help to extract the pids for a whole bunch of channels
perhaps this could be handled using 'dvbsnoop' within a script running periodically on the box (or similar).
but your suggestion with the "zapit-cycle" would be a good starting point. should be without need to modify zapit sources, because you could use 'pzapit' calls inside of a script.
With such a script installed "behind" an inet service writing to filesystem isn't even needed also. simply a "parser-friendly" stdout-stream would do the trick remote over net (TCP).
- GMo -
i think, selecting the transponder only followed by a PMT scan would help to extract the pids for a whole bunch of channels
perhaps this could be handled using 'dvbsnoop' within a script running periodically on the box (or similar).
but your suggestion with the "zapit-cycle" would be a good starting point. should be without need to modify zapit sources, because you could use 'pzapit' calls inside of a script.
With such a script installed "behind" an inet service writing to filesystem isn't even needed also. simply a "parser-friendly" stdout-stream would do the trick remote over net (TCP).
- GMo -
Sagem 1x Kabel, AVIA600_vb028, cam-alpha 01_02_105D, int. ucode, .sp_ts + .hw_sections