[Audacity-devel] Sierra: Plugins and LAME/FFmpeg not recognised

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.

I hope to update this evening and will report the results.

Cliff

Cliff Scott

2016-11-05 03:20:53 UTC

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale Andrews

2016-11-06 01:21:01 UTC

Thanks for testing, Cliff.

I'm not really clear, when Audacity did not see Nyquist plugins
previously on Sierra, was that the first time Gatekeeper had seen
Audacity? Had that Sierra startup disk ever seen previous OS X?

I "think" the AU's you mention are real-time plugins so it is correct
that they are not enabled. Audacity also doesn't support any
"aumu" instrument AU's.

Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale,
Well, the results are not what I expected.
Before I did the update I redid the initial test I reported just above this after giving the program a fresh Portable Settings and the Nyquist plugins enabled just fine so can't explain why they didn't the first time I tried.
Now, after the update, everything seems fine and all the effects can be enabled, except for 8 of the AU effects. FFmepg & LAME are ok as well. Strange thing is that on El Capitan I find those same 8 AU effects are not enabled. They can be set enabled, but after hitting OK they revert to NEW. Do you see this as well? The 8 are listed together and the first one in the group is AuSpatialMixer and the next 7 AU effects.
Cliff
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Cliff Scott

2016-11-06 03:06:37 UTC

Gale,

Unfortunately I had run other versions of Audacity on Sierra so Gatekeeper didn't complain on startup. It was a fresh install on a HD that used to have Mavericks, but it had been completely wiped for the install. If it's really important to isolate this I could do an install of Sierra 10.12.0 on an old HD to see what would happen with a brand new fresh install.

Ok, I won't worry about the plugins. Five are mixers of various types, 2 are players, 1 is a splitter which I suppose is a type of mixer as well.

On a different topic - Click track has been changed to Rhythm Track in the menu, but just noticed that it isn't yet in the manual, at least on the Effects page where it occurs twice. It may be still on the list of things to do, but I just wanted to mention it in case it had gotten overlooked.

Cliff

Post by Gale Andrews
Thanks for testing, Cliff.
I'm not really clear, when Audacity did not see Nyquist plugins
previously on Sierra, was that the first time Gatekeeper had seen
Audacity? Had that Sierra startup disk ever seen previous OS X?
I "think" the AU's you mention are real-time plugins so it is correct
that they are not enabled. Audacity also doesn't support any
"aumu" instrument AU's.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Peter Sampson

2016-11-06 09:08:36 UTC

Post by Cliff Scott
On a different topic - Click track has been changed to Rhythm Track in the

menu, but just noticed that it isn't yet in the >manual, at least on the
Effects page where it occurs twice. It may be still on the list of things
to do, but I just wanted to >mention it in case it had gotten overlooked.

That's because you are looking at the 2.1.2 Released Manual:
http://manual.audacityteam.org/man/index_of_effects_generators_and_analyzers.html
and
http://manual.audacityteam.org/man/generate_menu.html

Rather than the alpha development Manual where Steve and Gale have already
made the necessary changes
http://alphamanual.audacityteam.org/man/Index_of_Effects,_Generators_and_Analyzers
and
http://alphamanual.audacityteam.org/man/Generate_Menu

Peter

Post by Cliff Scott
Gale,
Unfortunately I had run other versions of Audacity on Sierra so Gatekeeper
didn't complain on startup. It was a fresh install on a HD that used to
have Mavericks, but it had been completely wiped for the install. If it's
really important to isolate this I could do an install of Sierra 10.12.0 on
an old HD to see what would happen with a brand new fresh install.
Ok, I won't worry about the plugins. Five are mixers of various types, 2
are players, 1 is a splitter which I suppose is a type of mixer as well.
On a different topic - Click track has been changed to Rhythm Track in the
menu, but just noticed that it isn't yet in the manual, at least on the
Effects page where it occurs twice. It may be still on the list of things
to do, but I just wanted to mention it in case it had gotten overlooked.
Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the

initial install. Nyquist plugins were not allowed to be enabled. They
showed up in the Add/Remove Plugins window, but enable would not stick.
Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was
able to export to an MP3 file.

