"faulty sequence tags" and shifted stereo channels

[kozikowski]

Should I upgrade (the macbook) to Sierra or would that invite more issues than it might solve?

That upgrade may take you out of forum help. I don't have a Sierra machine and I don't know any of the other elves do, either.

Koz

[kozikowski]

I think it's still true the default Audacity tries to save projects in /Applications. That's not a good idea and can lead to instability if it works at all. I do everything on the desktop and move work off to /Documents or other user folder when I'm done or have to stop work for a while.

Koz

[Gale Andrews]

Should I upgrade (the macbook) to Sierra or would that invite more issues than it might solve?

That upgrade may take you out of forum help. I don't have a Sierra machine and I don't know any of the other elves do, either.

Peter and I have Sierra, at least.

Audacity does support Sierra (see http://www.audacityteam.org/download/mac/#sysreq) - though at the moment there are problems on some machines that plugins and/or LAME and FFmpeg are blocked by Gatekeeper.


Gale

[Gale Andrews]

there is a note that "Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move" and I'm wondering whether that inadvertently happened before when the content shifted (even though I did not do any mono->stereo conversion). The .wav files have two channels by default, so even though the left & right are the same they ought to be recognised as stereo.

If you did hit that merge bug, it is fixed in 2.1.3-alpha now, so it will be fixed in 2.1.3 when released.

After editing together the tracks and saving the project, I quit audacity and then reopened by loading the project file. Got the message, "project check... detected 32 missing alias (.auf) blockfiles." I let audacity "regenerate alias summary files," saved, quit, opened again; now the project seems to be fine. So far no dislocations.

Am I getting this messages because of the wacky way I'm editing? I don't know how else to do it since there's no hold-all folder within the program for all the source files, such as in Final Cut, say. So I load each source into audacity, which of course creates a project window for it; then I copy whatever I need, paste it into my actual project, and when I'm done with the source file I close that window without saving (I don't need a project file for my raw material...). Is there a better (or correct) way of doing this that I'm missing?

On my testing of that scenario, the AUF files are not deleted from the project you pasted into, which would have to happen to produce the missing alias block files error. Where exactly are the source files (what path)?

However you are probably making it more confusing and inconvenient than it needs to be by using File > Open... for the source files, which causes each file to import into a new project. If instead you use File > Import > Audio... then the file will import into the same project instead of a new one.

Also, the AUF (alias) files are created because you have chosen to read uncompressed files (such as WAV or AIFF) directly from the file, rather than copy their data into the project. If you read directly, the source file must remain exactly where it was when you imported it into Audacity - you can't move, delete or rename the source files without corrupting your project. So consider going to Import / Export Preferences and changing the first preference at the top to "Make a copy of uncompressed audio files before editing (safer)".



Gale

[platypus67]

Thanks for all the suggestions. I have not had any more problems today since starting over, so I hope it was a gremlin that has decided to depart. One of these things probably fixed it (if it is fixed) and I'm sorry I didn't have the time to isolate which: I verified the drive (it was fine), fixed permissions (long overdue), deleted the audacity settings folder in the library, and updated to Sierra (Lame & ffmpeg working fine, phew). I look forward to 2.1.3. If I have any more insights into what happened (or the problem recurs), I will share. Cheers.

[platypus67]

Well, today during my attempt to save a new project Audacity (v2.1.2) popped up with a debug message before crashing ("SamplingTools needs to take control of another process for debugging to continue"). On restarting the program it managed to recover most of the project except for two clips, where a couple of seconds of the right channel had gone missing (I managed to replace those clips) but nothing got moved around otherwise. As you'd explained to me, that probably means a couple of .au files didn't make it. Not really sure it has anything to do with the previous issues I was having, unless these Tascam .wav files are causing issues once in a while. So maybe this doesn't even belong in this thread, but since Audacity generated a debug report my question is only, does this get sent to the developers automatically or should I find it and submit it? Cheers, G.

[Gale Andrews]

since Audacity generated a debug report my question is only, does this get sent to the developers automatically or should I find it and submit it?

The (Audacity) debug reports do not get sent to us automatically. I see you have attached them at http://forum.audacityteam.org/viewtopic ... 83#p317883. Thanks. I will ask there about that Sampling Tools message. It does not come from Audacity.


Gale