[Audacity-devel] I can't run 2.1.1 on El Capitan

Discussion:

Paul Licameli

2016-08-01 18:40:47 UTC

Perhaps a question for the Forum, but I ask here first.

I have had Audacity versions 2.1.1 and 2.1.2 downloaded to my Macbook. I
often use them when I need to compare 2.1.3 behavior with earlier versions
and understand which version introduced a regression.

Lately I upgraded from Yosemite to El Capitan. Now I can still run version
2.1.2, but not 2.1.1. Deleting audacity.cfg did not help, and restarting
did not help.

I have not yet tried reinstallation.

Has anyone else experienced this?

PRL

Cliff Scott

2016-08-01 19:48:50 UTC

Permalink

Paul,

I don’t know if this is your problem, but 2.1.1 had a problem with the temporary storage location. It only worked if you allowed it to choose the default location so if your preferences had a different directory it would not start. I have 2.1.1 and it works fine here on OSx 10.11.6. I’m using Portable Settings to keep the configurations separate so one version does to affect another.

Cliff

Post by Paul Licameli
Perhaps a question for the Forum, but I ask here first.
I have had Audacity versions 2.1.1 and 2.1.2 downloaded to my Macbook. I often use them when I need to compare 2.1.3 behavior with earlier versions and understand which version introduced a regression.
Lately I upgraded from Yosemite to El Capitan. Now I can still run version 2.1.2, but not 2.1.1. Deleting audacity.cfg did not help, and restarting did not help.
I have not yet tried reinstallation.
Has anyone else experienced this?
PRL
------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

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

Paul Licameli

2016-08-01 20:50:45 UTC

Permalink

Paul,
I donât know if this is your problem, but 2.1.1 had a problem with the
temporary storage location. It only worked if you allowed it to choose the
default location so if your preferences had a different directory it would
not start. I have 2.1.1 and it works fine here on OSx 10.11.6. Iâm using
Portable Settings to keep the configurations separate so one version does
to affect another.
Cliff

Post by Paul Licameli
Perhaps a question for the Forum, but I ask here first.
I have had Audacity versions 2.1.1 and 2.1.2 downloaded to my Macbook.

I often use them when I need to compare 2.1.3 behavior with earlier
versions and understand which version introduced a regression.

Post by Paul Licameli
Lately I upgraded from Yosemite to El Capitan. Now I can still run

version 2.1.2, but not 2.1.1. Deleting audacity.cfg did not help, and
restarting did not help.

Post by Paul Licameli
I have not yet tried reinstallation.
Has anyone else experienced this?
PRL

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

Post by Paul Licameli
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Cliff Scott

2016-08-01 21:50:47 UTC

Permalink

Are you starting with a blank setup? If youâre not already using the âPortable Settingsâ trick then I would try that to give it a totally fresh setup to start with. When the temp directory was anything other than the default it wouldnât start at all, like youâre seeing. What I was seeing at first was that I could change the temp directory and it would run until the next reboot. Then it would not start. Keeping the default temp directory solved the problem.

I was using Yosemite when 2.1.1 came out so the issue showed up there. You may have a different issue. Audacity has always worked on El Capitan here except that 2.1.1 still has the temp directory problem.

Cliff

Cliff, what I observe is that the main Audacity window never shows at all. If I click the application icon, I may briefly see the Audacity logo on the tool dock, but it disappears at once and the program exits.
PRL
Paul,
I donât know if this is your problem, but 2.1.1 had a problem with the temporary storage location. It only worked if you allowed it to choose the default location so if your preferences had a different directory it would not start. I have 2.1.1 and it works fine here on OSx 10.11.6. Iâm using Portable Settings to keep the configurations separate so one version does to affect another.
Cliff

------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel>
------------------------------------------------------------------------------
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Gale Andrews

2016-08-01 23:27:55 UTC

Permalink

Hi Cliff,

I think we prefer that bugs discussions and user experience
matters go on audacity-quality.

Anyhow, you're saying you're OK now?

I can never run 2.1.1 after latest 2.1.3-alpha because the
alpha now changes the tempdir to

/Users/<your username>/Library/Application Support/audacity/SessionData .

But deleting audacity.cfg usually solves that for me, without
creating Portable Settings folders.

Gale

Are you starting with a blank setup? If you’re not already using the
“Portable Settings” trick then I would try that to give it a totally fresh
setup to start with. When the temp directory was anything other than the
default it wouldn’t start at all, like you’re seeing. What I was seeing at
first was that I could change the temp directory and it would run until the
next reboot. Then it would not start. Keeping the default temp directory
solved the problem.
I was using Yosemite when 2.1.1 came out so the issue showed up there. You
may have a different issue. Audacity has always worked on El Capitan here
except that 2.1.1 still has the temp directory problem.
Cliff
Cliff, what I observe is that the main Audacity window never shows at all.
If I click the application icon, I may briefly see the Audacity logo on the
tool dock, but it disappears at once and the program exits.
PRL