Post by Cliff Scott
I hope to update this evening and will report the results.
Cliff

Gale,
Well, the results are not what I expected.
Before I did the update I redid the initial test I reported just above

this after giving the program a fresh Portable Settings and the Nyquist
plugins enabled just fine so can't explain why they didn't the first time I
tried.

Post by Cliff Scott
Now, after the update, everything seems fine and all the effects can be

enabled, except for 8 of the AU effects. FFmepg & LAME are ok as well.
Strange thing is that on El Capitan I find those same 8 AU effects are not
enabled. They can be set enabled, but after hitting OK they revert to NEW.
Do you see this as well? The 8 are listed together and the first one in the
group is AuSpatialMixer and the next 7 AU effects.

Post by Cliff Scott
Cliff
------------------------------------------------------------

------------------

Post by Cliff Scott
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------

------------------

Post by Gale Andrews
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Cliff Scott

2016-11-06 12:52:35 UTC

Actually I'm using a build I did on Nov 2nd which builds the help and it says 2.1.3 Alpha Manual. Apparently once built it does not update the manual on subsequent builds. In any case I'm glad the changes have been made.

Cliff

On a different topic - Click track has been changed to Rhythm Track in the menu, but just noticed that it isn't yet in the >manual, at least on the Effects page where it occurs twice. It may be still on the list of things to do, but I just wanted to >mention it in case it had gotten overlooked.

http://manual.audacityteam.org/man/index_of_effects_generators_and_analyzers.html <http://manual.audacityteam.org/man/index_of_effects_generators_and_analyzers.html>
and
http://manual.audacityteam.org/man/generate_menu.html <http://manual.audacityteam.org/man/generate_menu.html>
Rather than the alpha development Manual where Steve and Gale have already made the necessary changes
http://alphamanual.audacityteam.org/man/Index_of_Effects,_Generators_and_Analyzers <http://alphamanual.audacityteam.org/man/Index_of_Effects,_Generators_and_Analyzers>
and
http://alphamanual.audacityteam.org/man/Generate_Menu <http://alphamanual.audacityteam.org/man/Generate_Menu>
Peter
Gale,
Unfortunately I had run other versions of Audacity on Sierra so Gatekeeper didn't complain on startup. It was a fresh install on a HD that used to have Mavericks, but it had been completely wiped for the install. If it's really important to isolate this I could do an install of Sierra 10.12.0 on an old HD to see what would happen with a brand new fresh install.
Ok, I won't worry about the plugins. Five are mixers of various types, 2 are players, 1 is a splitter which I suppose is a type of mixer as well.
On a different topic - Click track has been changed to Rhythm Track in the menu, but just noticed that it isn't yet in the manual, at least on the Effects page where it occurs twice. It may be still on the list of things to do, but I just wanted to mention it in case it had gotten overlooked.
Cliff

Thanks for testing, Cliff.
I'm not really clear, when Audacity did not see Nyquist plugins
previously on Sierra, was that the first time Gatekeeper had seen
Audacity? Had that Sierra startup disk ever seen previous OS X?
I "think" the AU's you mention are real-time plugins so it is correct
that they are not enabled. Audacity also doesn't support any
"aumu" instrument AU's.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale,
Well, the results are not what I expected.
Before I did the update I redid the initial test I reported just above this after giving the program a fresh Portable Settings and the Nyquist plugins enabled just fine so can't explain why they didn't the first time I tried.
Now, after the update, everything seems fine and all the effects can be enabled, except for 8 of the AU effects. FFmepg & LAME are ok as well. Strange thing is that on El Capitan I find those same 8 AU effects are not enabled. They can be set enabled, but after hitting OK they revert to NEW. Do you see this as well? The 8 are listed together and the first one in the group is AuSpatialMixer and the next 7 AU effects.
Cliff
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi <http://sdm.link/xeonphi>
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi <http://sdm.link/xeonphi>
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Peter Sampson

2016-11-06 15:55:16 UTC

Post by Cliff Scott
Actually I'm using a build I did on Nov 2nd which builds the help and it

