Moog Music Forum

Hello Amos,

It happen only in Active Panel mode:

When a preset is saved it stay as I saved it, but often when I go back in Active Panel Mode the SubP refuse to accept these parameters (Multitrigger, Reset, and this problem about higher note being ignored sometimes too).

Sometimes I just make an Initialize preset and the SubP accept it and sometimes I make it 4 it time and it refuse to accept certain parameters of the re-initialization.

Maybe it's a problem coming from me but honestly I don't understand what can cause this, the USB and DIN are working correctly I think.

But like I said, sometimes the Sub Phatty just stop responding to Midi message in Local Mode Off ( in Ableton ) and I have to reboot it, so maybe there is something that link those two problems.

And it seems that I'm the only one to have this problem so it can be a local one...

I'll make more tests until Sunday, after that I'll go back to school for a dual accelerated formation during 3 years so I will not have time to go often on the forum I think.


Thanks.


PS:
A little sound that I've made with the SubP ( A part the percussions ) :

https://soundcloud.com/nofutureprod/nofuture-awah

Hello,

So I play with the SubP in Ableton Live today;

When I turn on the SubP, the Filter & AMP EG Multi trigger wasn't working ( And the EG Reset too I think but I'm not sure for the EG Reset).
I make several preset initialization on the SubP ( 6-7 I think) ;
The Editor was showing the correct parameters that initialize preset should generate but the EG Multi Trigger wasn't working on the SubP.
However with the Presets it was working correctly.

I had to reboot and then it worked this time. (It's not always the case sometimes it's still not working after several reboots.)


