All is working fine - installing the Firmware & Editor was easy and flawless... Thanks

It is, sadly, industry standard. Always good to wait at least a year or two when a product is released; unless, you just have to have it.JemenJ wrote:Word!
I cant but to think that this is a yet another example of rushed product release. Let the consumers pay big money for cripled synth. Beta testing should be dealt with before releasing new products to the market! Why we have a Little Phatty Stage II.... Why there are so many first versions of Little Phatty on the second hand market...? Must be a major harware desing flaw that could not be fixed by just updating firmware?
I'm waiting for Sub Phatty Stage II. Maby then the beta testing is over.
I've had the Sub Phatty since April; I would hardly have called it crippled even then. I did not participate in the editor beta, but I'm grateful to those who did.JemenJ wrote:Let the consumers pay big money for cripled synth. Beta testing should be dealt with before releasing new products to the market!
Hey, Murray.MuzzFuzz wrote:Hi All,
I agree with jjlucas76.
I personally don't mind beta testing the firmware updates as they become available. I've owned my SubP since early May and I bought it purely on the strength of Amos' NAMM demo video. The firmware in the synth he had for that demo was probably at a guess 1.03 or something and I certainly didn't see or hear anything that gave me any pause.
I'm really enjoying contributing to the forum and watching the synth grow. I think it's maturing nicely and personally I feel it is certainly more usable now than it was out of the box. (Implementation of sustain pedal response and the adjustment to the response of the knobs have been the two biggest improvements for my work.)
I agree with jjlucas76's comments about how difficult it is to keep track of current status.
I have kept all the firmware files I've downloaded and made a little document to note what I installed and when. Without functional software I'm pretty sure it's impossible to know what firmware is loaded.
Very early in the piece before testing became a subscription only game, I discovered an early version of the Windows editor software on the SubP FTP site (I was browsing that site regularly to obtain the latest updates because as the OP said, things became hard to follow. Of course it didn't work, so I posted a simple query about that and an error dump. Rather than a quick explanation and maybe an invitation to get on board, next minute the FTP access was blocked and we find ourselves in the current situation. I was disappointed with that. Also, I'm not one for posting "Where can I download the Editor?" notes every other day, as if we were reading some usenet software crack group from 20 years ago!
I too think the updates could be organised and documented better. A sticky would certainly be useful. I personally would like to see a document that summarises the changes, additions and fixes for each update.
On the other hand I understand Moog is a small company and Amos and his associates have a lot to deal with, so the extra work that goes into such documentation may slow the process down to an unacceptable rate. I love that Amos gets involved personally and that we're not having to raise a service ticket for each request that disappears into the ether. I don't want that to change. There has to be a happy medium somewhere.
Cheers,
Murray.