I recorded several files on my previous computer, a mac powerbook G4 (PPC OS 10.3.9). But now that I have upgraded to an MacBook Pro (intel OS 10.5.4), Audacity is not reading the .aup files properly. One file an entire track is silent. Another file, the audio playback is skipping and doesn't match the visual representation.
I tried switching to the Intel version of Audacity 1.2.5, but I had the same problem. What can I do to fix this?
-Daniel
upgrading from PPC to Intel problems
Forum rules
Audacity 1.2.x is now obsolete. Please use the current Audacity 2.1.x version.
Mac 0S X 10.3 and earlier are no longer supported but you can download legacy versions of Audacity for those systems HERE.
Audacity 1.2.x is now obsolete. Please use the current Audacity 2.1.x version.
Mac 0S X 10.3 and earlier are no longer supported but you can download legacy versions of Audacity for those systems HERE.
-
kozikowski
- Forum Staff
- Posts: 69374
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Re: upgrading from PPC to Intel problems
Do you still have access to the original machine?
If you do, Export all your valuable work as WAV files and copy them over to the new machine.
It is almost impossible to move Projects. An AUP file isn't a sound file. It's an XML audio production environment management file. You can open it up in TextEdit and read it. Some of it is in English.
http://kozco.com/tech/audacity/aup1.jpg
Magnify and scroll around. Note there are directories in the programming. This is a very simple file for illustration.
It could point to a pile of other individual files that make up an Audacity Project. If you didn't bring everything over with you from the old machine and place everything in the exact same folders, then you're dead. The AUP and the _DATA folder won't do it. It's not unusual for Audacity to be standing on thousands of other little sound files all over your machine.
The blue timeline waveforms come from two picture files. They can get badly out of step with the show--especially if you manually move something.
If you don't have access to the original machine, you may have no show(s).
Koz
If you do, Export all your valuable work as WAV files and copy them over to the new machine.
It is almost impossible to move Projects. An AUP file isn't a sound file. It's an XML audio production environment management file. You can open it up in TextEdit and read it. Some of it is in English.
http://kozco.com/tech/audacity/aup1.jpg
Magnify and scroll around. Note there are directories in the programming. This is a very simple file for illustration.
It could point to a pile of other individual files that make up an Audacity Project. If you didn't bring everything over with you from the old machine and place everything in the exact same folders, then you're dead. The AUP and the _DATA folder won't do it. It's not unusual for Audacity to be standing on thousands of other little sound files all over your machine.
The blue timeline waveforms come from two picture files. They can get badly out of step with the show--especially if you manually move something.
If you don't have access to the original machine, you may have no show(s).
Koz
Re: upgrading from PPC to Intel problems
It is most likely due to damaged projects.
The information on this page should explain: http://audacityteam.org/wiki/index.php? ... ement_Tips
The information on this page should explain: http://audacityteam.org/wiki/index.php? ... ement_Tips
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: upgrading from PPC to Intel problems
I do have the original laptop computer, and the project files on that machine still work fine (but the processor is 1/4 the speed of my new computer). When I copied the files, I did copy the aup file and the data folder and the parent folder, but I deleted the backup files. And didn't pay any attention to the documents or library folders. I had no idea the wave form was based on files that weren't in the data folder.
I had originally exported the project in mp3 format, but found it had exported wrong, and I needed to export it again in both mp3 and AIFF tonight. With the aup file I could fix it in 5 min, but if I had to recreate the project file, it would have taken a whole week. When I exported the file, I had 3 tracks in the project. I wanted 2 tracks exported together, and the third was muted, But I just realized that the third track had exported as well.
-Daniel
I had originally exported the project in mp3 format, but found it had exported wrong, and I needed to export it again in both mp3 and AIFF tonight. With the aup file I could fix it in 5 min, but if I had to recreate the project file, it would have taken a whole week. When I exported the file, I had 3 tracks in the project. I wanted 2 tracks exported together, and the third was muted, But I just realized that the third track had exported as well.
-Daniel
-
waxcylinder
- Forum Staff
- Posts: 14685
- Joined: Tue Jul 31, 2007 11:03 am
- Operating System: Windows 10
Re: upgrading from PPC to Intel problems
The third muted track was exported too due to a bug im 1.2.x wherbey it ignores the mute on export - this is fixed in 1.3
Workaround:
1) Delete the muted track
2) Export the project
3) use the Audacity UNDO function to restore the muted track
WC
Workaround:
1) Delete the muted track
2) Export the project
3) use the Audacity UNDO function to restore the muted track
WC
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * *
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * *
Re: upgrading from PPC to Intel problems
Yes, that was the 5-minute fix. But I had to go back to my old computer to do it. I still need a way of moving 5 entire projects from one computer to another.
I tried manually editing the path names in the aup file. But that didn't fix the problem.
-Daniel
I tried manually editing the path names in the aup file. But that didn't fix the problem.
-Daniel
Re: upgrading from PPC to Intel problems
Checklist.
- How did I create the project?
. . I recorded (OK, data are in projectname_data directory).
. . I imported a file (not OK, Audacity takes the sound from the ORIGINAL file (this is the default configuration))
. . . . . and I changed that file afrerwards ( !!!! not OK, Audacity reads from the new version and is confused !!! )
. . . . . and I removed the file afterwards (haha, Audacity will show waveform on zoom out but does not play the sound)
. . I eddited (cut, paste, delete, effects.) (this is OK, new data are in _data, old bits remain where they are, so there might be mixture of external and internal bits).
- Audacity or computer crashed / hang ( Forget about moving elsewhere, solve AND CHECK that on the old computer first. )
A thing to check if you think all is OK:
Note that Audacity can show 'sound' even if it does not have the sound. (It collects data to show different zooms quickly.)
HOW to I check that? Don't know. Listen to whole recording, each track (simlultaneously or separately). Or zoom in (how much? - don't know) at every place. Or read .aup file and check the presense of each file individually?
Audacity 1.3.5 has, I think, "Check dependance of external files" (or how they call it) in File menu.
If it also checks actuall pressence of all block files in _data - I do not know. I suppose it does NOT, though it could.
- How did I create the project?
. . I recorded (OK, data are in projectname_data directory).
. . I imported a file (not OK, Audacity takes the sound from the ORIGINAL file (this is the default configuration))
. . . . . and I changed that file afrerwards ( !!!! not OK, Audacity reads from the new version and is confused !!! )
. . . . . and I removed the file afterwards (haha, Audacity will show waveform on zoom out but does not play the sound)
. . I eddited (cut, paste, delete, effects.) (this is OK, new data are in _data, old bits remain where they are, so there might be mixture of external and internal bits).
- Audacity or computer crashed / hang ( Forget about moving elsewhere, solve AND CHECK that on the old computer first. )
A thing to check if you think all is OK:
Note that Audacity can show 'sound' even if it does not have the sound. (It collects data to show different zooms quickly.)
HOW to I check that? Don't know. Listen to whole recording, each track (simlultaneously or separately). Or zoom in (how much? - don't know) at every place. Or read .aup file and check the presense of each file individually?
Audacity 1.3.5 has, I think, "Check dependance of external files" (or how they call it) in File menu.
If it also checks actuall pressence of all block files in _data - I do not know. I suppose it does NOT, though it could.
Last edited by jan.kolar on Tue Aug 12, 2008 1:51 pm, edited 1 time in total.
Re: upgrading from PPC to Intel problems
Checklist2.
* The platform change -- Audacity is supposed to go over smoothly.
Care was taken for by devellopers, but there might be something overlooked or something unexpected. 1.2.5 is old, is not it?
But I would create a small project OO on the old and NN on the new. Including Import of a file.
Do OO.aup and NN.aup look the same? Slash '/' is not backslash ''. (Imported files had to be check more carfully). Small and large letter differ. If space used in a filename, does it make problem? Use no strange characters, just A-Z a-z 0-9. End of the lines - oops this is a magic. CR, NL, or CR NL. Does difference make problem or not?
* There was bug with interpretting hi sample rates in .aup files (Should be fixed in 1.3.6a). But you use standard 44100, don't you?
* Somebody had a problem with strange characters in .aup file. There should be no strange things in .aup. Try to delete them.
And know:
How I think the project should be moved:
1. Do not do that if you imported files with 'no-copy' option (which is default).
2. move name.aup and name_data to the same location.
3. Before and after,
I would open the project in 1.3.5 to see what it says. No action, no save, no 'delete whatever' just open and close without
any action. (I would not with 1.3.6 most probably, after it is released : - ( )
I would try what it says about File>Check External Dependencies or how is that called.
Again, no action, just "tell me".
4. If I would like to break rule 1, I would view .aup file and see if the path there is absolute or relative.
If .aup contains something like E:blahblebloo, It is likely that I have to edit the .aup file because
the other system does not have drive E and perhaps hates double colons : in filenames.
5. If I eddit the file, does it work worse than before my edit? Did I introduce wrong newlines or " &^ $ & ^__ThisIsStarSentenceDocument__$( *^ *& %^ " header? What happens if I edit my small healthy NN.aup,
remains it alive after that?
What did you help, if anything ?
* The platform change -- Audacity is supposed to go over smoothly.
Care was taken for by devellopers, but there might be something overlooked or something unexpected. 1.2.5 is old, is not it?
But I would create a small project OO on the old and NN on the new. Including Import of a file.
Do OO.aup and NN.aup look the same? Slash '/' is not backslash ''. (Imported files had to be check more carfully). Small and large letter differ. If space used in a filename, does it make problem? Use no strange characters, just A-Z a-z 0-9. End of the lines - oops this is a magic. CR, NL, or CR NL. Does difference make problem or not?
* There was bug with interpretting hi sample rates in .aup files (Should be fixed in 1.3.6a). But you use standard 44100, don't you?
* Somebody had a problem with strange characters in .aup file. There should be no strange things in .aup. Try to delete them.
And know:
How I think the project should be moved:
1. Do not do that if you imported files with 'no-copy' option (which is default).
2. move name.aup and name_data to the same location.
3. Before and after,
I would open the project in 1.3.5 to see what it says. No action, no save, no 'delete whatever' just open and close without
any action. (I would not with 1.3.6 most probably, after it is released : - ( )
I would try what it says about File>Check External Dependencies or how is that called.
Again, no action, just "tell me".
4. If I would like to break rule 1, I would view .aup file and see if the path there is absolute or relative.
If .aup contains something like E:blahblebloo, It is likely that I have to edit the .aup file because
the other system does not have drive E and perhaps hates double colons : in filenames.
5. If I eddit the file, does it work worse than before my edit? Did I introduce wrong newlines or " &^ $ & ^__ThisIsStarSentenceDocument__$( *^ *& %^ " header? What happens if I edit my small healthy NN.aup,
remains it alive after that?
What did you help, if anything ?
-
kozikowski
- Forum Staff
- Posts: 69374
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Re: upgrading from PPC to Intel problems
<<<But I had to go back to my old computer to do it.>>>
Which brings us back to: It's almost impossible to move Audacity Projects.
Yes the blue waveforms do come from the _DATA folder. It's the first two (or more) AU files. Start a really simple project, save it, and then go in and delete the first AU file. The "Left" waveform should vanish.
There are rules of thumb for this. Certainly the AUP file and the _DATA folder in their original positions. Then move the capture folder and directory. Then you need to find every imported sound segment and clip in all the projects and put them back where they were.
All of this is assuming you have no damage. Any damage in any of those files can trash a show.
Projects are brittle and easy to damage. If you've been producing extensive, complicated shows on the old machine, they may never come off the machine short of exporting the final work.
--------------------- = | = ------------------
Since you're in OSX and have two Macs, you can create an Image of the old machine and save it on an external drive. Or, if your machines are different enough in size, save it on the main drive of the new machine. My old iBook was 20G and easily fit on my new PowerBook with the 80G internal drive.
Turn everything off. Connect the two with a FireWire cable. Turn on the old machine in Target mode by holding down the T key during startup. Start the new machine and the old machine should arrive looking like a hard drive on the desktop.
Start Disk Utilities, select the old machine and New Image it to wherever you have room.
I suspect that if you restore that image to a fresh FireWire drive, you might be able to boot to it and run Audacity and your show(s) from there.
If your new machine is a deskside, restore the image to a second fresh internal hard drive, boot to that and run your whole old production in its entirety at the speed of the new machine.
Many things are possible with the new Macs, although f you crossed the Intel/Motorola barrier, a lot of this isn't going to work.
Koz
Which brings us back to: It's almost impossible to move Audacity Projects.
Yes the blue waveforms do come from the _DATA folder. It's the first two (or more) AU files. Start a really simple project, save it, and then go in and delete the first AU file. The "Left" waveform should vanish.
There are rules of thumb for this. Certainly the AUP file and the _DATA folder in their original positions. Then move the capture folder and directory. Then you need to find every imported sound segment and clip in all the projects and put them back where they were.
All of this is assuming you have no damage. Any damage in any of those files can trash a show.
Projects are brittle and easy to damage. If you've been producing extensive, complicated shows on the old machine, they may never come off the machine short of exporting the final work.
--------------------- = | = ------------------
Since you're in OSX and have two Macs, you can create an Image of the old machine and save it on an external drive. Or, if your machines are different enough in size, save it on the main drive of the new machine. My old iBook was 20G and easily fit on my new PowerBook with the 80G internal drive.
Turn everything off. Connect the two with a FireWire cable. Turn on the old machine in Target mode by holding down the T key during startup. Start the new machine and the old machine should arrive looking like a hard drive on the desktop.
Start Disk Utilities, select the old machine and New Image it to wherever you have room.
I suspect that if you restore that image to a fresh FireWire drive, you might be able to boot to it and run Audacity and your show(s) from there.
If your new machine is a deskside, restore the image to a second fresh internal hard drive, boot to that and run your whole old production in its entirety at the speed of the new machine.
Many things are possible with the new Macs, although f you crossed the Intel/Motorola barrier, a lot of this isn't going to work.
Koz
Re: upgrading from PPC to Intel problems
I see. I'm screwed. 
I also just found the strangest
bug. I tried to "export selection as mp3". WHILE the "Save As..." dialog box was open, as I started typing in a new file name, Audacity generated a new track and started recording. The new file name was going to be "pleasurePreview.mp3".
I'm using 1.2.6a, the same version I had on my Powerbook G4 computer. And I NEVER saw this bug on the G4.
-Daniel
I also just found the strangest
bug. I tried to "export selection as mp3". WHILE the "Save As..." dialog box was open, as I started typing in a new file name, Audacity generated a new track and started recording. The new file name was going to be "pleasurePreview.mp3". I'm using 1.2.6a, the same version I had on my Powerbook G4 computer. And I NEVER saw this bug on the G4.
-Daniel