Re: [vdr] vdr Digest, Vol 161, Issue 4

Am Tue, 30 Oct 2018 12:00:01 + schrieb vdr-requ...@linuxtv.org: > > I plan to upgrade my VDR box, with these two important features : > > - reading mkv files => I am using xineliboutput and vdpau. > > MKV is just a container for data streams and support is wide-spread. > Any half-decent

Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels

> >xineliboutput and VDPAU so I assume what you actually mean by mkv is > >being able to play back HD or greater content using VDPAU for decoding > >and xineliboutput to get the decoded frames to your tv. > Correct, my 4K mkv files are using H.265 codecs, HD files are using H.264. Since dumping

Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels

-Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de VDR User Envoyé : mardi 30 octobre 2018 01:38 À : mailing list: vdr Objet : Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels > I plan to upgrade my VDR box, with these two

Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels

> I plan to upgrade my VDR box, with these two important features : > - reading mkv files => I am using xineliboutput and vdpau. MKV is just a container for data streams and support is wide-spread. Any half-decent player supports mkv. It's also unrelated to xineliboutput and VDPAU so I assume

[vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels

Hello, I plan to upgrade my VDR box, with these two important features : - reading mkv files => I am using xineliboutput and vdpau. - receiving 4K channels => for HD, I am using old PCI/PCIE motherboard + TBS6928 (with CI). Could you share best hardware cpu/video/card,motherboard/..., & best

[vdr] diseq.conf

I have a lnb monoblock pointing to astra 19.2E hotbird, with a internal diseq 2x1 wich I use with diseq enabled and the default diseq.conf: S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38

[vdr] [ANNOUNCE] Duplicates plugin 1.0.1

Description: Shows duplicate recordings. Changes in 1.0.1: - Fixed header row after deleting or hiding recordings. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Thanks for you help Martin  Gesendet: Mittwoch, 10. Oktober 2018 um 11:50 Uhr Von: "Klaus Schmidinger" An: vdr@linuxtv.org Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope On 10/10/18 11:46 AM, Martin Gansser wrote: > I have contacted Andreas. > >

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 10/10/18 11:46 AM, Martin Gansser wrote: I have contacted Andreas. On advice of Andreas, I have defined the IOCTL myself in the file dvbhdffdevice.h this is the Patch: define_AUDIO_GET_PTS.patch with this patch i get this warnings: [2] ---

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hi Klaus, I will contact him. Many Thank Martin Gesendet: Dienstag, 09. Oktober 2018 um 11:31 Uhr Von: "Klaus Schmidinger" An: vdr@linuxtv.org Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope On 10/9/18 10:27 AM, Martin Gansser wrote: > Hello

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 10/9/18 10:27 AM, Martin Gansser wrote: Hello Klaus, will you provide a kernel> = 4.8 patch or will I need to contact the kernel developer for this? Hello Martin, please contact Andreas Regel about this. He maintains the dvbhddevice plugin. Greetings Klaus

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hello Martin! The Kernel maintainers removed it on purpose and in my opinion this was correct. So asking the maintainers is useless at all. BR, Jasmin Am 9. Oktober 2018 10:37:44 MESZ schrieb fnu : >Martin, > >just in case you missed it, that is obviously an issue of >vdr-plugin-dvbhddevice

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Martin, just in case you missed it, that is obviously an issue of vdr-plugin-dvbhddevice and not core VDR, maintained by Klaus ... Cheers Frank -Ursprüngliche Nachricht- Von: vdr Im Auftrag von Martin Gansser Gesendet: Dienstag, 9. Oktober 2018 10:27 An: vdr@linuxtv.org Betreff: Re:

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hello Klaus, will you provide a kernel> = 4.8 patch or will I need to contact the kernel developer for this? Martin Gesendet: Sonntag, 30. September 2018 um 11:36 Uhr Von: "Klaus Schmidinger" An: vdr@linuxtv.org Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hello! > Any idea why it was necessary to break these things? No, I just used Google to find it. > BTW: I always thought that Linux kernel policy is not to allow userspace > applications to break. Apparently this is no longer the case :-(. In general Kernel APIs do not change, but sometimes this

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 9/28/18 8:05 PM, Jasmin J. wrote: Hi! This is obsolete since Kernel 4.8: https://www.kernel.org/doc/html/v4.8/media/uapi/dvb/audio-get-pts.html So VDR would already have needed to be changed quite some time ago. I guess it is time to do it now. BTW: I always thought that Linux kernel

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 9/28/18 8:05 PM, Jasmin J. wrote: Hi! This is obsolete since Kernel 4.8: https://www.kernel.org/doc/html/v4.8/media/uapi/dvb/audio-get-pts.html Any idea why it was necessary to break these things? So VDR would already have needed to be changed quite some time ago. I guess it is time

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hi! This is obsolete since Kernel 4.8: https://www.kernel.org/doc/html/v4.8/media/uapi/dvb/audio-get-pts.html So VDR would already have needed to be changed quite some time ago. I guess it is time to do it now. In this particular case I would also suggest to create a patch for VDR 2.4.0, so

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

He tried to remove AUDIO_GET_PTS in 2011: https://github.com/torvalds/linux/commit/fa24198897ff0e8d34876be0e61f9b35d3c0d467 and had to revert it: https://github.com/torvalds/linux/commit/7a2b66b1bd26d717763985bad401410665fa0672 Alexander Am 28.09.2018 um 14:53 schrieb Klaus Schmidinger: On

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 9/28/18 12:02 PM, Alexander Grothe wrote: It seems this definition has been removed upstream, because it was considered to be "unused": https://github.com/torvalds/linux/commit/d21c249b26311dd193b100e65fc9e7ae96233d40#diff-56193b27b16cac28881a16f295c6ff3cL133 Signed-off-by: Mauro Carvalho

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

I have opened a fedora ticket [1] https://bugzilla.redhat.com/show_bug.cgi?id=1633979 thanks Martin   Gesendet: Freitag, 28. September 2018 um 12:02 Uhr Von: "Alexander Grothe" An: "VDR Mailing List" Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

It seems this definition has been removed upstream, because it was considered to be "unused": https://github.com/torvalds/linux/commit/d21c249b26311dd193b100e65fc9e7ae96233d40#diff-56193b27b16cac28881a16f295c6ff3cL133 Am Fr., 28. Sep. 2018 um 11:22 Uhr schrieb Klaus Schmidinger <

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 9/28/18 11:04 AM, Martin Gansser wrote: ok, the Fedora30 package [1] kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm contains the file /usr/include/linux/dvb/audio.h, but definition #define AUDIO_GET_PTS _IOR('o', 19, __u64) fehlt. [1]

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

ok, the Fedora30 package [1] kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm contains the file /usr/include/linux/dvb/audio.h, but definition #define AUDIO_GET_PTS _IOR('o', 19, __u64) fehlt. [1]

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

On 9/28/18 10:21 AM, Martin Gansser wrote: ... dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope if (ioctl(fd_audio, AUDIO_GET_PTS, ) == -1) { ^ dvbhdffdevice.c:569:33: note: suggested alternative:

[vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

Hi, i am trying to compile vdr-2.4.0 for Fedora 30 on the Fedora rpm build server, but this fails with the following error message [1]: g++ -O3 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches

Re: [vdr] Multiple vdr peers on same machine

> Actually it should be possible to run several VDRs on the same machine > without any exta efforts. All you need to do is use separate SVDRP ports > via the --port option. I was missing address of the machine from the other svdrphosts.conf. 127.0.0.1 there didn't help, because peering doesn't

Re: [vdr] Multiple vdr peers on same machine

On 9/25/18 8:52 PM, Mikko Tuumanen wrote: I have two vdr instances running on the same machine, one for recording and other for viewing. Then I wanted them to use the new vdr peer system to be able to edit timers from the viewing side. Running two vdr's didn't work because they both want to

[vdr] Multiple vdr peers on same machine

I have two vdr instances running on the same machine, one for recording and other for viewing. Then I wanted them to use the new vdr peer system to be able to edit timers from the viewing side. Running two vdr's didn't work because they both want to bind the 6419 port, so I made a work-around

Re: [vdr] TT S2 6400 IR Remote

Hi Detlef, Thanks very much for that. Detlef Heine wrote: Here it is: remote-ir.Up 00010001000E remote-ir.Down 000100010012 Snip ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TT S2 6400 IR Remote

Here it is: remote-ir.Up 00010001000E remote-ir.Down 000100010012 remote-ir.Menu 000100010028 remote-ir.Ok 000100010010 remote-ir.Back 000100010014 remote-ir.Left 00010001000F remote-ir.Right 000100010011 remote-ir.Red

[vdr] [ANNOUNCE] Duplicates plugin 1.0.0

Description: Shows duplicate recordings. Changes in 1.0.0: - Dropped support for VDR 2.2.0. - Added scanner thread for duplicates. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR ISDB-T support

Sorry for my reply of a very old message. My appology. El 13/09/2018 a las 22:31, Sergio Daniel Gomez escribió: Hi Thomas. Do you know TBS ISDB-T cards? Quad tuner https://www.tbsdtv.com/products/tbs6814-isdb-t-quad-tuner-pcie-card.html and multistandard octa tuner

Re: [vdr] VDR ISDB-T support

Hi Thomas. Do you know TBS ISDB-T cards? Quad tuner https://www.tbsdtv.com/products/tbs6814-isdb-t-quad-tuner-pcie-card.html and multistandard octa tuner https://www.tbsdtv.com/products/tbs6209-dvb-t2-c2-tc-isdbt-octatv-tuner.html Kind regrads Sergio El 04/08/2015 a las 7:06, Thomas

[vdr] vdr-convert version 2.2 released: Podcast mode added

/vdr-convert is a tool to accurately transcode VDR1.x and VDR2.x TV recordings, including all valid streams - video, audio (including AC3/DTS 5.1), Audio Description (AD), and DVB subtitles - into more compressed and accessible formats, while maintaining perceived quality with good compatibility.

[vdr] TT S2 6400 IR Remote

If there is anyone using the TT S2 6400 with the supplied IR receiver, remote and the "remote" plugin, could they please post a few lines from the remote.conf file? Thanks, Richard ___ vdr mailing list vdr@linuxtv.org

[vdr] [ANNOUNCE] Duplicates plugin 0.2.2

Description: Shows duplicate recordings. Changes in 0.2.2: - Updated kNone handling in main menu. - Improved duplicate recording copy constructor. - Added missing recordings lock release. - Simplified toggle hidden. - Fixed recordings locking sequence. - Check for vanished recorgins in info

[vdr] [ANNOUNCE] Duplicates plugin 0.2.1

Description: Shows duplicate recordings. Changes in 0.2.1: - Fixed menu updating bug introduced in version 0.2.0. Homepage for the plugin: http://projects.vdr-developer.org/projects/plg-duplicates ___ vdr mailing list vdr@linuxtv.org

[vdr] [ANNOUNCE] Duplicates plugin 0.2.0

Description: Shows duplicate recordings. Changes in 0.2.0: - Fixed compilation with VDR 2.4.0. - Improved delete and hide performance. - Refactored duplicate detection to own classes. Homepage for the plugin: http://projects.vdr-developer.org/projects/plg-duplicates

[vdr] powersaving with satip pluging

Hello, I've a vdrserver running with vdr 2.3.8 and satip plugin 2.3.1-GIT-e008ee0. It works great with a minisatip server 0.7.15. But it keeps the connection to the minisatip server open all the time, so the dvb adapter and lnb consumes power every time. I added the parameter "--detach" to the

[vdr] Modified VDR User Counter

In an effort to avoid possible problems with the new data protection law in Germany ("DSGVO"), I have modified the VDR User Counter in such a way that it no longer asks for or displays the user's name, public email address and homepage URL. Any such previously entered data has been deleted from

[vdr] ICAT​-EGVE​ 2018 Call For Papers

*ICAT-EGVE 2018 Call For Papers* The ICAT-EGVE 2018 conference will be held November 7th – 9th in Limassol, Cyprus. This is the merger of the 28th International Conference on Artificial Reality and Telexistence (ICAT 2018) and the 23rd Eurographics Symposium on Virtual Environments (EGVE 2018).

[vdr] VDR Portal

Hi, i lost my password for vdr portal, but i can't reset it because captcha doesn't work anymore. If someone who can login to vdr-protal would be so kind to inform the site admin about it. kind regards gerald ___ vdr mailing list vdr@linuxtv.org

Re: [vdr] [ANNOUNCE] VDR version 2.4.0 released

Thanks Klaus & all contributors to VDR! On Sun, Apr 15, 2018 at 3:44 AM, Karim AFIFI wrote: > Hi Klaus, > > Many thanks for this new release, and all the job around it ! > > Regards. > Karim > > -Message d'origine- > De : vdr [mailto:vdr-boun...@linuxtv.org] De

Re: [vdr] [ANNOUNCE] VDR version 2.4.0 released

Hi Klaus, Many thanks for this new release, and all the job around it ! Regards. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : dimanche 15 avril 2018 11:37 À : VDR mailing list Objet : [vdr] [ANNOUNCE] VDR version 2.4.0

[vdr] [ANNOUNCE] VDR version 2.4.0 released

VDR version 2.4.0 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.4.0.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9-2.4.0.diff MD5 checksums: 12c6a3abeadfa915fcfe736bb047a3ab vdr-2.4.0.tar.bz2

Re: [vdr] Video-Audio disruptions with 4.16+ kernel

On 12.04.2018 05:12, Richard Scobie wrote: ... Apr 11 09:46:18 vdr vdr[718]: [874] ERROR: driver buffer overflow on device 1 Apr 11 09:57:20 vdr vdr[718]: [892] ERROR: 1 TS packet(s) not accepted in Transfer Mode Apr 11 10:11:29 vdr vdr[718]: [914] ERROR: 6 TS packet(s) not accepted in

[vdr] Video-Audio disruptions with 4.16+ kernel

Apologies in advance for a somewhat long-winded post. I am using an Asrock Celeron based N3150M board with a TT S2 6400 card and a Digital Devices Cine S2 V7A card and 64bit kernels. The frontends on the TT card are unused in favour of the DD card - the TT card is just used for output. vdr is

Re: [vdr] Looking for DVB API documentation

Thanks for your reply, Klaus! On Mo, Apr 09, 2018 at 04:51:25 +0200, Klaus Schmidinger wrote: > On 09.04.2018 09:52, Josef Wolf wrote: > >Hello everybody, > > > >I am looking for the DVB API documentation. I know there is > > > > https://www.linuxtv.org/wiki/ > > > >and > > > >

Re: [vdr] Looking for DVB API documentation

On 09.04.2018 09:52, Josef Wolf wrote: Hello everybody, I am looking for the DVB API documentation. I know there is https://www.linuxtv.org/wiki/ and https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/dvb/dvbapi.html but the wiki states, the current API is v5. And there don't

[vdr] VDR 2.3.9: a few last minute fixes and last call for translations!

VDR version 2.3.9 is about to be released as stable 2.4.0 on April 15! The archive can be found here: ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9.tar.bz2 (this is still the same as in my announcement dated March 18). I have posted a few last minute fixes at

[vdr] Looking for DVB API documentation

Hello everybody, I am looking for the DVB API documentation. I know there is https://www.linuxtv.org/wiki/ and https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/dvb/dvbapi.html but the wiki states, the current API is v5. And there don't seem to exist any information about API v5.

[vdr] IEEE ISMAR 2018 - Call for Tutorials

*ISMAR 2018 - CALL FOR TUTORIALS* The ISMAR 2018 organizing committee invites proposals for tutorials associated with the ISMAR 2018 conference. The tutorials will be held on 16th and 20th October 2018, in Munich, Germany. The purpose of the tutorials is to expand the knowledge in the fields of

[vdr] IEEE ISMAR 2018 - Call for Workshops

*ISMAR 2018 - CALL FOR WORKSHOPS* The ISMAR 2018 organizing committee invites proposals for workshops to be held in the ISMAR 2018 main conference. The workshops will be held on 16th and 20th October 2018, in Munich, Germany. The purpose of the workshops is to provide participants with the

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Montag, den 02.04.2018, 18:40 +0200 schrieb Klaus Schmidinger: > On 02.04.2018 14:20, Oliver Endriss wrote: > > Am Montag, den 02.04.2018, 12:28 +0200 schrieb Klaus Schmidinger: > >> On 01.04.2018 19:01, Oliver Endriss wrote: > >> > ... > >> >> >> >> Does it make a difference whether the

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 02.04.2018 14:22, Torgeir Veimo wrote: Do you have any plans for more integrated means of running a client server setup like the streamdev setup? I like the raspberry pi since it's low power, and does hdmi-cec, but without sata I'm concerned with disk bandwidth with multiple recordings.

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 02.04.2018 14:20, Oliver Endriss wrote: Am Montag, den 02.04.2018, 12:28 +0200 schrieb Klaus Schmidinger: On 01.04.2018 19:01, Oliver Endriss wrote: > ... >> >> >> Does it make a difference whether the progress display is active or not >> >> >> when you set the mark? >> > >> > If the

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Do you have any plans for more integrated means of running a client server setup like the streamdev setup? I like the raspberry pi since it's low power, and does hdmi-cec, but without sata I'm concerned with disk bandwidth with multiple recordings. On 2 April 2018 at 21:27, Klaus Schmidinger

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Montag, den 02.04.2018, 12:28 +0200 schrieb Klaus Schmidinger: > On 01.04.2018 19:01, Oliver Endriss wrote: > > ... > >> >> >> Does it make a difference whether the progress display is active or > >> >> >> not > >> >> >> when you set the mark? > >> > > >> > If the progress bar is off, and you

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 02.04.2018 12:35, Torgeir Veimo wrote: Am Samstag, den 24.03.2018, 15:05 +0100 schrieb Klaus Schmidinger: At the time this was done, I was still using the TT S2-6400 as output device. Jut curious, what are you using now? A raspberry pi? Currently a Raspberry Pi, but I'm planning to use

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Samstag, den 24.03.2018, 15:05 +0100 schrieb Klaus Schmidinger: > At the time this was done, I was still using the TT S2-6400 as output device. Jut curious, what are you using now? A raspberry pi? -- -Tor ___ vdr mailing list vdr@linuxtv.org

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 01.04.2018 19:01, Oliver Endriss wrote: ... >> >> Does it make a difference whether the progress display is active or not >> >> when you set the mark? > > If the progress bar is off, and you set a mark, progress bar and > mark show up immediately. -> No problem. ... > Could it be that

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Samstag, den 24.03.2018, 15:05 +0100 schrieb Klaus Schmidinger: > On 19.03.2018 18:01, Oliver Endriss wrote: > > Am Montag, den 19.03.2018, 14:45 +0100 schrieb Klaus Schmidinger: > >> On 19.03.2018 01:33, Oliver Endriss wrote: > >> > Am Sonntag, den 18.03.2018, 23:29 +0100 schrieb Klaus

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 19.03.2018 18:01, Oliver Endriss wrote: Am Montag, den 19.03.2018, 14:45 +0100 schrieb Klaus Schmidinger: On 19.03.2018 01:33, Oliver Endriss wrote: > Am Sonntag, den 18.03.2018, 23:29 +0100 schrieb Klaus Schmidinger: >> On 18.03.2018 20:39, Oliver Endriss wrote: >> > Am Sonntag, den

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Montag, den 19.03.2018, 14:45 +0100 schrieb Klaus Schmidinger: > On 19.03.2018 01:33, Oliver Endriss wrote: > > Am Sonntag, den 18.03.2018, 23:29 +0100 schrieb Klaus Schmidinger: > >> On 18.03.2018 20:39, Oliver Endriss wrote: > >> > Am Sonntag, den 18.03.2018, 19:15 +0100 schrieb Klaus

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 19.03.2018 01:33, Oliver Endriss wrote: Am Sonntag, den 18.03.2018, 23:29 +0100 schrieb Klaus Schmidinger: On 18.03.2018 20:39, Oliver Endriss wrote: > Am Sonntag, den 18.03.2018, 19:15 +0100 schrieb Klaus Schmidinger: >> On 18.03.2018 18:55, Oliver Endriss wrote: >> > Hi, >> > >> > just

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

Am Sonntag, den 18.03.2018, 23:29 +0100 schrieb Klaus Schmidinger: > On 18.03.2018 20:39, Oliver Endriss wrote: > > Am Sonntag, den 18.03.2018, 19:15 +0100 schrieb Klaus Schmidinger: > >> On 18.03.2018 18:55, Oliver Endriss wrote: > >> > Hi, > >> > > >> > just installed vdr 2.3.9 and noticed that

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 18.03.2018 20:39, Oliver Endriss wrote: Am Sonntag, den 18.03.2018, 19:15 +0100 schrieb Klaus Schmidinger: On 18.03.2018 18:55, Oliver Endriss wrote: > Hi, > > just installed vdr 2.3.9 and noticed that there is a delay > when I try to set a recording mark, compared with vdr 2.2.0. > >

Re: [vdr] [ANNOUNCE] VDR developer version 2.3.9

Hi Klaus, My contribution to the translation of VDR. Regards, Yarema 2018-03-18 14:54 GMT+01:00 Klaus Schmidinger : > VDR developer version 2.3.9 is now available at > > ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9.tar.bz2 > > A 'diff' against the previous version

Re: [vdr] [vdr 2.3.9] Setting a mark is sluggish

On 18.03.2018 18:55, Oliver Endriss wrote: Hi, just installed vdr 2.3.9 and noticed that there is a delay when I try to set a recording mark, compared with vdr 2.2.0. Steps to reproduce: - Play a recording. - Press ok to display the progress bar. - Press 0 to set a mark. There is a notable

[vdr] [vdr 2.3.9] Setting a mark is sluggish

Hi, just installed vdr 2.3.9 and noticed that there is a delay when I try to set a recording mark, compared with vdr 2.2.0. Steps to reproduce: - Play a recording. - Press ok to display the progress bar. - Press 0 to set a mark. There is a notable delay between the keypress and the mark showing

Re: [vdr] [ANNOUNCE] VDR developer version 2.3.9

On 18.03.2018 17:59, Wolfgang Rohdewald wrote: On So, 2018-03-18 at 14:54 +0100, Klaus Schmidinger wrote: - Disabled the use of posix_fadvise() when reading (i.e. replaying), since it caused stuttering replay in fast forward and fast rewind mode in case the video directory is mounted

Re: [vdr] [ANNOUNCE] VDR developer version 2.3.9

On So, 2018-03-18 at 14:54 +0100, Klaus Schmidinger wrote: > - Disabled the use of posix_fadvise() when reading (i.e. replaying), since it > caused >stuttering replay in fast forward and fast rewind mode in case the video > directory >is mounted via NFS. You can re-enable it by setting

[vdr] [ANNOUNCE] VDR developer version 2.3.9

VDR developer version 2.3.9 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.8-2.3.9.diff MD5 checksums: 9e4202b046df9ea960d930ce99e967ab vdr-2.3.9.tar.bz2

[vdr] How to open the Hauppauge curved remote for cleaning??

I know it can be done, I've done it before. I've cleaned lots of other remotes. But there is some trick to getting one of these open and I can't figure it out. The "OK" butting needs cleaning. ___ vdr mailing list vdr@linuxtv.org

Re: [vdr] Channels getting deleted on new scan

Definitely true! We have an obsession with trying to be `different` or non-standard. For some reason people and companies don't feel "special" enough otherwise. On Sun, Mar 11, 2018 at 2:31 PM, Timothy D. Lenz wrote: > Standards??? what's that? Only thing around here that is

Re: [vdr] Channels getting deleted on new scan

Standards??? what's that? Only thing around here that is standard is to be proprietary On 3/11/2018 2:19 PM, Klaus Schmidinger wrote: On 11.03.2018 22:10, Timothy D. Lenz wrote: It turns out that both stations are owned by the same company. I have sent KGUN9 a second email about the conflict

Re: [vdr] Channels getting deleted on new scan

On 11.03.2018 22:10, Timothy D. Lenz wrote: It turns out that both stations are owned by the same company. I have sent KGUN9 a second email about the conflict and reported it to the FCC as interference because they interfering with each other. Looking at this site:

Re: [vdr] Channels getting deleted on new scan

It turns out that both stations are owned by the same company. I have sent KGUN9 a second email about the conflict and reported it to the FCC as interference because they interfering with each other. Looking at this site: https://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf I

Re: [vdr] Channels getting deleted on new scan

On 10.03.2018 01:21, Torgeir Veimo wrote: Isn't there a plugin that can change such data before it gets processed? The problem is that these are *duplicate* channels - they can't be in the channel list to begin with. They need to have different Transport Stream Ids. And as wen can see from

Re: [vdr] Channels getting deleted on new scan

Isn't there a plugin that can change such data before it gets processed? On 10 March 2018 at 08:47, Timothy D. Lenz wrote: > Wel, it gets better. Tonight I see VDR is grabbing guide data for 9x > and using it for 58.x. So 58.x data is now being lost. g > > > On

Re: [vdr] Channels getting deleted on new scan

Wel, it gets better. Tonight I see VDR is grabbing guide data for 9x and using it for 58.x. So 58.x data is now being lost. g On 3/9/2018 2:29 AM, Klaus Schmidinger wrote: On 08.03.2018 22:38, Klaus Schmidinger wrote: On 08.03.2018 22:13, Timothy D. Lenz wrote: I was hoping it was

Re: [vdr] Channels getting deleted on new scan

I sent an email to KGUN and if they don't fix the conflict right away, I guess I'll have to make a complaint to the FCC, not that it will do much good. On 3/9/2018 2:29 AM, Klaus Schmidinger wrote: On 08.03.2018 22:38, Klaus Schmidinger wrote: On 08.03.2018 22:13, Timothy D. Lenz wrote: I

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 09.03.2018 12:01, Patrick Boettcher wrote: On Fri, 9 Mar 2018 11:55:02 +0100 Klaus Schmidinger wrote: On 09.03.2018 11:51, Patrick Boettcher wrote: > On Fri, 9 Mar 2018 11:30:36 +0100 > Klaus Schmidinger wrote: > >> On 01.03.2018

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Fri, 9 Mar 2018 11:55:02 +0100 Klaus Schmidinger wrote: > On 09.03.2018 11:51, Patrick Boettcher wrote: > > On Fri, 9 Mar 2018 11:30:36 +0100 > > Klaus Schmidinger wrote: > > > >> On 01.03.2018 10:22, Patrick Boettcher wrote: > >> >

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 09.03.2018 11:55, Klaus Schmidinger wrote: On 09.03.2018 11:51, Patrick Boettcher wrote: On Fri, 9 Mar 2018 11:30:36 +0100 Klaus Schmidinger wrote: On 01.03.2018 10:22, Patrick Boettcher wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 09.03.2018 11:51, Patrick Boettcher wrote: On Fri, 9 Mar 2018 11:30:36 +0100 Klaus Schmidinger wrote: On 01.03.2018 10:22, Patrick Boettcher wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger wrote: > >> On 27.02.2018

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Fri, 9 Mar 2018 11:30:36 +0100 Klaus Schmidinger wrote: > On 01.03.2018 10:22, Patrick Boettcher wrote: > > On Wed, 28 Feb 2018 11:01:23 +0100 > > Klaus Schmidinger wrote: > > > >> On 27.02.2018 17:58, Patrick Boettcher wrote: > >> >

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 01.03.2018 10:22, Patrick Boettcher wrote: On Wed, 28 Feb 2018 11:01:23 +0100 Klaus Schmidinger wrote: On 27.02.2018 17:58, Patrick Boettcher wrote: > On Tue, 27 Feb 2018 16:54:35 +0100 > Klaus Schmidinger wrote: > >> Hello Patrick,

Re: [vdr] Channels getting deleted on new scan

On 08.03.2018 22:38, Klaus Schmidinger wrote: On 08.03.2018 22:13, Timothy D. Lenz wrote: I was hoping it was something simple I could fix in the conf. I haven't worked on it or in linux in a long time and don't have the free time to figure it all out again. I'll have to look at this some other

Re: [vdr] Channels getting deleted on new scan

On 08.03.2018 22:13, Timothy D. Lenz wrote: I was hoping it was something simple I could fix in the conf. I haven't worked on it or in linux in a long time and don't have the free time to figure it all out again. I'll have to look at this some other time. I am in the U.S. and these are ATA

Re: [vdr] Channels getting deleted on new scan

I was hoping it was something simple I could fix in the conf. I haven't worked on it or in linux in a long time and don't have the free time to figure it all out again. I'll have to look at this some other time. I am in the U.S. and these are ATA channels. They each have their own freq. and my

Re: [vdr] Channels getting deleted on new scan

On 08.03.2018 03:36, Timothy D. Lenz wrote: Haven't used the list in awhile I I think my first reply went to the wrong address. So redoing plus adding some info. 91 is 9.1 KGUN which is the local for ABC Broadcast Network A National Network. The other 9.x channels are assorted small stations.

Re: [vdr] Channels getting deleted on new scan

Haven't used the list in awhile I I think my first reply went to the wrong address. So redoing plus adding some info. 91 is 9.1 KGUN which is the local for ABC Broadcast Network A National Network. The other 9.x channels are assorted small stations. 581 or 58.1 is CW, Another big network.

Re: [vdr] Channels getting deleted on new scan

On 07.03.2018 00:04, Timothy D. Lenz wrote: So I'm using an old version of VDR, looks like 1.7.15 with the ATSC plugin. Just don't have the time to update everything. I noticed that the 9x locals stopped getting guide data. I did a new scan and the new list worked for 9x but would wipe 58x

[vdr] Channels getting deleted on new scan

So I'm using an old version of VDR, looks like 1.7.15 with the ATSC plugin. Just don't have the time to update everything. I noticed that the 9x locals stopped getting guide data. I did a new scan and the new list worked for 9x but would wipe 58x channels. comparing them, they changed the next to

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 01.03.2018 11:39, Patrick Boettcher wrote: On Thu, 1 Mar 2018 10:22:10 +0100 Patrick Boettcher wrote: On Wed, 28 Feb 2018 11:01:23 +0100 Klaus Schmidinger wrote: > On 27.02.2018 17:58, Patrick Boettcher wrote: > > On Tue, 27 Feb

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Thu, 1 Mar 2018 10:22:10 +0100 Patrick Boettcher wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger wrote: > > > On 27.02.2018 17:58, Patrick Boettcher wrote: > > > On Tue, 27 Feb 2018 16:54:35 +0100 > > > Klaus

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On 01.03.2018 10:22, Patrick Boettcher wrote: On Wed, 28 Feb 2018 11:01:23 +0100 Klaus Schmidinger wrote: On 27.02.2018 17:58, Patrick Boettcher wrote: > On Tue, 27 Feb 2018 16:54:35 +0100 > Klaus Schmidinger wrote: > >> Hello Patrick,

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Thu, 1 Mar 2018 10:22:10 +0100 Patrick Boettcher wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger wrote: > > > On 27.02.2018 17:58, Patrick Boettcher wrote: > > > On Tue, 27 Feb 2018 16:54:35 +0100 > > > Klaus

<    1   2   3   4   5   6   7   8   9   10   >