KVR Audio

RichardSemper · Post by **RichardSemper** » Wed Nov 06, 2013 9:37 pm

payne_bc wrote:By the way, the current tf3 package does not have all too many presets. How protective are you guys of the patches you create? If somebody would be willing to send me their patches after the competition is over, I'd package them with the final tf3 download and credit you in a readme. That way there'd be a richer selection of patches for other composers in the future.

Great! If I create any worthy enough I would be happy to see them included

Thanks for the great work debugging. This synth is getting better by the day.
Now most of the issues I had are sorted, starting to really enjoy some sound sculpting. This synth seems to have great potential!

Looks like there's a bonus prize for all participants this month - a thouroughly tested and debugged TUNEFISH

payne_bc · Post by **payne_bc** » Wed Nov 06, 2013 9:37 pm

bjporter wrote: Hey why don't you join in the One Synth Challenge as well? That would be awesome, and it looks like you already are doing such a thing.

It came to my mind too. But doesn't really feel right to me. After all I have dozens of unfinished tracks with my own synths and therefore have a headstart. I'd rather watch and fix bugs

V'ger · Post by **V'ger** » Wed Nov 06, 2013 9:41 pm

payne_bc wrote:
V'ger wrote: Getting corrupt archive error message with this zip
Right! No idea what happened there. Try again

Fine now, cheers.

H-man · Post by **H-man** » Thu Nov 07, 2013 1:21 am

payne_bc wrote:
H-man wrote:Another one to test:

1. Map ADSR1 to FREQUENCY in the Mod Matrix
2. Set DECAY on ADSR1 to halfway up (0.5, can be whatever really)
3. Increase the MOD value towards 10 (Max value)
4. Plugin crashes

Same details as above, happens on 41 or 96KHz and can be replicated every time. Crash usually comes in at Mod values of 4.0 and above.

Also, I'm using the mouse wheel to increase the Mod (ADSR1 of FREQUENCY) value.
Sorry, I tried both of your instructions. They both work stable here

EDIT: too fast. took a bit more playing, then I got it crashing, too
Fixed! Also fixed that issue about automating formant type. Should work now.

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

Hey thanks for that. So fast.

I've tested and the issue seems resolved ...certainly on my setup.

Got another one while I'm at it. When using the Additive OSC (Only)I get alot of "zipper" sounds when adjusting the Scale, Bandwidth etc.(via the GUI). I just tried using some DAW automation to alter the SCALE over time, on a gentle linear-slope, the Zipper or "tearing" is still there.

Additionally, when this happens, resource utilisation flies up to 100% and the whole DAW seems to lag.

Can you please have a look at this? Tried 41 and 96kHZ.

V'ger · Post by **V'ger** » Thu Nov 07, 2013 1:41 am

Tunefish really has very good range of sounds. From drums to pads etc, not all synths can do them all equally well.

abovethoughts · Post by **abovethoughts** » Thu Nov 07, 2013 2:58 am

Seeing all this work has me interested in giving v3 another try, but I just finished my track and uploaded using v2

payne_bc · Post by **payne_bc** » Thu Nov 07, 2013 8:59 am

H-man wrote: Got another one while I'm at it. When using the Additive OSC (Only)I get alot of "zipper" sounds when adjusting the Scale, Bandwidth etc.(via the GUI). I just tried using some DAW automation to alter the SCALE over time, on a gentle linear-slope, the Zipper or "tearing" is still there.

Additionally, when this happens, resource utilisation flies up to 100% and the whole DAW seems to lag.

I have some bad news for you. The additive synth can unfortunatelly not be automated in that way. Every time you change one of those timbre changing knobs the engine needs to recalculate the wavetable for it which unfortunatelly takes depending on your system easily 100ms or more. So it cannot be changed in realtime without lag and very high cpu usage. Maybe you noticed that for all addsynth instruments, after you start tunefish the first time the notes will not trigger right away but there is a certain initial lag until the instrument has been calculated. Not much I can do there unfortunatelly

idfpower · Post by **idfpower** » Thu Nov 07, 2013 9:12 am

