Hi there,
Here’s an update on firmware 1.1’s state of things that Amos posted on another thread in this forum last week. Thought this might be of interest here too…
Cheers
Ben
I’m perfectly happy to use the old awkward method if that’s all that’s holding it back. Too late to be a beta tester? 
Couldn’t agree more. It’s not having to negotiate the update that is frustrating it is not yet having the finished sequencer when I have tracks I want to use it on..
Sure it will be worth the wait though.
Patience is a virtue Its gonna be one hell of a mail day.
Really excited for this release. While I didn’t necessarily mind the old updating method, it wasn’t too user friendly. I’m glad they are putting out a solution for this. Can’t wait to see/try it. If you need an extra tester, or one in the future, look no further!!
ps im a developer too, so I should make for a good tester. steps to reproduce and all 
damn right Amos you’re the man!
thank you so much for your dedication! 
woohoo!!!
Hi Amos - do you have a release date for us please? I don’t want beta software, but I have a few projects planned that are based on the promissory upgrades you’ve offered. Any advice from yourself would be very welcome.
I notice the sub37 manual is no longer for sale, so I’ll speculate it’s because of the update… Perhaps an updated manual will be a possibility.
I would think it’s RSN…the nice thing about Moog, they do it right.
Very cool they are throwing in a new update app.
Personally, I wanted to see a bit of feature creep in the arp behavior but that will have to wait.
Curious what platforms are being targeted for this update app? Both Windows and OSX? At the same time?
It would probably be wise to have both a SysEx and app based update if at all possible. This would alleviate any complaints about OS support or software bugs that might accompany the new update app.
Personally I’ve had no issues with the current update model but I’d hate to think that myself or others would miss out on all the great features of the forthcoming update just because the update app doesn’t work with their OS.
C’mon Amos - a timeline update, please!
It’ll come when it’s ready and not before. As it should be. I don’t want to brick my nicest synth!
Wise words lushr
Amos sent me the beta last week. I guess they’re just getting that all polished off before release. It’s a lot of fun though and will be well worth the wait.
Hi,
as a late and very new beta tester for the v1.1, I refrained a few times to comment and express myself around it/its release time/its lot of new features/bugs and so on, for I think there is a kind of agreement between Moog and any beta tester to do so. We test, we report and comment to Moog only(mainly, and me only, to Amos), and Moog does what it wants to do with it (I think Amos does his utmost to correct and fix everything, takes note of the suggestions, sometimes tries his best to implement directly what seems to be the most interesting/useful ideas and so on). As I think it’s really a one (amazing) man job, I specially respect it, and the time that passes, I know is a time well spent towards the best firmware update possible. I don’t try here to tease anyone about the v1.1, just to temper the best I can the heat that quite understandably can build up around this release. v1.1 is already amazing, will be even better than the last week last release candidate, will come with a simpler uploading installer for MS Windows and Apple OS X.
So please, if you are waiting possibly for a long time now for this firmware and maybe need it for good pre reason, I urge you to keep calm and carry on, the wait will be worth it a thousand times.
That’s it, I won’t make other comments around this, I hope everyone understand I do this with the best intentions in mind for us users aswell as for Moog, which truely offers us an amazing support and user/client experience, even not speaking about the instruments and that incredible Sub37.
All the best to all,
Greg
What you need to remember, is that this is not a hobby to some people, including Moog. It is a business, with paying customers who wish to be kept up to date - without being subjected to the silent treatment for weeks on end after the expected date has well and truly passed. If the business makes a time-based promise to its customers it’s in the business’s interest to keep it or provide periodic updates that aren’t (literally) weeks apart. I have the utmost respect for Amos, Moog and its employees, but it’s not fair to their customer base if updates, or lack of, are not released on time after building people up with an expected delivery date. It’s smarter and better to say nothing up front until it’s ready, and then announce it to the world. I do not wish to be seen as the bad guy here because I dare to complain. I’m in this for the long haul and expect promises to be kept. As an enterprise software designer, I suppose that I am against “leaking” new features to the customer base before I know that they are deliverable.
To be fair - I don’t remember a “promise” ever being made regarding the release date. I believe that it was intended to be ready rather than promised to be available for a set date. I can assure you that those working on the update are doing their utmost to have it ready ASAP - poor fella’s been working weekends and holidays. You must understand that it is impossible to forsee what difficulties may lie ahead when developing a firmware with so many new features.
To have purchased an item for serious work based upon it having ceratin features that have not yet been finalised is a huge risk to take if that work is time critical. I feel for you that you find yourself compromised and I understand the frustration of things not happening when you had expected but it cannot be blamed in any way on Moog IMO. It certainly wasn’t the intetion to be behind schedule but alas unaviodable.
Which features particulalry are you needing to complete your project?
Because it is a business, Moog should wait as long as it takes to provide a flawlessly working update!
It is not uncommon that an update is released later because of unexpected delay. It is a actually a project and every project can have delays which bypass the initial release date. With all due respect, it’s your choice to start a project which relies on software/firmware that is not available yet so you knew and probably calculated that there could be a risk that the update was not available in time.. I don’t think it’s fair to complain about this to Moog.
I own Nord, Yamaha, Korg, Roland and Hammond stuff and none of these companies communicate as much and directly to the customers as Moog does..
Moog, nor Amos never promised anything. Amos merely said he’d hoped to have it wrapped up a weeks after NAMM.
As an enterprise software designer, you of all people should know better than to plan on completion of projects based on upcoming software updates.
The last update I can recall seeing was Amos mentioning that they decided to include an easier update mechanism which was now causing additional delay. If the status hasn’t updated, I see no reason why Amos, nor Moog should have to come in and give a status update on regular intervals with no status changes. It’s not like Moog is doing Agile development with daily standups with all of its customers.
You may not wish to be seen as a bad guy, but you essentially are because you’re making statements that simply are not true. Moog never promised this update would be out on any given date.