Moog Music Forum

14-bit MIDI output is working for me (you have to enable it first, then it works)
Panic function is working for me.

I'm testing the already-posted v1.3.8.

If you reported these things not working,
1) make absolutely sure you're really using the most recent firmware
2) describe to me exactly what you are doing step by step, omitting nothing.

Either you're doing it wrong or you've discovered a special case that doesn't work...
in either case I'll need enough detail to do exactly what you're doing to reproduce the behavior.

Now, on to the other recent reported items... I'll fix any of them that I can reproduce.

MuzzFuzz wrote:I've just upgraded to 1.3.8 and I'm finding that (with Local On) no matter how I try to use Panic, it does nothing.

Murray - try doing a Reset Globals operation, in case it helps?
(http://www.moogconnect.net/downloads/su ... v1_1_4.pdf - see bottom row)

also, look at a MIDI Monitor on your computer (with usb connecting computer to Sub Phatty) and see if CC#123 is sent by the Sub Phatty when you press/hold both Octave switches. It is definitely working over here.

lastly, I'll be fixing a couple of unrelated things today and so there will be a new firmware version; maybe wait and update to the new version once it's posted, and then try again.

-Amos

Hi Amos,

Amos wrote:

MuzzFuzz wrote:I've just upgraded to 1.3.8 and I'm finding that (with Local On) no matter how I try to use Panic, it does nothing.

Murray - try doing a Reset Globals operation, in case it helps?
(http://www.moogconnect.net/downloads/su ... v1_1_4.pdf - see bottom row)

also, look at a MIDI Monitor on your computer (with usb connecting computer to Sub Phatty) and see if CC#123 is sent by the Sub Phatty when you press/hold both Octave switches. It is definitely working over here.

lastly, I'll be fixing a couple of unrelated things today and so there will be a new firmware version; maybe wait and update to the new version once it's posted, and then try again.

-Amos

I'm sorry, it's silly operator error.

As I've said in other posts, I'm coming back to hardware synths after a long break. Some previous gear I've owned has had a Panic button that produced immediate silence. Checking the SubP again now, the Panic function works if I press *and hold* either octave button and then press *and hold* the other. Takes a split second to function. If there's post somewhere that spelled that out previously, I definitely missed it.

Thanks for being patient with me!

Murray.

sbell.sd wrote:At least one more bug...
I'm trying to send 14 bit midi data from the sub phatty (via the 5 Pin DIN MIDI output) to a nord g2 midi input. It only receiving the MSB midi data. I also tried this with another midi input device and it also only received the MSB midi data.

I just searched the Nord G2 manual and didn't spot anything explicit about it handling 14-bit MIDI CCs.
I recommend you should use a MIDI monitor on your computer (such as "MIDI Monitor" for OSX, or MIDI-Ox for Windows) and look at the MIDI output from the Sub to see if it's 14-bit or not. This removes the additional variable of whether or not your receiving device is handling that 14-bit data correctly or not.

edit: you could certainly build your own 14-bit MIDI handling in the G2 engine using some math modules, if it isn't automatic.

Cheers,

Amos

Hi Amos ~

I had a solitary crash happen with crash FW 1.3.8 with Ed/Lib 1.0 when I touched the Mod Wheel while recording SUB PHATTY Audio with SUB's AU Editor FX insert into Lp9 OSX 10.6.8 (report sent via eMail) but running very smooth otherwise

confirmed the Beta Team presets didn't install on OSX automatically, but load fine from PC version ~ nice to have them! thank you!

sbell.sd wrote:Is this a bug or by design???

With a 16 bit digital to analog converter (DAC) connected into the pitch control voltage input (and a 4 3/4 digit multimeter), I am getting unexpected jumps in the pitch of the sub phatty. I increment the DAC output, slowly, each increment is about .0003 volts, but the sub phatty doesn't change pitch until about 40 increments (plus or minus 5 increments)

The short answer is that it's by design. The Sub Phatty scans its pitch CV input and rejects noise below a certain threshold. There is a "coarse" and a "fine" threshold, and a 400 ms time-out. The voltage needs to change more than the coarse threshold before the pitch will update, so very small changes very slowly will be overlooked, until they add up to be greater than the coarse threshold.

If you really want to test the input resolution systematically, send +5V for an instant then send your new "test voltage"... then +5V then the next tiny increment of "test voltage" so as to fool the noise-rejection algorithm.

Real world performance will probably be somewhere between 12 and 14 bits of accuracy; no worse than 12 and probably no better than 14. I hope it is acceptable for your purposes... if not, hey it's a budget monosynth, it has its limitations.

I have reduced the coarse threshold by almost half, in the next firmware... this should help the external CV sensitivity to small changes, at the cost of it being easier to get spurious pot-value changes in response to vibration (like heavy bass on stage, which could be a problem for some people).

Okay, here's the latest and (it is to be hoped) greatest Sub Phatty firmware!

http://www.moogconnect.net/downloads/su ... _1_4_0.syx

Changes in this version:

1) lower threshold for analog voltage changes (less noise rejection = more sensitivity); evaluate.
2) fixed response to CC95 - Active Panel on/off.
3) global data is reset on firmware update now - might prevent funny issues on first updating, such as "release not working until a reboot" as reported earlier.

