Audacity Chrash/Bug

hoffman2k · Post by **hoffman2k** » Sun Aug 29, 2004 3:29 pm

Here are the following steps to reproduce this bug.

- open Live, and select audacity as your sample editor in prefs.
- Make a sample (record a couple of tracks to one)
- choose edit in the sample clip
- Audacity will open
- Export your sample
- close Audacity

Now Live wont play anymore, it acts like it normally would. (drag and drop,......)
But pressing play doesn't do a thing.
I also have to force quit in order to stop Live.

I'm on Osx panther on a dual G4

hoffman2k · Post by **hoffman2k** » Wed Oct 13, 2004 11:23 am

this seemed to work for a while. but with the latest versions (4,03 & 4,04) it freezes after editing a clip.

osx 10,3,5
dual g5 1,8

To reproduce, just install audacity 1,2,2.
select it as sample editor. edit a clip, export the clip and go back to Live.

cheers

hoffman2k · Post by **hoffman2k** » Sat Oct 16, 2004 5:05 pm

{gleeman} · Post by **{gleeman}** » Sat Oct 16, 2004 8:09 pm

the same for me...

hoffman2k · Post by **hoffman2k** » Thu Oct 21, 2004 3:15 pm

I mailed the developers of audacity and they said it's a live 4 thing.

This is a problem in Live 4 - audacity will be working simply as an audio editor on the file you supply. Note that you will have to export the audio file you have edited, and load this exported file back to Live 4.

Richard Ash

{gleeman} · Post by **{gleeman}** » Thu Oct 21, 2004 9:06 pm

i'm not really sure it is a live bug... but i can't make any test since my laptop has smashed down to the floor

anyway... may you control if the same problem can be encountered even with other music softwares ? open another software then audacity and try to make the other sw play. can you do it ? if not maybe audacity takes too much resources and stops other programs threads or stuff like that. if you cannot reproduce the bug in other softwares, it can be a live bug.

Ralf · Post by **Ralf** » Mon Oct 25, 2004 12:47 pm

hoffman2k wrote:I mailed the developers of audacity and they said it's a live 4 thing.

This is a problem in Live 4 - audacity will be working simply as an audio editor on the file you supply. Note that you will have to export the audio file you have edited, and load this exported file back to Live 4.

Richard Ash

I digged a bit into the problem and found out that audacity is crashing Live's audio engine when started, at least if they both use CoreAudio.
This happens if Live is running and you go to the Finder and start
audacity, without even opening an audio file. So, audacity is not just
"simply working as an audio editor" here

.
Unfortunately, you cannot turn off audio in audacity.
I also tried various audacity settings, it didn't help.

Don't know what audacity is doing that crashes Live. I'd very like to
know what it is, but unfortunately I cannot promise
that I'll have the time to find out. On Windows, btw.,
audacity is not crashing Live, but has other quirks, for which I'd say,
for the moment, it's not yet the editor of choice to work with from Live.

Yours,
Ralf

PS. The other 'problems' to use audacity as an "in-place-editor"
are, IMHO:
- strange handling of file names longer that 31 characters on MacOsX
- on windows: instead of opening a second document when asked
(via OLE2 IIRC), audacity is complaining that you should not start
a second instance, and then the file is not opened
- on both platforms: the need to export to AIFF/WAV each time is a bit
frustrating, there is no single function (e.g. Command/Ctrl-S) to save
the file in place in the same format as opened

hoffman2k · Post by **hoffman2k** » Mon Oct 25, 2004 1:25 pm

Thanks for looking into it.
I found another audio editor to do these tasks and it seems to work fine.
sound studio 2. it's shareware, but at least i do not have to export the files. as like you said is pretty frustrating.

Cheers

Audacity Chrash/Bug

Audacity Chrash/Bug

bump