vdr

vdr@linuxtv.org

2 participants
6731 discussions

[PLUGIN] recsearch - a simple search for recordings
by Lars Hanisch 22 Jan '14

22 Jan '14

Hi, For all, who wonder, where this change for vdr 2.1.3 comes from: > - The Recordings menu can now be called with a cRecordingFilter, which allows the > caller to have it display only a certain subset of the recordings here's the plugin, which uses it: recsearch https://github.com/flensrocker/vdr-plugin-recsearch It's a simple search for name, shorttext and description, the status (new/edited) and age of a recording. The main reason for me was to get a quick list of the new recordings of the last week. You can save various templates, organize them in categories and add a hotkey to them, so you can use something like User1 @recsearch 1 in your keymacros.conf to quickly execute a search. For vdr versions older than 2.1.3 there's a clone of the recordings menu of vdr 2.0.4 included, so you can use it for the current stable release. Comments are welcome. Lars.

4 6

Plugin request: speech recognition
by Marco Göbenich 22 Jan '14

22 Jan '14

Hi! I'm searching a speech recognition solution for vdr. I'm thinking of a plugin that transcribes streams while they are recorded, maybe into a file, or in something like DVB Subtitles, EPG. I need the timecodes and maybe something to set marks if text matches a list of keywords. Has anybody knowlegde on this topic and is able to write a plugin for vdr 1.6 (mandatory) and up. This is for a customer project and would be paid. Regards Marco -- Professional IT E-Commerce, Programmierung, Datenmigration, IT-Service Needful Marco Göbenich e.K. Auf der Haide 31a 56203 Höhr-Grenzhausen Fon +49 (0) 2624 / 95 29 300 Fax +49 (0) 2624 / 95 29 303 mg(a)needful.de http://www.needful.de HRA: 21295 AG Montabaur EG-Identn.: DE 280643122

1 0

vdr-fritzbox no longer working after FBF firmware upgrade
by Harald Milz 21 Jan '14

21 Jan '14

Hi all, I've been happily using vdr-fritzbox for a very long time. Since the last upgrade to Fritz!OS 5.50 and then to 5.53 (54.05.50 respectively 54.05.53) the plugin cannot connect to the FBF any more. The log: Jan 21 10:10:58 seneca vdr: [2393] [libfritz++/FritzClient.cpp:210] logging into fritz box using old scheme without SIDs. Jan 21 10:10:59 seneca vdr: [2393] [libfritz++/FritzClient.cpp:228] login successful. Jan 21 10:10:59 seneca vdr: [2393] [libfritz++/FritzClient.cpp:317] sending callList request. Jan 21 10:11:01 seneca vdr: [2393] [libfritz++/FritzClient.cpp:342] Exception in connection to 192.168.20.253 - Could not connect Jan 21 10:11:01 seneca vdr: [2393] [libfritz++/FritzClient.cpp:342] waiting 3600 seconds before retrying VDR and plugin are the standard versions in Ubuntu 12.04 LTS: ii vdr 1.7.22-1 ii vdr-plugin-fritzbox 1.4.1-4 didn't have an opportunity to check out later versions yet. Should that be fixed by now? THX! -- Do not overtax your powers.

2 1

popcorn hour A110 / HDX 1000 as vdr client?
by cedric.dewijs＠telfort.nl 18 Jan '14

18 Jan '14

Hi All, My headless VDR server is starting to be usable. Therefore I'm looking for a low-power client. I have been given an HDX 1000 (cross-flashed with the popcorn hour A110 firmware) I came across this german page, it looks like the A110 can be used as VDR client. http://www.popcornforum.de/showthread.php?tid=5201&pid=176551#pid176551 Does anybody has experience with this ? Is there other / better ways to use the popcorn hour A110 as a vdr client? Kind regards, Cedric

1 1

Epsilon Rikomagic MK802 IV mini PC: can it play movies in vdr / linux?
by cedric.dewijs＠telfort.nl 18 Jan '14

18 Jan '14

