Hi
I'm using the latest femon + vdr 170 + h.264 patch. If I will watch h264 dvb-s2 channels than some information in femon is missing -
Apid - 0 Spid - 0 Aspect ratio - reserved Frame rate - 0.00 Hz Video format - unknown Resolution - 0x0
Information about audio stream - #0 bitrate - free (0 kbit/s) mpeg layer - 0 sampling frequency - reserved
Is it possible to fill these fields ?
Goga
Goga777 wrote:
Hi
I'm using the latest femon + vdr 170 + h.264 patch. If I will watch h264 dvb-s2 channels than some information in femon is missing -
Apid - 0 Spid - 0 Aspect ratio - reserved Frame rate - 0.00 Hz Video format - unknown Resolution - 0x0
Information about audio stream - #0 bitrate - free (0 kbit/s) mpeg layer - 0 sampling frequency - reserved
With DVB-T those are ok, but missing are Transmission --- Modulation --- Coderate --- (H) --- (L) Guard --- and Bandwith is reported as 7Mhz, should be 8Mhz
On Sun, 13 Jul 2008, Lauri Tischler wrote:
With DVB-T those are ok, but missing are Transmission --- Modulation --- Coderate --- (H) --- (L) Guard --- and Bandwith is reported as 7Mhz, should be 8Mhz
The current femon plugin doesn't support multiproto, but for my knowledge multiproto DVB API should be compatible with old DVB API and therefore these fields should still be working. Does your channels.conf contain correct values for these entries?
BR, -- rofa
Rolf Ahrenberg wrote:
On Sun, 13 Jul 2008, Lauri Tischler wrote:
With DVB-T those are ok, but missing are Transmission --- Modulation --- Coderate --- (H) --- (L) Guard --- and Bandwith is reported as 7Mhz, should be 8Mhz
The current femon plugin doesn't support multiproto, but for my knowledge multiproto DVB API should be compatible with old DVB API and therefore these fields should still be working. Does your channels.conf contain correct values for these entries?
There are differences between 1.4.x and 1.7.0
This is from 1.7.0 YLE TV1;YLE:562000000:A0B8C23D23G8I0M64P0T8Y0:T:3:512:650=eng,651=dut:2321:0:17:8438:4097:0 YLE TV2;YLE:562000000:A0B8C23D23G8I0M64P0T8Y0:T:3:513:660=fin:2321:0:33:8438:4097:0 MTV3;MTV Oy:658000000:A0B8C23D23G8I0M64P0T8Y0:T:3:305:561=fin:817:0:49:8438:8193:0
This is from 1.4.3 YLE TV1;YLE:562000000:I0C23D23M64B8T8G8Y0:T:3:512:650=eng,651=dut:2321:0:17:8438:4097:0 YLE TV2;YLE:562000000:I0C23D23M64B8T8G8Y0:T:3:513:660=fin:2321:0:33:8438:4097:0 MTV3;MTV Oy:658000000:I0C23D23M64B8T8G8Y0:T:3:305:561=fin:817:0:49:8438:8193:0
On Sun, 13 Jul 2008, Lauri Tischler wrote:
There are differences between 1.4.x and 1.7.0
..but the common parameters are the same, so I cannot say where the problem might be until I (or someone else) have debugged it.
BR, -- rofa
On Wed, 9 Jul 2008, Goga777 wrote:
Apid - 0 Spid - 0
The pids should work - I cannot see why multiproto/h264/S2 would affect them.
Aspect ratio - reserved Frame rate - 0.00 Hz Video format - unknown Resolution - 0x0 Information about audio stream - #0 bitrate - free (0 kbit/s) mpeg layer - 0 sampling frequency - reserved
Is it possible to fill these fields ?
Sure. The femon's current implementation can only interpret these values from MPEG2 streams, so a support for H264 should be added. However, I'd like to broaden the cDevice interface to include most of this stuff, so the decoder could provide the information for any plugin/skin. Does anyone know, if this kind of statistics can be obtained from i.e. xinelib?
At the moment, I don't have any plans to start using the multiproto, so just start sending your patches and I'll merge them into next development version..
BR, -- rofa
Apid - 0 Spid - 0
The pids should work - I cannot see why multiproto/h264/S2 would affect them.
where from does femon read apid/vpid ? from channels.conf or from dvb stream directly (service table)? in both cases I don't understand how the multiproto can influence on this issue
Goga
btw - is it possible to add in femon the information about PMT, ONID pids ?
Goga
On Sun, 13 Jul 2008, Goga777 wrote:
where from does femon read apid/vpid ? from channels.conf or from dvb stream directly (service table)? in both cases I don't understand how the multiproto can influence on this issue
The pids are read directly from VDR's cChannels class: cChannel::Apid(), ...
btw - is it possible to add in femon the information about PMT, ONID pids ?
Yes, but interface functions should be added into core VDR as I don't want to yet another duplicate parsing...
As always, patches are welcome! :)
BR, -- rofa
-
Goga777 -
Lauri Tischler -
Rolf Ahrenberg