No no no, that's not what I meant at all. Many apologies if that's the way it came over.Cody wrote:OK... I get it .. I'll go away ...
koz and myself have no ownership of this product - it is your product just as much as it is mine.
We are all trying to get Audacity to work with your system. What I was saying was that in troubleshooting a problem it is necessary to eliminate possible causes until the root of the problem becomes evident.
The fact that it works fine with Pyro tells us that it is not a hardware problem (one possible cause eliminated).
70 GB free drive space - you could be running into problems here if you are editing multiple albums one after the other without closing Audacity in between each project. 1 album recorded at 48kHz 32 bit is around 2 GB. Normalize it and because of the "undo" data it's up to 4 gig. Run the noise removal and click removal and Eq it and you are up to about 10 gig. Repeat for another 2 albums and you are up to 30 gig - nearly half of your available space. Also Windows machines should always have at least 10% disk space free. 70 GB sounds like a lot, but if you are editing multiple albums you can rapidly use it up. This is one reason why it is important to close Audacity between projects. (one more possible cause eliminated).
This is sounding increasingly likely - the way to determine this is, as MDOC has said, by a process of elimination.MDOC wrote:There could be a software conflict in your system.
If it does, then at least you have a viable workaround as a last resort - Record in Pyro, edit in Audacity. Not an ideal solution, and it would certainly be better if we could resolve the issues.stevethefiddle wrote:Does Audacity work with the USB turntable disconnected?
Did I mention that on my XP machine, Audacity 1.3.4 was the most stable (no crashes ever). This version is still available for download.