confirmed that 14bit MIDI, panic function, and a few other things were working as intended.

robml: the issue you reported was not a firmware bug, but an Editor bug. I'll send out a new editor in a few minutes.

HumanByDesign: the change to Tilde (~) instead of asterisk (*) in preset names saved on the hardware was intentional. Windows OS does not allow asterisks in the file name, so it was causing problems in the windows Sub Phatty Editor to have preset names with asterisks in them. Tilde seemed like the safest alternative.

-Amos

HI all i was bussy with update with the firmware. i use my usb cable to connect it with my comp.
But the problem for me now is the midi is not BLINK, its only on! So far i cannot update my firmware. What can i do now?

Needa1 wrote:HI all i was bussy with update with the firmware. i use my usb cable to connect it with my comp.
But the problem for me now is the midi is not BLINK, its only on! So far i cannot update my firmware. What can i do now?

1) turn off the Sub Phatty, turn it back on.
2) what's it doing? anything?
3) if nothing, send me an email...
4) if LFO light is blinking, you can send the firmware again. before you try again, let me know how you're sending MIDI to the Sub Phatty (USB, DIN? through a USB hub or no?), what is your computer operating system, and what software you're using to send the firmware... thanks and good luck!

Also -- what was the previous firmware version on your Sub Phatty (what version were you updating from)?

Amos wrote:robml: the issue you reported was not a firmware bug, but an Editor bug. I'll send out a new editor in a few minutes.

hey amos

it's doing it outside of the editor, with my live panel.
looks like it's not saving or reloading properly.

also, fast decay is cc95 for the filter envelope, could you please let me know what cc is for the fast decay on the amp envelope. cc96 doesnt seem to work.

cheers

robml wrote:it's doing it outside of the editor, with my live panel.
looks like it's not saving or reloading properly.

also, fast decay is cc95 for the filter envelope, could you please let me know what cc is for the fast decay on the amp envelope. cc96 doesnt seem to work.

Hi Rob, your CC info is out of date... here's a new chart.
http://www.moogconnect.net/downloads/su ... v1_4_0.pdf

fast decay for filter eg is CC 117, for amp eg is 118.

CC95 now toggles "active panel" on/off... perhaps this is the source of your other confusion?
I have verified on my end that saving a preset does not change the state of any of the parameters.

Hello Amos.

Could you double check amp/filter eg reset and trigger mode?

I updated to the newest firmware, but those functions were not working.

Thanks.

Edit) working now. Never mind. I turned off and on SP. Now it is good.

bandmasta wrote:Hello Amos.

Could you double check amp/filter eg reset and trigger mode?

I updated to the newest firmware, but those functions were not working.

Thanks.

Edit) working now. Never mind. I turned off and on SP. Now it is good.

Hello

It happen to me very very often I still don't understand why, sometimes a "Initialize Preset" solve the problem, sometimes not, very annoying, it's the only problem I have ; EG Reset and Multitrigger
It's is the case from my very first version of the BETA firmware of the SubP from what I remember (Don't remember if it was working on the factory firmware).
A part this, everything work correctly for me.

Thanks Amos for your work I have so much fun with this beast.

A little Trashy Dubstep song made today, all the Bass and the "Melody" made with the SubP, with some processing on them : https://soundcloud.com/nofutureprod/nofuture-res-land
( Be carefull with the volume I'm not sure about the Scream, sounds good on my KRK and my Beyer DT880 but sound very bad (High Frequencies) on my outdoor headphones, advices on that are welcome, Thanks.

Needa1 wrote:HI all i was bussy with update with the firmware. i use my usb cable to connect it with my comp.
But the problem for me now is the midi is not BLINK, its only on! So far i cannot update my firmware. What can i do now?

same thing happens to me every time i try and upgrade from 1.3.9 to 1.4.0

when you turn the unit on the lfo rate blinks, just send 1.3.9 to it again and then it works.

but i cant get 1.4.0 to go on at all.

no hub, straight to usb via imac and c6.

cheers

robml wrote:but i cant get 1.4.0 to go on at all.
no hub, straight to usb via imac and c6.

what happens when you send the 1.4 file?
maybe try sysex librarian instead of c6?

It does seem like "something is up" with these EG settings, but they aren't misbehaving for me...
perhaps if one of you has a particular preset that is having funny EG settings under certain circumstances, you could send me the preset via email and I can test it here? just in case that's a factor... I don't know what it could be really...