I had to re-enter the commands into the app and now it works perfect!!
I noticed that while I was re-entering the commands that the channel changed on my three midi maesto’s!!! All three maestro’s went up one channel. I had beatbuddy on channel 1 and Onsong on channel 2 and voicelive3 extreme on channel 3.
I guess when the app updated it also changed the channels of all the saved custom modes. When I updated the firmware and the Default modes, it erased my custom modes on all three maesto’s.
When I re-programmed each device they each were re-programmed 1 channel higher. So they still wouldn’t work.
When I re-set the channel’s on each app setting for each maestro it all started working properly again.
OK guys - can you please help me with the following programming issue - next part or/and previous Part.
Please have a look at the attached pictures - this is what I defined for the “Next Part” command - unfortunately it’s not coming out of the transition
Where do I go wrong?
I’m just guessing but, try reversing your entrees.
Try setting up the “Finish Transition” first and then the “Next Part”
In other words have the “Finish Transition” on top.
It looks like it’s going to the “Finish Transition” first!!
Cheers @churchman, tried that already - you can’t - it kind of randomly (?} orders the commands… though I found out that the next part or previous part is working, but only if I press the button again - I. e. you press once the transition starts you press again the transition finishes and the next part starts - so, it’s the automatic transition missing…
Cheers for the suggestions @churchman - sadly disabling double tap function doesn’t make a difference & the footswitch is configured with the BB as momentary already - must be within the MM somewhere (not accessible by the app)… the MM seems to read the commands sequenceably but only when triggered by another button press…
Did you update the firmware on both the MM and the BB?
If not the app now has been updated automatically so turn on blue tooth on the MM and on app click on the firmware update.
There is also an update for the default modes ( beatbuddy and Aeros looper).
Also check that your BB firmware is up to date as well.
P/S After you update the firmware and the default modes, check your app channels, for some reason the update pushes all the command settings up one channel so you will have to manually go into each command and change the channel back to what you want.
The BB is at v3.8.0 & the MM is at v1.0.7 which I assume is the current firmware version for both units.
I think you may have a point with the momentary vs latching mode of the MM which we can’t change for the MM through the app (yet?)
Well, I guess we’ll have to wait until further developments come through - until then I continue with my BB plus footswitch…
The CC-113 command should work as a “press and release” in custom mode as it does in BeatBuddy mode in our next Maestro firmware update, which should (hopefully) be rolling out by next weekend.
I’ve noticed this too when putting commands in all at once, I forwarded this on. It will be added to our list of stuff to fix.
This only applied to footswitches, connected to the footswitch jack of the BeatBuddy, not devices connected via the MIDI port.
Hey guys! Sorry I hadn’t updated you, specially @TheWolf2103.
We noticed something confusing in the firmware update procedure and were trying to make it better.
We did make it marginally better, will test the improvement Today, then keep moving forward with the release.
Remember, you guys here are the second group outside of developers to look at the code.
It’s development team -> customer support team -> you -> people who opt in to open beta (none have done so yet) -> everyone.
So the customer support team detected we were obtuse on the UI… because this firmware update requires updating the default modes, and re-sending the custom mode to the device, and we didn’t properly point it out.
BUT! Having said that, even if the UI is still a bit cumbersome Today, we’ll let you guys know. After all, we can hash out any confusions in here.
JUST TO MAKE IT CLEAR:
This App Update will require a firmware update. You’ll move up to firmware 1.1.1
This App Update will also require a default mode update. You’ll know you updated the firmware and need to update the default mode because your MM will read “EEPROM INVALID”.
This App Update will also require a custom mode update. You’ll know your default mode updated properly because on the “main” mode selection page you’ll see a 1.1.1 on the lower left. Your custom mode will say it’s empty. You just reconfigure it and you should be good to go with all the goodies.
In fact the app is always crashing when updating the firmware (I have Samsung Galaxy S7) and I have done several sucessful firmware upgrades with the previous app versions. The default mode update goes through though but leave me with “EEPROM INVALID”.
I am not sure what to do now.
@Imagine
If you have another device, try uploading the firmware without updating the app. I think today’s top tip is update firmware first, then update the app.
Have you sent the crash reports in?
I am getting the same issues, I can upload custom modes and update default modes, however as soon as I press yes on update firmware, the app force closes. @iajrz
Think it’s something to do with android strict mode.
Exception class name. NetworkOnMainThreadException
StrictMode Java
Android.os.StrictMode$AndroidBlockGuardPolicy
