Announcing new Operating System, v1.4.0!

[aumwer]

Thanks for the update to all involved. Great job !

[Scott_V]

I'm sure it's in front of my nose, but where can I find the 1.4 download link?
Thank you,
Scott

[Oehi]

Great news to the finish of this year. Thank you so much Jim and John for your effort and dedication. Great work.

Werner

[Octupole]

John, Jim, thank you SO MUCH for your christmas gift - and in addition nearly a birthday present for me . I appreciate the MIDI implementation - can't wait to feed may Mackie C4's and my old faithful Emagic Sounddiver with that.

Season's greetings to you and all Solaris owners!

[niversen]

1.4.01 downloaded - its going on the Solaris in a moment! Again, many thanks! I would love to have a software interface that had some patch randomization and genomics like the SoundTower editors for Dave Smith Instruments. But with SYSEX support, it should even be possible to set up a Lemur patch or such on iPad and have the ability to do X-Y pads, touch faders and other goodies as an adjunct to the front panel. The SysEx functionality is actually a very big deal if we in the community put ourselves to figuring it out. There's a lot of possibility here.

[minorguy]

My apologies for the bug in the initial release that had to be pulled back. I missed it. It wasn't something that could be left in and fixed later. At least it's out for the holiday break.

[John Bowen]

... I would love to have a software interface that had some patch randomization and genomics like the SoundTower editors for Dave Smith Instruments. But with SYSEX support, it should even be possible to set up a Lemur patch or such on iPad and have the ability to do X-Y pads, touch faders and other goodies as an adjunct to the front panel. The SysEx functionality is actually a very big deal if we in the community put ourselves to figuring it out. There's a lot of possibility here.

I’ve had some interest expressed in having Midi Quest add a Solaris module to their Editor package. I should probably post a new topic asking about this, but of course, they are curious how many would be interested.

[jazzbo58]

Thanks to Jim and John! #200 is up to date. It was truly painless.
Cheers,
Jim

[synthologist]

"10) An extra parameter was added for the Osc modulation amount parameter when the destination is LinFM. This separated it from the amount parameter for Shape. Older presets will sound correct IF the destination is set to Shape. However, if the the preset uses destination LinFM, when the preset is loaded by an older OS the sound will not be the same because the Osc modulation amount will not be correct. Also note there is no way to make such a preset backward compatible by setting the Shape amount because the ranges for the two amount parameters are different."

Would anyone care to list any presets that are changed by this? We can compile a database

[John Bowen]

What he is saying is that any presets created now with v1.4.x will have this new parameter location, so if you get such a preset and are still using v1.3.1 or below, it won’t ‘know’ about the new value, and so any Linear FM will have to be tweaked - again, only if you are using an older OS.

Update - it might be that v1.4.x OS systems will also load a zero default value, so in this case, it would require a database of sounds that were using Lin FM. I’ve asked Jim for clarification.

[minorguy]

John is right. The only time you need to care is if you are using an old (1.3.1 or older) OS to load a preset that was saved with 1.4.0. And then only if an oscillator was using LinFM as a modulation destination.

You probably noticed in earlier OS versions that the amount for Shape and LinFM were "linked". They shared the same value. Except that LinFM amount had a different range---when you set a value of 11.4% for LinFM and switched the destination to Shape, the amount was then 11%. And when you switched back it was 11.0% because the .4 got dropped.

The reason this change had to be made was because the amount for Shape and LinFM destinations had a different range and this didn't work well for SysEx (or for that matter, NRPN or anything else). The amount for Shape had a range of 0 - 100% and the amount for LinFM had a range of 0 - 1000 in tenths of a percent. So when you received a SysEx message for the modulation amount, there was no way to tell what the value actually was without also knowing what the destination was.

There are other places where the modulation amount is shared, in the filter for example. But in all other cases the range is the same 0 - 100%. So it doesn't really matter.

[John Bowen]

Quick update - There was a small bug when using Compare mode that altered Mod Sources, now fixed in v1.4.0.2, which I’ve just posted. Please install this version if you have v1.4.0 or v1.4.0.1.

John B.

[scope4live]

Thanks guys

[urge]

Well, I'm having some difficulties. I'm on a Mac running Yosemite and I can't open the OS file to alter the text file. Preview is telling me the file can't be opened. Is there a specific app needed to unzip the file ?
Anyone else on a Mac updating? Thanks for the assist folks.

[urge]

Managed to sort it out. My CF card was missing the txt file. Thank you for your hard work on the OS.