TranceAddict Forums

TranceAddict Forums (www.tranceaddict.com/forums)
- Production Studio
-- Ableton Users


Posted by mfitterer1 on Nov-19-2009 01:52:

Ableton Users

Ok so I am having some issues with midi clips in ableton. I'm using 7.3 still at the moment.

By default midi clips in my ableton are all set to 120. I always thought up until now that the midi clips just went by the project tempo but i'm starting to think otherwise. It could be a 64 bit compatibility issue but I don't currently have another computer with everything loaded on to it to compare.

When I manually change all the clips back to 136 (the examples project tempo) not only does it sound different but as soon as I close and re-open the project it is re-set to 120.

My question is this. What is right and what is wrong?

Sick of dealing with this bullshit just want to be able to put my ideas down and be done with it


Posted by Zombie0729 on Nov-19-2009 01:57:

Re: Ableton Users

quote:
Originally posted by mfitterer1
Ok so I am having some issues with midi clips in ableton. I'm using 7.3 still at the moment.


Sick of dealing with this bullshit just want to be able to put my ideas down and be done with it


well you should go buy the program then, 7.0.3 is not even close to the last version (you're 15 versions away and i know the last hacked version of ableton was 7.0.3 due to some kid on the ableton forums responding like a retard). the reality is your midi clips don't need to be set for tempo, they are all clocked to the master.


Posted by Beatflux on Nov-19-2009 01:58:

Re: Ableton Users

quote:
Originally posted by mfitterer1
Ok so I am having some issues with midi clips in ableton. I'm using 7.3 still at the moment.

By default midi clips in my ableton are all set to 120. I always thought up until now that the midi clips just went by the project tempo but i'm starting to think otherwise. It could be a 64 bit compatibility issue but I don't currently have another computer with everything loaded on to it to compare.

When I manually change all the clips back to 136 (the examples project tempo) not only does it sound different but as soon as I close and re-open the project it is re-set to 120.

My question is this. What is right and what is wrong?

Sick of dealing with this bullshit just want to be able to put my ideas down and be done with it


Live 7 only goes up to 7.0.18.


Posted by Beatflux on Nov-19-2009 02:08:

Re: Re: Ableton Users

quote:
Originally posted by Zombie0729
well you should go buy the program then, 7.0.3 is not even close to the last version (you're 15 versions away and i know the last hacked version of ableton was 7.0.3 due to some kid on the ableton forums responding like a retard). the reality is your midi clips don't need to be set for tempo, they are all clocked to the master.


Google says there are versions higher than 7.0.3.


Posted by LoveHate on Nov-19-2009 02:25:

just buy it.


Posted by Zombie0729 on Nov-19-2009 02:37:

Re: Re: Re: Ableton Users

quote:
Originally posted by Beatflux
Google says there are versions higher than 7.0.3.


i think you're trying to agree with me? i said he's 15 versions behind (7.0.3 + .0.15 = 7.0.18)


Posted by Beatflux on Nov-19-2009 02:41:

Live 8 has been cracked.


Posted by Zombie0729 on Nov-19-2009 02:44:

digi rain upon thee


Posted by DjWoody on Nov-19-2009 03:07:

I had a similar issue, and YES, I own a legit copy of Ableton.

My issue is that when you drop a new clip to an empty box on session view, it will automatically set the BPM of the clip to 120. It won't even try to guess the correct BPM like it normally should.

My fix to this, obviously is to warp the track manually.

Honestly, it's not a big deal to me, it's more of an inconvenience.


Posted by Zombie0729 on Nov-19-2009 03:09:

quote:
Originally posted by DjWoody
I had a similar issue, and YES, I own a legit copy of Ableton.

My issue is that when you drop a new clip to an empty box on session view, it will automatically set the BPM of the clip to 120. It won't even try to guess the correct BPM like it normally should.

My fix to this, obviously is to warp the track manually.

Honestly, it's not a big deal to me, it's more of an inconvenience.


but he's talking Midi, i think you're talking audio. for audio make sure to hit the save button in the clip after you warp it your warp settings will save in the asd file


Posted by kitphillips on Nov-19-2009 05:06:

Re: Re: Ableton Users

quote:
Originally posted by Zombie0729
well you should go buy the program then, 7.0.3 is not even close to the last version (you're 15 versions away and i know the last hacked version of ableton was 7.0.3 due to some kid on the ableton forums responding like a retard). the reality is your midi clips don't need to be set for tempo, they are all clocked to the master.


There are more recent live 7 cracks I'm pretty sure.

As far as the original question goes I'm a bit confused. Theres definately no bug. You need to look at where the grid lines are in the midi clip to work out where the notes are triggering. Live does something wierd with midi clips tempo. If you import them, they always display at the current project's tempo, even if they were recorded at a different tempo. Despite that, they still have the right relative timing, so its as if they've been "warped". Its confusing, but it means you never really need to adjust the timings, so I'm not sure why you're doing that. If it sounds in time when you import the clip, then just leave it alone.


Posted by mfitterer1 on Nov-19-2009 12:24:

My version is legit it's not cracked. Excuse me for forgetting the 0 although I kinda feel like everyone knew what I was talking about regardless. On top of that the reason I haven't upgraded yet is because I got incredibly comfortable and don't want to re-learn version 8 or have issues because I've never had any up until now with 7.(0!).3. If it ain't broke why fix it?

The problem is noticed especially if you pick up an arrangement via cutting and pasting it. All of the midi clips go from 120 (default and what it usually is at) to 136 (tempo master clock speed). Also some of the swing parameters change on some clips but others don't. I'm really starting to think this is a XP 64 bit compatibility problem instead of an ableton problem. I have system crashes from time to time to I never used to have...


Posted by floyd741 on Nov-19-2009 13:15:

Ableton Live 8 does not have this problem.

Just sayin'


Posted by mfitterer1 on Nov-19-2009 20:20:

quote:
Originally posted by floyd741
Ableton Live 8 does not have this problem.

Just sayin'


That's the main reason I posted this. If it is a known bug or a compatibility issue then obviously i'll upgrade. However everyone has said it isn't which is a problem...


Posted by kitphillips on Nov-20-2009 07:09:

So is the audio actually audibly out of time? Or is it just displaying the wrong tempo?

Also, you need to understand the way that ableton does swing. Theres only a global swing amount (in live 7) for the whole project, so of course it'll change if you drag and drop a midi clip.


Posted by mfitterer1 on Nov-20-2009 11:01:

quote:
Originally posted by kitphillips
So is the audio actually audibly out of time? Or is it just displaying the wrong tempo?

Also, you need to understand the way that ableton does swing. Theres only a global swing amount (in live 7) for the whole project, so of course it'll change if you drag and drop a midi clip.


You're wrong about the swing in my version. I can set it for each and every clip on each and every track. I've tested to see if it was the swing algorithm creating the problem. It was not.

There is a noticeable difference between when the clips are at 120 and 136. The problem is to get them to 136 you have to manually warp them which means re-inputting each individual note. I don't know which one is correct and what i'm most afraid of is that I have learned incorrectly because i've been doing it this way from the start. How am I supposed to know whats right and what is wrong?


Posted by Nightshift on Nov-20-2009 11:18:

quote:
Originally posted by mfitterer1
You're wrong about the swing in my version. I can set it for each and every clip on each and every track. I've tested to see if it was the swing algorithm creating the problem. It was not.

There is a noticeable difference between when the clips are at 120 and 136. The problem is to get them to 136 you have to manually warp them which means re-inputting each individual note. I don't know which one is correct and what i'm most afraid of is that I have learned incorrectly because i've been doing it this way from the start. How am I supposed to know whats right and what is wrong?


Or you can just create a new blank clip and copy and paste the midi information then delete the original one.

Did that a few times.


Posted by kitphillips on Nov-22-2009 07:00:

quote:
Originally posted by mfitterer1
You're wrong about the swing in my version. I can set it for each and every clip on each and every track. I've tested to see if it was the swing algorithm creating the problem. It was not.

There is a noticeable difference between when the clips are at 120 and 136. The problem is to get them to 136 you have to manually warp them which means re-inputting each individual note. I don't know which one is correct and what i'm most afraid of is that I have learned incorrectly because i've been doing it this way from the start. How am I supposed to know whats right and what is wrong?


No I'm not wrong about the swing. Theres a global swing AMOUNT, but you can set the swing type in each clip. So that might be a cause of the difference if the global AMOUNT is different for each project, even if the swing type is the same.

Of course theres a noticable difference, but is the clip out of time when you first drag and drop it? If not, then leave it alone. You know what is right and wrong from listening, not looking at the tempo.



Powered by: vBulletin
Copyright © 2000-2021, Jelsoft Enterprises Ltd.