HELP - Recorded Dj Mixes Have Holes In them
plazzTT wrote:5.0.3 *seems* to work so far (*touch wood*)
this is possible, because i (and many others) almost immediatelly stopped using 5.03 when we discovered that:
clips firing in session view no longer always re-fired all the clips from the start marker position, when you stop and restart the transport.
so, possible that this new"behavior of clips in session was one possible answer they came up with for other problems we're discussing here. but in a lot of peoples opinions this only moved the mess from one area to another.
if you test 5.03 for a while using the teqniques i spelled out a couple of posts above, see if this records what you do accurately. if so then it sounds like what im saying is true
.
--
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
post i made a while back re: this issue and related ones:
http://www.ableton.com/forum/viewtopic. ... nge+record
http://www.ableton.com/forum/viewtopic. ... nge+record
--
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
Is there any definative (or even vague) changelist from 5.0.2 to 5.0.3? I know it went through a few betas, surely they told people what changed.
Going back to jesse's original problem of "gaps" in the arrangement. In 5.0.2, I did the thing where you switch off the loop, and the rest of the clip disappears in arrangement (but keeps playing). I then saved this arrangement/set (with the gap in it).
I installed 5.0.3 over 5.0.2, reloaded the set, and the gap had been filled. I'm not sure if it sounded quite like I wanted, but something has definately been "fixed" ("changed" anyway) regarding this problem in 5.0.3.
For me anyway, 5.0.3 does what I want better, and it "behaves" like I'd expect.
I'm new to this, supster, and I don't have the terminology yet. I don't really know what you mean by firing and re-firing (or transport)?
Going back to jesse's original problem of "gaps" in the arrangement. In 5.0.2, I did the thing where you switch off the loop, and the rest of the clip disappears in arrangement (but keeps playing). I then saved this arrangement/set (with the gap in it).
I installed 5.0.3 over 5.0.2, reloaded the set, and the gap had been filled. I'm not sure if it sounded quite like I wanted, but something has definately been "fixed" ("changed" anyway) regarding this problem in 5.0.3.
For me anyway, 5.0.3 does what I want better, and it "behaves" like I'd expect.
I'm new to this, supster, and I don't have the terminology yet. I don't really know what you mean by firing and re-firing (or transport)?
plazzTT wrote:I'm new to this, supster, and I don't have the terminology yet. I don't really know what you mean by firing and re-firing (or transport)?
ok ... say you have a row of clips (scene) in your session view. all 4 bar clips. 4 bar kick. 4 bar snare. 4 bar bass.
in pre-5.03 versions if you start all the clips running, looping around in 4 bar pattern ... then stop the transport anywhere along the way ... say, a bar after you start, or at the fourth bar .. wherever ..
in these earlier versions if you stop the clips running (spacebar or stop square at the top of the screen ... then restart again ... the clips would start playing from the beginning again.
they changed that in 5.03, so depending on where you stop and/or what length the clips are in relation to each other, they will not always refire from the beginning. sometimes they will fire from some other point, or even out of sequence with each other.
there are long threads about it somewhere on this forum ...
--
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com
NEW SPECS: Athlon 4200+ dual; A8N-SLI m/b; Win XP Home SP2; 1 GB RAM; 2x 7200 RPM HDD: 1 internal, 1 Firewire 800 (Firewire is project data drive); M-Audio Triggerfinger
josh 'vonster' von; tracks and sets
http://www.joshvon.com