We just released VLC 1.1.0
11–20 of 61 posts
Re: We just released VLC 1.1.0
#12Re: We just released VLC 1.1.0
#13VLC was my preferred player in Windows, and still remains my default in OS X. There is nary a format which the orange pylon cannot handle. Thanks to the VLC and FFMPEG guys for all the hard work!
Re: We just released VLC 1.1.0
#14Re: We just released VLC 1.1.0
#15Re: We just released VLC 1.1.0
#16Re: We just released VLC 1.1.0
#17Wondering what the technical problems with the ATI drivers were.
Well, those are pretty simple. For many reasons (that are debatable, but maybe this isn't the right place?), VLC can decode on the GPU and then gets the data back from the GPU to filter/restream/reencode to finally display it. Even if this isn't the fastest way, there are good reasons for it (I can explain if needed...) On ATI drivers, the data back path is slow, and you need a special GUID that ATI doesn't want/cann…
I'd personally be very interested in hearing some details about this, if you have a few moments to write something up (or even paste a few links to some mailing list posts or the like, somewhere that I can do some reading).
Re: We just released VLC 1.1.0
#18You really should use Sparkle for the OS X release. VLC is one of the few apps that doesn't use it and the built in updating mechanism in VLC never works anyway.
Re: We just released VLC 1.1.0
#19Wondering what the technical problems with the ATI drivers were.
Well, those are pretty simple. For many reasons (that are debatable, but maybe this isn't the right place?), VLC can decode on the GPU and then gets the data back from the GPU to filter/restream/reencode to finally display it. Even if this isn't the fastest way, there are good reasons for it (I can explain if needed...) On ATI drivers, the data back path is slow, and you need a special GUID that ATI doesn't want/cann…
Re: We just released VLC 1.1.0
#20Earlier quoted context omitted.
From my reading, it seems that the complaint is that ATI doesn't support hardware video decoding properly.
No, it is doing it fine. The irony is that if you have an Intel SSE4.1 chip, you can use a special trick to work-around this "bug".