Post by Cliff Scott
Paul,
I don’t know if this is your problem, but 2.1.1 had a problem with the
temporary storage location. It only worked if you allowed it to choose the
default location so if your preferences had a different directory it would
not start. I have 2.1.1 and it works fine here on OSx 10.11.6. I’m using
Portable Settings to keep the configurations separate so one version does to
affect another.
Cliff

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

Paul Licameli

2016-08-02 00:04:39 UTC

Permalink

Post by Gale Andrews
Hi Cliff,
I think we prefer that bugs discussions and user experience
matters go on audacity-quality.

Sorry, it was me that started this.

I upgraded my OS and 2.1.1 stopped working.

PRL

Post by Gale Andrews
Anyhow, you're saying you're OK now?
I can never run 2.1.1 after latest 2.1.3-alpha because the
alpha now changes the tempdir to
/Users/<your username>/Library/Application Support/audacity/SessionData .
But deleting audacity.cfg usually solves that for me, without
creating Portable Settings folders.

I tried deleting audacity.cfg but it did not work.

But maybe there is more than one audacity.cfg and I didn't get the correct
one. Must look closer.

PRL

Post by Gale Andrews
Gale

Post by Cliff Scott
Are you starting with a blank setup? If youâre not already using the
âPortable Settingsâ trick then I would try that to give it a totally

fresh

Post by Cliff Scott
setup to start with. When the temp directory was anything other than the
default it wouldnât start at all, like youâre seeing. What I was seeing

Post by Cliff Scott
first was that I could change the temp directory and it would run until

the

Post by Cliff Scott
next reboot. Then it would not start. Keeping the default temp directory
solved the problem.
I was using Yosemite when 2.1.1 came out so the issue showed up there.

You

Post by Cliff Scott
may have a different issue. Audacity has always worked on El Capitan here
except that 2.1.1 still has the temp directory problem.
Cliff
Cliff, what I observe is that the main Audacity window never shows at

all.

Post by Cliff Scott
If I click the application icon, I may briefly see the Audacity logo on

the

Post by Cliff Scott
tool dock, but it disappears at once and the program exits.
PRL

Paul,
I donât know if this is your problem, but 2.1.1 had a problem with the
temporary storage location. It only worked if you allowed it to choose

the

Post by Cliff Scott

default location so if your preferences had a different directory it

would

Post by Cliff Scott

not start. I have 2.1.1 and it works fine here on OSx 10.11.6. Iâm using
Portable Settings to keep the configurations separate so one version

does to

Post by Cliff Scott

affect another.
Cliff

versions

Post by Cliff Scott

Post by Paul Licameli
and understand which version introduced a regression.
Lately I upgraded from Yosemite to El Capitan. Now I can still run
version 2.1.2, but not 2.1.1. Deleting audacity.cfg did not help, and
restarting did not help.
I have not yet tried reinstallation.
Has anyone else experienced this?
PRL

Vaughan Johnson

2016-08-02 00:08:09 UTC

Permalink

thx, PRL. -- V

Post by Paul Licameli

Post by Gale Andrews
Hi Cliff,
I think we prefer that bugs discussions and user experience
matters go on audacity-quality.

Sorry, it was me that started this.
I upgraded my OS and 2.1.1 stopped working.
PRL

I tried deleting audacity.cfg but it did not work.
But maybe there is more than one audacity.cfg and I didn't get the correct
one. Must look closer.
PRL

Post by Gale Andrews
Gale

Post by Cliff Scott
Are you starting with a blank setup? If youâre not already using the
âPortable Settingsâ trick then I would try that to give it a totally

fresh

Post by Cliff Scott
setup to start with. When the temp directory was anything other than the
default it wouldnât start at all, like youâre seeing. What I was seeing

Post by Cliff Scott
first was that I could change the temp directory and it would run until

the

Post by Cliff Scott
next reboot. Then it would not start. Keeping the default temp directory
solved the problem.
I was using Yosemite when 2.1.1 came out so the issue showed up there.

You

Post by Cliff Scott
may have a different issue. Audacity has always worked on El Capitan

here

Post by Cliff Scott
except that 2.1.1 still has the temp directory problem.
Cliff
Cliff, what I observe is that the main Audacity window never shows at

all.

Post by Cliff Scott
If I click the application icon, I may briefly see the Audacity logo on

the

Post by Cliff Scott
tool dock, but it disappears at once and the program exits.
PRL

Paul,
I donât know if this is your problem, but 2.1.1 had a problem with the
temporary storage location. It only worked if you allowed it to choose

the

Post by Cliff Scott

default location so if your preferences had a different directory it

would

Post by Cliff Scott

