Announcing Poly-Ana Beta 0.11 Special offer save $60

[AdmiralQuality]

I don't mean to be the bearer of bad news, but I found another strange knob bug... if you click on the voice number knob and rotate it counterclockwise, it goes to -7 voices and says "VOICE UNASSIGNED!" at the top. Double-clicking the knob fixes the problem, setting it to -1 and then to 6.

Cut that out! Hahahah. Why are you intentionally trying to break the interface?

There is no double-click detection, so you're just seeing the result of moving the knob.

I'll doublecheck the math that converts that knob position to the number of voices. Thanks.

(I don't really consider any of this "bad news". I call these "Dr. it hurts when I do this" problems. The answer is, "Well then don't do that." Seriously though, I'll clean them up and the knob-relative thing will either eventually be fixed, or removed entirely. Also going to put limiter code in so the knobs can't go out of range, even if the host sends out of range values in through automation or parameter setting.)

[Prajch]

Breaking things is fun!

...The same counterclockwise problem applies to the mod source and waveform knobs...

I know, these really aren't major bugs (except for the semitone one) and they don't get in the way of using the synth. Just thought you should know.

[AdmiralQuality]

Breaking things is fun!

...The same counterclockwise problem applies to the mod source and waveform knobs...

I know, these really aren't major bugs (except for the semitone one) and they don't get in the way of using the synth. Just thought you should know.

Again, are you using circular or linear knob mode? Which host?

Thanks!

[Prajch]

FL Studio 6, in which Poly-Ana defaults to linear mode.

[AdmiralQuality]

Ah, I see the negative problem in linear mode with the knobs that have no endstops (that freewheel around and around). Will fix, thanks.

Also reminds me, I meant to put in an option to swap circlular and linear modes. Will do for the next release.

Man I hate linear mode. Mouse runs into the edge of the screen... etc... This is why I've not noticed this, thought I had it working months ago and haven't tested linear since. But that was before the values were going to the voice, it was GUI only, so I must not have noticed the negative values.

[TotcProductions]

BTW, Mr. AQ, you should edit the topic title to reflect the new version number.

Peace

[AdmiralQuality]

BTW, Mr. AQ, you should edit the topic title to reflect the new version number.

Peace

Entirely new thread coming soon. Just have some pictures to make and website updates that I still have to get to.

[TotcProductions]

BTW, Mr. AQ, you should edit the topic title to reflect the new version number.

Peace

Entirely new thread coming soon. Just have some pictures to make and website updates that I still have to get to.

Excellent.

[Prajch]

You should also edit your GUI to reflect the new version number.

[AdmiralQuality]

You should also edit your GUI to reflect the new version number.

It takes about an hour to produce the art for each color. Don't expect new art every time I raise the minor version number. In fact, I probably won't do new color files again until ver 1.0 so as we go through the Beta series you'll have to live with the version number being way off, if you're not using the default red.

But it reports the version number in the Parameter Display at the top when you select a program. And in the About Box.

By the way Prajch, got all your linear mode bugs fixed. Thanks for pointing that out. Expect yet another update, real soon.

[ATS]

damnit I can't restist anymore I gotta try this.

[Prajch]

You should also edit your GUI to reflect the new version number.

It takes about an hour to produce the art for each color. Don't expect new art every time I raise the minor version number. In fact, I probably won't do new color files again until ver 1.0 so as we go through the Beta series you'll have to live with the version number being way off, if you're not using the default red.

But it reports the version number in the Parameter Display at the top when you select a program. And in the About Box.

By the way Prajch, got all your linear mode bugs fixed. Thanks for pointing that out. Expect yet another update, real soon.

I didn't mean much by it; once again I'm just letting you know in case you forgot. Nice to hear about the bugs.

I have some questions I'd like to ask you.
* Would it be feasible to implement a copy/paste function for knob values?
* Could there ever be a way to type in values?
* What about seeing frequency on cutoff knobs? Is there some reason you can't do that?
* Now that you've added tooltips, couldn't you just shrink the GUI for smaller resolutions?
The text would be a bit blurry but I think the tooltips would do the job.

Just asking!

[AdmiralQuality]

I didn't mean much by it; once again I'm just letting you know in case you forgot. Nice to hear about the bugs.

I have some questions I'd like to ask you.
* Would it be feasible to implement a copy/paste function for knob values?

Can you show me another VSTi that has this function? What knob value do you want to copy to another knob?

Note that if you really wanted to do this now, you can save to the .polyana text format, then you could edit those files. I'm not sure that will still be available once we hit version 1.x though. It's just there right now so if I add more parameters, it won't break the ability to load your saved files.

* Could there ever be a way to type in values?

Same suggestion, you can edit the text files if you really want to do this. But no, by design, the Poly-Ana experience is supposed to be like using a real world analog synth. So you move knobs and LISTEN. The actual value is just an imaginary number that's essentially meaningless. And any numbers that are meaningful (i.e. center points on some knobs) already have detent positions to help you easily get the exact value.

* What about seeing frequency on cutoff knobs? Is there some reason you can't do that?

Because unless you're using no modulation at all on the filter (which is pretty unusual) then the cutoff value isn't the only knob affecting the cutoff frequency. Again, the actual value just doesn't matter, it's how it sounds that matters. Move the knob until your ear tells you it's right.

* Now that you've added tooltips, couldn't you just shrink the GUI for smaller resolutions?

Do you imagine that there's a "shrinkGUI()" function just sitting there waiting for me to drop it into the code? Again, I ask you to point out any other music plug-in product that offers this.

The text would be a bit blurry but I think the tooltips would do the job.

Just asking!

Heh, I swear some of you spend more time LOOKING at this instrument than you do playing it and LISTENING to it. Anyway, no, I'm not re-doing the entire GUI paradigm. I added a few options to address some people's concerns, but none of this helps it sound any better or be more CPU efficient. Maybe someday I'll throw in an entirely different interface with nothing but sliders and edit fields, but this is NOT a priority right now and my customers need me working on the SOUND right now.

[Prajch]

I don't know, I guess I'm naive but I thought you could resize the images... didn't mean you should really change anything. Like I've said before I really like the design. And I know it's all about listening; I was just curious.

[edit] Come to think of it z3ta+ lets you copy and paste certain settings. Don't really like that synth though.

[Improv]

...my customers need me working on the SOUND right now.

And this customer says bravo and thank you for maintaining your focus.



Who would have ever thought the sound of a vsti would be important!

Cheers