L5.0.2b3: strange orange dot behaviour
L5.0.2b3: strange orange dot behaviour
now that the "imaginary" grid is only 1 bar long it seems to have created a new strangeness to the orange dot phenomenon.
When nudging (forward) the start position of a clip that is longer than a bar, the orange dot seems to skip past the middle of the clip
To re-create:
Take a 2 bar clip and drag into session
Put global quantize to 1/4 ( or some other quantize smaller than that )
Select and trigger clip and start nudging forward (>>)
On nudging the orange dot goes to 1.2 then 1.3 but then on the 3rd nudge it zips all the way over to 2.4 (???)
very strange and definitely has to be a bug!
When nudging (forward) the start position of a clip that is longer than a bar, the orange dot seems to skip past the middle of the clip
To re-create:
Take a 2 bar clip and drag into session
Put global quantize to 1/4 ( or some other quantize smaller than that )
Select and trigger clip and start nudging forward (>>)
On nudging the orange dot goes to 1.2 then 1.3 but then on the 3rd nudge it zips all the way over to 2.4 (???)
very strange and definitely has to be a bug!
-
Stefan Haller
- Posts: 330
- Joined: Wed Apr 24, 2002 9:50 am
- Location: Ableton Headquarter
- Contact:
No, that's not a bug.
Remember that the orange dot indicates the position that the start marker would be set to if you were to press "Keep" now. Normally that position is within a range of half a bar to either side of where the start marker is now. However, if the start marker is inside the loop, we never move it out of the loop if you press Keep; we wrap it around to the end instead. That's why the orange dot is drawn near the end of the loop as well in that case.
Hope that makes sense.
Remember that the orange dot indicates the position that the start marker would be set to if you were to press "Keep" now. Normally that position is within a range of half a bar to either side of where the start marker is now. However, if the start marker is inside the loop, we never move it out of the loop if you press Keep; we wrap it around to the end instead. That's why the orange dot is drawn near the end of the loop as well in that case.
Hope that makes sense.
Stefan Haller
[email protected]
[email protected]
how does this logic work for a 4 bar loop, EG a vocal riff segment.
does this 1 bar loop mean that we will never be able to see where the start marker will really go to?
Eg I have a chorus like this:
"
Oh baby I love you,
but I really have to say,
you are like an orange dot,
moving in a mysterious way.
"
if I wanted to nudge so that the start maker was to start at the beginning of the word "Orange" ... IE I want my clip to sync start at that word - it makes sense to me that the orange dot would be indicating itself at that point. Like this :
.orange
Not at some imaginary point within a 1 bar loop, probably off the left hand side of my screen ... that would put it at 'Love' or somewhere ... I really don't know!

does this 1 bar loop mean that we will never be able to see where the start marker will really go to?
Eg I have a chorus like this:
"
Oh baby I love you,
but I really have to say,
you are like an orange dot,
moving in a mysterious way.
"
if I wanted to nudge so that the start maker was to start at the beginning of the word "Orange" ... IE I want my clip to sync start at that word - it makes sense to me that the orange dot would be indicating itself at that point. Like this :
.orange
Not at some imaginary point within a 1 bar loop, probably off the left hand side of my screen ... that would put it at 'Love' or somewhere ... I really don't know!
I should say : I've not personally experienced terrible functional problems with the dot, others obviously have.
the only issue I have had is one of understanding.
I think the flaw in the dot inclusion was mainly due to lack of a decent explanation of the concept behind it. Just one small paragraph was too little - as it was quite different from the previous way of doing things. Also this is probably the first abetonian function which operates on a "notional basis" IE it requires user conceptualisation of a notional grid rather than WYSIWYG like everything else.
I think they should extend the manual section for this important function in future editions.
the only issue I have had is one of understanding.
I think the flaw in the dot inclusion was mainly due to lack of a decent explanation of the concept behind it. Just one small paragraph was too little - as it was quite different from the previous way of doing things. Also this is probably the first abetonian function which operates on a "notional basis" IE it requires user conceptualisation of a notional grid rather than WYSIWYG like everything else.
I think they should extend the manual section for this important function in future editions.
so why are clips offset and play out of sync although I've never pressed keep in my entire life ?Stefan Haller wrote:No, that's not a bug.
Remember that the orange dot indicates the position that the start marker would be set to if you were to press "Keep" now.
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8
-
serotoninsteve
- Posts: 1094
- Joined: Wed Jan 28, 2004 2:27 pm
- Location: Luxembourg
Yes stoping the whole machine cures it, but it comes back, believe me.
I´ve found some other strangenesses, will post them tomorow, too late now.
Greetings
I´ve found some other strangenesses, will post them tomorow, too late now.
Greetings
MBP 15,4" 2,53GHz C2D 4Gb late 2008 / Mac OS X.6.2 / Novation Remote 37SL Compact / TriggerFinger / FaderfoxDJ2 / Padkontrol / UC33 / SM Audio TB202 / Audiofire2 / Apogee Duet / Event OPAL's / HD25 /
yes you have to juggle between space bar , revert, a double stop to go back to bar 1.1.1, and manually move the start marker :
I give up.
This is very frustrating because I was waiting for so many functions now included (set import, clip saving, width of tracks, complex mode) but this side of the program is such a time waster. I'm a slave to this program, and I hate that. Computers are here to help not to make life harder, and when a music program takes your energy in shit like that, you don't have inspiration for music.
I understand that people who make music using ready made loops and just putting them in square boxes won't have any problem, for they're not using live in depth. The frustration comes from working with previous versions, (that had limits hence eagerly waiting for this update) the warping WAS the innovation, scenes to arrange on the fly WAS an innovation.
THIS IS GONE IN NEW VERSION due to extremely poor design, and most of all, no testing from the programmers.
I spent 2 whole months reporting about that, and so have other people, but there are no improvements in sight. It's actually getting worse.
So bye bye
I give up.
This is very frustrating because I was waiting for so many functions now included (set import, clip saving, width of tracks, complex mode) but this side of the program is such a time waster. I'm a slave to this program, and I hate that. Computers are here to help not to make life harder, and when a music program takes your energy in shit like that, you don't have inspiration for music.
I understand that people who make music using ready made loops and just putting them in square boxes won't have any problem, for they're not using live in depth. The frustration comes from working with previous versions, (that had limits hence eagerly waiting for this update) the warping WAS the innovation, scenes to arrange on the fly WAS an innovation.
THIS IS GONE IN NEW VERSION due to extremely poor design, and most of all, no testing from the programmers.
I spent 2 whole months reporting about that, and so have other people, but there are no improvements in sight. It's actually getting worse.
So bye bye
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8