rendering leaves out one track

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
borg nagar
Posts: 53
Joined: Sat Apr 16, 2005 12:42 pm
Contact:

rendering leaves out one track

Post by borg nagar » Tue Apr 19, 2005 8:10 pm

For some reason the render to disk leaves out one audio track, which has a long wav file. It plays correctly and should be there in the sequence, but for some reason it doesn't get rendered. I've tried editing the wav and resaving, but that doesn't help.

I've got live 4.1.2, winXPsp2.

:edit: ok now i soloed the missing track and rendered it... the result is just really loud and high beep... almost like triangle wave, with the left channel much louder than the right.

:edit2: I got it rendered now after about ten attempts. I think Live was unable to write to the file, because all the warp markers changed back to defaults every time I opened the live set. So I saved the file with a new name and loaded it from the file browser into the set.

This was not the first time I encounter this problem. The audio file was recorded in live from an external input.

borg nagar
Posts: 53
Joined: Sat Apr 16, 2005 12:42 pm
Contact:

Very loud beep when rendering

Post by borg nagar » Fri Sep 09, 2005 2:19 pm

Now I'm having the same situation with Live 5. I'm trying to render a live set which normally plays good and doesn't seem to have any problems. But after rendering I get several notifications of "serious program error" and have to shutdown live from task manager. When I open the rendered wav, it's accompanied with a very high and loud beep. Looking at my previous post on the subject it seems I have been able to locate the problem by renaming the wav files in the liveset (but at that time I knew which file caused it).

Anyone have similar experiences? This has happened to me on 2 separate computers and 2 separate sound interfaces now.

:edit: I read this topic: http://www.ableton.com/forum/viewtopic.php?t=26354 and noted that timothyallan had almost the same kind of problem as I did. My problem was also solved the same way this time: I put all of my wav-tracks into RAM-mode. And they rendered fine. Thanks Timothy!

timothyallan
Posts: 5788
Joined: Wed Nov 24, 2004 11:05 pm
Location: Melbourne Australia
Contact:

Post by timothyallan » Sat Sep 10, 2005 11:45 pm

glad i could help! ;)

I contacted Ableton about this, but it's very hard to reproduce so I don't think the bug is going to get fixed anytime soon...

nice that you got it going though!

Cheers,
Tim

Locked