Hi All, I'm planning to buy an Epsilon Rikomagic MK802 IV to use as a VDR server / frontend. It's based on a Rockchip RK3188 (Quad core cortex A9(a)1.8GHz, quad core mali 400@533MHz) I wonder if this device can play full HD movies in linux. Does it uses the CPU for this, or does it use the mali cores, keeping the CPU free for other things? Best regards, Cedric

1 0

Re: [vdr] VDR test series about frame detector
by cedric.dewijs＠telfort.nl 15 Jan '14

15 Jan '14

>Then you compile the attached C++ file (unziped, of course): >> g++ -c framedetectortest.cpp > >Then you're linking it: >g++ -o framedetectortest framedetectortest.o remux.o ringbuffer.o thread.o tools.o i18n.o sections.o channels.o device.o audio.o ci.o receiver.o transfer.o player.o osdbase.o >status.o skins.o osd.o config.o font.o sources.o menu.o recording.o videodir.o timers.o epg.o dvbplayer.o menuitems.o remote.o keys.o interface.o plugin.o cutter.o themes.o >svdrp.o eit.o eitscan.o shutdown.o filter.o sourceparams.o dvbsubtitle.o pat.o sdt.o nit.o dvbdevice.o diseqc.o recorder.o dvbci.o libsi/libsi.a -lfontconfig -lfreetype -lpthread -ldl - >ljpeg > >Now you've got an application called framedetectortest, which you can feed your vdr recordings (*.ts files) to: >> ./framedetectortest 00002.ts > >The output looks about like this: > >Checking file at offset 0 >Without frame limit... Found I frame after 99452 bytes >With frame limit 5... Found I frame after 220336 bytes >With frame limit 6... Found I frame after 99452 bytes >TS package frame size needed for this video block: 6 >Maximum TS package frame size needed for this video recording: 6 > >I need reports which number your stream resulted in (the "Maximum TS package frame size") and what you've tested >(Cable? Satellite? Terrestrical? HD, SD? Your country?). The result is interesting even if it is 5 or 6. > >Thanks in advance, >Eike Hi Eike, In vdr 2.0.4 I have to add -lrt to the link command: $ g++ -c framedetectortest.cpp $ g++ -o framedetectortest framedetectortest.o remux.o ringbuffer.o thread.o tools.o i18n.o sections.o channels.o device.o audio.o ci.o receiver.o transfer.o player.o osdbase.o status.o skins.o osd.o config.o font.o sources.o menu.o recording.o videodir.o timers.o epg.o dvbplayer.o menuitems.o remote.o keys.o interface.o plugin.o cutter.o themes.o svdrp.o eit.o eitscan.o shutdown.o filter.o sourceparams.o dvbsubtitle.o pat.o sdt.o nit.o dvbdevice.o diseqc.o recorder.o dvbci.o libsi/libsi.a -lfontconfig -lfreetype -lpthread -ldl -ljpeg tools.o: In function `cTimeMs::Now()': /storage/home/ingeborg/Downloads/vdr-2.0.4/tools.c:674: undefined reference to `clock_gettime' /storage/home/ingeborg/Downloads/vdr-2.0.4/tools.c:655: undefined reference to `clock_getres' /storage/home/ingeborg/Downloads/vdr-2.0.4/tools.c:659: undefined reference to `clock_gettime' collect2: error: ld returned 1 exit status $ g++ -o framedetectortest framedetectortest.o remux.o ringbuffer.o thread.o tools.o i18n.o sections.o channels.o device.o audio.o ci.o receiver.o transfer.o player.o osdbase.o status.o skins.o osd.o config.o font.o sources.o menu.o recording.o videodir.o timers.o epg.o dvbplayer.o menuitems.o remote.o keys.o interface.o plugin.o cutter.o themes.o svdrp.o eit.o eitscan.o shutdown.o filter.o sourceparams.o dvbsubtitle.o pat.o sdt.o nit.o dvbdevice.o diseqc.o recorder.o dvbci.o libsi/libsi.a -lfontconfig -lfreetype -lpthread -ldl -ljpeg -lrt I see the following when running the command on recordings from digitenne, Netherlands: $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 165816 bytes With frame limit 5... Found I frame after 165816 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 324864 bytes With frame limit 5... Found I frame after 324864 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 276736 bytes With frame limit 5... Found I frame after 276736 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 141376 bytes With frame limit 5... Found I frame after 141376 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 273916 bytes With frame limit 5... Found I frame after 273916 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 205484 bytes With frame limit 5... Found I frame after 205484 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 $ ./framedetectortest ~/tmp/00001.ts Checking file at offset 0 Without frame limit... Found I frame after 243836 bytes With frame limit 5... Found I frame after 243836 bytes TS package frame size needed for this video block: 5 Maximum TS package frame size needed for this video recording: 5 Kind regards, Cedric