not start. I have 2.1.1 and it works fine here on OSx 10.11.6. Iâm

using

Post by Cliff Scott

Portable Settings to keep the configurations separate so one version

does to

Post by Cliff Scott

affect another.
Cliff

Post by Paul Licameli
Perhaps a question for the Forum, but I ask here first.
I have had Audacity versions 2.1.1 and 2.1.2 downloaded to my

Macbook.

Post by Cliff Scott

Post by Paul Licameli
I often use them when I need to compare 2.1.3 behavior with earlier

versions

Post by Cliff Scott

and

Post by Cliff Scott

Post by Paul Licameli
restarting did not help.
I have not yet tried reinstallation.
Has anyone else experienced this?
PRL

Cliff Scott

2016-08-01 19:59:11 UTC

Permalink

Yesterday for the first time I did some editing using the July 20 Nightly build of 2.1.3. In putting in the Meta Tags I noticed that the “tab” key is disabled. Is that intentional? The “return” key can be used to move to the next entry, but can’t be used to move to move through the entries as the second “return” key press closes the dialog. Arrow keys work so it is useable, but I was used to the “tab” key being an easy way to move through the entries. I like the change to the Genre line so I don’t have to enter a dummy character to allow me to type in the line anymore. Anyway, just curious as to the reason for the demise of the “tab” function in that dialog.

I like the pinch gestures as well, although occasionally I don’t get all three fingers down at the same time for dragging and it thinks I’m pinching. Just a matter of the operator being use to it though.

Cliff
------------------------------------------------------------------------------

Gale Andrews

2016-08-01 23:34:17 UTC

Permalink

Post by Cliff Scott
Yesterday for the first time I did some editing using the July 20
Nightly build of 2.1.3. In putting in the Meta Tags I noticed that
the “tab” key is disabled. Is that intentional?

Thanks for the report, but again I think this should go on the
-quality list unless it needs a low level coding discussion.

We do already know about it and I anticipate we will fix it for
2.1.3:
http://bugzilla.audacityteam.org/show_bug.cgi?id=1450 .

Gale

Post by Cliff Scott
The “return” key can be used to move to the next entry, but can’t be used to move to move through the entries as the second “return” key press closes the dialog. Arrow keys work so it is useable, but I was used to the “tab” key being an easy way to move through the entries. I like the change to the Genre line so I don’t have to enter a dummy character to allow me to type in the line anymore. Anyway, just curious as to the reason for the demise of the “tab” function in that dialog.
I like the pinch gestures as well, although occasionally I don’t get all three fingers down at the same time for dragging and it thinks I’m pinching. Just a matter of the operator being use to it though.
Cliff

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

Cliff Scott

2016-08-02 01:16:31 UTC

Permalink

Hi Gale,

Regarding running on El Capitan, As you have seen, I was answering a query from Paul. I don’t have any problem because I use portable settings so the settings for 2.1.1 never change unless I choose to change them.

Sorry if this is the wrong list. I wasn’t aware of a “quality” list other than the normal forum which I can use for these types of things if you’d rather. Do I have to subscribe to the “Audacity-quality” list or just use it?

Cliff

Post by Gale Andrews

Thanks for the report, but again I think this should go on the
-quality list unless it needs a low level coding discussion.
We do already know about it and I anticipate we will fix it for
http://bugzilla.audacityteam.org/show_bug.cgi?id=1450 .
Gale

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

Gale Andrews

2016-08-02 22:44:08 UTC

Permalink

Hi Cliff,

Yes sorry I did get temporarily confused, trying out GMail
conversation view for the first time. I tried to click on the
bar for your post but hit Paul's. That was my excuse, anyway.

-quality is a subscription list like -devel. There is a read-only
archive on SourceForge and a read/write archive on Nabble:
http://audacity.238276.n2.nabble.com/audacity-quality-f7561562.html .

You can subscribe yourself to it here:
https://lists.sourceforge.net/lists/listinfo/audacity-quality .

If you prefer I just whitelist you, so you can post but you
don't receive all the messages sent to the list, let me
know off list. If you did that you could still follow and
reply to any topic you wanted by doing so on Nabble.

Thanks again for reporting issues.

Gale

Post by Cliff Scott
Hi Gale,
Regarding running on El Capitan, As you have seen, I was answering a query from Paul. I don’t have any problem because I use portable settings so the settings for 2.1.1 never change unless I choose to change them.
Sorry if this is the wrong list. I wasn’t aware of a “quality” list other than the normal forum which I can use for these types of things if you’d rather. Do I have to subscribe to the “Audacity-quality” list or just use it?
Cliff

Post by Gale Andrews

Thanks for the report, but again I think this should go on the
-quality list unless it needs a low level coding discussion.
We do already know about it and I anticipate we will fix it for
http://bugzilla.audacityteam.org/show_bug.cgi?id=1450 .
Gale

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