Hello everyone! I'm from Argentina, and up to last month I've been using
VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the
last week I've been trying to upgrade to VDR 2.2 and I've found a
problem with ISDB-T cards: they are not supported.
As I'm really interested in using VDR, I was digging inside the code and
found a partial solution for this problem: as ISDBT is the same as DVBT,
I've changed the way delivery system is queried. My changes are applied
in a cloned repo at …
[View More]github:
https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728…
That's the only change I've made. Now I can enjoy my fresh upgraded VDR
installation!!
I think a better refactor should be made, but for now it's working
perfectly deployed as a docker container:
https://registry.hub.docker.com/u/chrodriguez/vdr
Thanks for this wonderfull project!
--
Lic. Christian A. Rodriguez
@car_unlp
[View Less]
Occasionally my signal drops out (haven't looked into it yet), and it
causes VDR to completely freeze and become defunct/zombie. That locks
up the drivers and the only way to resolve it is by rebooting. No core
file gets created. Does anyone know how to prevent the lock-up in the
first place? Could it be some kind of leak from the looping (see log
clip below)?
Here's a clip of the log when it happens. You can see how the log gets
filled with the same repeating lines until it crashes.
2016.Oct.…
[View More]28|12:08:55 video: slow down video, duping frame
2016.Oct.28|12:08:55 video: decoder buffer empty, duping frame
(5656/167423) 7 v-buf
2016.Oct.28|12:09:29 video: slow down video, duping frame
2016.Oct.28|12:16:09 [1297] [softhddev]Clear:
2016.Oct.28|12:16:09 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:09 audio/alsa: using device 'default'
2016.Oct.28|12:16:09 audio/alsa: start delay 336ms
2016.Oct.28|12:16:09 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:10 audio/alsa: start delay 336ms
2016.Oct.28|12:16:10 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:10 audio/alsa: start delay 336ms
2016.Oct.28|12:16:10 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:10 audio/alsa: start delay 336ms
2016.Oct.28|12:16:10 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:10 audio/alsa: start delay 336ms
2016.Oct.28|12:16:10 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:10 audio/alsa: start delay 336ms
2016.Oct.28|12:16:10 [1297] [softhddev]Clear:
2016.Oct.28|12:16:10 audio/alsa: using device 'default'
2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:11 audio/alsa: using device 'default'
2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:11 audio/alsa: using device 'default'
2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:11 audio/alsa: using device 'default'
2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:11 audio/alsa: using device 'default'
2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:11 audio/alsa: using device 'default'
2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:11 audio/alsa: start delay 336ms
2016.Oct.28|12:16:11 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:12 audio/alsa: start delay 336ms
2016.Oct.28|12:16:12 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:12 audio/alsa: start delay 336ms
2016.Oct.28|12:16:12 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:12 audio/alsa: start delay 336ms
2016.Oct.28|12:16:12 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:12 audio/alsa: start delay 336ms
2016.Oct.28|12:16:12 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:12 audio/alsa: start delay 336ms
2016.Oct.28|12:16:12 [1297] [softhddev]Clear:
2016.Oct.28|12:16:12 audio/alsa: using device 'default'
2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:13 audio/alsa: start delay 336ms
2016.Oct.28|12:16:13 [1297] [softhddev]Clear:
2016.Oct.28|12:16:13 audio/alsa: using device 'default'
2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:13 audio/alsa: start delay 336ms
2016.Oct.28|12:16:13 [1297] [softhddev]Clear:
2016.Oct.28|12:16:13 audio/alsa: using device 'default'
2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:13 audio/alsa: start delay 336ms
2016.Oct.28|12:16:13 [1297] [softhddev]Clear:
2016.Oct.28|12:16:13 audio/alsa: using device 'default'
2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode
2016.Oct.28|12:16:13 audio/alsa: start delay 336ms
2016.Oct.28|12:16:13 [1297] [softhddev]Clear:
[View Less]
I upgrade to fedora 25, and now vaapi with xineliboutput don't work for h264 channels. Works well with softhddevice. Attached is a log from vdr-sxfe.
Any hint?
Jose Alberto
Hi all,
I would like to run my headless VDR without a primary DVB (or suspended
output) but keep xineliboutput running. I can't figure out how.
My VDR has 4 receivers (2x Astra, 2x Hotbird) without MPEG decoder. It runs
vnsiserver (for my Kodi client), streamdev-server (for some browser / VLC
clients) and xineliboutput (because it's sometimes useful to have access to
the VDR console via remote). Alas, xineliboutput will always be the primary
DVB device and block a receiver, which is nasty …
[View More]when VDR is recording on one
bouquet, xineliboutput blocks another bouquet and I want to watch live TV on
just another bouquet, all on the same satellite.
Can I use the suspendoutput plugin while keeping xineliboutput active so that
I can access it with vdr-sxfe when needed?
TIA!
(I could "park" xineliboutput on an arbitrary hotbird channel though but I'd
like to have it automated ...)
--
Keep emotionally active. Cater to your favorite neurosis.
[View Less]
Hi,
I'm using the Sony PS3 Bluetooth remote for controlling VDR.
Everything works except for the repeating of key presses while holding
down the key on the remote.
I'm using the --lirc option for VDR to get the events from eventlircd.
I managed to generate an event for the key-down. e.g.:
KEY_ENTER
and also for the key-up event:
KEY_ENTER_rel
Here only a suffix is appended to the key name (_rel).
Is there a way to generate repeated key presses until the key-up
appears? That would be great.
…
[View More]If there is no way available yet, I could try to implement such a
functionality in the lirc.c of the VDR core.
Thanks a lot
Patrick
[View Less]
Hello,
You've got to read that information, there are so many amazing facts and I swear you are going to like it! Just read it here http://alfio.jgasher.com/3032
Hugs, Supporto IntraNet