8.1.3???
Re: 8.1.3???
@ self
just fired up Live and looked. Oh there they are!!!
I blame the foot switch, small icons and distance to DAW. This is obviously some kind of bug. Dennis I need this fixed right away or I may spend a ridiculous amount of time on line bitching about it!!
just fired up Live and looked. Oh there they are!!!
I blame the foot switch, small icons and distance to DAW. This is obviously some kind of bug. Dennis I need this fixed right away or I may spend a ridiculous amount of time on line bitching about it!!
LoopStationZebra wrote:it's like a hipster commie pinko manifesto. Rambling. Angry. Nearly divorced from all reality; yet strangely compelling with a ring of truth.
Re: 8.1.3???
Thank goodness for forums, I love them. I think its a product of my geek past and spending long hours in transit with wifi, troubleshooting the problems I had onstage the night before. Usually I have questions that can't be answered by anyone I know and I find a hint here that will lead me to come up with a solution.
Good point that most peeps don't post on the forums. I had Ableton tell me when I first started reporting problems that I might be the only person using Live the way I do. I've since met several people who use it similarly. People trying to do what I do write to me with their Live issues, and I usually point them to the forums...they're always like "there's an Ableton forum?". So he's probably right.
I can't imagine how else I would use Live, but I came at it probably from a different angle. We probably all think that the way we use it is THE WAY to use it. Lol.
Good point that most peeps don't post on the forums. I had Ableton tell me when I first started reporting problems that I might be the only person using Live the way I do. I've since met several people who use it similarly. People trying to do what I do write to me with their Live issues, and I usually point them to the forums...they're always like "there's an Ableton forum?". So he's probably right.
I can't imagine how else I would use Live, but I came at it probably from a different angle. We probably all think that the way we use it is THE WAY to use it. Lol.
MacBook Pro 2.93 Ghz, early 2009, 4GB RAM
OS 10.5.8
Live 8.1.4
Motu Ultralite + FCB1010 + SooperLooper + cello
twitter: zoecello
http://www.zoekeating.com
OS 10.5.8
Live 8.1.4
Motu Ultralite + FCB1010 + SooperLooper + cello
twitter: zoecello
http://www.zoekeating.com
-
- Posts: 670
- Joined: Thu Apr 04, 2002 3:31 pm
- Location: Ableton NYC
Re: 8.1.3???
Hi Zoe,
Ok, I want to try to duplicate your use case. Can you confirm that this is the scenario that causes the problem:
- record new audio into an Arrangement track, while the loop is enabled, and ensure that your recording loops back on itself at least once.
Further questions:
- are the clicks in the newly recorded file(s)?
- is there any pattern to which tracks are affected? (e.g. only odd numbered tracks, only tracks with certain effects, etc?)
- is this 100% reproducible?
- does it happen both with fades on and off?
- bit depth? sample rate?
Thanks,
Ok, I want to try to duplicate your use case. Can you confirm that this is the scenario that causes the problem:
- record new audio into an Arrangement track, while the loop is enabled, and ensure that your recording loops back on itself at least once.
Further questions:
- are the clicks in the newly recorded file(s)?
- is there any pattern to which tracks are affected? (e.g. only odd numbered tracks, only tracks with certain effects, etc?)
- is this 100% reproducible?
- does it happen both with fades on and off?
- bit depth? sample rate?
Thanks,
Dennis DeSantis
dennis.desantis@ableton.com
dennis.desantis@ableton.com
Re: 8.1.3???
+1, Dennis gets a beer.
Actually, that might not be a bad idea. Back when I was a beta-tester for the Emu Command Stations, I kept running into an obscure bug that very people ever would have noticed. As a result, it never seemed to ever get resolved in OS updates.
For me it was a big deal though, so I mailed the E-mu guys some cookies I made with a note attached saying "please fix big x,y,z". Sure enough, bug was fixed with the next OS update a couple weeks later.
Hmm....
Actually, that might not be a bad idea. Back when I was a beta-tester for the Emu Command Stations, I kept running into an obscure bug that very people ever would have noticed. As a result, it never seemed to ever get resolved in OS updates.
For me it was a big deal though, so I mailed the E-mu guys some cookies I made with a note attached saying "please fix big x,y,z". Sure enough, bug was fixed with the next OS update a couple weeks later.
Hmm....
tarekith
https://tarekith.com
https://tarekith.com
Re: 8.1.3???
bless you Dennis!
THANK YOU!!
yes, here's a screen capture of the setup. like this:- record new audio into an Arrangement track, while the loop is enabled, and ensure that your recording loops back on itself at least once.
yes- are the clicks in the newly recorded file(s)?
seems be all of them, just tested. happens with effects on or off (i've got reverb and compression on the master track)-- is there any pattern to which tracks are affected? (e.g. only odd numbered tracks, only tracks with certain effects, etc?)
yes, every time- is this 100% reproducible?
I just replicated it again, yes, fades on or off- does it happen both with fades on and off?
24/48- bit depth? sample rate?
THANK YOU!!
MacBook Pro 2.93 Ghz, early 2009, 4GB RAM
OS 10.5.8
Live 8.1.4
Motu Ultralite + FCB1010 + SooperLooper + cello
twitter: zoecello
http://www.zoekeating.com
OS 10.5.8
Live 8.1.4
Motu Ultralite + FCB1010 + SooperLooper + cello
twitter: zoecello
http://www.zoekeating.com
Re: 8.1.3???
fwiw, I just tried something prior to seeing zoe's screenshot and dennis' questions. (I'm on windows vista).
Here is what i did
1- Put a clip into session view sending midi note out thru a midi yoke (loopbe30) and set up midi map so this activates the global transport record button. Loopbe30 was set up in preferences as sending midi out thru track and back in as remote.
2- Global loop was active, but punch in/out were not active.
3- Armed the audio input track, and kept it armed.
4- I set the arrangement loop to start after 4 beats, and loop for another 4 beats.
The session "triggering" clip was 4 beats, with the triggering note on the first beat. So when I started the clip, this armed the global record, allowing recording audio, and then when it looped back around to "1" when the arrangment was coming into the global looped region (starting on beat 5) for the first time it disarmed the global record, and then re-armed it repeatedly every other time as the arrangement loop came back around.
Here is what I saw doing simply the above:
Triggering the scene started the transport, and the midi note armed the global record button. But this did not happen instantly, precisely on "1". Because the global transport is running, the triggering MIDI clip is recorded into the arrangement as well as the audio, and because recording did not happen precisely on "1", that arrangment- recorded triggering clip's start marker is behind the triggering note. So what actually happens when the loop in session comes back around, is a multiple triggering, one coming from the reflected clip in arrange, which results in a little tiny wee audio clip followed by the longer 'intended' clip.
(with punch in/out active, you can't see this happening as plainly, because the triggering clip is not reflected in arrangement.)
you might want to try this with punch in/out deactivated, to see if you see the same thing.
[edit] not sure how to work around this, if this is the same problem you are seeing. I'm thinking you'll need to mess with the track latency, but then it is hard to know when "1" is at the very get go.
Here is what i did
1- Put a clip into session view sending midi note out thru a midi yoke (loopbe30) and set up midi map so this activates the global transport record button. Loopbe30 was set up in preferences as sending midi out thru track and back in as remote.
2- Global loop was active, but punch in/out were not active.
3- Armed the audio input track, and kept it armed.
4- I set the arrangement loop to start after 4 beats, and loop for another 4 beats.
The session "triggering" clip was 4 beats, with the triggering note on the first beat. So when I started the clip, this armed the global record, allowing recording audio, and then when it looped back around to "1" when the arrangment was coming into the global looped region (starting on beat 5) for the first time it disarmed the global record, and then re-armed it repeatedly every other time as the arrangement loop came back around.
Here is what I saw doing simply the above:
Triggering the scene started the transport, and the midi note armed the global record button. But this did not happen instantly, precisely on "1". Because the global transport is running, the triggering MIDI clip is recorded into the arrangement as well as the audio, and because recording did not happen precisely on "1", that arrangment- recorded triggering clip's start marker is behind the triggering note. So what actually happens when the loop in session comes back around, is a multiple triggering, one coming from the reflected clip in arrange, which results in a little tiny wee audio clip followed by the longer 'intended' clip.
(with punch in/out active, you can't see this happening as plainly, because the triggering clip is not reflected in arrangement.)
you might want to try this with punch in/out deactivated, to see if you see the same thing.
[edit] not sure how to work around this, if this is the same problem you are seeing. I'm thinking you'll need to mess with the track latency, but then it is hard to know when "1" is at the very get go.
UTENZIL a tool... of the muse.
Re: 8.1.3???
This is the first Ableton live 8 release that actually works for me.Not one crash so far. No "not enough memory issues" either.I'm using the latest Jamstix 3 beta 15 and at last
-
- Posts: 670
- Joined: Thu Apr 04, 2002 3:31 pm
- Location: Ableton NYC
Re: 8.1.3???
Hi folks,
Please note that we updated the release candidate today. Links:
Best,
Please note that we updated the release candidate today. Links:
Best,
Dennis DeSantis
dennis.desantis@ableton.com
dennis.desantis@ableton.com
Re: 8.1.3???
Dennis DeSantis wrote:Hi folks,
Please note that we updated the release candidate today. Links:
Best,
Any change log available?
Ableton Trap Beats
https://www.youtube.com/channel/UCXl_L6 ... Gpm-zf7XEA
https://www.youtube.com/channel/UCXl_L6 ... Gpm-zf7XEA
-
- Posts: 55
- Joined: Fri May 13, 2005 10:44 am
Re: 8.1.3???
So now we are in RC mode...
First it was beta 1, 2 ,3 ..,13..
Now it is RC (sounds better ) 1, 2 .... etc; etc;
First it was beta 1, 2 ,3 ..,13..
Now it is RC (sounds better ) 1, 2 .... etc; etc;
iMac i7 Quad Core 2.8GHz 32GB RAM • OS X.10 • Apogee Duet • NI Kontrol S49 • Maschine Mikro MKII • Cubase 8.5 • Live 9.6 Suite • Logic Pro X • Reason 9 • WaveLab Elements 9 • Various VST's, AU's and hardware synths, etc;
-
- Posts: 193
- Joined: Tue Jun 23, 2009 2:54 pm
Re: 8.1.3???
Not a big deal but "spectrum" is still badly lagging...
Re: 8.1.3???
bump up the refresh rate?housemusiclover wrote:Not a big deal but "spectrum" is still badly lagging...
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
-
- Posts: 670
- Joined: Thu Apr 04, 2002 3:31 pm
- Location: Ableton NYC
Re: 8.1.3???
Yes, this is a known issue.housemusiclover wrote:Not a big deal but "spectrum" is still badly lagging...
Thanks,
Dennis DeSantis
dennis.desantis@ableton.com
dennis.desantis@ableton.com
-
- Posts: 193
- Joined: Tue Jun 23, 2009 2:54 pm
Re: 8.1.3???
Thanks but nope, it's totally independet of the refresh rate.Tone Deft wrote:bump up the refresh rate?housemusiclover wrote:Not a big deal but "spectrum" is still badly lagging...
Only happens when folded out and on mouseover.
Dennis confirmed the behaviour a few days ago (also on nvidia card), someone else didn't have the problem but had an ati card iirc. Not sure...
Anyway, just realized that the newest Voxengo Span also shows freq PLUS note so i don't really care.
edit: again too late
-
- Posts: 10586
- Joined: Sat Jan 17, 2009 5:57 pm
- Contact:
Re: 8.1.3???
nathannn wrote:i used to get this all the time.... for some reason i always think things like this are due to user error on my part.LoopStationZebra wrote:Cool. My snap crackle pop has vanished with 8.1.3 when I record new clips.
However,
Crackle still there whenever I change scenes or do anything on the Launchpad that involves the right hand side control buttons. meh.
Wicked crackle when I record into Looper. Interesting thing is that it always happens at the start of the 2nd bar, lol.
FUCK.
i rarely ever question the software. i guess i should come on here and try to see if others are having the same problems as me.
tigali wrote: I only came onto this thread to see if this particular problem had been solved in the latest version. I'm still using 8.1.0 and it's a problem thats really bumming me out. The project I was working on today had this going on and it uses zero 3rd party plugins. The only non-native stuff are some audio clips I recorded in myself, the rest is built in sounds. The problem came and went a couple of times without me doing anything but restarting the program.
HeadrickProductions wrote: I've hard this same problem with the sanp crackle pop on the launchpad. You two are the first time I've seen others talk about it. Everyone else keeps telling me that it is my fault due to how I've had it setup. My apc 40 does not have the same issues.
Thanks for letting me know
Tone Deft wrote:that kind of problem does sound like you're using too small of a buffer size.
After quite a bit of time spent testing and trying stuff, the problem with the Looper crackle is still there. Tried a fresh new template, various buffer sizes from low to super high, etc etc. Nothing worked. The crackle sometimes starts at the 2nd bar as I first wrote, but this past session it would start at the first bar upon playback. Total bummer. Not sure at all what to try now. I'll see if I can drag out Mobius Looper again and give that a go I suppose. Ugg.
I came for the
But stayed for the
But stayed for the