Available now: Tone2 Icarus v3.2

[tumface]

@tumface

Interesting remarks. However your claims are not true. I added 2 pictures.

• At the attack fase. You see the highest + sample is above -6 dB, all - samples are below -10 dB. An explanation for this asymmetry in the time axis: the waveform is just asymmetric. Could be a (clever) design choice.

It's a saw wave, which is asymmetric. The non-linear appearance of your graph is caused by whatever scaling rule is used for the Y-axis, not an asymmetric amplification in Icarus. Sounds in Icarus would be very distorted if amplified the positive pole separately from the negative pole

During the sustain fase. Zoomed in at sample level: obviously oscillating. An explanation tor the oscillation during sustain fase: integers. Given the key a single waveform doesn't perfectly fit within a fixed amount of samples. (this might be the reason for the asymmetry during attack fase as well).

Integer is irrelevant here. The problem is that the zoomed-out waveform is not being generated without enough accuracy in the visualization.

You see the audio program (Ocenaudio) tries to regenerate / redraw the (continuous) curve. The start of the next waveform is almost as high as the one shown.

Yes, this is what I showed in my earlier screenshot. The zoomed-out view does not use this level of accuracy, even though it probably should.

[Essent]

@tumface

Interesting remarks. However your claims are not true. I added 2 pictures.

• At the attack fase. You see the highest + sample is above -6 dB, all - samples are below -10 dB. An explanation for this asymmetry in the time axis: the waveform is just asymmetric. Could be a (clever) design choice.

It's a saw wave, which is asymmetric. The non-linear appearance of your graph is caused by whatever scaling rule is used for the Y-axis, not an asymmetric amplification in Icarus. Sounds in Icarus would be very distorted if amplified the positive pole separately from the negative pole

During the sustain fase. Zoomed in at sample level: obviously oscillating. An explanation tor the oscillation during sustain fase: integers. Given the key a single waveform doesn't perfectly fit within a fixed amount of samples. (this might be the reason for the asymmetry during attack fase as well).

Integer is irrelevant here. The problem is that the zoomed-out waveform is not being generated without enough accuracy in the visualization.

You see the audio program (Ocenaudio) tries to regenerate / redraw the (continuous) curve. The start of the next waveform is almost as high as the one shown.

Yes, this is what I showed in my earlier screenshot. The zoomed-out view does not use this level of accuracy, even though it probably should.

That is why I supplied 3 screenshots with a high zoom level so you can view individual samples, so the wave editor's bias when displaying audio data becomes irrelevant at this zoom level.

[Teksonik]

That is why I supplied 3 screenshots with a high zoom level so you can view individual samples, so the wave editor's bias when displaying audio data becomes irrelevant at this zoom level.

Why don't you post some audio examples to explain why it matters at all? I think you might be focusing on minutiae.

Anyway, this is a great update. I'm loving the new filters and synthesis options.

Icarus 3.2 is an awesome synth.

[Essent]

That is why I supplied 3 screenshots with a high zoom level so you can view individual samples, so the wave editor's bias when displaying audio data becomes irrelevant at this zoom level.

Why don't you post some audio examples to explain why it matters at all? I think you might be focusing on minutiae.

Initially I was interested in the shape of the attack. That is normal, isn't it?

[Teksonik]

That is why I supplied 3 screenshots with a high zoom level so you can view individual samples, so the wave editor's bias when displaying audio data becomes irrelevant at this zoom level.

Why don't you post some audio examples to explain why it matters at all? I think you might be focusing on minutiae.

Initially I was interested in the shape of the attack. That is normal, isn't it?

It's normal to be interested in the sound of the attack. Being concerned about how it looks is perhaps not normal. If you think something affects the sound in a meaningful way then you'll have to provide evidence so the developer can look into the issue.

Otherwise it's all just kind of pointless pedantry. None of the other users seem to hear a problem so that may tell you something right there. But again if you can prove something of importance then by all means do so.....

[Essent]

That is why I supplied 3 screenshots with a high zoom level so you can view individual samples, so the wave editor's bias when displaying audio data becomes irrelevant at this zoom level.

Why don't you post some audio examples to explain why it matters at all? I think you might be focusing on minutiae.

Initially I was interested in the shape of the attack. That is normal, isn't it?

It's normal to be interested in the sound of the attack. Being concerned about how it looks is perhaps not normal. If you think something affects the sound in a meaningful way then you'll have to provide evidence so the developer can look into the issue.

Otherwise it's all just kind of pointless pedantry. None of the other users seem to hear a problem so that may tell you something right there. But again if you can prove something of importance then by all means do so.....

