vdr

vdr@linuxtv.org

1 participants
6750 discussions

20 Years of VDR
by Josce 19 Mar '20

19 Mar '20

>Back then a VDR was something special, while today it's just an ordinary device. Well, I am sitting here installing vdr yet again on a new pc :) It might be old, it might be this and that, but to me it is still the best there is. Simple, efficient and works all the time. I have been using it since the first version, and I will probably use it for as long as it can be used. So again, thank you Klaus! Josce

3 2

"noepg" plugin and vdr-2.4.1
by Karim AFIFI 15 Feb '20

15 Feb '20

Hello, I have an issue with noepg under vdr-2.4.1 (modifying channel yes/no is not stored). Do you know where I could find the last version for vdr-2.4.1, or a patch ? Thanks a lot. Karim

1 0

vdr-2.4.1 and vaapi => issues audio and video
by Karim AFIFI 25 Jan '20

25 Jan '20

Hello, I continue to buid my new vdrbox : Mint 19.3 / Desktop Cinnamon 3840x2160 @ 60 Hz / intel gpu / vaapi plugin / vdr-2.4.1 Driver seems to be OK : vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.1.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSlice VAProfileVP9Profile2 : VAEntrypointVLD Running mpv from a terminal is OK : mpv -vo=vaapi --hwdec=vaapi /DATA/file1080p.mkv Playing: /DATA/file1080p.mkv (+) Video --vid=1 (*) (h264 1920x800 24.000fps) (+) Audio --aid=1 --alang=fre (*) (dts 6ch 48000Hz) (+) Subs --sid=1 --slang=fre (*) 'Forced' (subrip) AO: [pulse] 48000Hz 5.1(side) 6ch float Using hardware decoding (vaapi). VO: [vaapi] 1920x800 vaapi[nv12] AV: 00:00:09 / 01:27:44 (0%) A-V: 0.000 I have some issues with VDR and vaapi-plugin : - pictures are extremely slow on every channels (dvbt and dvbs) - no sound on dvbt (beause eac3 ?) , picture and sound out of sync on dvbs I found many errors in syslog (see below) , but I don't know what's wrong. Could you please help me to fix this isssue ? Thanks a lot. Karim syslog Jan 25 12:03:03 pctest vdr: [2546] VDR version 2.4.1 started Jan 25 12:03:03 pctest vdr: [2546] switched to user 'test' Jan 25 12:03:03 pctest vdr: [2546] codeset is 'UTF-8' - known Jan 25 12:03:03 pctest vdr: [2546] found 28 locales in /usr/local/src/vdr-2.4.1/locale Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-femon.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-mpv.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-vaapidevice.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-skinsoppalusikka.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading /DATA/configVDR/setup.conf ... Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (1/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (2/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (3/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (4/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (5/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (6/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (7/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (8/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (9/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (10/0) 0 ... Jan 25 12:03:06 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (38/0) 4 Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: supports video processing Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: noise reduction supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: 0,00 - 1,00 ++ 0,03 = 0,50 Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: enabling denoise filter (pos = 0) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: deinterlacing supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: bob deinterlace supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: motion adaptive deinterlace supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: motion compensated deinterlace supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: enabling deinterlacing (pos = 1) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: sharpening supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: 0,00 - 1,00 ++ 0,03 = 0,50 Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: enabling sharpening filter (pos = 0) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: enabling color balance filters Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: supported color balance filter count: 4 Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: hue (-180,00 - 180,00 ++ 1,00 = 0,00) (pos = 2) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: saturation (0,00 - 10,00 ++ 0,10 = 1,00) (pos = 2) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: brightness (-100,00 - 100,00 ++ 1,00 = 0,00) (pos = 2) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: contrast (0,00 - 10,00 ++ 0,10 = 1,00) (pos = 2) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: skin tone enhancement supported Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: 0,00 - 4,00 ++ 1,00 = 0,00 Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: enabling skin tone filter (pos = 3) Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: allocating 1 forward reference surfaces for postprocessing Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: allocating 0 backward reference surfaces for postprocessing Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video/vaapi: changing to 0 forward reference surfaces for postprocessing Jan 25 12:03:06 pctest vdr: [2577] VAAPI-ERROR: video/vaapi: black surface displayed Jan 25 12:03:06 pctest vdr: [2577] VAAPI-ERROR: video: decoder buffer empty, duping frame (1087892848/0) 0 v-buf Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video: --:--:--.--- +0 0 0/\ms 0+1 v-buf Jan 25 12:03:06 pctest vdr: [2577] VAAPI: video: 4:50:57.552+8888 0 0/\ms 0+5 v-buf Jan 25 12:03:07 pctest vdr: [2555] changing name of channel 509 from 'Eurosport,;SMR6' to 'Eurosport OBSOLETE,;OBSOLETE SMR6' Jan 25 12:03:07 pctest vdr: [2555] changing name of channel 510 from 'LCI,;SMR6' to 'LCI OBSOLETE,;OBSOLETE SMR6' Jan 25 12:03:17 pctest vdr: [2570] VAAPI: audio/alsa: using device 'hw:0,7' Jan 25 12:03:17 pctest vdr: [2570] VAAPI-ERROR: audio/alsa: set params error: Argument invalide Jan 25 12:03:17 pctest vdr: [2570] VAAPI-ERROR: audio: can't set channels 0 sample-rate 0Hz Jan 25 12:03:17 pctest vdr: [2574] ERROR: 1 TS packet(s) not accepted in Transfer Mode Jan 25 12:03:17 pctest vdr: [2577] VAAPI-ERROR: video: initial slow down video, frame 99 Jan 25 12:03:17 pctest vdr: [2577] VAAPI-ERROR: video: decoder buffer empty, duping frame (1087892848/0) 0 v-buf Jan 25 12:03:17 pctest vdr: [2577] VAAPI: video: --:--:--.--- +0 0 0/\ms 0+1 v-buf Jan 25 12:03:19 pctest vdr: [2577] VAAPI: video: 4:51:10.152+8888 0 0/\ms 1+5 v-buf Jan 25 12:03:32 pctest vdr: [2570] VAAPI: audio/alsa: using device 'hw:0,7' Jan 25 12:03:32 pctest vdr: [2570] VAAPI-ERROR: audio/alsa: set params error: Argument invalide Jan 25 12:03:32 pctest vdr: [2570] VAAPI-ERROR: audio: can't set channels 0 sample-rate 0Hz Jan 25 12:03:32 pctest vdr: [2577] VAAPI-ERROR: video: initial slow down video, frame 98 Jan 25 12:03:32 pctest vdr: [2577] VAAPI-ERROR: video: decoder buffer empty, duping frame (1087892848/0) 0 v-buf Jan 25 12:03:32 pctest vdr: [2577] VAAPI: video: --:--:--.--- +0 0 0/\ms 0+1 v-buf Jan 25 12:03:33 pctest vdr: [2577] VAAPI: video: 4:51:23.512+8888 0 0/\ms 1+5 v-buf ... Jan 25 12:03:44 pctest vdr: [2570] VAAPI: audio/alsa: using device 'hw:0,7' Jan 25 12:03:44 pctest vdr: [2570] VAAPI-ERROR: audio/alsa: set params error: Argument invalide Jan 25 12:03:44 pctest vdr: [2570] VAAPI-ERROR: audio: can't set channels 0 sample-rate 0Hz Jan 25 12:03:44 pctest vdr: [2577] VAAPI-ERROR: video: initial slow down video, frame 99 Jan 25 12:03:44 pctest vdr: [2577] VAAPI-ERROR: video: decoder buffer empty, duping frame (1087892848/0) 0 v-buf Jan 25 12:03:44 pctest vdr: [2577] VAAPI: video: --:--:--.--- +0 0 0/\ms 0+1 v-buf Jan 25 12:03:45 pctest vdr: [2577] VAAPI: video: 4:51:36.032+8888 0 0/\ms 1+5 v-buf

1 0

French DVB-T Channel IDs vs. EIT Channel IDs
by Patrick Boettcher 25 Jan '20

25 Jan '20

Hi list, since some time (1-2 years) I noticed that the DVB-T channels do not show EPG anymore. I'm not sure what is the root-cause: either it was the migration of French DVB-T to HD (in 2016) or an update of VDR. Anyway, this morning I took the time to figure out what is wrong and here is what I found. In short, the channel-ID generated from the one received in the EIT does not correspond to a known channel-ID from the channel list, and VDR drops the whole section: In cEIT::cEIT (from eit.c) we see tChannelID channelID(Source, getOriginalNetworkId(), getTransportStreamId(), getServiceId()); cChannel *Channel = Channels->GetByChannelID(channelID, true); and channel is NULL in my case. I added some debug prints to GetByChannelID() in the search loop: printf("sid: %d == %d, %s, %s %d\n", Channel->Sid(), sid, (const char *)ChannelID.ToString(), (const char *)Channel->GetChannelID().ToString(), Channel->GetChannelID() == ChannelID); And here is an example of what I get: sid: 517 == 517, T-8442-2-517, T-0-506-517 0 The internal channel ID of vdr reads T-0-506-517. 517 is the SID, 506 is the radio-channel frequency in MHz. This is the right internal channel for this EIT-section. The EIT-channel-ID is telling me that 8442 is the original network ID and 2 might be the radio-channel ID. I tweaked the operator==() of ChannelID to make it work, but not in a contributable manner. How should this be fixed correctly? Is this a regression introduced somewhere? Can it be solved by configuration? Thanks for any help. best regards, -- Patrick.

4 22

Utilising Nvidia HW En/Decode capabilities with ffmpeg
by Richard Scobie 18 Aug '19

18 Aug '19

Not directly applicable to vdr, but for those transcoding recordings or using plugins that use ffmpeg, here's a useful recent article around using the hardware encode/decode capabilities of Nvidia's cards. https://devblogs.nvidia.com/nvidia-ffmpeg-transcoding-guide/ Regards, Richard

1 0

[ANNOUNCE] VDR version 2.4.1 released
by Klaus Schmidinger 17 Jun '19

17 Jun '19

VDR version 2.4.1 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.4.1.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.4.0-2.4.1.diff MD5 checksums: b2897fe6b6e6711d512a69642b1b8ec1 vdr-2.4.1.tar.bz2 cf5f328165e1a48e28e68b6709312e63 vdr-2.4.0-2.4.1.diff This version fixes a few bugs that came up after the release of version 2.4.0. The changes since version 2.4.0: - Fixed handling the tfRecording flag in the SVDRP commands MODT and UPDT (reported by Johann Friedrichs). - Fixed a possible invalid locking sequence in case a remote timer handling error message is displayed on the OSD and the skin tries to lock the Recordings or DeletedRecordings list in its Flush() function (for instance by calling cVideoDiskUsage::HasChanged()). To do this, the call to Skins.Message() in menu.c's HandleRemoteModifications() has been changed to Skins.QueueMessage(), and cSkins::ProcessQueuedMessages() is now called unconditionally in the main loop, and checks whether the current cSkinDisplay object (if any) implements SetMessage(). - Fixed locking the Channels list in cDisplayChannel, where the lock was still held when Flush() was called (reported by Matthias Senzel and Uwe Scheffler). - Fixed shutdown after user inactivity in case a plugin is keeping the OSD open (reported by Ulrich Eckhardt). - Fixed switching through encrypted channels with the Up/Down keys (thanks to Helmut Binder). - Now deactivating MTD support if a non MCD capable CAM is inserted after removing a previously used CAM that is MCD capable (thanks to Helmut Binder). - Added support for DVB devices with more than one frontend that all use the same dvr and demux. Note that in order for this to work, you must not set symbolic links like "demux1 -> demux0" and "dvr1 -> dvr0", as is mentioned in some user manuals of multi frontend DVB cards. - Reverted the change "The EIT filter no longer parses data from "other TS"...". It led to missing EPG data on channels from Canal Digital Norway (reported by Stian B. Barmen). - Fixed accessing the actual frontend on multi frontend devices (thanks to Helmut Binder). - Fixed opening the UDP port in peerdemo (thanks to Robert Hannebauer). - Fixed handling PATs that contain no PMTs. - Fixed processing the last entry in the scan list of the EIT scanner (thanks to Helmut Binder). - Fixed processing transponder data in the NIT (thanks to Helmut Binder). - Fixed triggering the SDT filter when parsing the NIT (thanks to Helmut Binder). - Added support for EAC3 audio from other sources (thanks to Jürgen Schneider). - No longer logging tuning timeouts for transponders that are announced in the NIT but are not currently broadcasting. - Fixed processing SI::T2DeliverySystemDescriptor when typecasting it over an SI::ExtensionDescriptor (reported by Helmut Binder). - Fixed sorting recordings alphabetically. - Fixed dropping capabilities in case cap_sys_time is not available. - Fixed updating the cursor position when switching channels with the Channel+/- keys while the Channels menu is open. - Fixed handling shared CA pids (thanks to Onur Sentürk). - Now touching the .update file in the video directory after removing deleted recordings, so that other VDRs that use the same video directory will update their list of (deleted) recordings and thus won't display too much empty disk space. - Fixed the install target in case of multiple jobs (thanks to Chris Mayo). - Fixed mapping SIDs in MTD (thanks to Helmut Binder). - Fixed updating the checksum in the CA table after mapping EMM PIDs for MTD (thanks to Helmut Binder). - Fixed a compiler warning in ExchangeChars() (thanks to Helmut Binder). - Fixed a compiler warning and a possible buffer overflow in cCiMMI::SendAnswer(). - Fixed a possible invalid lock sequence if the main menu is open and the user switches to a channel that is currently not available, using the Channel+/- keys. - Fixed handling remote timers in case the response to LSTT is '550 No timers defined'. - Fixed a compiler warning in cIndexFile::ConvertToPes() and added __attribute__((packed)) to tIndexPes and tIndexTs (suggested by Helmut Binder). - Fixed handling repeat function for keyboards. - Added a workaround for broadcasters who set an event to status "not running" where this is inappropriate; implicitly setting events to "not running" is now also logged. - Fixed asserting free disk space in case there is no local timer currently recording. - The default maximum size of a cPixmap has been raised to the maximum possible value. - Increased PLAYERBUFSIZE to (MAXFRAMESIZE * 5) to avoid stuttering replay under heavy system load, and to better document that this buffer size is related to the maximum frame size. - Fixed inconsistent behavior in case only certain devices are used (selected by the '-D' option). - Fixed a wrong variable name in cFileName::cFileName(). - If cSkins::Message() is called from a background thread and Type is not mtStatus, the call is now automatically forwarded to QueueMessage(). - Fixed handling the S2SatelliteDeliverySystemDescriptor for transponders broadcasting in "backwards compatibility mode" according to ETSI EN 300 468 (thanks to Onur Sentürk). Have fun! Klaus

1 0

VDR reports wrong disk usage
by Damien Bally 16 Jun '19

16 Jun '19

Hi My vdr recordings are stored on an openmediavault server. The vdr box (rpi 2) is given access to them by nfs. # df -ah /mnt/mmcblk0p3/tv Filesystem Size Used Available Use% Mounted on 192.168.0.40:/export/vdrrecords 3.6T 1.2T 2.5T 32% /mnt/mmcblk0p3/tv VDR nevertheless wrongly reports : Total: 1:02h (1.6GB) | Free: 1:01h (1.5GB) The problem appeared when I switched from MLD 5.1 to MLD 5.4 (VDR ver. 2.4.0) It seems like VDR kept disk usage of the SD card before mounting the nfs share in /etc/fstab. How can I fix this ? Thank you for helping Damien

1 0

Tuning on multi-standard PCI card not testing all frontends
by Nick Burrett 09 Jun '19

09 Jun '19

I have a TBS 6522 tuner card, which has 4 ports, presented as two DVB devices. The DVB-C/DVB-T ports share the same muxer as the DVB-S/S2. VDR correctly detects this: Jun 09 13:29:13 tv.house vdr[16535]: [16535] DVB API version is 0x050B (VDR was built with 0x050B) Jun 09 13:29:13 tv.house vdr[16535]: [16535] frontend 0/0 provides DVB-T,DVB-T2,DVB-C,ISDBT,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 6522 DVB-S/S2/DVB-T/T2/C ") Jun 09 13:29:13 tv.house vdr[16535]: [16535] frontend 0/1 provides DVB-S,DVB-S2,DSS with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Silicon Labs Si2183") Jun 09 13:29:13 tv.house vdr[16535]: [16535] frontend 1/0 provides DVB-T,DVB-T2,DVB-C,ISDBT,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("TurboSight TBS 6522 DVB-S/S2/DVB-T/T2/C ") Jun 09 13:29:14 tv.house vdr[16535]: [16535] frontend 1/1 provides DVB-S,DVB-S2,DSS with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Silicon Labs Si2183") Jun 09 13:29:14 tv.house vdr[16535]: [16535] found 2 DVB devices Currently I have DVB-T connected to /dev/dvb/adapter0/frontend0 and a DVB-S connected to /dev/dvb/adapter1/frontend1. The streams from DVB-T work fine but the DVB-S streams do not work at all. The problem appears to be that VDR never attempts to test frontend 1/1 for a signal and instead continually retries frontend 0/1: Jun 09 14:14:30 tv.house vdr[16891]: [16897] frontend 0/1 timed out while tuning to channel 26 (BBC Two HD), tp 210847 Jun 09 14:15:33 tv.house vdr[16891]: [16897] frontend 0/1 timed out while tuning to channel 26 (BBC Two HD), tp 210847 Jun 09 14:16:36 tv.house vdr[16891]: [16897] frontend 0/1 timed out while tuning to channel 26 (BBC Two HD), tp 210847 Jun 09 14:17:40 tv.house vdr[16891]: [16897] frontend 0/1 timed out while tuning to channel 26 (BBC Two HD), tp 210847 Jun 09 14:18:44 tv.house vdr[16891]: [16897] frontend 0/1 timed out while tuning to channel 26 (BBC Two HD), tp 210847 It would be useful if it were possible to change the --device parameter to be more explicit about which DVB devices should be enabled e.g. --device=A,F;A,F i.e. --device=0,0;1,1 from my configuration so that VDR wouldn't unnecessarily keep trying to get a signal from frontend 0/1. Regards, Nick

1 1

Re: [vdr] Index of /Developer/Patches/vdr-2.4
by Klaus Schmidinger 03 Jun '19

03 Jun '19

On 03.06.19 21:18, Karim AFIFI wrote: > ... > Do you plan to provide soon a vdr-2.4.1 release with all of them ? Yes. There is one problem with the channel display on the Raspberry Pi that still needs to be solved, and after that I'm planning to release version 2.4.1. Klaus

2 1

Re: [vdr] Questions about good hardware to view VDR 4K
by Karl-Heinz Volk 03 Jun '19

03 Jun '19

I just purchased an Amazon FireTV 4k stick and this is amazing. It is working until 2160p60 consuming 1..2 Watt using an USB power supply. Why is there no VDR for Android using network DVB sources? Kind Regards Karl-Heinz Am Mi., 8. Mai 2019 um 19:01 Uhr schrieb Karim AFIFI < karim.afifi(a)laposte.net>: > Hi, > > I am looking for an ATX motherboard with PCI and PCIE slots, for using > with new VDR 4K (PCI S2-3200+CI and PCIE Hauppauge quad), and ASTERISK (PCI > Digium FXO/FXS card). > > At the beginning, I was thinking about an Intel 1151 socket (for best > vaapi support), like this one (*): > > https://www.asus.com/Motherboards/TUF-H310-PLUS-GAMING/HelpDesk_Manual/ > > Unfortunately, I noticed HDMI is v1.4, with 4k@24Hz only ! > > I am afraid that I need to add a PCI-E video card to achieve 4k@60Hz. > > Is it correct ? If so, I have two questions : > 1) could you advice about fanless + VAAPI compatible product ? > 2) any feedback about best plateform/chipset : AMD vs Intel ? > > Thanks a lot. > Karim > > > (*) using with low TDP quad core CPU, for example i3-8100T. > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > -- Karl-Heinz Volk Pastorenweg 78 B 28237 Bremen

5 4

← Newer
1
...
6
7
8
9
10
11
12
...
675
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr