Stories
Slash Boxes
Comments

SoylentNews is people

posted by mrpg on Sunday February 11 2018, @10:56AM   Printer-friendly
from the vetinari dept.

VideoLAN has released version 3.0.0 of the VLC media player for Windows, Linux, BSD, Android, and macOS. The new version is billed as enabling hardware decoded playback of 4K, 8K, and 360-degree video (in a demonstration video, VLC 3.0.0 is shown playing 8K 48fps 360-degree video on a Samsung Galaxy S8).

3.0.0 adds support for (not exhaustive):

Linux/BSD default video output is now OpenGL, instead of Xvideo.

The 3.0.x branch of VLC will be maintained as long-term support versions and will be the last releases on Windows XP (with significant limitations), Vista, macOS 10.7, 10.8 & 10.9, iOS 7 & 8, Android 2.x, 3.x, 4.0.x & 4.1.x, and the last to run on compilers before gcc 5.0 and clang 3.4, or equivalent.

From VLC Android developer Geoffrey Métais's blog post about the release, which discusses why Chromecast support took so long to add, as well as other missing features that have now been added to the Android version:

Chromecast support is everywhere and VLC took years to get it, right, but there are plenty of good reasons for it:

First of all, VideoLAN is a nonprofit organization and not a company. There are few developers paid for making VLC, most of them do it in their free time. That's how you get VLC for free and without any ads!

Also, VLC is 100% Open Source and Chromecast SDK isn't: We had to develop our very own Chromecast stack by ourselves. This is also why there is no voice actions for VLC (except with Android Auto), [and] we cannot use Google Play Services.

Furthermore, Chromecast is not designed to play local video files: When you watch a Youtube video, your phone is just a remote controller, nothing more. Chromecast streams the video from youtube.com. That's where it becomes complicated, Chromecast only supports very few codecs number, let's say h264. Google ensures that your video is encoded in h264 format on youtube.com, so streaming is simple. With VLC, you have media of any format. So VLC has to be a http server like youtube.com, and provide the video in a Chromecast compatible format. And of course in real time, which is challenging on Android because phones are less powerful than computers.

At last, VLC was not designed to display a video on another screen. It took time to properly redesign VLC to nicely support it. The good news is we did not make a Chromecast specific support, it is generic renderers: in the next months we can add UPnP support for example, to cast on any UPnP box or TV!

Also at The Verge and Tom's Hardware.

Related: Stable Release of VLC 1.0 for Android
VLC 2.0 for Android Released
EU Offers Cash Bounties to Improve the Security of VLC Media Player
Google Won't Take Down Pirate VLC With 5M Downloads (Update: They Have Taken it Down)


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Interesting) by Anonymous Coward on Sunday February 11 2018, @11:26AM (4 children)

    by Anonymous Coward on Sunday February 11 2018, @11:26AM (#636329)

    The real question is: does it convert %20's and %5D's and other crap in the URI field of the playlist to something actually useful? Or include a readable "filename" field?

    Last time I checked, it was impossible to get human-readable filenames in the playlist window, and the feature request for it was either denied or ignored, I don't remember which. I tried to dig through the source code to see if I could implement it myself, but to no avail :/ It seemed that I'd need to get familiar with a large portion of the codebase to do it, and that'd require a sizable time commitment...

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1  
  • (Score: 1, Insightful) by Anonymous Coward on Sunday February 11 2018, @05:55PM (3 children)

    by Anonymous Coward on Sunday February 11 2018, @05:55PM (#636395)

    maybe if stupid freaking windows users would quit putting spaces in everything... of course you'd probably hear gabriel's trumpet if that happened.

    • (Score: 3, Insightful) by arslan on Monday February 12 2018, @12:39AM (1 child)

      by arslan (3462) on Monday February 12 2018, @12:39AM (#636513)

      I dunno, the computer should cater to my preferences, not the other way around. Most users prefer to have space breaks between words (for English at least, not sure about other languages)... no wonder "The year of the linux desktop" never got anywhere

    • (Score: 0) by Anonymous Coward on Monday February 12 2018, @03:00AM

      by Anonymous Coward on Monday February 12 2018, @03:00AM (#636549)

      I count a single space in the name of this file I just loaded in VLC: %E7%AC%AC01%E8%A9%B1%20%E3%80%8C%E5%A7%8B%E3%81%BE%E3%82%8A%E3%81%A8%E7%B5%82%E3%82%8F%E3%82%8A%E3%81%AE%E3%83%97%E3%83%AD%E3%83%AD%E3%83%BC%E3%82%B0%E3%80%8D.mp4

      "Stupid freaking Windows users"? Get off of your high horse, you moron. An occasional %20 instead of a space is not *that* much of a problem, but as soon as you have non-English filenames, it's all line-noise. Unicode is 30 years old, FFS! Even browser address bars convert codes into readable characters!