payne_bc wrote:Maybe you noticed that for all addsynth instruments, after you start tunefish the first time the notes will not trigger right away but there is a certain initial lag until the instrument has been calculated.

Ha

Well that cleared up a space in my "why the heck is that X thing happening..."

Thanks for the info

Man I love this forum, everyday I learn something new

crimsonwarlock · Post by **crimsonwarlock** » Thu Nov 07, 2013 9:14 am

payne_bc wrote:Maybe you noticed that for all addsynth instruments, after you start tunefish the first time the notes will not trigger right away but there is a certain initial lag until the instrument has been calculated. Not much I can do there unfortunatelly

It seems to do that also when I load another patch, is that correct ? (not a problem in any way of course).

payne_bc · Post by **payne_bc** » Thu Nov 07, 2013 9:15 am

Yep, it does that whenever you try to play an instrument with addsynth that you did not yet use in that session

H-man · Post by **H-man** » Thu Nov 07, 2013 9:32 am

payne_bc wrote:
H-man wrote: Got another one while I'm at it. When using the Additive OSC (Only)I get alot of "zipper" sounds when adjusting the Scale, Bandwidth etc.(via the GUI). I just tried using some DAW automation to alter the SCALE over time, on a gentle linear-slope, the Zipper or "tearing" is still there.

Additionally, when this happens, resource utilisation flies up to 100% and the whole DAW seems to lag.
I have some bad news for you. The additive synth can unfortunatelly not be automated in that way. Every time you change one of those timbre changing knobs the engine needs to recalculate the wavetable for it which unfortunatelly takes depending on your system easily 100ms or more. So it cannot be changed in realtime without lag and very high cpu usage. Maybe you noticed that for all addsynth instruments, after you start tunefish the first time the notes will not trigger right away but there is a certain initial lag until the instrument has been calculated. Not much I can do there unfortunatelly

That's not bad news, that's just information, thanks for taking the time to explain it. Worth checking anyway.

The effort you are putting into this thing now is not lost on me and I would like to add that I really like the GUI design ...easy to navigate and yet very easy on the eyes for long sessions.

payne_bc · Post by **payne_bc** » Thu Nov 07, 2013 9:47 am

H-man wrote: That's not bad news, that's just information, thanks for taking the time to explain it. Worth checking anyway.

The effort you are putting into this thing now is not lost on me and I would like to add that I really like the GUI design ...easy to navigate and yet very easy on the eyes for long sessions.

Thank you

Compare that with TF2 and you see the learning process that happened after years of usage of it

Btw, for me that WAS bad news since I always wanted to automate that thing. That is why v4 is actually optimized enough that you not only CAN animate the addsynth wavetable but it usually happens automatically all the time unless you explicitly shut it off. Causes much more dynamic sounds, unfortunatelly v4 also uses a bit more cpu. But nowhere near 100%

H-man · Post by **H-man** » Thu Nov 07, 2013 10:31 am

payne_bc wrote:
H-man wrote: That's not bad news, that's just information, thanks for taking the time to explain it. Worth checking anyway.

The effort you are putting into this thing now is not lost on me and I would like to add that I really like the GUI design ...easy to navigate and yet very easy on the eyes for long sessions.
Thank you Compare that with TF2 and you see the learning process that happened after years of usage of it
Btw, for me that WAS bad news since I always wanted to automate that thing. That is why v4 is actually optimized enough that you not only CAN animate the addsynth wavetable but it usually happens automatically all the time unless you explicitly shut it off. Causes much more dynamic sounds, unfortunatelly v4 also uses a bit more cpu. But nowhere near 100%

Cool. The main reason I tried to automate the SCALE value is because it sounds awesome!

I'll certainly be looking out for v4

JKF Flashico · Post by **JKF Flashico** » Thu Nov 07, 2013 11:58 am

Hi payne_bc, I want to also thank you that you have developing this Great synth. This is very creative and potential synth to the make sound design

You have also done Great job in bugs fixing and so fast!.

H-man · Post by **H-man** » Thu Nov 07, 2013 12:44 pm

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.

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