Moog Music Forum

... i do agree, Amos. Wondered years ago why there was a choice to disable latching to begin with.

Take your time, we all appreciate the hard work getting all of the user requested happening. It's not easy!

thanks, jgirv

I agree; no need for latch disable! Thanks for all the hard work, Amos! I can't wait to use the new OS!

Amos,
I installed the Beta OS and noticed that the Volume sensitivity was not effecting the HP output. I'm not sure if you intended it to be this way for monitoring, but thought I should let you know.
edit. more problems. I am getting stuck notes while pressing more than 1 key at a time while volume sensitivity is up. This happens every now and then and seems to happen more often with long hard notes.

Benjaminam: What model LP do you have?

Thanks very much for the bug reports - I'm looking into it now.

Amos, there seem to be problems with code 3.1 and POLYPHONY mode (tested on STAGEII and SLIM):

- ARP doesn't continue playing back after a second note is pressed
- Sometimes both synths play at the same time instead of round-robin.

Thanks, Kami.

I can confirm HeadphoneVol Bug (if it is a bug, that is)

No stuck notes here, LP SE I

Amos wrote:Benjaminam: What model LP do you have?

Thanks very much for the bug reports - I'm looking into it now.

I own a Stage 2. Here is a video I made that documents the issue: http://www.youtube.com/watch?v=YbEHhQJvLpI .The stuck note occasionally occurs when Vol Sensitivity is turn up past 0 and two notes are stuck simultaneously

I think the stuck notes on Stage / Stage II bug is now fixed. I'm having no problems on my unit.
Also I fixed the volume velocity to headphone output... it was a simple oversight.
Volume velocity sensitivity will never be perfect; it's a bit of a "hack" ... that's why there's a little click when you play a soft note right after a very loud note.
Also, the envelope times can seem different on headphone output vs. the main output.
I recommend to use the main output with volume knob at maximum and adjust your system level accordingly. I don't use the headphone ouput (that's why I hadn't noticed the volume velocity issue)

Cheers,

Amos

(oops) almost forgot to post new links! This is beta 2:

Slim Phatty -
Windows: http://seamslikereality.com/moog/Slim_P ... A2_WIN.zip
Mac: http://seamslikereality.com/moog/Slim_P ... A2_MAC.zip

Little Phatty Stage / Stage II -
Again, this is a beta, update at your own risk, read the instructions carefully, etc...
Windows: http://seamslikereality.com/moog/LP_Sta ... A2_WIN.zip
Mac: http://seamslikereality.com/moog/LP_Sta ... A2_MAC.zip

(if you've already updated, just need to run PhattyLoader from these new files)

Hey Amos,

I'm currently running 3.04S 635 on an LPSII.

I just downloaded the Mac update in the message before this one. You mention only needing to run the PhattyLoader but I'm not having any luck with that. I can select my LP USB but it won't receive. On a whim I tried re-loading the bootloader but it seems now I don't even have the FW UPDATE setting on my machine. I'm pretty sure it was there previously. Maybe you got rid of it with v3?

In any case, I can transfer presets back and forth so I know I have communication happening but no PhattyLoader love via USB. Should I try MIDI?

MIDI (vs USB) made no difference. Data definitely being sent but can't seem to get the LP into the mode to receive. Strange as I was able to do it before.

Dumb question maybe but is your Phatty 'listening'?

aka.. You have to power up while holding Master then confirm as instructed.

@EMwhite - Wow - thanks for that! I don't know how I missed the power-up while holding MASTER but that was the missing mojo for me.

3.1S 648! Here I am.

Thanks again! I owe you one!

Amos - one question that I hope to validate tonight if time but will incoming MIDI notes work properly with the volume velocity capabilities as well? I'm assuming yes but thought I would ask. Thanks!

earsmack wrote:@EMwhite - Wow - thanks for that! I don't know how I missed the power-up while holding MASTER but that was the missing mojo for me.

3.1S 648! Here I am.

Thanks again! I owe you one!

Tricky sometimes. Some devices (and in the case of Phatty, which used to) respond to the first few bytes of a SysEx 'delivery' of code. Patches that are sent in still work this way.

Others (like the Phatty with the current v1.1 boot loader) must be enabled, start fresh with a 'flash' (erasure) of code NVram, etc.

The loader (the 3.x scheme) is actually the best approach since you cannot inadvertently send the wrong code to the device unless it's listening; also since it flashes the firmware first, it's in a clean state and not doing anything else.

Assuming the Boot loader code is solid, the chances of 'bricking' are slim to none (no pun intended there) because you can ALWAYS boot up into a "ready" safe state with nothing else going on, no other data, etc.

But general advice is to ALWAYS confirm that you have the right interface selected, the right Code version selected, and to choose the right packet size and time between each data block sent (on my Tribute only the slowest/smallest works reliably).

I agree - got it working now - so far so good. I'm finding I'm liking the volume velocity setting around the 3 setting personally. 8 is a little too sensitive for me.