New Firmware v3.1 for Slim Phatty, LP Stage and Tribute

[electronicpoison]

658 update file : Hello i could not see this file in the message below! B.d.electronicpoison

[Amos]

see a few posts later for the current version, build # 660.

djfood: I don't have Cubase at work but I have a version of it at home; I'll check it.
Pass-Thru mode seems to work OK for me. If Local Control is ON, it works as normal... if Local Control is OFF, then you must send the MIDI from the LP back into the LP somehow... I assume you are doing this in Cubase, but maybe that's where the problem is. When I use MIDI-OX to send MIDI in a loop from the LP MIDI OUT to the LP MIDI IN, I have no problem with Pass-Thru mode.

You might try connecting a MIDI cable directly from LP MIDI OUT to MIDI IN... set Local Control OFF, Analogue Mode - PASS_THRU... and see if it works. If so, then perhaps it is a problem with the way Cubase is set up?

[spin]

wow amos thank you very much!

just a question: i can't select anymore mod amount on little phatty stage II...it works only on calibration preset; in other presects i have to press/held the amount button to display the modulation amount, otherwise it doesen't light up and i can't see the led value (i see a generic led value set to maximum but it doesen't refer to anything). Could you tell me if is a prolem of my lp or not? It is strange that amount led works only on calibration patch while it doesen't work on other presects. No problems about this on slim phatty.

I ve tested arpeggatior for a while it works good!
Just a thing for LFO SYNC CLOCK....i found strange behaviour on 3 and 4 whole clock...on cubase 6 the lfo reset before it finish the cycle. No problems with other clocks^^

Thanks for your work, hope this helps!

[jgirv]

.. i had the same issue, but I haven't upgraded to the latest-greatest (as of last night)

...it's only for certain patches. The Mod Amount LED doesn't stay lit. But if you hold it down you can adjust the value. Of something.

...I'm sure it's like having a boxing match in a small closet for Amos to work with this new OS. continued thanks from all of us! - jgirv

[EMwhite]

Check pot mapping under advanced preset. Make sure they are not mapped!

The shifting of bits as new features have been added have this effect.

Ran into this yesterday (and in the past) Amos knew what it was immediately.

[spin]

yes there is a pot mapping problem. All presets have MOD PARAMETER mapped to something that isn't off

[Amos]

oops! I can fix this very easily... it's a funny side effect of my recent changes; I suspect if you set a preset to have pot mapping OFF for the modulation pot, and save the preset, it will remain fixed... but obviously all the presets have not changed, it's something I did. Don't worry, I'll fix this. Let me know if you have any other issues.

I'll test the 3 and 4 bar LFO times now... I know it's correct for arpeggiator, but I may not have checked LFO last night.

[The Beatsmith]

Thank you for this update! It has fixed the midi problems i was having - i eventually gave up and just used my LP Stage 2 raw, just as audio into Logic

Now i can record the midi for just the notes, mod and pitch wheel and nothing else... great!

I keep local control ON, but I use an 'External Instrument' in Logic to record the midi...

The update did fail the first time, i had to reduce the data rate, as is suggested in the readme troubleshooting... it was plugged into my Mac Pro octo 2.8ghz 2008, 10.6.7.

I can now record just the midi i want without having to use any weird filtering...

Looking forward to exploring the other features too!

Thanks Amos

Eddie

[nikola]

.. i had the same issue, but I haven't upgraded to the latest-greatest (as of last night)

...it's only for certain patches. The Mod Amount LED doesn't stay lit. But if you hold it down you can adjust the value. Of something.
- jgirv

i can confirm this.

[electronicpoison]

hello, now i have a problem to update my Lp stage II. the first update to 3.1. 653/32 went perfect. but now i want to upate to 659 and nothing happens. when i go to system utilities i do not fid the point FW update anymore????????? the last point in my system utilities is now calibration. what can i do?? ciao from Hamburg

[Amos]

OK, the Mod Amount button issue is fixed. Some interesting things I discovered:

1) this problem seems to go back to the earliest v3 beta release for Little Phatty. Funny it didn't come up until now.
2) A lot of the Little Phatty Stage II Edition factory presets have Pot Mapping enabled for the modulation pot; not for any good reason that I know of... they just do. You can check that this is so, even on OS 2.21.

So, fixes in this version:

1) LFO MIDI Sync "3 Whole" and "4 Whole" times are fixed
2) Modulation Amount button behaviour on Little Phatty is fixed
3) added some "default" values for Glide (on, not legato) and LFO Key Trigger (off) for old presets, so their behavior doesn't change with the new firmware. Of course you can change these parameters and save the presets how you like.

OS 3.1 build 660 for TRIBUTE EDITION
OS 3.1 build 660 for STAGE/STAGE II EDITIONS
OS 3.1 build 660 for SLIM PHATTY

I should probably include a README file explaining how to load this firmware... but, I think the beta testing period is almost done now. For electronicpoison:

To update firmware on a unit that is already running OS 3.x:

1) be sure you're all set to do the update, because the next step will erase the current firmware.
2) turn off the unit, turn it back on while holding down the MASTER button. Press PRESET to confirm update.
-The display should show: "Erasing Flash... Checking for USB Module... Please Send Firmware."
3) then open the PhattyLoader program, go to File menu and open the most recent update hex file. Then click Update Firmware to send.

[geoscience]

Amos,

The link for version 660 for the slim seems to point to the 659 file. Thanks for doing all of this for us!

- Geoscience

[Amos]

The link for version 660 for the slim seems to point to the 659 file. Thanks for doing all of this for us!

Fixed! and, you're very welcome.

[spin]

Thanks for update amos!

note: in glide mode there are not other values, only ON or LEGATO. hope this helps!

[Amos]

spin: that"s correct. glide OFF is done using the glide button on the panel. when glide is on, option are on (always on) or legato.
maybe the wording of this option could be improved?