One-Synth-Challenge 57: Tunefish - Chat & Gossip

[RichardSemper]

Okay, I think this one is a genuine bug:

Maxing out the RESONANCE on the LPF results in a crash. Seems to be related to high frequencies again.

1. Create a square two octaves up
2. Turn up the CUTOFF on the LPF
3. Turn up the RESONANCE on the LPF (usually above 80 - 85)
4. Crash (and ear splitting noise!)

So far the other filters seem fine.

I did this also. resulted in the track maxing out. No crash, but also no more sound from that instance of the plugin. All other instances continued to work fine.
NOTE - I have put limiter on master track to avoid splitting ears, since the first versions of this plugin did wild things like this all the time.

[Kondarivan]

Okay, I think this one is a genuine bug:

Maxing out the RESONANCE on the LPF results in a crash. Seems to be related to high frequencies again.

1. Create a square two octaves up
2. Turn up the CUTOFF on the LPF
3. Turn up the RESONANCE on the LPF (usually above 80 - 85)
4. Crash (and ear splitting noise!)

So far the other filters seem fine.

I did this also. resulted in the track maxing out. No crash, but also no more sound from that instance of the plugin. All other instances continued to work fine.

^ This. And now I'm so grateful for Reaper's auto-mute feature

[payne_bc]

Okay, I think this one is a genuine bug:

Maxing out the RESONANCE on the LPF results in a crash. Seems to be related to high frequencies again.

1. Create a square two octaves up
2. Turn up the CUTOFF on the LPF
3. Turn up the RESONANCE on the LPF (usually above 80 - 85)
4. Crash (and ear splitting noise!)

So far the other filters seem fine.

Ok, couldn't make it crash but the ear raping is confirmed
Here's the remedy At least I cannot manage to get it to do that again. Feel free to try.

http://www.tunefish-synth.com/beta5/vst24_tf3_x64.zip
http://www.tunefish-synth.com/beta5/vst24_tf3_x86.zip

[H-man]

ear raping is confirmed

Thanks yet again, I'll give it a try.

I actually did have Vladg/Sound's Limiter No.6 on the master bus however I had disabled it because I'm not really familiar with it and the way is colours the sound yet.

On another note, starting to get some sweet noises out of this thing

[V'ger]

Obvious but worth reminding that for DAWs without an auto-protection system, it's of course good practice to ALWAYS have a brickwall limiter on the master bus. Like said, Limiter No6 also does brickwall limiting, but maybe best used for normal limiting so best with a no-frills dedicated one at the very end of the chain to protect you and the hardware:
Barricade
LoudMax
FR-LIMIT 87
Volume Eleven

[H-man]

Thx for the reminder V'ger.

To be honest, in this case it was a little more like this:

http://gph.is/YBbKqe

[nitrowheels]

First of all thanks payne_bc for being so quick interacting and applying code changes. To my taste your synth is excellent.

One thing I noticed and I'd like to report (hoping to be helpful) is that, by using patches like 'basedrum 2' or (with less evidence) 'basedrum 3', I experiment clicking (see the attached screenshot).

Can anyone confirm this? No external effects in use, neither insert nor send, or on the Master ch, just the plain vsti just loaded in Live 8.1.4. If you need more tech specs just let me know.



Cheers!

[ccDuckett]

I'm one of those who've started many OSCs but never finished to submit on time, hopefully this case will be different. There have been some crashes from tweaking patches, but nothing that hasn't improved with each successive update thus far.

The clicking described/pictured above seems to be related to release;
I noticed that I don't hear it if the the key is held down, only if I try "tapping" it. Anyone else?

Also, another big "Hooray" for such a responsive and helpful developer!

[animehaus]

Yes, I noticed those clicks as well. I sent some PMs to payne_bc, regarding those issues. Those were the patches with more noticeable clicks:

Bass, Short - every attack
Basedrum - if playing fast, click happens, aparently on release
Snare 2 - on release
Basedrum 2 - on release
Basedrum 2 (after Noise, before Hum) - on release
Basedrum 3 - if playing fast, click happens, aparently on release

I managed to reduce the problem with the slope slider, but the clicks still appear frequently, sometimes randomly.

And yep, the support's been pretty amazing!

[payne_bc]

First of all thanks payne_bc for being so quick interacting and applying code changes. To my taste your synth is excellent.

One thing I noticed and I'd like to report (hoping to be helpful) is that, by using patches like 'basedrum 2' or (with less evidence) 'basedrum 3', I experiment clicking (see the attached screenshot).

Can anyone confirm this? No external effects in use, neither insert nor send, or on the Master ch, just the plain vsti just loaded in Live 8.1.4. If you need more tech specs just let me know.



Cheers!

ok, I'll work on those clicks next. Let's see if I can get it fixed This one might take a couple days though. Might be tricky.

[V'ger]

For those with clicks etc, don't forget to try increasing your sound card's buffer size to see if that can be a quick fix. (Of course DAW preferences or project setting too if that is set to override or match the audio card)

[ccDuckett]

V'ger- thanks for the reminder- but just to clarify, the clicks are definitely from the synth, coming before the effects section within it. I tend to keep my buffer size set at 1024, since increased latency isn't as frequent a headache for me as making sure all the various audio elves are playing nicely together

[nitrowheels]

Thanks V'ger, I can confirm, the clicking comes from the synth: no clicking with any other synth and effect here (many vst(i)s, some of them heavy ones regarding cpu processing power or the use of the audio buffers). The clicking, showed in the pic, happens at precise events, like when releasing after a short time. You can hear (and see in pic before: the red circles) the click cuased by the abrupt stopping of the dry sound and the effects then that still continue, correctly, to produce their output. Hope it helps.

[chilledpanda]

I got clicks at the start and end of each note play by turning everything off,
so just using the single additive synth, no fx,filters etc.
I rendered out some single note play and stuck the wave in a sample editor. It looks like as if your not starting/ending your waveform on a zero crossover so you get clicks, but playing with it a bit more, e.g. add adsr 1 to the volume via the matrix. When setting the attack to zero then a single click is heard on the note start, setting a longer attack you hear multiple clicks at the beginning of the attack, same happens on release, short release single click, longer release more clicks towards the end of the release.
Now I maybe wrong (and I don't want to come across as someone telling their "grandma how to suck eggs") as I don't know what number representation you are using (integer/single or double floating point numbers, but guessing one of the floating points.
This honestly sounds like you are possibly using floating point numbers and the calculations with small numbers are causing floating point numbers that are too small to be represent a number and end up as NaNs.

[H-man]

Hi again,

I am now pretty well satisfied that all of the previous issues I have raised are resolved with Beta 5 ...thanks

I have found some new ones related to the mod matrix when setting the LFO's to modulate Frequency or spread in particular. Again, higher Mod values will crash the plugin.

Can anyone confirm this on their setup?

I do have two other questions tho related to:

1. Negative Mod values seem to have exactly the same effect rather than inverse

2. The Spline and Additive OSC seem to pitched differently and are quite discordant when played together

Could I (again) request some clarification on these?

Thx