says 2.1.3 Alpha Manual.

Hmmm that's odd those changes were made while I was away last week of
September and
first week of October. :-//

Peter.

Post by Cliff Scott
Actually I'm using a build I did on Nov 2nd which builds the help and it
says 2.1.3 Alpha Manual. Apparently once built it does not update the
manual on subsequent builds. In any case I'm glad the changes have been
made.
Cliff

Post by Cliff Scott
On a different topic - Click track has been changed to Rhythm Track in

the menu, but just noticed that it isn't yet in the >manual, at least on
the Effects page where it occurs twice. It may be still on the list of
things to do, but I just wanted to >mention it in case it had gotten
overlooked.
http://manual.audacityteam.org/man/index_of_effects_
generators_and_analyzers.html
and
http://manual.audacityteam.org/man/generate_menu.html
Rather than the alpha development Manual where Steve and Gale have already
made the necessary changes
http://alphamanual.audacityteam.org/man/Index_of_Effects,_Generators_and_
Analyzers
and
http://alphamanual.audacityteam.org/man/Generate_Menu
Peter

Post by Cliff Scott
Gale,
Unfortunately I had run other versions of Audacity on Sierra so
Gatekeeper didn't complain on startup. It was a fresh install on a HD that
used to have Mavericks, but it had been completely wiped for the install.
If it's really important to isolate this I could do an install of Sierra
10.12.0 on an old HD to see what would happen with a brand new fresh
install.
Ok, I won't worry about the plugins. Five are mixers of various types, 2
are players, 1 is a splitter which I suppose is a type of mixer as well.
On a different topic - Click track has been changed to Rhythm Track in
the menu, but just noticed that it isn't yet in the manual, at least on the
Effects page where it occurs twice. It may be still on the list of things
to do, but I just wanted to mention it in case it had gotten overlooked.
Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Sierra,

Post by Gale Andrews
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the

Post by Cliff Scott
I hope to update this evening and will report the results.
Cliff

Gale,
Well, the results are not what I expected.
Before I did the update I redid the initial test I reported just above

this after giving the program a fresh Portable Settings and the Nyquist
plugins enabled just fine so can't explain why they didn't the first time I
tried.

Post by Cliff Scott
Now, after the update, everything seems fine and all the effects can

be enabled, except for 8 of the AU effects. FFmepg & LAME are ok as well.
Strange thing is that on El Capitan I find those same 8 AU effects are not
enabled. They can be set enabled, but after hitting OK they revert to NEW.
Do you see this as well? The 8 are listed together and the first one in the
group is AuSpatialMixer and the next 7 AU effects.

Post by Cliff Scott
Cliff
------------------------------------------------------------

------------------

------------------------------------------------------------

------------------

------------------------------------------------------------
------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi_______
________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
------------------------------------------------------------
------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Cliff Scott

2016-11-06 22:56:20 UTC

Peter,

I don't know on the Windows platform, but when building for the Mac there is a script that builds the manual, but I've only seen it run once when it first worked for me so I think it just looks and sees that the files are there so doesn't take the time to download and build it again. Probably if I deleted the manual files it would get the current ones.

73,
Cliff Scott
AE5ZA

Post by Cliff Scott
Actually I'm using a build I did on Nov 2nd which builds the help and it says 2.1.3 Alpha Manual.

Hmmm that's odd those changes were made while I was away last week of September and
first week of October. :-//
Peter.
Actually I'm using a build I did on Nov 2nd which builds the help and it says 2.1.3 Alpha Manual. Apparently once built it does not update the manual on subsequent builds. In any case I'm glad the changes have been made.
Cliff

