Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Oct 2013 20:07:37 +1100
From:      Kubilay Kocak <koobs.freebsd@gmail.com>
To:        David Chisnall <theraven@FreeBSD.org>,  Alexey Dokuchaev <danfe@FreeBSD.org>
Cc:        svn-ports-head@FreeBSD.org, svn-ports-all@FreeBSD.org, William Grzybowski <wg@FreeBSD.org>, ports-committers@FreeBSD.org
Subject:   Re: svn commit: r331964 - head/multimedia/vlc
Message-ID:  <5270CC59.6080002@FreeBSD.org>
In-Reply-To: <204A47D8-F1CE-4140-ABFD-5E3A47FE6660@FreeBSD.org>
References:  <201310291555.r9TFtUPK027583@svn.freebsd.org> <20131030055710.GA14262@FreeBSD.org> <204A47D8-F1CE-4140-ABFD-5E3A47FE6660@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30/10/2013 7:53 PM, David Chisnall wrote:
> On 30 Oct 2013, at 05:57, Alexey Dokuchaev <danfe@FreeBSD.org> wrote:
> 
>> On Tue, Oct 29, 2013 at 03:55:30PM +0000, William Grzybowski wrote:
>>> New Revision: 331964
>>> URL: http://svnweb.freebsd.org/changeset/ports/331964
>>>
>>>  - Disable OSS (it is broken in vlc 2.1.0 and FreeBSD #9760)
>>>  - Use pulse audio
>>
>> This makes VLC officially broken on FreeBSD.  While I only use VLC on
>> non-Unix platform (mplayer satifies my needs better elsewhere), it is
>> sad to see another popular player to go. :(
>>
>> Are there changes to fix OSS problems (and move PA back to OPTIONS,
>> where it belongs)?
> 
> I agree, this seems very unfortunate.  OSS works out of the box and provides a trivial API that does everything that VLC needs with low latency.  PulesAudio... doesn't.  What was broken with OSS upstream?  
> 
> David
> 

I think this is more a consequence of the lack of a FreeBSD environment
for upstream to keep an eye on more than anything.

wg and I did briefly talk about it with the crew @ #videolan/FreeNode
IRC last night, so they're *basically* aware, and I have been working
with them over the past month or too since picking up multimedia/x264,
which has resulted in an 2 official x264 FreeBSD buildbots.

In the meantime, perhaps a revert to 2.0.x or a vlc20/vlc21 port
distinction might prove valuable while we work with upstream to narrow
down exactly what's going on.

Either way, getting in front of the 8-ball proactively with upstream is
a far cry better than issues that come as a surprise like this.

vlc is only gone if we let it go.

Koobs



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5270CC59.6080002>