Forum Replies Created
-
Posts
-
If I upgrade from 1.42 to 1.44 will I be able to import the my old pages made on 1.42 via sysex? From the manual it says you can’t transfer / import machine states between different OSs. Does one page count as a machine state or do they mean the "entire machine state"?
So here’s how I reproduce this:
Start with a blank page.
In page mode, select a step anywhere on the page.
Double click on the step’s track selector to go into track mode
Double click on velocity to go into the velocity attribute page
Click on the edit button to turn it yellow (preview mode I think it’s called?)
On track zero you’ll see the position of your step.
Hold down the corresponding step on track zero and on the right circle it will show you the velocity of the step (64 by default) and the pitch.
While you have the step held down, press any button in the inner circle to change the step’s pitch.
The velocity will also change (by itself!) to 60.In work right now but I’ll double check and document this more carefully when I get home. If I remember correctly the bug only presented itself when in attribute map mode, and not in page mode when I move the pitch knob.
Hello and welcome,
all you have to do is press and hold the GRID button and while you hold it press the red blinking Program button.
PS – the machine has to be stopped for this to work.My answer to question 2 is "always on".
Remember to look at what happens to chained tracks, but I am sure you thought about that.
Great work, looking forward to try it out.
Generally i don’t need a midi offset, but i rarely use ableton as a master as i generally use a hardware setup with the computer just for recording purposes. However when i do have it set up for sync purposes – it seems fine without an offset – i know that ableton’s sync can be a little unreliable though… you should see if you can get the latency on your soundcard down – sometimes this can be the problem – i’m not sure what that alesis card is like for latency, but you need to try an reduce the latency as much as possible, and then use the ableton offset to make it sync exactly right
Regardless – 250ms is gigantic – even if you need an offset, it should be only a few milliseconds either way…
are you definitely using ASIO sound drivers?
CarlLofgren wrote:
Quote:robert wrote:Quote:Maybe you already statet it, but how does the MPC behave when slaved to Live in your setup?And what exactly is your MIDI setup? How’s the stuff connected?
Hm. Let’s make things more simple by leaving out the MPC for now. It’s not the main concern anyway.
Setup. Huu… Dell laptop, Dual core, 2 GB RAM, XP Pro SP2, Alesis Firewire interface, EMU 2×2 MIDI interface, Virus TI, and of course the O. Live 7.07.
Connections goes like this
Octopus Out goes to EMU MIDI in, and EMU MIDI out goes Octpus In.
You need to try and isolate the problem – as robert said – try and sync the mpc and ableton (get rid of the octopus altogether for the moment) and see if there are still timing problems (i think there will be)… or try sync the octopus to cubase – i suspect everything will be fine with cubase and there is some problem inside ableton…
250ms is a lot, it shouldn’t be anything like that – it makes me think the problem has to be inside ableton somewhere – are you using the correct ASIO audio driver in ableton? make sure you’re not using the wdm/directx driver… there must be something in the software settings that is causing the lag as the hardware seems fairly straightforward – i have much more complicated setups and have no issues with latency or lag
The other possibility is that you have got some sort of crazy midi loop that is causing problems – but i think you’d have much bigger problems if that was the case…
Post edited by: machina, at: 2008/07/24 22:13
Post edited by: machina, at: 2008/07/24 22:14
That teaches me, never post before going to sleep…
ok so you want to do 12 over 16…
1.5/2 = 0.75
Use 1.5 multiplier and play every second note.
If you need something special (a twelve step line) you’ll need to chain two tracks and mute the last 8 steps.
Anyway, I will go to sleep soon after this but that seems to work (if I understood what you’re after).
Cheers,
/RQuote:I was trying to get a 12 step track to play in the same amount of time as a 16 step track at multiplier of 1. This would require a multiplier of .75 on the 12 step trackWe need this!
but isn’t the point that you don’t use all 16 steps?… 16 steps make no sense in triplet time. make the track length 12 steps and then use 1.5 or 1/1.5
Post edited by: machina, at: 2008/07/22 05:16
In my book, 12 over 16 means triplets. check the 1.5 multiplier. (dunno if in future future-retro it means something else) 16*1.5 = 12.
I must have been the only one that cried for months over the "broken" 1.5 multiplier.
Cheers,
/R
