Hi,
I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use
multiple frontend.
So I get:
/dev/dvb/adapter0/demux0
/dev/dvb/adapter0/demux1
/dev/dvb/adapter0/dvr0
/dev/dvb/adapter0/dvr1
/dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/frontend1
/dev/dvb/adapter0/net0
/dev/dvb/adapter0/net1
The bus of the two frontend is shared, isn't possible to get access to both
frontend simultaneously, so I get an -EBUSY error by trying accessing
frontend1 if frontend0 is …
[View More]in use.
VDR doesn't support yet the second frontend, and it try to get exclusive
access on both frontend on start, so the second frontend is inusabile.
Vdr should probe for multiple frontend at start, and access frontend only on
channel change.
Please can someone give me an help to wrote a patch for this issue?
Best Regards,
Eddi
[View Less]
hello
your second patch doesn't work : no sound on eac3 channel
if you want there is a sample of vdr hd-eac3 recording here:
http://dl.free.fr/ew4rJddM8
103mo
else , i don't know what mailing-list is the more indicate for debuging
the vdr or xine-dev mailing-list ?
Hello,
Any current vdr doesn't respect valid dvb device frequency ranges.
Here on a EPG-Scan it's generate many messages on syslog, like :
DVB: adapter 0 frontend 0 frequency 177500000 out of range
(470000000..860000000)
DVB: adapter 0 frontend 0 frequency 177500000 out of range
(470000000..860000000)
DVB: adapter 0 frontend 0 frequency 177500000 out of range
(470000000..860000000)
Any of my three DVB-T devices have different frequency ranges,
and the primary device can't receive VHF-…
[View More]channels.
frontend 0:0 frequency range 470000000..860000000
frontend 1:0 frequency range 51000000..858000000
frontend 2:0 frequency range 177000000..858000000
Therefore i attach a simple patch to check provided frequency ranges of
used dvb-t device driver.
Andreas
[View Less]
Hi,
I created two timers:
5:S19.2E-1-1101-28106:2011-02-26:1330:1500:50:99:Das Traumhotel - Afrika:
9:S19.2E-1-1079-28006:2011-02-26:1300:1500:10:99:Wintersport:
The second timer was recorded for the complete time. The first Timer
was ignored, in spite of the higher priority.
This is related to VPS: A VPS timer seems to be ignored as long as
other recorings block the devices. In this logic, the priority of the
recoring is ignored.
Note: For this test, I started VDR with --device=0 so only …
[View More]one device
is used. I used no patch (plain 1.7.16) and only one plugin
(dvbsddevice).
Regards, Markus
[View Less]
Hi all,
The plugin for integrating analog MPEG2 cards by Hauppauge (et al.) into the vdr has a new home.
http://projects.vdr-developer.org/projects/show/plg-pvrinput
It's adapted to the latest changes of vdr (>= 1.7.13). For older versions the plugin-param-patch is still needed. Take a
look at the README to adjust your channels.conf to the matching syntax of your vdr.
http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/READMEhttp://projects.vdr-developer.org/repositories/…
[View More]entry/plg-pvrinput/HISTORY
I think, it's stable enough to be tested by you. :-)
Use the new home page for documenting bugs you encounter.
A short changelog:
- the generated TS now contains valid PAT, PMT and PCR packets so streaming with streamdev-server now works in TS mode.
The used PIDs are the same as in the TS of cx18 cards, so the vdr will not alter them in mixed environments.
vpid: 301+101=2 ; apid: 300 ; tpid: 305
- the Hauppauge HD PVR is now supported but uses different PIDs as the cx18/ivtv cards.
vpid: 4113+4097=27 ; apid: 0;4352
- for radio channels no more video packets are sent. If you use a PVR350 as output device make sure you have a recent
version of the pvr350-plugin which generates black video on its own.
- if you use a PVRUSB2 make sure you have the latest driver otherwise you can see occasionally no picture after a
channel switch. The corresponding patch of pvrusb2 will be integrated in kernel 2.6.34.
- if you experience stuttering video on switching channels you can tweak some buffers with some parameters in the
setup.conf (stop your vdr before editing, of course)
pvrinput.ReadBufferSizeKB = 64 // size of buffer for reader in KB (default: 64 KB)
pvrinput.TsBufferSizeMB = 3 // ring buffer size in MB (default: 3 MB)
pvrinput.TsBufferPrefillRatio = 0 // wait with delivering packets to vdr till buffer is filled up to x%
If the default values don't make you happy, please report working values for your setup. Please report also your used
input and output devices.
The latest versions of w_pvrscan and wirbelscan supports the new vdr 1.7.13 syntax if you don't want to change your
channels.conf by hand.
http://wirbel.htpc-forum.de/w_pvrscan/index2.htmlhttp://wirbel.htpc-forum.de/wirbelscan/index2.html
Here's the announcement in the vdr-portal:
http://www.vdr-portal.de/board/thread.php?threadid=95389
Have fun!
Lars.
[View Less]
Hi Guys, I have two ATSC adapter.
On one I scan my channels, create my channels.conf file (via a convoluted
script), the channels work on that laptop using 1.6. I make a couple of
edits to allow it to work on 1.7.12, but a particular frequency causes VDR
to crash and get restarted by the watchdog..
The offending frequency is 567000, It's a Qam256 ATSC Cable frequency. I
have an HVR1850 PCI-E adapter. Unfortunetly, it's the mux with all my
local SD channels, although I can watch the HD ones, …
[View More]two channels don't
have HD versions..
I can't see anything in dmesg or the vdr log which causes a problem.
As an aside, a scan using w_scan to create a kaffeine channels.conf file
on that adapter, doesn't find anything on that frequency. Am I getting
interference from something? Any ideas?
[View Less]
Hey all,
Ever had the trouble that your remote's color navigation key weren't the
same as VDR's? Well I wrote this patch the past 4 hours which lets you
configure them.
By doing so, the order of the buttons in the menu changes depending on
whatever you tell it to. So finally that remote can match whatever is
displayed on screen.
This only works for the classic and st-tng skins, as those are supplied
with VDR. The Skin needs to support this feature. If there is no skin
support, the setting …
[View More]simply gets ignored by that skin. Since only the
order of the buttons in the skin are being changed any plugin
configuration will be independent from this change. What I mean is that,
when a plugin has configured blue to take you straight to the photo
gallery, the blue button will still do this, no matter where it is on
the remote. If the plugin however used the blue key to fast forward,
because it is the right most key, and thus made sense logically there,
it will no longer when you move the keys around. Practically, this will
boil down to a handful of plugins depending on location which imo is a
little weird anyway :)
Also, I patched it on a Gentoo box using the latest 1.6 ebuild they have
so line numbers may be a little off in the patch due to various patches
Gentoo may apply. It's the only dev. box for VDR I have so forgive me on
that.
I'm looking forward to the review :)
Oliver
[View Less]
Hi list,
I've uploaded the final patch version of the h.264 NALU fill removal for
VDR 1.7.16.
The patch deletes NALU fill data from h.264 streams while recording. The
overall stream structure isn't modified, only complete TS packets of
NALU fill data are dropped. On HD TV channels that use fixed video
bandwidth, this can save 40-60% file size without loosing any data.
The patch must be enabled at settings -> recordings, and can be
activated/deactivated individually for each recording by …
[View More]adding the
keyword NALUDUMP or NALUKEEP to the recording name.
Also available is the standalone tool that processes ts files. The new
version uses the same buffering as the patch, and should otherwise
produce identical output compared to the 0.0.1 tool.
Get it at:
http://www.udo-richter.de/vdr/naludump.html (de)
http://www.udo-richter.de/vdr/naludump.en.html (en)
Cheers,
Udo
[View Less]