xine-lib/src/video_dec/libvdpau, branch 1.2.0 xine-lib git mirror Oops. Omitted headers. 2012-01-01T21:08:37+00:00 Darren Salt linux@youmustbejoking.demon.co.uk 2012-01-01T21:08:37+00:00 f9cca44a36be9b3892194d724e942d9b7b174cf6 






Kill a few trivial compiler warnings.
2011-12-31T22:28:23+00:00

Darren Salt
linux@youmustbejoking.demon.co.uk

2011-12-31T22:28:23+00:00

96801061c49f647d815b01375037484c374a813f












A new vdpau h264 decoder that has proven to work better than the previous one.
2011-12-31T22:10:59+00:00

Christophe Thommeret
hftom@free.fr

2011-12-31T22:10:59+00:00

fc5e20969e6e15e7157f15e4368bfe51676be2ef












Disable strict-aliasing where it caused compiler warnings
2011-10-15T20:11:45+00:00

Christian Ruppert
idl0r@gentoo.org

2011-10-15T20:11:45+00:00

0f53dcaa8cae2d37e886fff0d7a44ed6e679aeb4












Fix bad width in vdpau vc1 decoder
2011-07-06T10:14:15+00:00

Jerome Lacarriere
lacarriere.j@gmail.com

2011-07-06T10:14:15+00:00

53ec0b8ab9e7076d84221bbd5ea84978239a1afc












Use "quietened" build if automake 1.11 was used.
2011-05-16T23:12:50+00:00

Darren Salt
linux@youmustbejoking.demon.co.uk

2011-05-16T23:12:50+00:00

41032c035366c25547bc7ce470638624c23a405e












Fixed minor issues with debug logging.
2011-03-22T10:03:23+00:00

Andreas Auras
yak54@inkennet.de

2011-03-22T10:03:23+00:00

6e3610eb726674925f9c4b51aaa45f0d94bcd388












vdpau_mpeg12: fix frame duration calculation when repeating frames or fields.
2011-02-20T22:38:32+00:00

Reinhard Nißl
rnissl@gmx.de

2011-02-20T22:38:32+00:00

77aa841ba7f4249dceaea6470cb025f976a6e57a

Frame duration calculation for repeated frames or fields is now correct,
but video_out_vdpau.c needs to be adjusted too, because for now it will
show for example 1.5x top field and 1.5x bottom field instead of 1x top
field, 1x bottom field and 1x top field again.





Frame duration calculation for repeated frames or fields is now correct,
but video_out_vdpau.c needs to be adjusted too, because for now it will
show for example 1.5x top field and 1.5x bottom field instead of 1x top
field, 1x bottom field and 1x top field again.







Remove incorrect enum value which caused a value shift of successors
2011-01-23T00:38:13+00:00

Reinhard Nißl
rnissl@gmx.de

2011-01-23T00:38:13+00:00

c8e0257887a361a0b2b7a759309bcdb822d479b2

According to ITU-T Rec. H.264 (03/2005), Table D-1, there is no such
indicated display of picture. As a result, succeeding enum constants
were mapped to the wrong values.





According to ITU-T Rec. H.264 (03/2005), Table D-1, there is no such
indicated display of picture. As a result, succeeding enum constants
were mapped to the wrong values.







Avoid "broken stream" message in vdpau_decoder_render, caused by decoder_init
2011-01-22T23:59:24+00:00

Reinhard Nißl
rnissl@gmx.de

2011-01-22T23:59:24+00:00

dc70c32e0f7614f52958e1b37da5b215aaafaafe

The image allocated in decoder_init can immediately be freed after getting
access to accel_data. Accessing the accel pointer afterwards is safe for non
frame related functions although the frame has been freed as freed frames are
not deallocated but put into a free frame queue.





The image allocated in decoder_init can immediately be freed after getting
access to accel_data. Accessing the accel pointer afterwards is safe for non
frame related functions although the frame has been freed as freed frames are
not deallocated but put into a free frame queue.