Thanks for testing, Cliff.
I'm not really clear, when Audacity did not see Nyquist plugins
previously on Sierra, was that the first time Gatekeeper had seen
Audacity? Had that Sierra startup disk ever seen previous OS X?
I "think" the AU's you mention are real-time plugins so it is correct
that they are not enabled. Audacity also doesn't support any
"aumu" instrument AU's.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale,
Well, the results are not what I expected.
Before I did the update I redid the initial test I reported just above this after giving the program a fresh Portable Settings and the Nyquist plugins enabled just fine so can't explain why they didn't the first time I tried.
Now, after the update, everything seems fine and all the effects can be enabled, except for 8 of the AU effects. FFmepg & LAME are ok as well. Strange thing is that on El Capitan I find those same 8 AU effects are not enabled. They can be set enabled, but after hitting OK they revert to NEW. Do you see this as well? The 8 are listed together and the first one in the group is AuSpatialMixer and the next 7 AU effects.
Cliff
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi <http://sdm.link/xeonphi>
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi <http://sdm.link/xeonphi>
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi_______________________________________________ <http://sdm.link/xeonphi_______________________________________________>
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>

Gale Andrews

2016-11-07 01:56:30 UTC

I'm planning to test sometime on a fresh install of Sierra that has never seen
Audacity then try 2.1.3-alpha. However we do know that 2.1.0 and 2.1.2 have
been reported with the same issue. It won't hurt if you have time to
try it too.

Gale

Post by Cliff Scott
Ok, I won't worry about the plugins. Five are mixers of various types, 2 are players, 1 is a splitter which I suppose is a type of mixer as well.
On a different topic - Click track has been changed to Rhythm Track in the menu, but just noticed that it isn't yet in the manual, at least on the Effects page where it occurs twice. It may be still on the list of things to do, but I just wanted to mention it in case it had gotten overlooked.
Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Cliff Scott

2016-11-11 20:46:23 UTC

Gale,

Just installed Sierra 10.12.1 to a fresh HD. Loaded Audacity 2.1.3 built 11/2/16 and it starts without Gatekeeper complaining at all. At that time I didn't have FFMpeg or Lame installed. Installed them and Audacity found them just fine. All effects were picked up including 2 that I added to the Plugins directory. In summary, I find no issues at all. Gatekeeper complains about some other software I loaded after that, but the usual RMB and Open allowed them to run. Not sure what the deal is as this build isn't signed, but Gatekeeper doesn't complain. Must be something else involved that I don't understand.

Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale Andrews

2016-11-11 22:05:18 UTC

Thanks for testing, Cliff. Is this an external hard drive? Might Gatekeeper be
looking at settings in other partitions somewhere?

It's possible using the terminal to remove Gatekeeper's saved policies for
certain applications but I found that quite buggy last time I tried it.

Gale

Post by Cliff Scott
Gale,
Just installed Sierra 10.12.1 to a fresh HD. Loaded Audacity 2.1.3 built 11/2/16 and it starts without Gatekeeper complaining at all. At that time I didn't have FFMpeg or Lame installed. Installed them and Audacity found them just fine. All effects were picked up including 2 that I added to the Plugins directory. In summary, I find no issues at all. Gatekeeper complains about some other software I loaded after that, but the usual RMB and Open allowed them to run. Not sure what the deal is as this build isn't signed, but Gatekeeper doesn't complain. Must be something else involved that I don't understand.
Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Cliff Scott

2016-11-11 22:59:15 UTC

This is on an external HD.

I don't think it's looking at the other HD for Gatekeeper because Audacity 2.1.2 exhibits the problem. Gatekeeper complained when I tried to open it. The normal RMB, Open got it to run, but the Nyquist plugins could not be activated.

Cliff

Post by Gale Andrews
Thanks for testing, Cliff. Is this an external hard drive? Might Gatekeeper be
looking at settings in other partitions somewhere?
It's possible using the terminal to remove Gatekeeper's saved policies for
certain applications but I found that quite buggy last time I tried it.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale Andrews

2016-11-11 23:37:17 UTC

The problem of disabled plugins has definitely been reported in recent
2.1.3-alpha, after the user ran 2.1.2.

Gale

Post by Cliff Scott
This is on an external HD.
I don't think it's looking at the other HD for Gatekeeper because Audacity 2.1.2 exhibits the problem. Gatekeeper complained when I tried to open it. The normal RMB, Open got it to run, but the Nyquist plugins could not be activated.
Cliff

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Cliff Scott

2016-11-11 23:51:30 UTC

