Best way to cause synth to ignore rebuilding of a port??

[Jan Beich]

Kevin Oberman <rkoberman at gmail.com> writes:

> On Wed, Mar 8, 2017 at 8:40 AM, Lars Engels <lars.engels at 0x20.net> wrote:
>
>> On Wed, Mar 08, 2017 at 04:34:45PM +0000, Matthew Seaman wrote:
>> > On 2017/03/08 16:04, Bob Willcox wrote:
>> > > Note that I haven't tried ver 52 of firefox, but from what I've read
>> it sounds
>> > > like all plugins/addons other than flash are no longer supported.
>> >
>> > Make that: all *NPAPI* plugins other than Flash are now unsupported.
>> > That's stuff like the Java plugin or the OpenH264 Video Codec from Cisco
>> > (which I seem to have installed and can no-longer remember why.  Some
>> > sort of video conference thing a long time ago).
>>
>> The OpenH264 plugin is shipped out of the box.

Only on Tier1 platforms (Windows, OS X, Android, Linux) where Firefox
downloads it[1] shortly after install. The situation is similar with
Widevine CDM or soon PPAPI Flash[2]. Even if someone provided FreeBSD
binaries or implemented a wrapper[3] it'd also lower security due to
lack of sandboxing[4]. WebAssembly should obsolete native code but
existing plugins are unlikely to go away in near future.

[1] Downstream builds lack patent license, see http://www.openh264.org/BINARY_LICENSE.txt 
[2] http://searchfox.org/mozilla-central/source/browser/extensions/mortar/host/flash/bootstrap.js
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1295853#c13
[4] https://wiki.mozilla.org/Security/Sandbox

> And is required for HTML5 video if it is X.264 encoded, as it most often is.

OpenH264 only supports Baseline profile and primarily used for WebRTC.
For HTML5 videos Firefox uses FFmpeg (H.264, VP9), libvpx (VP8), libtheora.

$ x264 -o bar.mp4 foo.y4m
[...]
x264 [info]: profile High, level 3.0
[...]