xineliboutput-devel Mailing List for VDR xine-lib output device
Brought to you by:
phintuka
You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(7) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(3) |
Jun
(3) |
Jul
(5) |
Aug
(15) |
Sep
(3) |
Oct
|
Nov
(1) |
Dec
(1) |
2010 |
Jan
(6) |
Feb
(8) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
2012 |
Jan
(7) |
Feb
(7) |
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(4) |
Jul
(6) |
Aug
(3) |
Sep
(2) |
Oct
(4) |
Nov
(3) |
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jose A. R. <jos...@gm...> - 2015-12-22 23:30:37
|
I have a problem with vdr-sxfe with vaapi, when moving from marks in a recording. It is a know problem? Jose Alberto |
From: tomek_n <to...@o2...> - 2014-11-18 21:04:33
|
Hi, finally managed to translate the plugin and I think it's ready for merging. The translation has few fuzzy lines, but further users input is needed to rule out errors. If there are any problems, please, contact me. -- Regards, Tomasz Maciej Nowak. |
From: Milan H. <hra...@gm...> - 2014-02-05 10:39:18
|
From: Manfred Schmidt-V. <man...@ma...> - 2013-12-20 15:23:34
|
On 20.12.2013 15:40, Roland Scheidegger wrote: > Happens for me too since some months (though I was using self-compiled > ffmpeg). I think it's due to some changes in ffmpeg. IIRC it only > happens with h264 channels, and only with multithreading enabled. Seems > like the context teardown isn't thread safe or something like that. > As a workaround, I set video.processing.ffmpeg_direct_rendering:0 which > fixes this (I haven't checked recently if some more changes somewhere > actually fixed this). Comes with a performance cost of course but it's > better than disabling multithreading. > > Am 20.12.2013 13:21, schrieb Manfred Schmidt-Voigt: >> Hi, >> >> Most times when I switch channels on my Desktop VDR I get a segfault in >> xineplug_decode_ff.so >> >> Here is a Backtrace: >> >> Core was generated by `/usr/local/src/VDR/vdr -w 300 -l 3 -c /etc/VDR -v >> /video -g /tmp -L /usr/local/'. >> Program terminated with signal 11, Segmentation fault. >> #0 0xa7f24c26 in ?? () from >> /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so >> (gdb) bt >> #0 0xa7f24c26 in ?? () from >> /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so >> #1 0xb259e6b9 in _x_free_video_decoder () from >> /usr/lib/i386-linux-gnu/libxine.so.2 >> #2 0xb25a0413 in ?? () from /usr/lib/i386-linux-gnu/libxine.so.2 >> #3 0xb7761cf1 in start_thread (arg=0xac008b40) at pthread_create.c:311 >> #4 0xb7461c3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 >> >> >> It appears after the last update in Debian SID. My VDR here on the >> desktop is for managing and cutting all the recordings. It has the >> streamdev client as input and vdr-sxfe as output. xineliboutput is the >> latest CVS version, VDR is 2.02. >> Here is my normal XINE environment: >> >> ii libxine2 1:1.2.4-dmo2 i386 Xine media player >> library, meta-package (development branch). >> ii libxine2-bin:i386 1:1.2.4-dmo2 i386 Xine >> video/media player library, binary files. >> ii libxine2-dev:i386 1:1.2.4-dmo2 i386 Xine >> video player library, development packages. >> ii libxine2-ffmpeg:i386 1:1.2.4-dmo2 i386 >> MPEG-related plugins for libxine2. >> ii libxine2-gnome:i386 1:1.2.4-dmo2 i386 >> GNOME-related plugins for libxine2. >> ii libxine2-misc-plugins:i386 1:1.2.4-dmo2 i386 >> Input, audio output and post plugins for libxine2. >> ii libxine2-plugins 1:1.2.4-dmo2 all Xine >> video/media player library, meta package. >> ii libxine2-x:i386 1:1.2.4-dmo2 i386 X desktop >> video output plugins for libxine2. >> >> >> Attached is the log from the console, when I start VDR interactivly and >> the relevant part of the syslog. >> >> Kind regards >> Manfred >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> xineliboutput-devel mailing list >> xin...@li... >> https://lists.sourceforge.net/lists/listinfo/xineliboutput-devel >> > > Thank you, it seem so that this parameter also solved my problems here. I will check further on... -- ------- Manfred Schmidt-Voigt ------- ----- www.mannitec.de ----- ------- mailto:man...@ma... ------- |
From: Roland S. <rsc...@gm...> - 2013-12-20 14:58:15
|
Happens for me too since some months (though I was using self-compiled ffmpeg). I think it's due to some changes in ffmpeg. IIRC it only happens with h264 channels, and only with multithreading enabled. Seems like the context teardown isn't thread safe or something like that. As a workaround, I set video.processing.ffmpeg_direct_rendering:0 which fixes this (I haven't checked recently if some more changes somewhere actually fixed this). Comes with a performance cost of course but it's better than disabling multithreading. Am 20.12.2013 13:21, schrieb Manfred Schmidt-Voigt: > Hi, > > Most times when I switch channels on my Desktop VDR I get a segfault in > xineplug_decode_ff.so > > Here is a Backtrace: > > Core was generated by `/usr/local/src/VDR/vdr -w 300 -l 3 -c /etc/VDR -v > /video -g /tmp -L /usr/local/'. > Program terminated with signal 11, Segmentation fault. > #0 0xa7f24c26 in ?? () from > /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so > (gdb) bt > #0 0xa7f24c26 in ?? () from > /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so > #1 0xb259e6b9 in _x_free_video_decoder () from > /usr/lib/i386-linux-gnu/libxine.so.2 > #2 0xb25a0413 in ?? () from /usr/lib/i386-linux-gnu/libxine.so.2 > #3 0xb7761cf1 in start_thread (arg=0xac008b40) at pthread_create.c:311 > #4 0xb7461c3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 > > > It appears after the last update in Debian SID. My VDR here on the > desktop is for managing and cutting all the recordings. It has the > streamdev client as input and vdr-sxfe as output. xineliboutput is the > latest CVS version, VDR is 2.02. > Here is my normal XINE environment: > > ii libxine2 1:1.2.4-dmo2 i386 Xine media player > library, meta-package (development branch). > ii libxine2-bin:i386 1:1.2.4-dmo2 i386 Xine > video/media player library, binary files. > ii libxine2-dev:i386 1:1.2.4-dmo2 i386 Xine > video player library, development packages. > ii libxine2-ffmpeg:i386 1:1.2.4-dmo2 i386 > MPEG-related plugins for libxine2. > ii libxine2-gnome:i386 1:1.2.4-dmo2 i386 > GNOME-related plugins for libxine2. > ii libxine2-misc-plugins:i386 1:1.2.4-dmo2 i386 > Input, audio output and post plugins for libxine2. > ii libxine2-plugins 1:1.2.4-dmo2 all Xine > video/media player library, meta package. > ii libxine2-x:i386 1:1.2.4-dmo2 i386 X desktop > video output plugins for libxine2. > > > Attached is the log from the console, when I start VDR interactivly and > the relevant part of the syslog. > > Kind regards > Manfred > > > > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > > > _______________________________________________ > xineliboutput-devel mailing list > xin...@li... > https://lists.sourceforge.net/lists/listinfo/xineliboutput-devel > |
From: Manfred Schmidt-V. <man...@ma...> - 2013-12-20 12:21:43
|
Hi, Most times when I switch channels on my Desktop VDR I get a segfault in xineplug_decode_ff.so Here is a Backtrace: Core was generated by `/usr/local/src/VDR/vdr -w 300 -l 3 -c /etc/VDR -v /video -g /tmp -L /usr/local/'. Program terminated with signal 11, Segmentation fault. #0 0xa7f24c26 in ?? () from /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so (gdb) bt #0 0xa7f24c26 in ?? () from /usr/lib/i386-linux-gnu/xine/plugins/2.3/xineplug_decode_ff.so #1 0xb259e6b9 in _x_free_video_decoder () from /usr/lib/i386-linux-gnu/libxine.so.2 #2 0xb25a0413 in ?? () from /usr/lib/i386-linux-gnu/libxine.so.2 #3 0xb7761cf1 in start_thread (arg=0xac008b40) at pthread_create.c:311 #4 0xb7461c3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 It appears after the last update in Debian SID. My VDR here on the desktop is for managing and cutting all the recordings. It has the streamdev client as input and vdr-sxfe as output. xineliboutput is the latest CVS version, VDR is 2.02. Here is my normal XINE environment: ii libxine2 1:1.2.4-dmo2 i386 Xine media player library, meta-package (development branch). ii libxine2-bin:i386 1:1.2.4-dmo2 i386 Xine video/media player library, binary files. ii libxine2-dev:i386 1:1.2.4-dmo2 i386 Xine video player library, development packages. ii libxine2-ffmpeg:i386 1:1.2.4-dmo2 i386 MPEG-related plugins for libxine2. ii libxine2-gnome:i386 1:1.2.4-dmo2 i386 GNOME-related plugins for libxine2. ii libxine2-misc-plugins:i386 1:1.2.4-dmo2 i386 Input, audio output and post plugins for libxine2. ii libxine2-plugins 1:1.2.4-dmo2 all Xine video/media player library, meta package. ii libxine2-x:i386 1:1.2.4-dmo2 i386 X desktop video output plugins for libxine2. Attached is the log from the console, when I start VDR interactivly and the relevant part of the syslog. Kind regards Manfred -- ------- Manfred Schmidt-Voigt ------- ----- www.mannitec.de ----- ------- mailto:man...@ma... ------- |
From: zaverel <za...@fr...> - 2013-08-22 17:57:56
|
Hello, I do some test with vdr-2.0.2 and latest skinnopacity and that not perfect : That work but there is problem of refresh with xv http://postimg.org/image/h3z4ccmq5/ http://postimg.org/image/nr1uzcy13/ http://postimg.org/image/49tehpez9/ vdr-sxfe --height=400 --width=500 --tcp --hud --video=xv --verbose 6231] [vdr-fe] Keypress: XKeySym m [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6231] [vdr-fe] Keypress: XKeySym Down [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6231] [vdr-fe] Keypress: XKeySym Down [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6231] [vdr-fe] Keypress: XKeySym Down [6241] [vdr-sxfe] unscaled video window: 598,74 1263x921 [6241] [vdr-sxfe] scaled video window: 156,28 329x341 [6231] [vdr-fe] Keypress: XKeySym Down .... With vaapi scalevideo don't stop and vdr-sxfe crash http://postimg.org/image/tx8d3hlhp/ vdr-sxfe --height=400 --width=500 --tcp --hud --video=vaapi --verbose [8258] [demux_vdr] PMT changed, resetting demuxer [8258] [demux_vdr] audio stream changed: 00000000 -> 03010000 [8249] [lastpts ] stream changed from (nil) to 0x8234a0 [8249] [lastpts ] new stream is vdr stream [8247] [vdr-fe] Keypress: XKeySym m [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 156,28 329x341 [8247] [vdr-sxfe] Video window size changed from 500x400 to 329x341 [8247] [vdr-fe] Event: INFO WINDOW 329x341 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 103,24 216x291 [8247] [vdr-sxfe] Video window size changed from 329x341 to 216x291 [8247] [vdr-fe] Event: INFO WINDOW 216x291 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 68,20 142x248 [8247] [vdr-sxfe] Video window size changed from 216x291 to 142x248 [8247] [vdr-fe] Event: INFO WINDOW 142x248 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 45,17 93x211 [8247] [vdr-sxfe] Video window size changed from 142x248 to 93x211 [8247] [vdr-fe] Event: INFO WINDOW 93x211 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 29,15 61x180 [8247] [vdr-sxfe] Video window size changed from 93x211 to 61x180 [8247] [vdr-fe] Event: INFO WINDOW 61x180 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 19,13 40x153 [8247] [vdr-sxfe] Video window size changed from 61x180 to 40x153 [8247] [vdr-fe] Event: INFO WINDOW 40x153 200 frames delivered, 1 frames skipped, 0 frames discarded [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 13,11 26x130 [8247] [vdr-sxfe] Video window size changed from 40x153 to 26x130 [8247] [vdr-fe] Event: INFO WINDOW 26x130 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 9,9 17x111 [8247] [vdr-sxfe] Video window size changed from 26x130 to 17x111 [8247] [vdr-fe] Event: INFO WINDOW 17x111 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 6,8 11x94 [8247] [vdr-sxfe] Video window size changed from 17x111 to 11x94 [8247] [vdr-fe] Event: INFO WINDOW 11x94 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 4,7 7x80 [8247] [vdr-sxfe] Video window size changed from 11x94 to 7x80 [8247] [vdr-fe] Event: INFO WINDOW 7x80 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 3,6 4x68 [8247] [vdr-sxfe] Video window size changed from 7x80 to 4x68 [8247] [vdr-fe] Event: INFO WINDOW 4x68 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 2,5 2x58 [8247] [vdr-sxfe] Video window size changed from 4x68 to 2x58 [8247] [vdr-fe] Event: INFO WINDOW 2x58 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 1,4 1x49 [8247] [vdr-sxfe] Video window size changed from 2x58 to 1x49 [8247] [vdr-fe] Event: INFO WINDOW 1x49 [8257] [vdr-sxfe] unscaled video window: 598,74 1263x921 [8257] [vdr-sxfe] scaled video window: 1,4 0x41 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 1388 Current serial number in output stream: 1389 I don't know who is the guilty : skinnopacity ,xineliboutput or both For vdpau , i don't know. By the way , it's seem that -m option don't work since this option is unavailable +#ifdef HAVE_XRANDR +" -m --modeswitch Enable video mode switching\n" +#endif Anyway thanks for your work. See you |
From: zaverel <za...@fr...> - 2013-03-19 16:34:26
|
Le 09/01/2013 17:37, zaverel a écrit : > Le 07/01/2013 09:57, Petri Hintukainen a écrit : >> On ke, 2012-11-14 at 16:25 +0100, zaverel wrote: >>> Le 14/11/2012 13:02, Petri Hintukainen a écrit : >>>> Attached patch (fix1.diff) should fix this. If not, fix2.diff disables >>>> that functionality for video streams. >>>> If fix1 does not help, maybe you could provide short sample recording >>>> (something like one second should be OK) ? Or some log output with >>>> attached log.diff patch ? >>>> >>>> >>>> - Petri >>>> >>> Hello, >>> >>> fix1.diff don't work. >>> >>> fix2.diff work. >>> >>> log.diff seem to have a typo >>> >>> that don't compile with >>> this->pes_length but is ok with this->pes_leng >>> >>> >>> i attach fix1.log and a link to a sample recording >>> >>> http://dl.free.fr/jD6c3V0t6 >>> >> Thanks for the log and sample, it helped me to find the root cause of >> this problem. >> >> This should be fixed in CVS now. >> >> >> - Petri >> >> >> > > hello, > > i'm afraid that's not perfect: > > Now video is good but i have random crash between 2 and 3 mn > when i am on iptv channel and only iptv channel. > > this is the log just before the crash > > video_out: throwing away image with pts 12930689 because it's too old > (diff : 3744). > video_out: throwing away image with pts 12934352 because it's too old > (diff : 9146). > video_out: throwing away image with pts 12938012 because it's too old > (diff : 14568). > video_out: throwing away image with pts 12945682 because it's too old > (diff : 25124). > video_out: throwing away image with pts 12953558 because it's too old > (diff : 26362). > video_out: throwing away image with pts 12961625 because it's too old > (diff : 54743). > video_out: throwing away image with pts 12969871 because it's too old > (diff : 64692). > video_out: throwing away image with pts 12978285 because it's too old > (diff : 74464). > Floating point exception > > See you > > Hello, I don't know if it's safe but latest xineliboutput + your patch fix2.diff and iptv doesn't crash anymore and there is no flood in log. So maybe patch has to be applied for everyone. By the way, what is the statut about ffmpeg and xine-lib-1.2 cvs? the latest working version is ffmpeg-1.0.5 More recent version doesn't compile or not work at all with vaapi. see you. |
From: zaverel <za...@fr...> - 2013-01-09 16:37:35
|
Le 07/01/2013 09:57, Petri Hintukainen a écrit : > On ke, 2012-11-14 at 16:25 +0100, zaverel wrote: >> Le 14/11/2012 13:02, Petri Hintukainen a écrit : >>> Attached patch (fix1.diff) should fix this. If not, fix2.diff disables >>> that functionality for video streams. >>> If fix1 does not help, maybe you could provide short sample recording >>> (something like one second should be OK) ? Or some log output with >>> attached log.diff patch ? >>> >>> >>> - Petri >>> >> Hello, >> >> fix1.diff don't work. >> >> fix2.diff work. >> >> log.diff seem to have a typo >> >> that don't compile with >> this->pes_length but is ok with this->pes_leng >> >> >> i attach fix1.log and a link to a sample recording >> >> http://dl.free.fr/jD6c3V0t6 >> > Thanks for the log and sample, it helped me to find the root cause of > this problem. > > This should be fixed in CVS now. > > > - Petri > > > hello, i'm afraid that's not perfect: Now video is good but i have random crash between 2 and 3 mn when i am on iptv channel and only iptv channel. this is the log just before the crash video_out: throwing away image with pts 12930689 because it's too old (diff : 3744). video_out: throwing away image with pts 12934352 because it's too old (diff : 9146). video_out: throwing away image with pts 12938012 because it's too old (diff : 14568). video_out: throwing away image with pts 12945682 because it's too old (diff : 25124). video_out: throwing away image with pts 12953558 because it's too old (diff : 26362). video_out: throwing away image with pts 12961625 because it's too old (diff : 54743). video_out: throwing away image with pts 12969871 because it's too old (diff : 64692). video_out: throwing away image with pts 12978285 because it's too old (diff : 74464). Floating point exception See you |
From: zaverel <za...@fr...> - 2012-11-14 15:25:16
|
Le 14/11/2012 13:02, Petri Hintukainen a écrit : > Attached patch (fix1.diff) should fix this. If not, fix2.diff disables > that functionality for video streams. > If fix1 does not help, maybe you could provide short sample recording > (something like one second should be OK) ? Or some log output with > attached log.diff patch ? > > > - Petri > Hello, fix1.diff don't work. fix2.diff work. log.diff seem to have a typo that don't compile with this->pes_length but is ok with this->pes_leng i attach fix1.log and a link to a sample recording http://dl.free.fr/jD6c3V0t6 see you |
From: Petri H. <phi...@us...> - 2012-11-14 12:02:24
|
On ma, 2012-10-29 at 20:26 +0100, zaverel wrote: > Hello, > > commit: demux-ts: flush complete PES packets immediately don't seem good > > http://xineliboutput.cvs.sourceforge.net/viewvc/xineliboutput/vdr-xineliboutput/xine/ts2es.c?r1=1.16&r2=1.17&sortby=date > > > it break h264 video from iptv plugin. > Only sound work. > > When i play xine http://127.0.0.1:37890 that work (video+audio) > > > If i reverted the commit , video+audio work like before with vdr-sxfe. Attached patch (fix1.diff) should fix this. If not, fix2.diff disables that functionality for video streams. If fix1 does not help, maybe you could provide short sample recording (something like one second should be OK) ? Or some log output with attached log.diff patch ? - Petri |
From: zaverel <za...@fr...> - 2012-10-29 19:26:08
|
Hello, commit: demux-ts: flush complete PES packets immediately don't seem good http://xineliboutput.cvs.sourceforge.net/viewvc/xineliboutput/vdr-xineliboutput/xine/ts2es.c?r1=1.16&r2=1.17&sortby=date it break h264 video from iptv plugin. Only sound work. When i play xine http://127.0.0.1:37890 that work (video+audio) If i reverted the commit , video+audio work like before with vdr-sxfe. See you. |
From: zaverel <za...@fr...> - 2012-10-26 14:32:56
|
Hello, what i say before is not really true: In fact it's a bug in xine-lib-1.2 and ffmpeg mpeg2 http://anonscm.debian.org/hg/xine-lib/xine-lib-1.2-vdpau/rev/a611988a4401 If i revert that patch all my mpeg2 sd channels works (but with errors in log). but engine.decoder_priorities.ffmpegvideo:1 in ~/.xine/config_xineliboutput work now. I send a mail to xine mailing-list but with no answer until now. http://sourceforge.net/mailarchive/forum.php?thread_name=508A9B90.4030609%40free.fr&forum_name=xine-user see you |
From: zaverel <za...@fr...> - 2012-10-19 16:08:57
|
Hello, I find what was wrong => README.vaapi https://github.com/huceke/xine-lib-vaapi/blob/vaapi/README.vaapi in config_xineliboutput with engine.decoder_priorities.ffmpegvideo:1 few sd mpeg channels does'nt work => black screen if i use engine.decoder_priorities.ffmpegvideo:0 or engine.decoder_priorities.ffmpegvideo:1 engine.decoder_priorities.mpeg2:1 all sd channels works. Some others settings like # VAAPI Mpeg2 softdecoding # bool, default: 0 #video.processing.vaapi_mpeg_softdec:0 # VAAPI Mpeg2 softdecoding deinterlace # bool, default: 0 #video.processing.vaapi_mpeg_softdec_deinterlace:0 don't work at all and are erase from config_xineliboutput i don't know if it's normal but finaly xine-lib-vaapi work. See you |
From: zaverel <za...@fr...> - 2012-10-16 19:18:48
|
hello, I just buy new hardware: Intel Core i3 3220T (Ivy Bridge hd graphics 2500) and MSI B75A-G43 I have installed all libva + libva-intel-driver + xine-lib-vaapi and latest ffmpeg and xineliboutput + kernel 3.6.2 vainfo is good: libva info: VA-API version 0.33.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so libva info: Found init function __vaDriverInit_0_33 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.33 (libva 1.1.1.pre1) vainfo: Driver version: Intel i965 driver - 1.0.18 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264Baseline : VAEntrypointVLD VAProfileH264Baseline : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD But that don't work like expected with vdr-sxfe : dvb-t hd and dvb-t sd work with vaapi but not for all sd channel For 20 sd channels, 4 (alway the sames) don't work => black screen + audio If i use xine-ui those 4 channels works. What can i do to debug that ? vdr-sxfe --verbose ..... [31829] [demux_vdr] PMT changed, resetting demuxer yv12_to_nv12 strange -41472 ffmpeg_video_dec: vaapi_mpeg_softdec 0 ffmpeg_video_dec: vaapi_mpeg_softdec_deinterlace 0 [31829] [demux_vdr] audio stream changed: 00000000 -> 03010000 yv12_to_nv12 strange -41472 ffmpeg_video_dec: VAAPI Enabled in config. ffmpeg_video_dec: force AVDISCARD_DEFAULT for VAAPI ffmpeg_video_dec: direct rendering enabled ffmpeg_video_dec: direct rendering enabled video_out_vaapi VAAPI Supported Profiles : VAProfileMPEG2Simple VAProfileMPEG2Main VAProfileH264Baseline VAProfileH264Main VAProfileH264High VAProfileVC1Simple VAProfileVC1Main VAProfileVC1Advanced <unknown> video_out_vaapi VAAPI Profile VAProfileMPEG2Main supported by your hardware libva info: VA-API version 0.33.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so libva info: Found init function __vaDriverInit_0_33 libva info: va_openDriver() returns 0 video_out_vaapi vaapi_open: Vendor : Intel i965 driver - 1.0.18 video_out_vaapi vaapi_init : Context width 720 height 576 video_out_vaapi vaapi_init : Profile: 1 (VAProfileMPEG2Main) Entrypoint 1 (VAEntrypointVLD) Surfaces 50 video_out_vaapi vaapi_init : guarded render : 1 video_out_vaapi vaapi_init : glxrender : 0 video_out_vaapi vaapi_init : glxrender tfp : 0 video_out_vaapi vaapi_init : is_bound : 1 video_out_vaapi vaapi_init : scaling level : name default value 0x00000000 yv12_to_nv12 strange -41472 yv12_to_nv12 strange -41472 yv12_to_nv12 strange -41472 .... yv12_to_nv12 seem to be about osd when display it but osd work. Thanks for reply what can i looking for. See you. |
From: zaverel <za...@fr...> - 2012-09-03 08:14:53
|
>> Hello, >> to be more precise ,mediaplayer don't display file name at all for .avi >> , mpg, mp4 >> That work only for few mkv with good tag name (and not the file name of >> mkv). >> >> Thanks for reply. > This should be fixed now. > > > - Petri > > > hello, yes i just test latest cvs and it's ok now. thanks for your work. see you |
From: Petri H. <phi...@us...> - 2012-09-02 19:23:07
|
On ke, 2012-08-29 at 13:02 +0200, zaverel wrote: > Le 28/08/2012 21:31, Petri Hintukainen a écrit : > > On pe, 2012-08-24 at 15:46 +0200, zaverel wrote: > >> hello, > >> > >> there is a long time that the name of video is not display when start or > >> press ok when video is playing > >> > >> > >> screenshot from mediaplayer vdr-sxfe > >> http://imageshack.us/photo/my-images/525/videod.png/ > >> > >> screenshot from record's vdr > >> http://imageshack.us/photo/my-images/827/recordz.png/ > >> > >> Some skins hide this so that's visible more or less > >> > >> Note that some mkv with good info in (not the name of video) are goody > >> named. > > Sometimes name may be missing. In that case it should display file name > > instead of empty title. > > > > > Hello, > to be more precise ,mediaplayer don't display file name at all for .avi > , mpg, mp4 > That work only for few mkv with good tag name (and not the file name of > mkv). > > Thanks for reply. This should be fixed now. - Petri |
From: zaverel <za...@fr...> - 2012-08-29 11:03:26
|
Le 28/08/2012 21:31, Petri Hintukainen a écrit : > On pe, 2012-08-24 at 15:46 +0200, zaverel wrote: >> hello, >> >> there is a long time that the name of video is not display when start or >> press ok when video is playing >> >> >> screenshot from mediaplayer vdr-sxfe >> http://imageshack.us/photo/my-images/525/videod.png/ >> >> screenshot from record's vdr >> http://imageshack.us/photo/my-images/827/recordz.png/ >> >> Some skins hide this so that's visible more or less >> >> Note that some mkv with good info in (not the name of video) are goody >> named. > Sometimes name may be missing. In that case it should display file name > instead of empty title. > > Hello, to be more precise ,mediaplayer don't display file name at all for .avi , mpg, mp4 That work only for few mkv with good tag name (and not the file name of mkv). Thanks for reply. see you |
From: Petri H. <phi...@us...> - 2012-08-28 19:32:34
|
On pe, 2012-08-24 at 15:46 +0200, zaverel wrote: > hello, > > there is a long time that the name of video is not display when start or > press ok when video is playing > > > screenshot from mediaplayer vdr-sxfe > http://imageshack.us/photo/my-images/525/videod.png/ > > screenshot from record's vdr > http://imageshack.us/photo/my-images/827/recordz.png/ > > Some skins hide this so that's visible more or less > > Note that some mkv with good info in (not the name of video) are goody > named. Sometimes name may be missing. In that case it should display file name instead of empty title. > And another thing : > > is that normal on remote frontend only video work in mediaplayer ? > i have to mount the share from the server to the client else subtitle > (.srt) are not use when playing video > and info time are not good Some formats are not streamable, and with some formats you'll lose some information (total time etc.). Subtitles should work, but I haven't tested that lately. - Petri |
From: zaverel <za...@fr...> - 2012-08-24 13:47:20
|
hello, there is a long time that the name of video is not display when start or press ok when video is playing screenshot from mediaplayer vdr-sxfe http://imageshack.us/photo/my-images/525/videod.png/ screenshot from record's vdr http://imageshack.us/photo/my-images/827/recordz.png/ Some skins hide this so that's visible more or less Note that some mkv with good info in (not the name of video) are goody named. And another thing : is that normal on remote frontend only video work in mediaplayer ? i have to mount the share from the server to the client else subtitle (.srt) are not use when playing video and info time are not good see you |
From: Chris R. <ran...@ya...> - 2012-07-29 22:02:51
|
> Yes, both xine-lib versions should work equally well with xineliboutput. For reference: * I am using Fedora 17's VDR 1.7.27 RPM, and libxine1.2.2 RPMs compiled from the repository. * xineliboutput is passed these parameters: --local=none --remote=37890 * xine-ui is my front-end. * For some reason, xineliboutput's vdr_event_cb() function is receiving a XINE_EVENT_UI_PLAYBACK_FINISHED event, which sets this->control_running = 0. Cheers, Chris |
From: Chris R. <ran...@ya...> - 2012-07-29 13:02:18
|
----- Original Message ----- >> Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input >> plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'. > > Wrong mrl (xineliboutput uses xvdr:// ...) Ah, xine-lib-1.2 contains another plugin: xineplug_vdr.so. When I remove this plugin, xine-ui has enough room to display the xvdr button. Pressing the xvdr button results in the exact same spectacular failure as with xine-lib-1.1 where xine-ui displays nothing from VDR except "No Signal", if I'm lucky. > Yes, both xine-lib versions should work equally well with xineliboutput. Indeed - it fails equally with both... Jul 29 13:57:34 endgame vdr: [20992] [xine..put] Detected video size 720x576 Jul 29 13:57:47 endgame vdr: [20984] [xine..put] Client 0 connected: 127.0.0.1:54423 Jul 29 13:57:47 endgame vdr: [20984] loading /etc/vdr/plugins/xineliboutput/allowed_hosts.conf Jul 29 13:57:47 endgame vdr: [20984] creating directory /etc/vdr/plugins/xineliboutput/pipes.20976 Jul 29 13:57:47 endgame vdr: [20984] removing /etc/vdr/plugins/xineliboutput/pipes.20976 Jul 29 13:58:16 endgame vdr: [20976] switching to channel 2 Jul 29 13:58:17 endgame vdr: [20993] TS buffer on device 1 thread ended (pid=20976, tid=20993) Jul 29 13:58:17 endgame vdr: [20992] buffer stats: 82156 (3%) used Jul 29 13:58:17 endgame vdr: [20992] receiver on device 1 thread ended (pid=20976, tid=20992) Jul 29 13:58:17 endgame vdr: [21023] receiver on device 1 thread started (pid=20976, tid=21023) Jul 29 13:58:17 endgame vdr: [21024] TS buffer on device 1 thread started (pid=20976, tid=21024) Jul 29 13:58:17 endgame vdr: [20984] [xine..put] Client connection 0 closed Jul 29 13:58:17 endgame vdr: [20984] [xine..put] Closing connection 0 Jul 29 13:58:17 endgame vdr: [21023] [xine..put] Detected video size 720x576 Have you tested with VDR 1.7(.27)? Cheers, Chris |
From: Chris R. <ran...@ya...> - 2012-07-29 12:47:57
|
----- Original Message ----- > Does pkg-config give correct include path for libavutil (pkg-config > libavutil --cflags) ? If yes, this should be fixed in CVS now. It says: # pkg-config libavutil --cflags -I/usr/include/ffmpeg So this is correct. However, anything checking for libavutil headers would need to include this during any autoconf step. (Which is probably where xine-lib-1.2 goes wrong...) Cheers, Chris |
From: Petri H. <phi...@us...> - 2012-07-29 09:00:14
|
On la, 2012-07-28 at 14:44 -0700, Chris Rankin wrote: > Hi, > > I've cloned the git repository at git://projects.vdr-developer.org/xineliboutput and > compiled it against xine-lib-1.2. (Like xine-lib-1.2, I needed to patch the Makefile > before xineliboutput would compile: > > diff --git a/Makefile b/Makefile > index 47ffdec..84f6e41 100644 > --- a/Makefile > +++ b/Makefile > @@ -179,7 +179,7 @@ endif > ### Includes and Defines (add further entries here): > ### > > -INCLUDES += -I$(VDRINCDIR) > +INCLUDES += -I$(VDRINCDIR) -I/usr/include/ffmpeg > > ifeq ($(ARCH_APPLE_DARWIN), yes) > INCLUDES += -I/sw/include That's expected if headers or libraries are installed to non-default places. You can give the path to configure script as parameter or add it to Make.config file. Does pkg-config give correct include path for libavutil (pkg-config libavutil --cflags) ? If yes, this should be fixed in CVS now. > I'm thinking no-one else is using Fedora, or these build breakages would have been noticed already!) > > Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input > plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'. Wrong mrl (xineliboutput uses xvdr:// ...) > Yeah, right. > > Is anyone actually *testing* xine or xineliboutput any more? Because I've tested xinelibout > against both xine-lib-1.1 and xine-lib-1.2 and it has utterly failed to do anything with either! Yes, both xine-lib versions should work equally well with xineliboutput. I've experienced some problems when both 1.1.x and 1.2.x are installed at the same time. Also make sure you don't have loads of old xine plugins in /usr/lib/xine/plugins/ - Petri |
From: Chris R. <ran...@ya...> - 2012-07-28 21:45:05
|
Hi, I've cloned the git repository at git://projects.vdr-developer.org/xineliboutput and compiled it against xine-lib-1.2. (Like xine-lib-1.2, I needed to patch the Makefile before xineliboutput would compile: diff --git a/Makefile b/Makefile index 47ffdec..84f6e41 100644 --- a/Makefile +++ b/Makefile @@ -179,7 +179,7 @@ endif ### Includes and Defines (add further entries here): ### -INCLUDES += -I$(VDRINCDIR) +INCLUDES += -I$(VDRINCDIR) -I/usr/include/ffmpeg ifeq ($(ARCH_APPLE_DARWIN), yes) INCLUDES += -I/sw/include I'm thinking no-one else is using Fedora, or these build breakages would have been noticed already!) Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'. Yeah, right. Is anyone actually *testing* xine or xineliboutput any more? Because I've tested xinelibout against both xine-lib-1.1 and xine-lib-1.2 and it has utterly failed to do anything with either! Cheers, Chris |