After 30 min the SubP wasn't sending or receiving midi from Ableton Live via USB, a clip was playing in Loop and suddenly sounds and midi stopped.
( But it don't make the sound that Windows OS do when there is a USB cable connected or disconnected )
The connection to the VST Editor inside Ableton via DIN ( Midi USB Interface ) was still working, all the movements that I was making on the SubP was received by the Editor.

I had to reboot, then it worked.

After that, I had a stuck note problem, I pressed the panic button ( Octave + & - at the same time ) and it stop make sounds, then connection was loosed again.

After that I turn off the SubP and was a little bit bored so i stopped for the day.


Anyone having those issues ?

EDIT:

I try with the new editor 1.0.3 but I still have these envelope problems.

Mac OS 10.8.4
Logic Express 9.1.8 [64bit]
Sub P. Firmware 1.4.1
Editor ver. 1.0.2

Standalone Editor:

When using editor via USB & running Logic
Patch 4-1
Turn everything to 0 or center
All buttons off except Gated glide, Midi sync and fast decay for both Amp and Env.
Turn Glide Rate to max
Amp Sustain to max
Amp Release to max
Make sure OSC 1 is on Tri
Play some notes
Seems ok….
Now try to change the wave to around a Saw
Note will not sound at all or cut in and out as knob is turned.
MIDI transmits, but something odd is happening to audio.

I'm suspecting again, that this has something to do with an initialized patch being saved and brought to Sub P during 1.4.0, and doing odd things after updating to 1.4.1. This is consistent with each firmware update. The only way to ameliorate the issue seems to be recreating a new initial patch with each successive, new version.

Amos wrote:only the response curve of the mixer volume pots is changed.
however, the new volume curve makes the noise more usable, because it doesn't start to overdrive until a higher level now.
overdrive sounds great on oscillators, not as good on the noise.

sweet - will have to check it out when i get some time

cheers

regarding a recent email i received 31st august 13

1. i would add an overview to the instructions. explain what the instructions are for and why.

2. step one says this "The PITCH AMT, HARD SYNC, and ACTIVATE PANEL buttons may also blink on/off." I found that only the PITCH AMT, HARD SYNC and LFO RATE lights blinked, not the ACTIVATE PANEL panel light.

i managed to do the update without incident.

i would also suggest adding a step between 7 and 8.

"In the C6 application, click on ""Sub_Bootloader_v2_Updater.syx" and then click the close button"

I was concerned that the C6 app might try and resend the bootloader firmware, even if the instructions say to highlight one file, i think it could be confusing and of concern for the end user.

cheers

here are my thoughts after updating to SubPhatty_v268_2_0_0.syx

1. the noise is now much better. it's usable now which is good.

2. all of my presets are now not sounding as they did when i created them. some are drastically different, some are only slightly different but have lost their magic. im guessing more curves were changed than just the noise. im a bit pissed to be honest, i put a lot of effort into those presets, some of which are now destroyed and others that will have to be fixed.

tried to go back to "SubPhatty_v239_1_4_0.syx". wouldnt take. must be the new bootloader cant update older firmwares. (crying smiley) goodbye awesome sounds...

is there a way to go back??

resonance curve changed too? multidrive curve changed too? all mixer curves changed? ;(

EDIT: all good now. had to do a calibration to get it sounding good again phew back to sounding like the best synth on the market

hey, run a note calibration and it should fix everything - it's all in the tuning.
I need to amend the instructions, there is a change to the pitch-CV generation and it requires a re-cal.
No other pot curves or parameter values were changed.

note calibration is shift mode - bank 3, bank 4, patch 4 ... press low c# key twice to launch. Should take 5-10 minutes and then everything ought to sound right. let me know.

Amos wrote:hey, run a note calibration and it should fix everything - it's all in the tuning.
I need to amend the instructions, there is a change to the pitch-CV generation and it requires a re-cal.
No other pot curves or parameter values were changed.

note calibration is shift mode - bank 3, bank 4, patch 4 ... press low c# key twice to launch. Should take 5-10 minutes and then everything ought to sound right. let me know.

thanks amos. had me sweating there for a bit all good now.

Ever since I upgraded to the latest firmware/editor my Sub Phatty oscillator 1 (and therefore 2 and the Sub) appear to be pitched exactly 1 semitone flat of normal tuning. I have done the Note Calibration and Initialize Global Parameters procedures as listed within the manual at least 3 times and it is still exactly one semitone flat. Any ideas?

Firmware: 2.0.0
Editor: 1.0.3

Thanks

just recalibrated and checked here, it's bang on pitch... is your fine tune knob off-center, by any chance?

I keep seeing people stating they're running firmware 2.0.0, but the most recent download I can find in this thread is the 1.4.1 beta which I'm running. Is this 2.0.0 firmware available or only to people in the beta testing team?

Also robml is referring to an e-mail from August 31, but I haven't received any such e-mail. Also beta testers only?

I'm kind of confused about why the 1.x beta firmwares are released publicly in this thread, but the 2.x doesn't seem to be. And the editor beta is completely private?

Public discussions about (maybe) non-public firmwares and editors are freaking me out!

hi, sorry about that -- I should have set up a private forum for beta editor discussion.
I'm not an administrator on the Moog forum though, so I would have had to set something up myself...
I'm afraid I took the lazy way out and just posted here. It seemed natural since the firmware beta was indeed public.

The only reason the v2.0 firmware is not public, is because it requires an update to the boot loader firmware in order to run, and we wanted to test that update very carefully in a limited way before releasing it to the public.

I'm happy to say that all our tests were successful and the update is ready for public release. We will make an official announcement in the coming week.

Alright, all clear now. Thanks.

So where is this editor? I'm not interested in a beta. I'm wondering where the officially released editor is? Or more accurately, when. I appreciate the time put into it, no doubt. But... Well it's been pretty well expressed by others. Non the less, were waiting. Albeit impatiently at this point.

cjolson80 wrote:So where is this editor? I'm not interested in a beta. I'm wondering where the officially released editor is? Or more accurately, when.

I believe this question was answered one day/two posts ago:

Amos wrote:I'm happy to say that all our tests were successful and the update is ready for public release. We will make an official announcement in the coming week.