[vdr] Converting HD recording
Good evening all, I've got a bunch of old recordings made with VDR, like a 20 GB HD recording. I'd like to slim it down a bit, but don't really know where to start. How do you convert a show recorded on BBC HD to a more compact file? -- /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.1
Multiproto_plus is quite outdated, Manu (the maintainer) has done a bunch of updates on the original multiproto tree (http://jusst.de/hg/multiproto) He even added support for the old API (yay) and merged the latest V4L tree with it. Basically, it compiles and it just works with everything :) /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg Klaus Schmidinger schreef: VDR developer version 1.7.1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.1.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.0-1.7.1.diff WARNING: This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. This version marks the first step towards using TS (Transport Stream) as recording format. It does this by switching the Transfer Mode to TS and introducing all the necessary cDevice and cPlayer functions to handle TS. Actual recording is still done in PES, though. This should provide a reasonable developing and testing environment for HDTV device plugins to prepare for replaying TS. There appears to be a problem with replaying the payload from TS packets on Full-Featured DVB cards. On some channels this works rather fine (with only very small glitches from time to time), while on other channels there are heavy glitches and sometimes even the audio goes mute. My initial approach to replaying TS on FF cards was to simply strip the TS header and send the payload to the usual PlayVideo() and PlayAudio() functions, since the driver itself examines the data and assembles the 2KB PES packets it sends to the hardware. Since the FF cards can replay the TS data as it comes in from the transponder, my assumption was that the same should be possible in Transfer Mode. But maybe there is something wrong with this assumption? Could this be a driver problem? I don't think that simply throwing memory at the problem is the solution. Any thoughts? The changes since version 1.7.0: - Adapted the tuning code to the new DVBFE_SET_DELSYS API (thanks to Reinhard Nissl). VDR now uses the driver from http://jusst.de/hg/multiproto_plus. - Updated the Italian OSD texts (thanks to Diego Pierotto). - Removed obsolete $(NCURSESLIB) from the Makefile. - Implemented handling the standard component descriptor for AC3 (stream=4), as it will soon be used by the German ARD channels (thanks to Michael Pennewiß for advance information about this change). The previously used Premiere pseudo standard (stream=2, type=5) still works, but has apparently been wrongfully used by broadcasters from the beginning. - Added missing description of the 'S' channel parameter to vdr.5 (reported by Reinhard Nissl). - The SVDRP signon message now indicates the character encoding in use, as in 220 video SVDRP VideoDiskRecorder 1.7.1; Fri May 2 16:17:10 2008; ISO-8859-1. This may be useful for instance for external tools that provide EPG data, so that they can correctly encode the strings. - No longer calling FcFini() to avoid problems with older (broken) versions of fontconfig (suggested by Edgar Toernig). - Removed the compile time option VFAT to allow users of precompiled binary distributions to have full control over whether or not to use the --vfat option at runtime (suggested by Michael Nork). - First step towards switching to TS (Transport Stream) as recording format: + The new function cDevice::PlayTs() is used to play TS packets. + The new functions cDevice::PlayTsVideo() and cDevice::PlayTsAudio() are used to play video and audio TS packets, respectively. + The new function cAudio::PlayTs() is used to play audio TS packets. + The new class cPatPmtGenerator is used to generate a PAT/PMT pair that precedes the TS data in Transfer Mode. + The new class cPatPmtParser is used by cDevice to parse the PAT/PMT data in a TS in order to find out which streams it contains. + The new class cTsToPes is used to convert TS packets to a PES packet. + cTransfer no longer uses cRemux, and doesn't run a separate thread any more. It just generates a PAT/PMT and sends all received TS packets to the primary device's PlayTs(). + Live subtitle display no longer uses a ring buffer and separate thread. + cPesAssembler has been removed. Old VDR recordings only contain complete PES packets. + Since a TS needs to have a PAT/PMT, which requires the video stream type to be explicitly given, the format of the VPID field in the channels.conf file and the SVDRP commands NEWC/MODC/LSTC has been extended. The video stream type now follows the VPID and optional PPID, separated by an '=' sign. - Updated the sources.conf file (thanks to Oleg Roitburd). - Fixed a possible integer overflow in GetAbsTime() (thanks to Alexander Rieger). - Fixed
Re: [vdr] VDR Development
That's really the one thing that keeps me from using VDR: no multiple frontends. And I've tried the stream-thing plugin. I actually really like VDR's interface. I believe the people I'm creating this for, my parents, would be better of with it, too. /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg [EMAIL PROTECTED] schreef: VDR User [EMAIL PROTECTED] writes: I will however give you an example. There was a time when the majority of dvb users I talk to used VDR, and only a few guys used MythTV. Now the opposite is true. The majority of those people are using MythTV and few are left who still use VDR. Why? Primarily lack of support for what's already been previously discussed a million times.. Lack of support for HDTV, MPEG4, DVB-S2, and a recording format that is actually usable. The only surprise to me is how many people burn their recordings to DVD. I don't have any interest in doing that but clearly a whole lot of other people do. i'm not into dvb-s2 yet. Without talking about this hype technology, what about : - multiple frontend+osd support - complex channel handling (no no not talking about xml, i hate xml) - sourcecap patch (having to patch vdr for such a feature is a no-go for a lot of people) I tend to agree, in the end a lot of people will move to bloat^Wmythtv. (and i agree, a lot of people have stopped using vdr) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new dvb api ?
I was wondering what the people on the VDR ml thought about this. Now that multiproto is finally complete, and VDR has excellent support for it, some people want to create a completely new API. They say this is so that future modulations could be better supported, but multiproto can offer that support, too, with not much effort and without breaking compatibility. Overall, the call for this new API seems like something personal between the developers, but I'm on slippery ice here. It seems stupid that the users would have to pay for some fight by having to wait another few months for this new API to get completed. /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg Goga777 schreef: http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Multiproto runvdr script
Hi everyone, I would love to use a runvdr script made for the multiproto drivers, does anyone here have any examples I could base it on? It seems like there are lots of variables to take into account. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR server clients?
Hi everyone, I've seen lots of tutorials about VDR but one thing still isn't clear: can it or can it not have multiple clients watching different programs? I know it's impossible with xine-plugin to even have multiple streams, but xineliboutput seems to be able to output multiple streams over a network. The reason I'm asking this is because I've never actually had it work ... I'm always getting a permission denied message, along with it stating that the host's ip needs to be in my svdrp.conf file, which doesn't exist. My svdrphosts.conf file, on the other hand, is perfectly in order, but still it won't work. If it is possible I can finally toss mythtv out of the window and deploy vdr over the house! -- /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR-xine + ffmpeg? (h.264 problems)
Reinhard Nissl schreef: Try to cheat decoding in ~/.xine/config: video.processing.ffmpeg_choose_speed_over_accuracy:1 video.processing.ffmpeg_pp_quality:0 video.processing.ffmpeg_skip_loop_filter:all video.processing.ffmpeg_thread_count:2 Interesting, it gave it a bit of a boost, although not a lot. Video isn't as choppy as it used to be (actually, the video is now just as good as on Windows without coreavc, which is still choppy) but the audio is missing mostly... I think I'll have to give the other's suggestion, the coreavc thing, a go, which isn't going without problems, too: I'm trying to apply Xine-lib's dshowserver patch ( http://code.google.com/p/coreavc-for-linux/wiki/XineInstall ) But apparantly in the last week or so a lot of stuff changed so the patch is useless. I tried getting a specific revision but it says *the repository doesn't support revision lookup* so I'm stuck. # patch -p1 /tmp/coreavc-for-linux/xine/dshowserver.patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |diff -r 66e1654718fb src/libxinevdec/Makefile.am |--- a/src/libxinevdec/Makefile.amMon Apr 14 22:38:03 2008 +0200 |+++ b/src/libxinevdec/Makefile.amSat May 17 09:08:43 2008 -0700 -- File to patch: Dshowerver is running as it should, but there is no libxinecdec folder in /tmp/xine-lib-cvs-13-04-2008/src (Instead it moved to some map in .hg/data and all) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Xine-lib error
Hey all, Because I've been trying to get h.264 to work today, I tried to make ffmpeg myself, and now I'm unable to compile xine-lib! I completely removed my ffmpeg installation and all, it still won't work. The problem must be with libpostproc or something, but I have those files: # ./autogen.sh --with-external-ffmpeg --disable-dxr3 make make install ldconfig ... ipts -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wpointer-arith -g -MT xineplug_post_planar_la-pp.lo -MD -MP -MF .deps/xineplug_post_planar_la-pp.Tpo -c pp.c -fPIC -DPIC -o .libs/xineplug_post_planar_la-pp.o pp.c:35:27: error: postprocess.h: No such file or directory pp.c:61: error: ‘PP_QUALITY_MAX’ undeclared here (not in a function) pp.c:81: error: expected specifier-qualifier-list before ‘pp_context_t’ pp.c: In function ‘set_parameters’: pp.c:92: error: ‘post_plugin_pp_t’ has no member named ‘lock’ pp.c:92: warning: passing argument 1 of ‘pthread_mutex_lock’ from incompatible pointer type pp.c:96: error: ‘post_plugin_pp_t’ has no member named ‘lock’ pp.c:96: warning: passing argument 1 of ‘pthread_mutex_unlock’ from incompatible pointer type pp.c: In function ‘get_help’: pp.c:124: error: ‘pp_help’ undeclared (first use in this function) pp.c:124: error: (Each undeclared identifier is reported only once pp.c:124: error: for each function it appears in.) pp.c:127: warning: format ‘%s’ expects type ‘char *’, but argument 4 has type ‘struct xine_post_api_parameter_t *’ pp.c: In function ‘pp_init_plugin’: pp.c:157: warning: ‘xine_xmalloc’ is deprecated (declared at ../../../include/xine/xineutils.h:606) pp.c: In function ‘pp_open_plugin’: pp.c:194: error: ‘PP_FORMAT_420’ undeclared (first use in this function) pp.c:194: warning: assignment makes integer from pointer without a cast pp.c:196: error: ‘PP_CPU_CAPS_MMX’ undeclared (first use in this function) pp.c:196: error: invalid operands to binary | pp.c:196: warning: statement with no effect pp.c:198: error: ‘PP_CPU_CAPS_MMX2’ undeclared (first use in this function) pp.c:198: error: invalid operands to binary | pp.c:198: warning: statement with no effect pp.c:200: error: ‘PP_CPU_CAPS_3DNOW’ undeclared (first use in this function) pp.c:200: error: invalid operands to binary | pp.c:200: warning: statement with no effect pp.c:202: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:202: warning: statement with no effect pp.c:203: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:203: warning: statement with no effect pp.c:205: error: ‘post_plugin_pp_t’ has no member named ‘lock’ pp.c:205: warning: passing argument 1 of ‘pthread_mutex_init’ from incompatible pointer type pp.c: In function ‘pp_dispose’: pp.c:232: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:233: error: implicit declaration of function ‘pp_free_mode’ pp.c:233: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:234: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:234: warning: statement with no effect pp.c:236: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:237: error: implicit declaration of function ‘pp_free_context’ pp.c:237: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:238: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:238: warning: statement with no effect pp.c: In function ‘pp_draw’: pp.c:286: error: ‘post_plugin_pp_t’ has no member named ‘lock’ pp.c:286: warning: passing argument 1 of ‘pthread_mutex_lock’ from incompatible pointer type pp.c:288: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:296: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:297: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:299: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:299: error: implicit declaration of function ‘pp_get_context’ pp.c:299: warning: statement with no effect pp.c:301: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:302: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:303: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:303: warning: statement with no effect pp.c:307: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:308: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:308: error: implicit declaration of function ‘pp_get_mode_by_name_and_quality’ pp.c:309: warning: statement with no effect pp.c:311: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:312: error: implicit declaration of function ‘pp_postprocess’ pp.c:316: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ pp.c:316: error: ‘post_plugin_pp_t’ has no member named ‘pp_context’ pp.c:319: error: ‘post_plugin_pp_t’ has no member named ‘lock’ pp.c:319: warning: passing argument 1 of ‘pthread_mutex_unlock’ from incompatible pointer type pp.c:321: error: ‘post_plugin_pp_t’ has no member named ‘pp_mode’ make[3]: *** [xineplug_post_planar_la-pp.lo] Error 1 make[3]: Leaving directory
Re: [vdr] Xine-lib error
Goga777 schreef: you should install this kernel headers - postprocess.h p.c:35:27: error: postprocess.h: No such file or directory in the debian you can find this package http://packages.debian.org/etch/libpostproc-dev That's just it, I have my kernel's header file, I have libpostproc-dev, I know exactly where postprocess.h is! (/usr/include/postproc/postprocess.h) I even made a symlink in /usr/include/libpostproc/ ... Thing is, this compile worked, untill after I compiled ffmpeg from source. Once I did that xine-lib never wanted to compile again. I guess I'll just reinstall Ubuntu again, because I can't seem to sort it out and I need my sat tonight. I just wish I could figure out WHY it suddenly stopped working! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR-xine + ffmpeg? (h.264 problems)
Hello everyone, I followed a german tutorial on how to install VDR with xine. It had some patches for better h.264 playback, but when I tune to BBC HD, it's still painfully slow, and the image is quite bad, too! I compiled xine with the ffmpeg option (external ffmpeg or something) but I never installed ffmpeg nor are there any instructions on how to do so. I mean, I could compile ffmpeg eventually, I just need to know if I need to apply any more patches or so ... I installed ffmpeg from the repository, but it doesn't seem to have any effect. Thank you for your time, Jelle De Loecker ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Building VDR 1.7.0 - skincurses error?
Udo Richter schreef: Jelle De Loecker wrote: skincurses.c:793: error: ‘WINDOW’ was not declared in this scope skincurses.c:793: error: ‘w’ was not declared in this scope skincurses.c:793: error: ‘initscr’ was not declared in this scope The WINDOW data structure is provided by ncurses library. You may need a different/newer version of libncurses-dev. (imho one of the 'wide character' versions for unicode.) The solution was quite simple: The suse tutorials on the vdr wiki didn't say which dependencies you needed, like the libn5curses (or something like it) Afterwards I had the same problem with some other plugins, but since they were in the repository I could do a apt-get build-dep vdr-plugins-burn and most of the time that would have fixed it. However, sometimes I needed to sift through the error messages and find the correct packages in synaptic. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 - Patched for S2-3200 - Diseqc.conf
Jelle De Loecker schreef: I've finally gotten VDR to work with my Technotrend S2-3200 card, but I just can't seem to get this diseqc.conf file right! S19.2E 11700 V 9750 [E0 10 38 F0] S19.2E 9 V 10600 [E0 10 38 F1] S19.2E 11700 H 9750 [E0 10 38 F2] S19.2E 9 H 10600 [E0 10 38 F3] S28.2E 11700 V 9750 [E0 10 38 F4] S28.2E 9 V 10600 [E0 10 38 F5] S28.2E 11700 H 9750 [E0 10 38 F6] S28.2E 9 H 10600 [E0 10 38 F7] I have a diseqc 2.0 switch, but since the S2-3200 card only supports Diseqc 1.2 I'm not really sure what to use! It's a regular 4x1 switch Apparantly a regular 4x1 switch doesn't need the F0 - F1 bits at the end, and this will do. As I see it, the first hex-code is used for the option and the second hex-code is used for the position. (A/A-A/B-B/A-B/B) 22 Position A 23 Option A 26 Position B 27 Option B # port 1 option a position a # port 2 option a position b # port 3 option b position a # port 4 option b position b So in your setup I assume that you have ports and LNBs like this: 1 - S19.2E 2 - S28.2E 3 - S23.5E 4 - S13.0E This diseqc.conf should do the trick: # port 1 S19.2E 11700 V 9750 t v W15 [E0 10 23] W15 [E0 10 22] W15 t S19.2E 9 V 10600 t v W15 [E0 10 23] W15 [E0 10 22] W15 T S19.2E 11700 H 9750 t V W15 [E0 10 23] W15 [E0 10 22] W15 t S19.2E 9 H 10600 t V W15 [E0 10 23] W15 [E0 10 22] W15 T # port 2 S28.2E 11700 V 9750 t v W15 [E0 10 23] W15 [E0 10 26] W15 t S28.2E 9 V 10600 t v W15 [E0 10 23] W15 [E0 10 26] W15 T S28.2E 11700 H 9750 t V W15 [E0 10 23] W15 [E0 10 26] W15 t S28.2E 9 H 10600 t V W15 [E0 10 23] W15 [E0 10 26] W15 T # port 3 S23.5E 11700 V 9750 t v W15 [E0 10 27] W15 [E0 10 22] W15 t S23.5E 9 V 10600 t v W15 [E0 10 27] W15 [E0 10 22] W15 T S23.5E 11700 H 9750 t V W15 [E0 10 27] W15 [E0 10 22] W15 t S23.5E 9 H 10600 t V W15 [E0 10 27] W15 [E0 10 22] W15 T # port 4 S13.0E 11700 V 9750 t v W15 [E0 10 27] W15 [E0 10 26] W15 t S13.0E 9 V 10600 t v W15 [E0 10 27] W15 [E0 10 26] W15 T S13.0E 11700 H 9750 t V W15 [E0 10 27] W15 [E0 10 26] W15 t S13.0E 9 H 10600 t V W15 [E0 10 27] W15 [E0 10 26] W15 T Should you need to edit the first port I got this solution from the archive from these very own mailing lists, but it was very hard to find so I thought I'd post it again. It works like a charm: http://www.linuxtv.org/pipermail/vdr/2005-October/005517.html (thank you *Sami J. Mäkinen)* ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Building VDR 1.7.0 - skincurses error?
Good day everyone, I've decided to use VDR 1.7.0 on my linux box, together with my Technotrend S2-3200 DVB-S2 card. Now, it's quite hard to find a decent tutorial on how to compile VDR from source, but at least I found this in the wiki: http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2_-_xine It's german, and I don't completely understand it, but I wrestled through it. Right up to the point where I need to compile the plugins! ... skincurses.c: In member function ‘virtual bool cPluginSkinCurses::Initialize()’: skincurses.c:793: error: ‘WINDOW’ was not declared in this scope skincurses.c:793: error: ‘w’ was not declared in this scope skincurses.c:793: error: ‘initscr’ was not declared in this scope make[1]: *** [skincurses.o] Error 1 make[1]: Leaving directory `/usr/local/src/vdr/PLUGINS/src/skincurses' ... make[1]: Entering directory `/usr/local/src/vdr/PLUGINS/src/svdrpdemo' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/src/vdr/PLUGINS/src/svdrpdemo' *** failed plugins: skincurses make: *** [plugins] Error 1 What could be causing this and how can I fix it? I'm using LinuxMCE 0710 - Kernel 2.6.22-14-generic Thank you for your patience, Jelle De Loecker ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