Eh ..... you have almost 20k posts, you should know something about synths. You know shape of the attack is an important part of the volume envelope!? You do not have to take my word for this, but everybody else will confirm this.

[Tone2 Synthesizers]

@Essent:
You made incorrect measurements and are doing false assumtions.
Please don't distribute missinformation.

- EQ was not bypassed before doing the measurements. This shifts the phase of the signal
- The software you used to make the screenshot suffers from aliasing when displaying zoomed-out waveforms. It displays garbage. It's not the synth that does things wrong

I won't waste any time discussing or answering this further as there is nothing wrong and there was never anything wrong with the attack.

[Examigan]

Did you see my question from yesterday?

[Tone2 Synthesizers]

I will take a look at this. But will need to connect my old Andromeda first to be able to test it.
- Make sure you switched off MPE in setup.
- try the standalone or vst2 to make sure that the DAW does not alter any midi messages
- you must use 'polyphonic aftertouch' as a mod source in the matrix. Do not use normal 'aftertouch'
- patch voicing must be set to polyphonic

[Examigan]

I will take a look at this. But will need to connect my old Andromeda first to be able to test it.
- Make sure you switched off MPE in setup.
- try the standalone or vst2 to make sure that the DAW does not alter any midi messages
- you must use 'polyphonic aftertouch' as a mod source in the matrix. Do not use normal 'aftertouch'
- patch voicing must be set to polyphonic

I think you were answering someone else (?), but my questions were here:

I'm not sure if there is a way to do this, but I'd like to be able to send only certain Oscs to the Glitch section and not whichever others. I know I can turn off certain Oscs from reaching the Filter section. I'd like that for the Glitch section too.

Also, is there a way to add patch notes so they show up in the browser?

[Essent]

@Essent:
You made incorrect measurements and are doing false assumtions.
Please don't distribute missinformation.

- EQ was not bypassed before doing the measurements. This shifts the phase of the signal
- The software you used to make the screenshot suffers from aliasing when displaying zoomed-out waveforms. It displays garbage. It's not the synth that does things wrong

I won't waste any time discussing or answering this further as there is nothing wrong and there was never anything wrong with the attack.

I pressed the init button. I would have expected this clears all settings, except maybe a filter cutoff. Why would an init leave an EQ on?

I explained why the software showing the audio was not wrong because I could zoom in at sample level.

I do not claim there is anything "wrong" with the attack of your synth. I was just curious about the shape of it and another user made some interesting remarks about my observations.

[Tone2 Synthesizers]

@Essent:
Because it is a musical instrument and not a scientific device. And I decided to make it sound this way.
You can easily build your own template init patches and save them in templates.

@examigan:
It might be possible but i will have to check it out.
It's sunday evening and i am not sitting in front of my computer. I will answer your question tomorrow when i am back to work.

[Essent]

After creating a clean saw of my own I did indeed get a 'clean' attack as expected. Nothing wrong with Icarus, nothing wrong with the audio software.

However I would advise to rethink what an init button should do for a big synth like this where it is easy for someone new to Icarus to overlook some settings.

[Teksonik]

As Markus said,

Icarus is a musical instrument not a scientific instrument.

Don't overthink it.

EDIT: I see you've had an epiphany so all is good now.

[Tone2 Synthesizers]

I'm not sure if there is a way to do this, but I'd like to be able to send only certain Oscs to the Glitch section and not whichever others. I know I can turn off certain Oscs from reaching the Filter section. I'd like that for the Glitch section too.

Also, is there a way to add patch notes so they show up in the browser?

1) Oscilltors and filters are processed per voice. The glitch sequencer is processed global per synth instance like the effects section.

It offers these routings:
Post FX: Glitch is proecessed after the effects section
Synth only: Glitch processes the output of the synth
Drums only: Glitch processes the output of the drums

What would be technically possible is such a routing for a future update:
Left: Glitch sequencer - Right: Bypass glitch sequencer
Then you could use the osc panning to control the glitch send level.

2) Technically it's not possible to implement a keyboard that works 100% relieable in all DAWs and plugin formats. There are a number of DAWs that steal keyboard input for certain keystokes as they use them as a hotkey (e.g. the 'space' key missing in Orion as it uses this one for play/pause). I am sure some troublemakers (especially here on kvr) would complain loudly about 'buggy' keyboard.
Since I am tired of having to deal with such bullshit, I won't implement it. Sorry.

When you open the patch browser and take a look at the right row you'll notice that the synth automatically tags the supported patch play modes like velocity, legato etc. The name of the patch author is also displayed automatically. If a Patch has a name that ends with 'EXM' it displays 'Designed by Examigan'.