Announcing Poly-Ana Beta 0.11 Special offer save $60

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

right, that unmanaged error i had earlier, i got the same notice again and it was while i was changing the LFO 1 shape.

Fortunately id just saved the patch as a text file moments before. You can get it here :

http://relivethefuture.com/music/patche ... ap.polyana

I can repeat the error by loading the patch and changing the lfo shape.
Top

Post

HunterKiller wrote:Admiral Quality, I'd say the GUI seems to be an issue for alot of people.

Aside from that, Congratulations man!!
Color coding the knobs might help as well. The small silver circle in the middle of each knob could be colour coded so that you could tell at a glance that all blue knobs were OSc1 functions. Etc.

It would be a start.
Top

Post

Thanks marvo. Good testing! Will take a look.
Top

Post

Ok, the semitone thing.

If I load an instance of polyana and then the first thing I do is to click the semitone offset knob (on any oscillator), the knob jumps to point straight down and the readout at the top says '+2147483624 Semitone'. When i then let go of the mouse button the display and knob jump to +24 (or sometimes -24) but the Live CPU meter reads something over 100% (between 100 and 300) and everything goes S-L-O-W until i close the GUI.

Then after a few seconds my computer starts responding again. If i then try to play some midi it then goes slow for a while so I have to delete the instrument and start again.

I can adjust the semitone parameters without problem through Live's normal parameter display so it seems like it could be something UI related.
Top

Post

Wow marvo, that's a weird one! BTW I tried your clap sound (cool!) and didn't see the same problem with changing the LFO 1 waveform, but I haven't tested it in Live yet. Will get to it...

What version are you using by the way?
Top

Post

Live 6.01, the latest version.

On the earlier topic of clicking envelopes, I reckon keep them as they are, you can make great bass drums :)
Top

Post

marvotron wrote:Live 6.01, the latest version.

On the earlier topic of clicking envelopes, I reckon keep them as they are, you can make great bass drums :)
I'm still not sure exactly what people mean by clicking envelopes. The only clicking I hear is when the velocity level control is used, and the release is interrupted by the attack. This unfortunately HAS to produce a click (because, among other reasons, it's possible for the new envelope to be QUIETER than the one that's still releasing.)

I'd love to find a way around that but I couldn't think of one. Open to suggestions though! I suppose there could be smoothing to make the click less noticeable.

And obviously they click when attack time is set to zero, but if that's the click that's bothering you just add a bit more attack. And yes, the gates click (though to me that's a FEATURE)... but I think I'll eventually add an option to smooth the gates for folks who don't like it. Someday after the more important stuff is filled in.
Top

Post

The envelopes are just fine :shrug:
Top

Post

Ok Admiral, I'm on board :) After 3 days I just like it better and better. This is what I'd hoped my moog voyager would sound like (but doesn't). So it's now up for sale...

2 more quick bugs:
(1) when you close the gui and reopen in sx 3.1.1, the synth is bypassed (don't know if that's just a demo thingie, I haven't received my auth key yet)
(2) when you open the gui, the poly setting is always on 6, regardless of what the actual value is

Any thoughts on the question I raised about the scaling of the filter cutoff?
Top

Post

After some more investigation i've found that its just Live that is doing something which is making your GUI code go a bit wrong.

In Live when I open the display I cant rotate any continuous dial anti-clockwise. Once its gone clockwise I can rotate it back but it always stops at the initial position i.e. I can keep winding it clockwise as much as i like but i can only wind it back as far as I wound it forward..

I tried the plug in Plogue Bidule and that doesnt suffer from the problem at all, similarly i cant reproduce the semitone dial problem in Bidule either.

basically Live is doing something weird with the UI. Its probably a different weirdness but Cameleon had some UI bugs that were only present in Live. But maybe the Camel Audio guys can shed some light on what the problems were and how to get around them :)
Top

Post

suthnear wrote:Ok Admiral, I'm on board :) After 3 days I just like it better and better. This is what I'd hoped my moog voyager would sound like (but doesn't). So it's now up for sale...
Wow, thanks! I'll trade you a copy of Poly-Ana for the Moog! ;)

2 more quick bugs:
(1) when you close the gui and reopen in sx 3.1.1, the synth is bypassed (don't know if that's just a demo thingie, I haven't received my auth key yet)
That sounds like a bug. I've seen that happen before when there's problems. Thanks, I'm on it.

(2) when you open the gui, the poly setting is always on 6, regardless of what the actual value is
Will check this as well. Thanks!

Any thoughts on the question I raised about the scaling of the filter cutoff?
Um, oh the knob scale itself right? Are you sure you didn't have any additional modulation that might have been pushing the scale one way or the other? It feels pretty good to me. There is definitely some room at both ends where you won't hear much change because you're in sub-sonic or ultra-sonic but this extra range room is needed as modulation can push the center off.

Also, Poly-Ana's filters go past the project's sample rate (truely into ultra-sonic, just like a real analog synth) so there has to be some room at the top where you won't hear much change.

I'm also very hesitant to change the scaling of a knob as important as filter cutoff because that will break everybody's presets. Now, I've said in the docs to be prepared for that, but I only want to do this if it's really necessary.

What's everyone else think? How's the scaling on the filter cutoff knob?

Marvotron, great observations! That will help a lot. Thanks.
Top

Post

How to break an oscillator :

With the default patch loaded.

1. Switch off ModWheel on LFO1
2. Change the FM modulation selector on OSC1 to Mix1 and turn the mod amount all the way up.
3. Change the first selector on Mix to LFO 1
4. Turn up the first mod amount on Mix 1

As you get near the top the oscillator will cut out and stop working ( at around 6.8 ) If you tweak the mod amounts back to lower settings it doesnt come back.

If you then change the shape of osc1 with the shape dial at some point it will click a few times and spring back to life.
Top

Post

marvotron wrote:How to break an oscillator :

With the default patch loaded.

1. Switch off ModWheel on LFO1
2. Change the FM modulation selector on OSC1 to Mix1 and turn the mod amount all the way up.
3. Change the first selector on Mix to LFO 1
4. Turn up the first mod amount on Mix 1

As you get near the top the oscillator will cut out and stop working ( at around 6.8 ) If you tweak the mod amounts back to lower settings it doesnt come back.

If you then change the shape of osc1 with the shape dial at some point it will click a few times and spring back to life.
Ah, was wondering who'd be first to find the "high pitch" error. Yes, if an oscillator goes too high a problem happens. You can also get this problem by tuning the oscillator as high as it will go, playing a high MIDI note, and using a lot of up pitchbend.

Bypassing then unbypassing Poly-Ana usually fixes this as that action will cause most internal state to re-init.

Will fix. Thanks!
Top

Post

Ok, I can reliably crash polyana in ext v1.4:
(1) load polyana
(2) attach a midi connection in ext
(3) play on an attached midi keyboard
(4) then while playing, open the gui
(5) profit. er, sorry, that's hard crash not hard cash ;)
Top

Post

suthnear wrote:Ok, I can reliably crash polyana in ext v1.4:
(1) load polyana
(2) attach a midi connection in ext
(3) play on an attached midi keyboard
(4) then while playing, open the gui
(5) profit. er, sorry, that's hard crash not hard cash ;)
Yup. Playing while GUI opening seems to cause crashes across all hosts. Already 99% sure what this is, just haven't gotten to it yet. I hope to have a fix out for it on Monday (but forgive me if it takes a day or two longer, as you can imagine this is a busy time over here!)

Thanks again folks.
Top
Post Reply

Return to “Instruments”