Tempo change with patterns

[YESMAN]

   I noticed that when changing banks and selecting a new pattern, the pattern tempo is that from the previous pattern. If I load the pattern again the tempo changes to the proper saved value for that pattern. Anyone else see this?
Also, upon power up the Tempo comes up as 120 bpm, If I reload the pattern, the Tempo does not update. I have to change banks, then go back to the first bank and reload the pattern, then the Tempo updates. It seems to be specific to the Bank-01 patterns, I need to look at it a bit more.

[ben arturia]

Hi YESMAN,
Did you check global tempo preference in the MidiControlCenter ?
Best
Ben

[YESMAN]

Yes,
 That is how I got to this point. As I said Tempo changes work, the problem appears to be associated with the Bank-01 locations. If I change banks and select the Bank-02 slot the pattern Tempo will be correct, if I choose the Bank-01 slot the Tempo will not update until I reload the pattern. Hey, after a little more checking I don't think this is related just to the Bank-01 slot, it seems to be related to the first slot selected at a bank change or slot a-01 at power-up. I'll have to look further, I have not had time to do a more complete check.

 Ok, set up a few patterns with various known tempos in Bank A-01 thru 03 & Bank B-01 thru 03. When changing a bank & selecting a pattern slot the pattern will retain the tempo from the previous preset, reloading the preset will update the tempo to the pattern preset tempo. This is consistent. Are others seeing this, any response will be appreciated.

 On power-up the tempo defaults to 120 BPM. trying to reload A-01 does not update the tempo, I can load the other patters in the bank and have the tempo update. The only way I can get A-01 to update is to switch to another bank, then go back to the a bank and load/reload A-01.

  Thanks,
       B-

[ben arturia]

Hi YESMAN,

First please check that you have the latest firmware revision 1.0.18 :
https://www.arturia.com/support/updates&manuals

Then back up your sequences using the MdiControlCenter.
Perform a reset factory (please note that this will erase all your sequences) by pressing SAVE COPY PASTE and ERASE while booting the machine.

Let me know if it fix your issue.
Best
Ben

[YESMAN]

Ben,
 Yes, I have firmware V 1.0.18 running, did a reset no change. Also noted that the MCC wanted to update the MB, but the V it wanted to update to was 1.0.12
shouldn't this be 1.0.18?
    Thanks,
         B-

[ben arturia]

Hi YESMAN,

You're right something is wrong here.
A1 pattern tempo is never recalled properly.
About the firmware yes the version is 1.0.18 not 1.0.12.

Thanks

[YESMAN]

Ben,
Thanks very much for the quick responses and keeping on this. At the least I know its not a problem with my unit or me! It is something that is more of an annoyance than a deal breaker.
     B-

[ben arturia]

You're welcome !

[YESMAN]

Well, just wondering if this will be addressed. Are other users seeing this? It is not just A1 that exhibits the problem. If I load say A3 it's at 93 BPM. I then change the BPM to 100. If I reload A3 the BPM stays at 100. If I then load B4, then go back to A3 and load twice the BPM returns to 93. Maybe I'm missing something in the MMC settings. I will look into that. Or maybe a reinstall.

[YESMAN]

Is anyone else seeing this, Please take a moment to respond.
    Thanks

[YESMAN]

Anyone, Bueller,Bueller......

[Moho]

Anyone, Bueller,Bueller......

You picked the wrong day to ask, they're all at NAMM

[YESMAN]

Yeah, you're right about that. I was also hoping some users would respond as to what they find.

[jarreolog]

Hi,
Has this issue been resolved?
Because I'm experiencing similar inconsistent tempo changes (I'm on firmware version 1.0.18).

On a different, but related, note: is there a way for the Minibrute 2S to automatically load the last used pattern on startup (i.e., the one which was loaded at the moment of turning off the device)?

Thanks,
Pete

[psienide]

It has not been resolved on my end. Other loading issues like spontaneously switching the load bank to a different bank than the one you're in also plague this.

Unfortunately, it seems like Arturia has abandoned this product, so I wouldn't expect any firmware update to fix the issues.