This download contains new firmware updater apps for both Mac and Windows.
Please try these first and let me know if they work for you, and if you get any security warnings etc. (that should all be fixed now).
There are sysex files included in case the updater doesn’t work, but please do try the updater first.
If any trouble with the update, let me know.
Here’s what’s new in v1.1.14:
fixed a possible MIDI feedback loop when changing presets while the editor was connected
now keeps the editor in sync when toggling COMPARE on/off
this installer properly fixes the internal default preset (the one that is loaded when you INIT from the hardware) — still need to update Editor to use same Init settings
Sustain Pedal function now works in combination with Arpeggiator/Sequencer.
STEP EDIT mode: fixed a bug introduced in previous beta firmware; current-step indication on PRESET LEDs during playback now behaves correctly.
Thanks very much for checking this out, and let me know (and/or post on the moogmusic.com beta testing forum) if you have any issues or still experience any firmware bugs.
the updater v1.1.14 starts and shows " installing firmware" and on the sub 37 “Flash erased” unti this all is ok.
but the second installationsphase stops at 71 %.
I tried it two times.
The sub 37 shows on the global menu: M1.1.14 P1.1.13
Win 10 (x64) connected with USB
Edit: i tried it first with the Win 10 Midi driver, now with the MIDI_DriverSetup_v3.30.0 all works fine !
Hi all, I have installed the latest update (twice) and in since doing so I have lost the audio output. Have checked with headphone out as well but still no output.. So far I have tried rotating the main and headphone out knobs and the filter Cuttoff from nil to max with no change in output. Am I missing something obvious in the settings which are still the same as previous version that worked fine. Many thanks, Glyn.
PS I have just reinstalled the previous version 1.1.13, all works fine, then put in new version, again no sound output Guess I will carry on with 1.1.13. for now. Cheers Glyn.
This is kind of a big deal… it’s not acceptable for new firmware to cause the sound output to stop!
Fortunately or not, it seems you are the only person to report this symptom, so far. Obvious things to try after updating to the new firmware would be to toggle the MUTE button on/off on the hardware. Try this first… then try INIT SETTINGS from the global menu. Try these things after updating to v1.1.14 firmware and let me know if they make any difference in the silence.
Obvious things to try after updating to the new firmware would be to toggle the MUTE button on/off on the hardware. Try this first… then try INIT SETTINGS from the global menu. Try these things after updating to v1.1.14 firmware and let me know if they make any difference in the silence.
Thanks!
Amos[/quote]
Hi Amos, tried the mute and resetting of globals but alas still no output from main or headphone outs. Cheers Glyn.
Hey , I just ran the update (Win 7 x64) and in previous updates all went through perfectly as a reference . As soon as the Sub 37 started the update it got to FLASH ERASED and the software updater just sat there and did nothing , the Installed Version read , unknown. I left it for about 5 minutes but nothing happened, no update ever commenced. So I reset the Sub 37, and on powerup without even touching the pitch wheel it went instantly to the screen
FIRMWARE UPDATE
Flash Erased
Ready For Code .
I thought the unit was bricked with no firmware, so I unplugged the USB connection from the PC and left it there and after a minute or 2 it started the update on it’s own . All back up and working fine after the update finished.
My installation on OS X 10.10.5 went very smoothly.
Then… at first I thought I lost all sound (as someone earlier mentioned).
But… I realized what had happened and I sort of liked it.
I have a pedal plugged into the Volume CV port. Up until now, no matter where the pedal was located the volume came on at the level stored in the preset. Moving the pedal then would adjust the volume. My pedal was in the full back (e.g.: volume off) position. As soon as I moved it forward my audio came back. I sort of like this feature!
Incidentally, a good method of debugging a problem like this is to remove anything connected to any port on the Sub 37 except the audio output. Prior to discovering this (after realizing the volume was off) I powered down the Sub 37, unplugged both MIDI DIN jacks, the USB and my two CV pedals. When I powered the Sub 37 back on it worked perfectly. Working backwards I was able to figure out what had happened.
There is a glitch I discovered in the Stand-Alone Editor which I will post about in a separate thread…
there might be something wrong with your pitch-bend wheel; better check it. If it isn’t working properly, contact techsupport@moogmusic.com or call the factory.
actually on rereading this I may be mistaken… sounds like for whatever reason the update simply didn’t begin, the first time. That’s interesting but doesn’t point to any trouble with the pitch wheel.
the reason I mention it is because of the hardware maneuver to get into bootloader mode, which is the fine tune and cutoff knobs fully counterclockwise and the pitch wheel held at maximum… if it forced into that state just from turning on the power (without you holding the pitch wheel up), it might suggest that the pitch wheel was giving a wrong output voltage. However, what you describe is normal for the case where firmware has not been successfully loaded yet after an initial attempt; the unit always boots with that sequence of messages until valid firmware is loaded in.
The installer didn’t worked for me..so I used Elektron C6 to send the files and everything seems to be fine.
Firmware 1.1.14 and panel version 1.1.3 (i believe) is this correct?
yes and no… technically, if you send the new “step 3” and “step 4” files successfully, the panel version should also be 1.1.14.
However, there’s no change to the panel firmware at all this time, except for the updated version number. So you can leave it for now. There will be a final v1.2.0 build, for release. (that’s if there are no additional, incrementall builds next week… depends if there are still deal-breaking bugs)
Hi,
I had exactly the same issue as timbuk… the second install got sucked at 71% but at the third time it went fine.
By the way, thanks Amos for the explanation with the editor.prefs files… The editor is now running smooth !!!
Hi all, problem sorted, it was the CV inputs as Flareless reported earlier. Removed the CV ins from my Pro 2 reinstalled and it all works fine now. Many thanks, Glyn.
Guess I will carry on with 1.1.13. for now. Cheers Glyn.
