Anna - Hybrid Synth Feature Request thread

[stefancrs]

Alrighty. Should the normal pitch band have a patch definable range? What range of the, uhm, range? Up to +/- 24 semitones?

I really like this baby. Also got my vote in the DC.
What about a possibility to set "PB up" and "PB down" separately? And of course PB as a modulation source.
I wish it had a lower CPU consumption or at least a "reduced cpu" mode, perhaps by disabling the most cpu intensive matrix sources/targets or simplifying the wave generation (maybe allow a sound designer to choose from full/simplified wave gen and extended/reduced mod matrix)

Anna is great. Keep her going!

HiEnergy

Separate up/down it is then
The wave generation itself does not eat much CPU unless one automates the oscillator settings, and modulation matrix sources / targets does not eat extra CPU unless you actually hook them up. For instance, if the LFOs aren't connected to anything via the mod matrix they won't eat any CPU, same goes for modulation envelopes (you have to set env 1 and 2 in the filters to zero to be able to turn all envelopes off though!).

One has to remember to only use for instance the spread knob if necessary and set it to absolute zero otherwise, when it's not at zero, you're running three oscillators instead of one, making it possible to have up to 12 oscillators up and running, and that eats quite a lot of CPU.

[stefancrs]

Tried it in Orion,on an Athlon 3200+, and the cpu is high 15% on a mono patch and between 23 and 30% chord (three finger). Also the time to load the instrument is about 10 seconds, and about half that to close it! This is a synth Edit problem, as I have it with every synth edit (err) synth.
Having said that, this is a great sounding synth!

When using the same patch CPU usage should be the same for one voice and three voices (and four), so I guess you compared different patches?

Both loading times and CPU load is being worked on

[stefancrs]

it sounds very good, but any external modulation above a certain frequency causes audio glitches and CPU fluxuations. I am using AMD athlon 64, NOT pentium, so it can't be denormal issues.
I have experienced this time and time again with Synthmaker plugins. Is there some fix that can be applied to this problem?

anyway, very nice synth. pretty GUI and definitely an excellent sound to it.
-g

We will look into it, is this when automating just one parameter or several? Modulating oscillator settings will always cause CPU spikes / fluxuations though, since the waveforms has to be recalculated when one changes the osc settings.

hi
just one parameter. i didn't try any more since it didn't like just one. It's not just yours though, so it might be one of the SM modules...?
dunno.
hope it's not my system! Athlon64 3500+ / 1gigRAM / winXPhome / ATI Radeon xpress200Mobile (chipset/graphics) any recognizeable conflicts there between HW and SM?

Do you remember if it was an oscillator parameter or something else? If it's not an oscillator setting parameter it needs to be fixed
That system should be just fine as far as I know.

[stefancrs]

1. CPU is very high for me (26% on the first patch) on a 1.7 Pentium M (core solo).

2. Is there midi mapping?

3. Aftertouch, keytracking and mod wheel as sources in the mod matrix.

I should've probably started with a patch designed for low CPU as the first patch

There's no midi mapping yet, but it is on the list in the first post in this thread.

Will add aftertouch and mod wheel, key tracking is already there, called "pitch", unless it's something else you're after?

[stefancrs]

I really couldn't give a hoot about any other features until the cpu and load/adjustment time issues are addressed.

Like I said before, this is a great synth just dying to break free.

I'll second that. I commented on this with respect to the KVR developer competition. I still haven't voted. It's between three cheese and anna..

IMNSHO both rocks

[Z3R0T0N1N]

hi stefan:
i will chck it out again. i suspekt it may have bean PW or something, so...

but why would that happen? that would still be a pretty unique situation for me.

The other synthmaker synths that i have had that problem with, it was also an oscillator thing, but i have not experienced that with other synths.
do you think that is something that might be addressed with SM, or is it just how it has to be?

[stefancrs]

hi stefan:
i will chck it out again. i suspekt it may have bean PW or something, so...

but why would that happen? that would still be a pretty unique situation for me.

The other synthmaker synths that i have had that problem with, it was also an oscillator thing, but i have not experienced that with other synths.
do you think that is something that might be addressed with SM, or is it just how it has to be?

If it's not an oscillator setting it is a more general SM issue. If it's an oscillator setting it's due to the design of this specific oscillator. The wavetables are recalculated if you fiddle with slope, waveform, internal oscillator FM, modulator frequency etc, and those calculations need a bunch of CPU. That's not a generic SM issue, it's how I made this synth. One can easily make a square wave oscillator with automatable PW that does not need to recalculated any wave tables if one so desires

[Z3R0T0N1N]

hi stefan:

you were right, i was trying to automate the oscillator. It works at a slower rate, of course, so that's fine. Thanx for your help.

I just kind of assumed it was the same issue i had with other SM synths, but things seem to be getting better with SM plugins. Although stronghold and stronghold mini seem buggy as hell - sadly too, stronghold could be amazing!

I think Anna could be the best synth developed in Synthmaker so far nice work.