5.2 STILL CHOPPING OFF TIME AT START OF RENDERED TRACKS !!!!
-
- Posts: 38
- Joined: Tue Jan 17, 2006 6:08 pm
man, you're the one that needs help.James Cater wrote:I'm sorry but if you still don't get this then I really can't help you.
it sounds like you're a bit clueless if you can't find the first fucking beat of a bar, taking you forever to find it ...
I also think it would be quicker to remove one bar on 11 tracks than coming here and complain about it. I'd say ten minutes to crop 11 tracks, if you take your time.
Isn't there someone around you with a sense of rhythm that could do it for you ?
I'm outta here
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8
-
- Posts: 760
- Joined: Wed Oct 01, 2003 4:51 am
> I design and write real time banking trading systems in C++/C# for a living. These
> systems are 10x the size and complexity of Ableton so I belive I am qualified to
> highlight design flaws in this product.
I think you'll find that that qualifies you to write real time banking systems.
...and I wasn't insulting you...I was trying to help you, but it's taken more than a few posts for you to express that the problem is not due to any fault in Ableton, but rather due to a workflow problem created by your cd-burning software, which seems to be unable to put track markers in a single audio file...Granted that it would be great if Ableton could burn a CD including track markers as part of the render process, but actually, now that I think about it, I haven't burnt an audio cd for more than a couple of years.
I for one would much prefer that Ableton simply render exactly what it was told to, rather than guess that I wanted it to consider something that happened earlier in time. What if I had a 3 minute delay on a track that was 2 minutes ago in the timeline? Should Ableton divine that I needed that data as well? How does Ableton work out what third party VST and AU plugins are doing in the timescale without even knowing what those plugins are doing?
> systems are 10x the size and complexity of Ableton so I belive I am qualified to
> highlight design flaws in this product.
I think you'll find that that qualifies you to write real time banking systems.
...and I wasn't insulting you...I was trying to help you, but it's taken more than a few posts for you to express that the problem is not due to any fault in Ableton, but rather due to a workflow problem created by your cd-burning software, which seems to be unable to put track markers in a single audio file...Granted that it would be great if Ableton could burn a CD including track markers as part of the render process, but actually, now that I think about it, I haven't burnt an audio cd for more than a couple of years.
I for one would much prefer that Ableton simply render exactly what it was told to, rather than guess that I wanted it to consider something that happened earlier in time. What if I had a 3 minute delay on a track that was 2 minutes ago in the timeline? Should Ableton divine that I needed that data as well? How does Ableton work out what third party VST and AU plugins are doing in the timescale without even knowing what those plugins are doing?
-
- Posts: 38
- Joined: Tue Jan 17, 2006 6:08 pm
I agree that Ableton cannot take account of every eventuality within every plugin, especially if there are long time delays.
However a delay of 2 minutes is extremely unlikely and I suspect that going back by 1 bar before the start of the render point would cover 99% of all problems with effects that have a delay component (reverbs, delays, phasers, flangers etc)
Thank you for the earlier suggestion of recording the entire mix from the master, this would certainly help in future if I can't find a simple workaround.
I HAVE FOUND A WORKAROUND TO THIS PROBLEM....
I can use automation to ensure that the delay is always exactly 0ms at the track marker points.
Thanks to everyone for all the assistance.
However a delay of 2 minutes is extremely unlikely and I suspect that going back by 1 bar before the start of the render point would cover 99% of all problems with effects that have a delay component (reverbs, delays, phasers, flangers etc)
Thank you for the earlier suggestion of recording the entire mix from the master, this would certainly help in future if I can't find a simple workaround.
I HAVE FOUND A WORKAROUND TO THIS PROBLEM....
I can use automation to ensure that the delay is always exactly 0ms at the track marker points.
Thanks to everyone for all the assistance.
Hello James,
One thing that I don't get quite well: you are putting a delay on the track, with the dry/wet parameter set to 100% wet right ?
If so, the direct sound from the track does not output, but only the sound coming from the delay.
Tell me what I didn't get right here.
Kind regards,
Amaury
One thing that I don't get quite well: you are putting a delay on the track, with the dry/wet parameter set to 100% wet right ?
If so, the direct sound from the track does not output, but only the sound coming from the delay.
Tell me what I didn't get right here.
Kind regards,
Amaury
Ableton Product Team
-
- Posts: 38
- Joined: Tue Jan 17, 2006 6:08 pm
-
- Posts: 760
- Joined: Wed Oct 01, 2003 4:51 am
ROFL.
if you're looking for feel, why not just push a few warp markers around over the first 30 bars or so of each track. better still for that authentic vinyl lumpy bass sound, prepare each audio file with a inverse RIAA eq curve, and then apply a RIAA eq curve at playback. if you use 'repitch' the RIAA curve will realistically stay the same whilst the pitch of the track moves under it. ad some crackle, and by the time you're done you could have mixed the fucking thing with a couple of turntables and some records.
(just jokes - somehow I knew you were going to say that you were using delay to create 'mix feel' the instant you said '14ms' and 100% wet)
if you're looking for feel, why not just push a few warp markers around over the first 30 bars or so of each track. better still for that authentic vinyl lumpy bass sound, prepare each audio file with a inverse RIAA eq curve, and then apply a RIAA eq curve at playback. if you use 'repitch' the RIAA curve will realistically stay the same whilst the pitch of the track moves under it. ad some crackle, and by the time you're done you could have mixed the fucking thing with a couple of turntables and some records.
(just jokes - somehow I knew you were going to say that you were using delay to create 'mix feel' the instant you said '14ms' and 100% wet)