Slashdot Mirror
VLC 1.0.0 Released
rift321 writes "VLC media player, which we all know for simplifying the playback of pretty much any codec out there, has finally released version 1.0.0. Here's a quick list of improvements: live recording, instant pausing and frame-by-frame support, finer speed controls, new HD codecs (AES3, Dolby Digital Plus, TrueHD, Blu-Ray Linear PCM, Real Video 3.0 and 4.0), new formats (Raw Dirac, M2TS) and major improvements in many formats, new Dirac encoder and MP3 fixed-point encoder, video scaling in fullscreen, RTSP Trickplay support, zipped file playback, customizable toolbars, easier encoding GUI in Qt interface, better integration in Gtk environments, MTP devices on Linux, and AirTunes streaming."
That wasn't Michael.
It was Janet. (Ms. Jackson if you're nasty)
(Oh god I didn't type that.. too much Micheal Jackson news... it's rotting my brain....)
VLC 1.0.0 and 1.1.0 can be compiled with VAAPI to get hardware acceleration.
VLC supports hardware acceleration on nVidia G80 and higher hardware using VDPAU on Linux. As soon as ATI releases a XvBA driver, hardware acceleration should be possible through VAAPI.
You might want to read this then. It appears that there are even patches available for vdpau (=NVIDIA's hardware acceleration). I haven't tried this yet myself though (but will be as soon as I get home from work).
Gentlemen! You can't fight in here, this is the war room!
I had that happen with the Canadian mirror. I refreshed the page (as instructed at the very top), got a U.S. mirror, and everything was fine.
I wonder if there isn't any copy protection mechanism that breaks the player. I once tried to rip a Wall-E DVD and it appeared to have over 60GB in it. They are using false sectors in the disk to fool rippers. Perhaps these DVDs you tried to watch have some similar "feature" that messes up the Linux software. You could try playing the .vob files directly as a workaround.
Where is that guy who'd die defending what I had to say when I need him?
Any remaining Tiger users needn't bother. As of this version, VLC requires Mac OS X 10.5. This is not obvious from the website.
Hate to go off topic, but I was having a similar problem and so far, Xine has played all the discs that VLC and MPlayer couldn't.
Much improved in recent releases, IMO. You should give it another try and see if it's any better.
Thats too bad for you, vlc plays 1080p h264 content just fine on my cheapo dualcore AMD.
Follow-up to my own comment:
When you run the 1.0.0 installer (in Windows) it will detect earlier versions and ask if it can uninstall them before installing the new version. So far, so good.
-Rich
I know Winamp was (is?) like that. When you adjust the volume, it adjusts the Wave output in Windows. This is fine if you're using Winamp all the time, but if you switch to another media player (I used to be a big fan of The Core Media Player until it died), you're left with turning your volume to max and still not being able to hear anything.
I traded all my mod points for these magic beans.
Software patents are afaik not valid anywhere else in the world (luckily),
They are valid in Japan. Some other countries too, try wikipedia.
When information is power, privacy is freedom.
That does not help. Saying "well, you can just compile in support for ____" shouldn't be acceptable in this day and age. You shoudn't have to compile in support for a given piece of hardware into a player: this is why we have things called "drivers" and "APIs".
That's what the 'API' part of VAAPI is :-)
There's nothing wrong with having compile-time options in open-source software. It's the job of the package and distribution maintainers to abstract this kind of thing away from end users. It'll be a while before this 1.0.0 release filters down to users' desktops through their package managers, which you could wait for and not have to worry about it (this is certainly what I'll be doing)... but if you want the latest and greatest direct from the developers as soon as it's released then you can't complain about having to get your hands a bit dirty.
They tend to stagger the updates just a bit on the automatic updates... They post it on the website for those who absolutely must have it now, while the casual users, using a perfectly good 0.9.9a, will get it sometime over the course of the next few days, or when they next get around to opening it.
Uh, I think you need to look a little harder.
VLC supports CC on Linux and OSX.
xine supports CC but you have to manually add the settings to your xine config closed caption (search for "subtitles.closedcaption" options).
mplayer has complete support for VDPAU as well as support for things like SSA/ASS subtitles. While the current repository versions tend to run a bit behind the development versions (bzip2 archive) at mplayerhq.hu, rvm's builds as part of his smplayer project are quite up-to-date. smplayer is a fine GUI front-end to mplayer as well, and it runs on both Linux and Windows.
are you sure VLC is using hardware acceleration? mess around with Tools - Preferences - Video button - Output dropdown box, see if DirectX video output mode helps.
So then what is the difference between subtitles and closed captions??
According to Wikipedia:
Most of the world does not distinguish captions from subtitles. In the United States and Canada, these terms do have different meanings, however: "subtitles" assume the viewer can hear but cannot understand the language or accent, or the speech is not entirely clear, so they only transcribe dialogue and some on-screen text. "Captions" aim to describe all significant audio contentâ"spoken dialogue and non-speech information such as the identity of speakers and, occasionally, their manner of speakingâ"along with music or sound effects using words or symbols.
To me, this sound like the difference is entirely the content of what gets displayed. So why should VLC be able to display subtitles and not closed captions??? I don't get it!
Apparently you don't know what "lossless" actually means.
Sure he does, lossless encoding takes out the "whooosh" sound.
I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
From the release notes:
Changes between 0.9.9a and 1.0.0:
* Closed Captions using the SCTE-20 standard are now correctly decoded
Apparently that's not enough then, is it?
The tyrant will always find a pretext for his tyranny - Aesop
Burn it in UDF format. UDF doesn't have a size limit. There's also a workaround for ISO: multiple extents, but I haven't tried that.