Problem when Rendering

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
David
Posts: 665
Joined: Sat Oct 26, 2002 6:53 pm

Problem when Rendering

Post by David » Thu Aug 05, 2004 10:54 am

Hi there,

Having a slight issue when rendering. Last night I rendered off a whole track but the first bar would never render correctly. This was occuring when I was rendering from midi to audio with VSTi's, not audio to audio.

It just seems to happen with exactly the first bar, thereafter everything renders fine.

Please refer to the snapshot for a clearer picture.

Thanks,

David

Image

_David

Post by _David » Thu Aug 05, 2004 3:05 pm

Hi,

Here is some further info. I didnt include with my first post:-

- Live Version 4

- Render Settings: Normalize (Off), Render as Loop (Off), File Type (Wav), Bit Depth (24Bit), Sample Rate (44.1kHz), Create Analysis File (Off), Convert To Mono (Off)

- Audio Hardware - Built in Laptop Soundcard (Toshiba Satellite Laptop - SoundMax Digital Audio DX)
- Audio Driver - MME/DirectX
- Midi Hardware - Oxygen 8 Midi Controller
- Input Latency - 28ms
- Output Latency - 23ms
- VST Plugin NI FM7

yannxou
Posts: 153
Joined: Fri Feb 27, 2004 8:39 pm
Location: Barcelona
Contact:

Post by yannxou » Fri Aug 06, 2004 8:08 pm

Hello,

Something like this happened to me last week when I processed a few drum loops through some fx at a time. I could hear the delay caused by the plugins but I thought that rendering would go fine.

I don't know whether this is related to the plugin delay compensation but it seems that there isn't neither when rendering. :?:

raapie
Posts: 1035
Joined: Fri Apr 12, 2002 8:13 am
Location: The Hague, Netherlands
Contact:

..

Post by raapie » Sun Aug 08, 2004 12:28 pm

had the same problem with latest beta. on all vsti's but only with normalize active.
Marco Raaphorst

music, sound & story maker

https://melodiefabriek.com

Andreas Zapf
Posts: 290
Joined: Mon Sep 08, 2003 10:01 am
Location: Ableton Headquarter
Contact:

Post by Andreas Zapf » Tue Aug 17, 2004 3:58 pm

Hi folks,

thank you for reporting.

The bug will be fixed in the next free update (4.0.2) which is coming soon.


Regards
Andreas Zapf
[email protected]

Locked