ok heres a possible bug:
sorry if anyone has come up with this already,
load up an audio clip with a bit of silence at the start, zoom in on the first warp maker, im right in thinking you need to hold shift now to adjust the point in accordance with the start of the audio yeah, its ok if you zoom in a bit, but when i zoom a lot and try to move the audio closer to the first warp marker i find the audio can jump back way from the marker and ive got to zoom back out to find it, its a little weird to explain wish i had a screen recorder but have a try and see if anyone can see something similar happening. i even had the whole audio track disappear in one incident when investigating this, see what you come up with.
Michael
[amo] setting the first warp marker
-
gustavo bravetti
- Posts: 132
- Joined: Wed Oct 18, 2006 12:11 am
- Contact:
Re: [amo] setting the first warp marker
[I DIDN'T UNDERSTAND THE FIRST POST, PLEASE IGNORE THIS ANSWER]
I don't know if this is your problem but sometimes something like what you described happens using mp3 files.
When an audio file is analyzed for the first time a waveform data is pre generated for quick waveform visualization, and that is what you see when you are in a wide/far zoom view, now when you go closer there is a point that Live re analyze that part of the audio data to show you fine details.
When you work with mp3 you are actually working on a temporal .wav file, then you load your project in another computer, and because you are using mp3 all the temporal .wav files are created again. In that process could happens that because a difference on the mp3 codec, a bit of silence is added or removed on the beginning. If that difference is very small, let's say a few milliseconds, Live thinks it is the same audio file and then it uses the old waveform data, then when you zoom at a deep/closer level, Live go for the real waveform data (re analyze) and there you see a jump.
Note that all this is a theory based on my own experience, and may be some on my explanation doesn't occurs exactly as I explain it.
I always advise to use wave files in projects that are intended to be used on different machines.
Best
I don't know if this is your problem but sometimes something like what you described happens using mp3 files.
When an audio file is analyzed for the first time a waveform data is pre generated for quick waveform visualization, and that is what you see when you are in a wide/far zoom view, now when you go closer there is a point that Live re analyze that part of the audio data to show you fine details.
When you work with mp3 you are actually working on a temporal .wav file, then you load your project in another computer, and because you are using mp3 all the temporal .wav files are created again. In that process could happens that because a difference on the mp3 codec, a bit of silence is added or removed on the beginning. If that difference is very small, let's say a few milliseconds, Live thinks it is the same audio file and then it uses the old waveform data, then when you zoom at a deep/closer level, Live go for the real waveform data (re analyze) and there you see a jump.
Note that all this is a theory based on my own experience, and may be some on my explanation doesn't occurs exactly as I explain it.
I always advise to use wave files in projects that are intended to be used on different machines.
Best
Last edited by gustavo bravetti on Wed Mar 18, 2009 5:51 pm, edited 1 time in total.
Re: [amo] setting the first warp marker
Hi,
I'm wondering: are you not experiencing what is described here:
http://forum.ableton.com/viewtopic.php?p=853851#p853851
Regards,
Amaury
I'm wondering: are you not experiencing what is described here:
http://forum.ableton.com/viewtopic.php?p=853851#p853851
Regards,
Amaury
Ableton Product Team