On Oct 29, 2018, at 22:03, Michael wrote:
> On 2018-10-29, at 7:47 PM, Ryan Schmidt wrote:
>
>> On Oct 29, 2018, at 21:26, Michael wrote:
>>
>>> So two things when I attempted to update macports and ffmpeg.
>>>
>>> Number 1: There was a HUGE chain of things to update first. Surprising to
>>
On 29 Oct 2018, at 23:07, Michael wrote:
So for what it's worth, after writing this out and going over what it
takes, I have ffmpeg finally working:
x264 @20171225_0 (active)
x265 @2.8_1 (active)
x265 @2.9_0
Something has to be out of date, and at least this is the least out of
date.
sh-3.2$ port installed ffmpeg
The following ports are currently installed:
ffmpeg @4.0.2_1+gpl2+x11 (active)
sh-3.2$ type ffmpeg
ffmpeg is /opt/local/bin/ffmpeg
sh-3.2$ otool -L /opt/local/bin/ffmpeg | grep libx2
/opt/local/lib/libx264.152.dylib (compatibility version 0.0.0, current
ve
So for what it's worth, after writing this out and going over what it takes, I
have ffmpeg finally working:
x264 @20171225_0 (active)
x265 @2.8_1 (active)
x265 @2.9_0
Something has to be out of date, and at least this is the least out of date.
On 2018-10-29, at 7:47 PM, Ryan Schmidt wro
On 2018-10-29, at 7:47 PM, Ryan Schmidt wrote:
> On Oct 29, 2018, at 21:26, Michael wrote:
>
>> So two things when I attempted to update macports and ffmpeg.
>>
>> Number 1: There was a HUGE chain of things to update first. Surprising to me
>> was what looked like all of Xwindows.
>>
>> XWi
On Oct 29, 2018, at 21:26, Michael wrote:
> So two things when I attempted to update macports and ffmpeg.
>
> Number 1: There was a HUGE chain of things to update first. Surprising to me
> was what looked like all of Xwindows.
>
> XWindows? Why?
>
> After X, it updated openssl, then sqlite3, t
