Erik's Problems With Audacity, or any other software |
|
Erik's Problems With Audacity, or any other software |
|
|
|
|
Sep 23 2007, 01:59 AM |
if it's not a problem I would like to warn people here about audacity.. It is free for a reason, it keeps chrashing (especially the mac version). The PC version also chrashes, once me and the band lost hours and hours of recording because it chrashed during export.. I didn't want to save the project, because saving often causes problems in audacity.. So I would not recomend it. As a suggestion EriK - contact Audacity and provide them with as much detail as you can. That way they may be able to bug fix and supply a hotfix if it is indeed an issue with Audacity. If they don't know about it though then they can't attempt to fix it. Working with the team will benefit other users by helping develop a more robust product. This goes really for ANY software commercial, shareware or freeware. Indeed if you look at the forum boards of the majority (probably all) the commercial daws you will find people logging issues, particularly after a new version has been released. To put this in to some context - the number of possible hardware permutations that a pc can be made from is massive - get one bit wrong and you may not achieve compatibility between hardware and software. Add to that potential software (and user installation) clashes/issues and beta testing a complicated program becomes a massive endeavor and frankly pretty much impossible to ensure 100%. I'm certainly not suggesting that Audacity is perfect, or that it might not be behind the problems that Erik has encountered - it may be - but give the developers information and try to let them work on a fix. As to why Audacity is free - it is free because the developers believe in and support open source software and no other reason. By being free it has enabled many users to try out music and broadcast production who otherwise may never have been able. Cheers, Tony -------------------- Get your music professionally mastered by anl AES registered Mastering Engineer. Contact me for Audio Mastering Services and Advice and visit our website www.miromastering.com
Be friends on facebook with us here. We use professional, mastering grade hardware in our mastering studo. Our hardware includes: Cranesong Avocet II Monitor Controller, Dangerous Music Liasion Insert Hardware Router, ATC SCM Pro Monitors, Lavry Black DA11, Prism Orpheus ADC/DAC, Gyratec Gyraf XIV Parallel Passive Mastering EQ, Great River MAQ 2NV Mastering EQ, Kush Clariphonic Parallel EQ Shelf, Maselec MLA-2 Mastering Compressor, API 2500 Mastering Compressor, Eventide Eclipse Reverb/Echo. |
|
|
||
|
|
|
Sep 23 2007, 03:05 AM |
Interesting -
Installed the 1.3beta on 25 pcs of differing hardware configurations for a radio production course here in July Erik and had no issues. Suggest your school IT bod talks to Audacity as I'm sure they'd be interested in what the issue might be. Cheers, Tony -------------------- Get your music professionally mastered by anl AES registered Mastering Engineer. Contact me for Audio Mastering Services and Advice and visit our website www.miromastering.com
Be friends on facebook with us here. We use professional, mastering grade hardware in our mastering studo. Our hardware includes: Cranesong Avocet II Monitor Controller, Dangerous Music Liasion Insert Hardware Router, ATC SCM Pro Monitors, Lavry Black DA11, Prism Orpheus ADC/DAC, Gyratec Gyraf XIV Parallel Passive Mastering EQ, Great River MAQ 2NV Mastering EQ, Kush Clariphonic Parallel EQ Shelf, Maselec MLA-2 Mastering Compressor, API 2500 Mastering Compressor, Eventide Eclipse Reverb/Echo. |
|
|
||
|
|
|
Sep 25 2007, 02:39 AM |
Sounds like you might have an internal feedback loop going on Steve. That would produce both the noise you're experiencing and crash the sequencer (it would crash any sequencer tbh).
Cheers, Tony -------------------- Get your music professionally mastered by anl AES registered Mastering Engineer. Contact me for Audio Mastering Services and Advice and visit our website www.miromastering.com
Be friends on facebook with us here. We use professional, mastering grade hardware in our mastering studo. Our hardware includes: Cranesong Avocet II Monitor Controller, Dangerous Music Liasion Insert Hardware Router, ATC SCM Pro Monitors, Lavry Black DA11, Prism Orpheus ADC/DAC, Gyratec Gyraf XIV Parallel Passive Mastering EQ, Great River MAQ 2NV Mastering EQ, Kush Clariphonic Parallel EQ Shelf, Maselec MLA-2 Mastering Compressor, API 2500 Mastering Compressor, Eventide Eclipse Reverb/Echo. |
|
|
||
|
|
|
Sep 26 2007, 07:01 PM |
If it's feedback Steve it's most probably because at some stage the inputs and outputs of Audacity have become connected causing an internal loop. You need to break that loop to stop it. Otherwise what happens is that the output signal is routed to the input, re-recorded and possibly amplified, sent back to the output only to reappear at the input - ad infinitum up to the point where the system overloads and crashes.
In the first instance I'd check how your recording input and monitoring output are assigned in Audacity and assign them to different channels. The detail in Audacity is in Preferences>Audio. If its not this then it may be how your soundcard is set up either in software or physically. Cheers, Tony -------------------- Get your music professionally mastered by anl AES registered Mastering Engineer. Contact me for Audio Mastering Services and Advice and visit our website www.miromastering.com
Be friends on facebook with us here. We use professional, mastering grade hardware in our mastering studo. Our hardware includes: Cranesong Avocet II Monitor Controller, Dangerous Music Liasion Insert Hardware Router, ATC SCM Pro Monitors, Lavry Black DA11, Prism Orpheus ADC/DAC, Gyratec Gyraf XIV Parallel Passive Mastering EQ, Great River MAQ 2NV Mastering EQ, Kush Clariphonic Parallel EQ Shelf, Maselec MLA-2 Mastering Compressor, API 2500 Mastering Compressor, Eventide Eclipse Reverb/Echo. |
|
|
||