02-22-2020, 08:22 AM
Ok, that's great info, I agree that the midi interface is not a likely culprit, even if it is the latest firmware it may be worth a reflashing as it may just be a setting that accidentally got switched or something I can't think of that just fixes itself with a reinstall. a couple more things to try first:
For both Motifs set them to a short even numbered pattern length, then choose a rhythm that has a trigger every beat and just to keep things under control, shorten that down and make it an even number of beats. set clk division to x4. In the menu turn the setting for pad quantisation off. Try playing that and see if that lines things up for you.
Turn down the tempo to something low, and listen to the drone while watching the beat indicator, if the on screen tempo indicator is lit (red on the one and then the next three are a different color) that indicates a down beat and with the 5 dots and 4 filled squares, you should be hearing the drone trigger in time. This test can help us figure out if it's actually everything else that's been off.
Let me know if any of that returns good info!
Jesse
For both Motifs set them to a short even numbered pattern length, then choose a rhythm that has a trigger every beat and just to keep things under control, shorten that down and make it an even number of beats. set clk division to x4. In the menu turn the setting for pad quantisation off. Try playing that and see if that lines things up for you.
Turn down the tempo to something low, and listen to the drone while watching the beat indicator, if the on screen tempo indicator is lit (red on the one and then the next three are a different color) that indicates a down beat and with the 5 dots and 4 filled squares, you should be hearing the drone trigger in time. This test can help us figure out if it's actually everything else that's been off.
Let me know if any of that returns good info!
Jesse