Agreeing that giving a 'Library' option isn't a good plan.
Not agreeing that FFMpeg is the way to go.
I have joined the opus list and posted on this topic.
On 02/11/2012 22:16, Gale Andrews wrote:
> | From Martyn Shaw <martynshaw99@...>
> | Fri, 02 Nov 2012 00:59:02 +0000
> | Subject: [Audacity-devel] Opus format
>> On 01/11/2012 05:26, Gale (Audacity Team) wrote:
>>> "Martyn Shaw-3" wrote:
>>>> I am thinking that we should add opusenc.exe and opusdec.exe to our
>>>> 'libraries' (in prefs) and then add 'Opus' to our 'Files of type:' on
>>>> import and 'Save as type:' on export (if we have the importer/exporter.
>>> Thanks for looking into this, Martyn.
>>> As you say, the libavcodec vulnerability is still an open issue. If we
>>> able to update to FFmpeg 1.0 then we get Opus encoding/decoding included
>>> with FFmpeg (if libopus is enabled)
>> True, but the FFMpeg encoding 'options' window is a confusing mass,
>> for me (and I know a little about codecs). That interface would
>> frighten off most people! I would like a nice clean interface for
>> Opus (like for MP3), since it's for 'general purpose' use, rather than
>> 'codec expert' users.
> I agree the "Custom FFmpeg Export" window is a little intimidating
> at first, but if Opus was implemented via FFmpeg, wouldn't we
> give it its own menu item "Opus Files (FFmpeg)" like the others?
FFMpeg has it's place, but it's not a 'standard'. There is an IETF
'standard' here that we can use directly. Going via a third-party is
not an option, for me.
>> and we don't worry the user with
>>> another download/installer or Libraries choice.
>> I'm thinking that we could (on Win) ship the latest opusenc.exe and
>> opusdec.exe files with any release, which would add less than 0.5MB to
>> the download, but users could use another pair of files (via prefs) if
>> they wanted to for some special reason. So no worries to the user
> If using the Libraries Prefs was not mandatory - Audacity picked
> up the binaries as long as they were in the expected location (for
> Win and Mac, probably the folder the Audacity executable was in) -,
> are there many special reasons for the extra Libraries preference?
> If we kept the opus binaries updated, the only reason I can think
> would be wanting to use a different location to keep the binaries in.
> I just wonder if we need that Libraries complication if the binaries
> are shipped integrally with no initial choice where to put them.
OK, I agree. We shouldn't add the complication of users being able to
change the library/exe via the prefs, just use the shipped versions.
>> We still have to do the work
>>> on the Opus encoding options.
>>> We already support Opus encoding by exporting using "external program",
>>> so it's only decoding that we don't yet support at all.
>> We do, but only by user knowing and typing command-line stuff. Most
>> of our users don't do that sort of thing.
> Also true, but I'm figuring Opus is still very much a niche format at
> the moment. Support among browsers and media players is still
> very incomplete (on Win). If you know enough to use VLC or Foobar
> 2000, our "external program" export shouldn't be too bad.
>>>> I am assuming that the command-line options for opusenc will remain
>>>> constant across versions so we won't have to change with any
>>>> updates, which would be a great advantage compared to FFMpeg.
>>> Indeed, but it would (IMO) be a great advantage if in the future if we
>>> could also use the FFmpeg binaries (e.g. FFmpeg.exe) that way too.
>> That's OT for me, and I don't want to get involved with FFMpeg at this
>>> Assuming the GPL-compatible licence presents no problem, eventual
>>> native support for Opus (no downloads needed) seems a goal worth
>>> aiming for?
>> No, I think that using other peoples exe files is better; less code
>> from us, more flexibility for the user. But I'm win-centric and lazy.
>> So are most of our users.
> That's exactly why I think we should make it is simple as we can
> for the lazy users (at least when Opus becomes more mainstream).
> Ideally, just a new "Opus Files" entry in the file type import or
> export choices, with no other decisions needed other than the
> Opus export options.
> It would still look "built-in" to the user if there were no LIbraries
> Preferences complications, even if we were actually using the
> shipped binaries.
> My 2p, anyhow.
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> audacity-devel mailing list