Ok. Will test that sequence. I ran 2.1.3 first. Possibly having 2.1.2 installed with the problem causes 2.1.3 to inherit the problem if using the same config.

Cliff

Post by Gale Andrews
The problem of disabled plugins has definitely been reported in recent
2.1.3-alpha, after the user ran 2.1.2.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Cliff Scott

2016-11-12 04:30:01 UTC

Gale,

Well, I can't prove anything here.

Went back and deleted all Audacity installs and the Audacity directory in Application Support. Installed 2.1.2 and it had the usual problem of no Nyquist plugins. Everything else seems ok. Installed 2.1.3A over it and it picked up the Nyquist plugins. Something in the 2.1.2 installs runs foul of Gatekeeper or something related that the Nyquist plugins are not recognized. 2.1.3 doesn't have that problem. I certainly don't have any idea of what could be the issue. Maybe being at 10.12.1 level makes a difference. Don't have a 10.12.0 install anymore to try. I suspect most if not all Sierra users will be at the 10.12.1 level by the time 2.1.3 is released. Are we fighting a ghost here? Could you, Gale, contact someone that reported the problem and see if it still exists after they do the update to Sierra?

Cliff

Post by Gale Andrews
The problem of disabled plugins has definitely been reported in recent
2.1.3-alpha, after the user ran 2.1.2.
Gale

[...]

I imagine that requiring cryptic terminal commands is not only
"inconvenient" but way beyond most Mac users.

Are we any clearer why that happens on some Sierra machines and
not others? Does it always happen on a new Sierra install that is not
an upgrade from earlier OS X and so has no previous version of
Audacity? My Sierra is an upgrade and I don't have the issue.
Do we understand why rebooting or executing the Audacity shell app
can also (usually) work around it?
If we moved the "Nyquist" and "Plug-ins" folders inside the bundle,
and recommended LAME and FFmpeg installers that installed
inside the Audacity bundle, would that solve it?
My guess is that this is not repeatable. There don't seem to
be enough complaints.
*If* this is really repeatable for any new user of Audacity on Sierra,
and if we could do something to prevent users having to use the
Terminal (such as changing the bundle or the recommended
LAME/FFmpeg installers) then I think we would have to track
this on Bugzilla at minimum P2.
It's also possible that a fully codesigned DMG might already
have solved at least the Nyquist plugins issue, so that's another
reason for making a codesigned installer available tor
pre-RC testing.
Gale

FYI, tried on my Sierra which has not been updated yet from the initial install. Nyquist plugins were not allowed to be enabled. They showed up in the Add/Remove Plugins window, but enable would not stick. Lame & FFmpeg appeared to be ok. Looked normal in Preferences and I was able to export to an MP3 file.
I hope to update this evening and will report the results.
Cliff

Gale Andrews

2016-11-12 14:11:58 UTC

Thanks again for testing. Well, Steve reported the issue and he is
easily contactable.
Perhaps he can try again in 10.12.1 newly installed on a fresh drive.

Regardless, this is something we will want to test again when there is
a codesigned 2.1.3 installer available for pre-release testing.

Gale

Post by Cliff Scott
Gale,
Well, I can't prove anything here.
Went back and deleted all Audacity installs and the Audacity directory in Application Support. Installed 2.1.2 and it had the usual problem of no Nyquist plugins. Everything else seems ok. Installed 2.1.3A over it and it picked up the Nyquist plugins. Something in the 2.1.2 installs runs foul of Gatekeeper or something related that the Nyquist plugins are not recognized. 2.1.3 doesn't have that problem. I certainly don't have any idea of what could be the issue. Maybe being at 10.12.1 level makes a difference. Don't have a 10.12.0 install anymore to try. I suspect most if not all Sierra users will be at the 10.12.1 level by the time 2.1.3 is released. Are we fighting a ghost here? Could you, Gale, contact someone that reported the problem and see if it still exists after they do the update to Sierra?
Cliff

Post by Gale Andrews
The problem of disabled plugins has definitely been reported in recent
2.1.3-alpha, after the user ran 2.1.2.
Gale