Available now: Tone2 Icarus v3.2

[Tone2 Synthesizers]

https://www.tone2.org/forum/index.php?topic=3083.0

[Tone2 Synthesizers]

Hi Markus,
can you please explain how custom skins work? Like how and where to pu the backround image? What is the name convention? And how to change the color of the knobs circle? What is the perfered image size?
And what else to take care off?

Thank you!

https://www.tone2.org/forum/index.php?topic=3083.0

[Tone2 Synthesizers]

...MPE in legato doesn't work. I thought maybe the update didn't work, but checked the about info and it is indeed 3.1.

I just checked it out and it works fine here (PC, Roli Seaboard, Icarus Standalone).

- In Icarus go to SETUP and enable 'force MPE'.
- In your DAW make sure that you DAW transmits all 16 Midi channels to the plugin (not all DAWs do support this with VST3). You can force this by using the Standalone, AU or VST2 version.

[Echoes in the Attic]

...MPE in legato doesn't work. I thought maybe the update didn't work, but checked the about info and it is indeed 3.1.

I just checked it out and it works fine here (PC, Roli Seaboard, Icarus Standalone).

- In Icarus go to SETUP and enable 'force MPE'.
- In your DAW make sure that you DAW transmits all 16 Midi channels to the plugin (not all DAWs do support this with VST3). You can force this by using the Standalone, AU or VST2 version.

Sorry should have mentioned my system. Using a Mac with Bitwig and VST3. Will check the AU in Ableton. And yes I have Icarus set to force mpe (mod wheel to timbre). Device set to mpe. Mpe is working somewhat however the same issues are there as before (a new legato note can’t be pitch bent and returning to a previously cut off note loses its expression momentarily causes jumps in pitch or expression).

Shouldn’t be the DAW in this case though as several other VST3 synths work perfectly fine with legato in MPE (e.g. Equator, Current, Surge, Plasmonic, Generate, Noisy, Vital, 6 Sines, Audio Modeling)

[Tone2 Synthesizers]

As mentioned in my previous answer: Try the AU or VST2 version if you DAW does not transmit all midi signals in VST3 format.
MPE requires all 16 midi channels

[3lu5iv3]

Can u change the title from available soon: to released?

[Tone2 Synthesizers]

sure!

[Teksonik]

https://www.tone2.org/forum/index.php?topic=3083.0

Excellent. All I really wanted to do with skinning was change the background color to an even neutral grey and the method in your link worked perfectly for that task. It's much easer for my eyes now.

Is there any way to edit the backgrounds of the other skins such as "Dark Blue (Popular)" etc?

I don't have the skills or talent to create skins from scratch but is it possible for someone who does to make entirely new skins with custom knobs etc? The following bullet point would seem to indicate so:
[*]Added support for custom skins.

The new file path persistence when loading waveforms feature is a godsend. It makes building wavetables from single waveforms so much easier.

Thanks for this update.

EDIT: I'm just curious, is this post "over-dramatizing, bean-counting, whining or arguing" ?

[Echoes in the Attic]

As mentioned in my previous answer: Try the AU or VST2 version if you DAW does not transmit all midi signals in VST3 format.
MPE requires all 16 midi channels

Bitwig is probably the best and most comprehensive MPE Daw. It transmits all channels. MPE works fine on polyphonic mode, but same problems persist as before for mono legato as before the update. No change. And as I mentioned there are many (which I listed specific examples of) that work perfectly with vst3.

When I get a minute I will test the AU in Ableton Live and report back in case it’s a vst3 only issue.

[morphex]

https://www.tone2.org/forum/index.php?topic=3083.0

Thank you so much for the update. The range of possible sounds is absolutely phenomenal!!

[Tone2 Synthesizers]

@Echoes in the Attic:

I already answered to you twice: Use VST2, Standalone or AU if you require MPE / Midi. Bitwig supports VST2. There are no disadvantages by using this version.
It is a well known fact that the VST3 format can not properly handly midi channels.
I will not further discuss about the technical mess of Steinberg's VST3 format as there are plenty of other threads about it in the developer forum.
If you need further help you can send an email to support@tone2.com.

[Echoes in the Attic]

@Echoes in the Attic:

I already answered to you twice: Use VST2, Standalone or AU if you require MPE / Midi. Bitwig supports VST2. There are no disadvantages by using this version.
It is a well known fact that the VST3 format can not properly handly midi channels.
I will not further discuss about the technical mess of Steinberg's VST3 format as there are plenty of other threads about it in the developer forum.
If you need further help you can send an email to support@tone2.com.

@Tone2 I’ve already listed a whole bunch of synths that work perfectly with MPE in VST3, so it doesn’t seem to be a well known fact at all. If you are not able to fully support it that is your decision and I have no comment. It may justifiably not be worth the ROI to support. But your release notes state that VST3 is supported with MPE since V3 and the 3.1 release notes do not indicate that improvements are limited to AU and VST2. So it’s natural to assume you’d want bugs reported. And useful for Cubase users to know that this particular improvement doesn’t apply to them. What you do with that info is up to you of course. I’m just letting you know from a customer experience.

I look forward to testing the AU as that could still be useful in Ableton or Logic.

Is the trackpad not working consistently only a VST3 issue as well? Will test that as well with AU and report.

[Tone2 Synthesizers]

I tried to solve the issue that you reported with the trackpad in this update. I did this fix *exclusively* for you as we did not receive any reports from other users. I am sorry that it did not work for you. You can contact me by email if you want to beta test.
I will move on now and will not answer further questions as we do not have a support forum on kvr. The right place is here:
https://www.tone2.com/faq.html

[Tone2 Synthesizers]

I further want to point out that Icarus 3 and all our other synths are rock solid. We did not receive a single valid crash report since over one year. So there is no need at all to over-dramatize, bean-counter, whine or argue here

[Echoes in the Attic]

I further want to point out that Icarus 3 and all our other synths are rock solid. We did not receive a single valid crash report since over one year. So there is no need at all to over-dramatize, bean-counter, whine or argue here

I very much agree and was thinking the same thing. A bug report should simply be that, a report about the facts without any emotion. It’s great that you made an effort to fix the trackpad issue. Too bad it didn’t work out and I did say it was disappointing but it’s still an amazing synth and not the end of the world that trackpad scrolling doesn’t work. Massive X doesn’t have trackpad scrolling at all so at least you tried!