1 0

Frame detector glitch
by Eike 14 Jan '14

14 Jan '14

Hello! I'm experiencing what I'd call a glitch of VDR's frame detector class. There's a define #define MIN_TS_PACKETS_FOR_FRAME_DETECTOR 5. According to my experiences, this number of TS packages in not always enough to detect frames as early as possible. Thus it is a matter of chance if detection will be fed with enough data to detect the first frame or if it will glitch through to another one. I think we should avoid such situations. I attached demo code (needs some includes and to be compiled and linked with VDR) which shows the behaviour and I stored a short TS sample at http://ein-eike.de/wordpress/wp-content/uploads/2014/01/vdr-sample.ts The code checks when an I frame is found, at first with full data available, and then with data dripping in with a frame size of 5, 6 ... until the dripping data yields the same result as the flooding data. I get the following output from the given example: Checking file at offset 0 Without frame limit... Found I frame after 190256 bytes With frame limit 5... Found I frame after 398560 bytes With frame limit 6... Found I frame after 190256 bytes TS package frame size needed for this video block: 6 Maximum TS package frame size needed for this video recording: 6 Unfortunately, I cannot tell if 6 is the definite number to avoid such glitches or if other circumstances would need a higher number. I wrote the code such as people might try it out on their video files so we could experiment. (I could provide a Linux executable as well.) Ciao, Eike

3 3

vdr-xine and vdr-2.1.3
by Joerg Riechardt 11 Jan '14

11 Jan '14

Hi, Reinhard Nissl’s vdr-xine is still my favorite output plugin. The additional parameter in cDevice::TrickSpeed() breaks fast forward, instead of increasing the speed in three steps, it is always most fast. Has anybody a patch for this, or is planning to create one? Joerg

2 2

Best IDE for VDR development?
by cedric.dewijs＠telfort.nl 08 Jan '14

08 Jan '14

Hi All, What is the best IDE to use for VDR development under linux? Up to now I have used nano, but then I can only view one file at a time, and there's no source code analysis. Kind regards, Cedric

2 1

[ANNOUNCE] VDR version 2.0.5 released
by Klaus Schmidinger 07 Jan '14

07 Jan '14

VDR version 2.0.5 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.0.5.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.0.4-2.0.5.diff MD5 checksums: f58b9836a60440fde84480a2e37ee91d vdr-2.0.5.tar.bz2 3a1788b3c178eda372dd25071c06e763 vdr-2.0.4-2.0.5.diff This version fixes a few minor bugs that came up after the release of version 2.0.4. The changes since version 2.0.4: - The LIRC remote control now connects to the socket even if it doesn't yet exist when VDR is started (thanks to Lars Hanisch). - Fixed a missing initialization in the c'tor of cSkinLCARSDisplayChannel (thanks to Marko Mäkelä). - Fixed uninitialized item area coordinates in cSkinLCARSDisplayMenu (reported by Marko Mäkelä). - Fixed a possible crash if the recordings list is updated externally while the Recordings menu is open (reported by Lars Hanisch). - Added a missing closing ')' in the help and man page entry of the --vfat option (reported by Lars Hanisch). - Fixed setting the name of the video directory to avoid a crash when using --genindex, and also to use the correct directory with --edit (the latter reported by Marko Mäkelä). Have fun! Klaus

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr