Thread: mplayer vdpau
View Single Post
Old 09-28-09, 03:04 PM   #1198
piotro
Registered User
 
Join Date: May 2007
Posts: 72
Default Re: mplayer vdpau

@danoscar

Thx for trying help !
Unfortunatelly patch works only for analog audio.
For SPDIF based systems I' receiving error like below.

IMHO Your patch isn't fully resolving issue - it is rather workaround, as wrong synchronization direction is still present (TV->mplayer playback).

I believe only proper solution is solution proposed by "uau". Also for me all this looks like constrain of vdpau design.
Having possibility to inform player code about display rate is essential for keeping sync. If judder less playback is expected - only sync display to source is solution.

Honestly speaking, I'm little surprised. Design where we are not able to sync display to source is IMHO issue - as long as we want to use VDPAU as support for serious player with no judder, no tearing playback.

Unfortunately - due bug in all nv VDPAU driver versions - approach with free running player and display, both with the same fps, isn't working for non-integer refresh rates (at lest in my system)

br

br

Code:
----------------------------
Increasing filtered audio buffer size from 0 to 65536
Syncing speed to double display vsync rate 1.0427083050% ??,?% 0 0                                                                                     
Building audio filter chain for 50050Hz/2ch/ac3 -> 48000Hz/2ch/ac3...
[dummy] Was reinitialized: 50050Hz/2ch/ac3
[libaf] Adding filter lavcresample 
[libaf] Adding filter format 
[format] Sample format big-endian AC3 not yet supported 
*** [vo] Direct Rendering (slices) mp_image_t, 1920x1088x0bpp RGB packed, 0 bytes
Unicode font: 661 glyphs.
Unicode font: 661 glyphs.


MPlayer interrupted by signal 11 in module: decode_audio
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
minimyth@FE-Salon:~ $
piotro is offline   Reply With Quote