Audacity Forum

I'm using 1.2.6. I just finished an original song with drums, piano, and multiple vocal and guitar tracks. Problem is that everyone that has heard it, including myself thinks it should be a little slower. I've selected all the tracks, used change tempo, and slowed it down a couple beats per minute, but then all the tracks are out of synch and run at different tempos. I believe that Audacity only uses the length of the first track selected to calculate and thus applies a wrong change percentage to all other tracks. Short of mixing all the tracks down to one track(which I really don't want to do), does anyone know a solution to this problem?

I've just tried it in Audacity 1.3.8 and it will change the tempo of all selected tracks correctly.

Yeeeeeyy.....er....hold on.....awe crap. I appreciate the idea steve. I changed the tempo, started listening and the rythem guitar, piano, and drums seemed right on, then the solo came in off time and the three other guitar fills near the end came in off too. Not sure what thats about. Also the tempo change seems to have effected the quality as far as a garble in the background static/high end. I may have to play with it a little. Otherwise I could just rerecord those guitar parts. Ugg, trying to get the guitar sound just right was a pain. I may work on it tomorrow, its late. I'll post my results. Thanks again steve. Btw, anyone found any reason not to use 1.3.8 as far as stability or function issues?

hughjass wrote:anyone found any reason not to use 1.3.8 as far as stability or function issues?

Some users have experienced a few teething issues with 1.3.8, though it seems pretty stable so far on my machine.
The main issues appear to be:
1) If the computer already has VST plug-ins installed, there may be problems (Audacity won't open or crashes straight away) if any of the VSTs are incompatible with Audacity.
2) In some cases Audacity fails to start due to what looks like an installation error. If you get this type of problem, more information, and the fix can be found here: http://forum.audacityteam.org/viewtopic ... 745#p45745

Other than that it's looking good (and I love the new Mixer).

Of course the developers are working hard to resolve these issues and nightly releases are available for testing. It is probably worth trying and the chances are that you will be lucky and have no problems with it. If any problems do arise, let us know, or just go back to 1.2 for a while.

Ok, update. Step forward, step back. I went into each track and generated silence at the front and back end until they were all exactly the same lenth. Ran change tempo and yeah!, everything stays in synch. So after all that I go to save the project (which was created in 1.2.6 and opened through 1.3.8) and it tells me Can't save.The project is not writable or my disk is full. Well my disk certainly isn't full. Maybe I open both and copy/paste each track from 1.2.6 to 1.3.8? Have to try that later....any other suggestions would be appreciated. I'm leaving the project open till then.

Nother update. Hopefully my trial and error will help others. Well I opened up my 1.2.6 project in 1.3.8 and while unable to save it, I was able to open another 1.3.8 and copy the tracks over to that one and then save. Sweet right. Well then I made a few changes and went to save again and got the same "Could not save project. Perhaps D:audacityfilename is not writable or the disk is full". Anyone have an idea what thats all about? I have 100s of Gigs of space and it seems hap hazzard as to when this comes up. I'd hate to put more work into this and get stuck not being able to save again. Help?

hughjass wrote:went to save again and got the same "Could not save project. Perhaps D:audacityfilename is not writable or the disk is full". Anyone have an idea what thats all about? I have 100s of Gigs of space and it seems hap hazzard as to when this comes up.

Is D: an internal or external hard drive? (not sure how much of a difference this will make, but trying to build up a picture of what's going on).
What filename are you using for the project?
How much space is there on your C: drive?

335 Gigs free space. D is an internal HD. File name is "nexttoyouXX". XX being a number(I increase the number everytime I save. I think I'm on 14) I did the "open it through 1.3.8 and then open another 1.3.8 and copy the tracks over" thing with another song and it seems to be working. Not sure what the difference is, and its a pain, but I do like the useablility of 1.3.8 better and prefer using it. Haven't really messed with nexttoyou since I last posted, but it is currently saved in 1.3.8. Just curious if its a revision compatibility thing or if its my computer/something I'm doing. must sleep. Been watching old Overkill and nuclear assault videos on you tube. Not sure how that happened.

hughjass wrote:File name is "nexttoyouXX". XX being a number(I increase the number everytime I save. I think I'm on 14)

I presume that is "nexttoyou14" without the quotes.
Numbering each Save is a very good idea - it eats up a lot of disk space but provides a back trace of "restore points" in case anything goes wrong. (I do the same).

hughjass wrote:Just curious if its a revision compatibility thing or if its my computer/something I'm doing.

As far as I can tell it's not something that you are doing, but the only version compatibility issue that I'm aware of is that Audacity 1.2 can not open Audacity 1.3 projects. As far as I know Audacity 1.3.8 should be able to open projects from Audacity 1.2 or any previous version of 1.3

hughjass wrote:but it is currently saved in 1.3.8.

So you managed to Save the project in the end. You were saying that it would not save - did you have to do something different to make it save?

Yeah, I had to open my 1.2.6 project through 1.3.8 and then open another 1.3.8, then copy each track over to the newly opened 1.3.8. I had the old problem again once, but then I did two things (so I'm not sure which one did it), I went to the audacity folder where all my data was saved and deleted 5 or 6 project files along with their data files and then..heh...changed the name to "nexttoyoupleasework" instead of "nexttoyouxx" (with no quotes in the actual file). Should I be posting this in the 1.3.8 unstable forum? When I started this post It was a 1.2.6 issue and it has kind of evolved.