Solved Maschine not keeping in time?

I've been working on a song for a long time with a BPM of 124. For some reason it has started going out of time. The metronome keeps time in the first section but soon the song goes away from the beat. I can't work out what has happened. I noticed the problem when I was extending or shortening scenes. When I dragged on the arranger to make patterns longer or shorter it wasn't extending or shortening to the bar any more. So maybe I have accidentally changed that. Anyway it's a problem I have never seen before and I would love to solve it otherwise I will somehow have to rebuild my complex song from scratch. One symptom of it is shown in the attached screenshot where you can see that the scene has a little gap before and after it...

 

Prior to that point in your arrangement, you have a Section (a "Scene" in the Arranger) that has an odd length and is therefore throwing off the metronome (and would do for sync sampling too).

I've brought this flaw up several times and reported it directly as many, but noone seems to care. It's ridiculous behaviour, especially for a pattern-based sequencer.

 

I'm curious to know the application or advantage of using odd length patterns and also how your workflow works generally cause i never saw a project with over 59 scenes before...
What kind of music do you do?

 

I obviously can't speak for the OP, but one reason can be to add a little time in between sections that isn't a whole bar or even a whole number of beats e.g., for that extra half second of a dramatic pause before the next section starts.

It's Scene 59, but only bars 17-20. Every time you create a new Scene/Section a new incremented Scene is created, so when trying new Scene variations, it's pretty easy and quick to get up to those numbers of Scenes, even if all of them aren't used in the arrangement.

 

I see... That's very uncommon in EM as it's a mixing nightmare but I can totally see how it can make sense for other styles.

 

EM as in electronic music? If you think.ots uncommon in such a massive and widely encompassing genre as "electronic music", I think you need to branch out more.

 

I didn't want to use the 'D' but I should have... EDM, there I said it.
Maybe it's you who needs to branch IN!!! Wait.. that didn't make sense.. sorry.
Don't want to hijack this discusssion

 

Ah, well, that's a different story altogether...

Please close the door on your way out.

But more seriously, the OP's issue, if it is what I suspect, is a really serious issue and flaw with the sequencer in my opinion.

 

To me, the more i read the OP the more it sounds like he added the odd length by accident, let's see what he replies back.
I'm not sure how the metronome can be on beat/sync when the sections are offbeat and odd sized though...

 

The OP's issue might very well be due to an accident, but the issue still exists: https://www.native-instruments.com/...n-following-scenes-with-an-odd-length.312873/

Granted, in some circumstances, it would be expected for the metronome to be "out of time" e.g., play range includes an obscure length Scene, but there are many scenarios where it makes no sense for it to be out of sync/phase and that actually hampers workflow (see linked thread).

 

Thanks for all the replies and sorry for not replying earlier. Reading this, I think I added an odd length bar by mistake. Something weird happened when I tried to change the length of bars in the normal way in Pattern view. Instead of adding whole bars as usual when I click and drag, it’s adding partial bars - don’t know why! Someone asked about the track - here it is (work in progress). This version was before the timing problem.

 

you have Maschine 3

how did you add an odd bar, Maschine does not permit you to have more than one time signature, did they add that there in the future in version 3

I hae come across the before with songs in Maschine.. I seem to remember I had to reconstruct the song by saving the parts and then creating a new project. also have had it occur wit using midi sync

 

If you hold shift while changing the pattern/scene sizes you can select odd lenghts...
Maschine 3 !? MIDI sync? what are you talking about?

Glad you got it sorted it out, and cool track BTW.

 

This is technically accurate (no time signature changes within a Project), but a little misleading as you can easily work around this using different Pattern lengths to have as many different time signatures in a Project as you like - practically, it doesn't really matter that the transport header says 4/4 (or whatever).

The thread title says "Maschine 3".

 

Oh... Snap. I always overlook the thread titles, my bad. I edited it out to avoid further confusion.

 

I still have this exact same problem with maschine Mk2. NI knows about it, since they disable comments on anything mentioning this issue.
I have tried triggering scenes with notes and with program changes. Tried adding a beat to every pattern change (so it's early) but the pattern still triggers on the 2nd beat. Even ableton's delay function won't offer a solution, i tried as much as negative 50 milliseconds. Checked all the loop lengths and retrigger settings and even tried all the different grid settings. Keeps doing the same shitty thing.

Really a useless piece of kit for live performances this way.

 

I experienced a similar phenomenon, I was having logic "trigger" in the 2nd beat. well what was in fact happening was the it was triggering on time but the latency using bluetooth headphones on a M1 Mac mini (little sound card support) was at 190ms, making the sound reach me on the 2nd beat.... using wired headphones it was back to 9ms.... btw, that is terrible bluetooth performance as on my iPad Pro the latency for bluetooth is only 18ms with the same exact headphone... ... so perhaps it could be a latency issue as well... but.. I remember there is another issue and I have encountered something like that as well with midid notes that started before the actual start point of the measure, so the note does not play.. if it is the main beat it will sound like it starts on the second. the way to fix it is the delete the note and replace it manually. usually occurs when pasting midi sequences.