Main command: Buy an Atomic!
Just kidding! My other guitarist has a Stomp, and it’s great!
Yes I can also confirm cadence-9 is working 
- result 
It worked!!! It didn’t crash, and I was able to update. Nice update, guys!
Friends, we’re stabilizing a release, hopefully the last in the “cadence” series.
With this, we’re going to make generally available features you’ve been enjoying for a bit, like sending messages on step or on release, or being able to send messages via bluetooth.
We’ll move on to the “delight” series of releases, which won’t focus so much in introducing new features or capabilities of the MM, but in making it easier to understand, navigate, and use the app.
The main goal with cadence-10, which you will have available any moment now in the App Store, is that the app doesn’t crash – and that we can tell if it does!
Let me know if in regular use it crashes for you, because we will be promoting this release to Production.
I’ll clue you into specifics of the the delight series later, but in general:
- We expect to keep the pace of about one release a week for you guys
- We expect to increase the pace of releasing to general availability to at least once every two weeks
- Changes are expected to impact appearance and usability, not “actual features”.
- We expect to end the delight series by the end of the Summer
About the iOS app – I’m sure you’re impatient right now – it’s moving towards being roughly equivalent to what we have in the baseline release series. We expect to have it in the Apple App Store by the end of the month, and skip the whole cadence-specific developments to catch up with the delight series of releases ASAP.
I’ll keep you posted. It’s been a long road, and what the app and MIDI Maestro are Today is very superior to what we had in mind and hand on January. I hope you’ll continue to inspire us to introduce even more improvements, so that what we have next January leaves Today’s version in the dust.
Thank you all for your continued support, it’s been great having you by our side – I get cold sweat only by thinking what would’ve happened if we’d gone to production with the issues that affected @TheWolf2103, or @Imagine, or everyone of you who helped us test and work out kinks.
Thank you all for allowing us to steadily walk up to an amount of features we feel happy about (hence cadence ;)) now that we have a little jewel let’s polish it so it’s delightful.
One specific I will give you: we’re planning to insert all of the BB and Aeros commands used in the Default Modes so that you can use them in your Custom Modes as soon as feasible, probably by the end of next week if things go well in production with the Cadence release.
Lots of love, best of wishes, and a million thanks!
5 Likes
Thanks for the update @iajrz - looking forward to the future updates & hopefully “presets” in a pull-down menu to choose for the standard BeatBuddy functions - that would things so much easier
Keep the good work coming 
Logic Pro or other DAW
Yamaha DTX devices
Apps - Loopy, Quantiloop, Onsong, Ultimate Tabs, Ableton, Amplitube, etc.
I can’t find the rest of this conversation: Can you give me some context, please?
Hey Joe,
I think that’s a reply to the “what gear do you use that MM should work with” question.
P
Thanks, Phil! I scanned but didn’t see it.
Yeah, Phil’s got it. I hit reply to that message, and when I view it, it does show in that thread, but also seems to post as a new message… operator error I guess.
1 Like
Hey @iajrz Irving!
I know I’ve been quiet lately, the work from home thing has turned out to be a really busy time! But I’m back with a request: Can we get a double-tap command function?
It’s the last really big thing I need (that might be a lie ). If I can get that on the MM, I can rack my BB; If not, that changes my programming layout on my MM, because I’ll plan for having the BB right there next to the MM.
Big request made. Now, I want to turn my attention to all the good work you guys have done to the software and available functionality. I haven’t had time to play with it in a while, and, now that I have again, I want to say to you, Irving, @DavidPackouz and @BeatBuddy_Support, that you guys are doing a spectacular job! I am really pleased with the progress and software support, and even if it is slightly unwieldy, it gets the job done.
My next requests are going to be much higher level:
- The ability to save individual button programming so I can drag and drop them across different custom layouts
- A “Save As” function, so I can more easily duplicate related commands (things like transitions that share the exact same information except for the value sent to the CC). Maybe something as simple as, if I change the name, you don’t overwrite the original?
- Ability to save and export commands/command lists/programming, button definitions and custom layouts. Followed by – you guessed it…
- Ability to import commands/command lists/programming, button definitions and custom layouts
Those last two would make it easier to help people doing their own programming, and we could create a community library of functions and layouts. In addition, some of us enterprising folks could add command and layout libraries for other products (I have a Hughes & Kettner GrandMeister and an Atomic Amplifire that are crying out for better MIDI control).
Thanks for all you’re doing – I am so happy to see the MM getting this kind of love!
Hey, I was wondering about the ext and exp jacks. Is there any information about these? Are you guys working on having the app be responsive to those Jack’s? Thanks.
1 Like
Working on Exp Pedal coming soon~!
1 Like
When will we see an iOS version?
Right, everyone with an iPhone – please chime in: we’re doing a closed alpha. Send an email to irving@singularsound.com with the subject MM App iOS alpha.
The iOS version, for reasons we hope never to bump into again, will have an UI much like the “baseline” series of releases – same thing will happen with functionality.
After the alpha testing results satisfactorily we’ll do catch-up with the Android capabilities in a blitz, so that we’d expect them both to be on the same state by the end of August.
It’s a pain, I know; and not what we’d like to have at this time; but we’re taking measures to avoid something like this again: We’re internalizing iOS development, being clearer with our roadmaps and developer docs.
In fact, we look forward to internalizing more and more of the processes required to deliver a great experience to you all. It’s taking some time, but I hope the improvements across the board are visible to you – faster response on all projects, more stability, more transparency.
Heck, I wanted to put together my debut single in the first half of the year and couldn’t: I’ve not been able to devote time to that, absorbed as I’ve been pushing towards a more trustworthy, more predictable, more exciting – and frankly, more likable – development team.
So iOS will be a bumpy ride, but our lessons learned from Android mean it’s going to be shorter if not more comfortable. It will all depend on how the alpha goes, and how internalization of the development workflow happens.
Thank you for your continued support, everyone. We’re about to hit an inflection point in the history of Singular Sound, and I’m excited to say I’ve helped make it happen. Faster and more reliable development is just the start of the changes I’m bringing to dev. I hope to tell everyone more in a few weeks.
4 Likes
<3 I’d love to give you that MM double tap; we have it in a backburner, and look at it and think about it from time to time.
We’re working on internalizing MM firmware development, and thinking about the hardware constraints we have, to see how we could go about doing something about double tap and other features we want to put in.
The main issue we see with double tap is that they’d not coexist peacefully with down-press or release commands, because the ones tied to a single press would have to be delayed (while we confirm if this is a single or double tap).
If you could describe what usecase you have for the double tap – ie, how the button would be configured in all – it would help guide our thinking.
Use case? Exactly what the main pedal uses a double-tap for: To end the song. Basically, I’d love to turn the bottom three buttons on the MM into a button-for-button replacement for the main pedal and outboard switches.
On the main pedal, I suspect you currently differentiate between a double-tap and two taps based on the tempo of the current song, so that could present a challenge, but, then, I suspect most people double-tap at roughly the same speed regardless of the tempo, so the workaround there might be to offer some control over the maximum acceptable gap to recognize a double-tap.
1 Like
Alrighty, I’ll look into this with that very particular setup in mind, see if we can come up with something satisfactory. I already have some ideas. Thanks for the feedback.
1 Like
Not sure if this has been considered, but could you send midi commands on a page change?
So if I were to use the ext buttons to go to the next page, could the MM send PC or CC commands as the next page is displayed?
This would be useful if the MM was used for set lists, or if you want to initiate a transition on BB as you go to the next page. Or maybe change amp channel per page.
Something to add to the feature list 