Poly-Ana: Coming soon from Admiral Quality.

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

Post

zerocrossing wrote:
nusound mind wrote:I don't find the cpu hit bad at all if you adjust things. Anti-aliasing really helps, or turn down sound quality to 192, oversampling, polyphony, etc. Not as high quality obvs., but still sounds decent enough imo even then.

Honestly I think the 3 new gui's are fine, esp. compared to that original one. That first one looks brutal. jmo
Put preset 048 "Solo Brass" on at 192 khz. Play some high notes. Not even that high. Wince at the aliasing. Turn "anti-alasing on." Say, "WTF?" Turn anti-aliasing off. Boost quality up to 768. Note it's better, but still noticably aliasing. Load up XILS 4. Never use Poly-Ana again.
I was hoping this wouldn't be the case but I tried this out and you are right, there is a lot of aliasing in all modes. Thing is I never noticed this before in my usual use of the Poly-ana so unsure how much of an impact this would be for people - I suppose it depends on particular use.

Post

It's not fair to say aliasing is bad, and bandlimited oscillators are good, when the actual processes of Frequency Modulation and such are inherently increasing the required bandwidth. It may even depend on what waveform is chosen, when using FM, as FM is seriously prone to aliasing in ALL synths. So maybe PA is just letting the user go further than acceptable, damn the consequences, full steam ahead. There is enough oversampling to get a good result from even the "wrongest" modulations. On that note, IL Sytrus has 64x oversampling. FM isn't for everyone, or even sane people, so don't worry about it.

Post

chaosWyrM wrote:
rod_zero wrote:
So if wagtunes is using an old monitor he already has a good size of GUI, a new one will only make it smaller.
this.
i dont know why you guys are telling him to get a bigger/better monitor if hes already complaining that guis are too small. larger monitor = smaller gui
All I'm saying is both on a 22" Monitor at 1650x1050 and a 27" at 1920x1080 Poly-Ana's GUI is perfectly functional. He's keeps bitching about things being Microscopic. There is a solution. :shrug:

I haven't used a 17" monitor for 18 years......for good reason. :wink:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

david.beholder wrote:
Teksonik wrote: Is Poly-Ana perfect ? No. Is it worth $45 ? In my opinion Yes.
Can you use it or program it's ugly UI? No! .
YES ! Even before the new GUIs.....but then I know what I'm doing....... :wink:
david.beholder wrote:Can you stand to dev attitude? No.
Mike is a jerk. I told him his attitude would cost him sales and he laughed it off. If his attitude bothers you then don't buy Poly-Ana. I've owned it for years and I love it......... :shrug:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

zerocrossing wrote:
Teksonik wrote:
zerocrossing wrote: Load up XILS 4. Never use Poly-Ana again.
I'm sorry did I miss the link to where XILS 4 dropped from $190 to $45 and dropped the requirement for iLok ?

Is Poly-Ana perfect ? No. Is it worth $45 ? In my opinion Yes.

Oh and try the AA button............ :wink:
You're right. If you want cheap and subpar sound, it's the one to go for.
It doesn't sound cheap or sub-par here. Maybe you need new speakers....or ears... :hihi:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

wagtunes wrote: The problem is not the size of the GUI, though it could be a little bigger. The problem is with all the crap that they crammed into one screen.
Those are called "controls" and they make the sound. If Poly-Ana is too complex for you or $45 is too much then pass. Pretty simple. :wink:

Just please stop bitching about "Microscopic" GUI's until you join the 21st century......... :hihi:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

I'm having a hard time authorizing the Beta 1.3 on MacOSX 10.12.3. I created a folder in MacHD/Library/Application Support/Admiral Quality/Poly-Ana and placed the authorizing text file in there. I Restarted Live, and no-go when I launched Poly-Ana....still in demo mode. I know I'm doing something wrong. Just not sure what it is

Post

W23 wrote:I'm having a hard time authorizing the Beta 1.3 on MacOSX 10.12.3. I created a folder in MacHD/Library/Application Support/Admiral Quality/Poly-Ana and placed the authorizing text file in there. I Restarted Live, and no-go when I launched Poly-Ana....still in demo mode. I know I'm doing something wrong. Just not sure what it is
Delete .txt so your file ends with .key .
Also, make sure it's in the "hidden" MacHD/user/library/Application Support directory.

Post

nicksohn wrote:Ryzen has SSE?
I heard PAis optimized for Intel SSE.
I don't think it is about SSE.
Either way, there are various version of SSE, and I think SSE 2 is the most common one with plugins. Our Phenom II processors do support SSE 1 to 4, albeit not all sub-versions of those. For instance not 4.1 and 4.2, but only 4a. Not sure what consequences that has, you would have to ask a developer :)

Post

Teksonik wrote:
wagtunes wrote: The problem is not the size of the GUI, though it could be a little bigger. The problem is with all the crap that they crammed into one screen.
Those are called "controls" and they make the sound. If Poly-Ana is too complex for you or $45 is too much then pass. Pretty simple. :wink:

Just please stop bitching about "Microscopic" GUI's until you join the 21st century......... :hihi:
Again, the GUI itself is not too small. But when you put too many controls on one page, each individual control becomes too small. I can't read the descriptions of each individual control. Getting a larger monitor is NOT GOING TO FIX THAT.

And what may be functional to YOU may NOT be functional to somebody with bad eyesight.

Pretty simple. ;)

Post

For me personally the problem is that the bigger the monitor, the smaller the GUI. What I can still read on a 17" notebook display, becomes basically useless on a desktop with 24" screen.
I think many of the small GUI's were developed by young programmers using notebooks.

Post

fluffy_little_something wrote:For me personally the problem is that the bigger the monitor, the smaller the GUI.
The size of the monitor is only one factor. The resolution of the monitor is an equally important factor. As is the distance of the monitor from your eye.

The onscreen size of a UI is dependent on the ratio of the screen's resolution to its dimensions; dots per inch.

If you use a bigger monitor, with the same resolution the GUI will not be smaller, it will be the same physical size.

If you use a bigger monitor, with a lower resolution the GUI will be physically larger.

And of course, if you're going to talk about perceived size rather than the actual dimensions as displayed onscreen, desktop screens are typically further away than laptop screens, so UIs will appear smaller when they're not
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."

Post

Back in 2015 at KVR i posted my own skin available in two sizes: 1512x801 and 1200x636 pixels

Both are available at the "Banks & Patches" page for Poly-Ana here at KVR:
http://www.kvraudio.com/product/poly-an ... /downloads

I just installed the bigger version as described there and it seems to work properly here in Windows 10 64-bit.

The skin uses my own design (also for the knobs) and arangement of the controls. It is called "Flatland" as it is a 2D skin without 3D effects.

There was a lot of trouble and/or bashing in that old thread where people including me posted and discussed their skins and finally it was closed (actually there semed to be more than one that was closed). Later it was forbidden to discuss Poly-Ana further at KVR (as was mentioend earlier here).
I really do not want to be involved in such discussions and/or bashing again. Either you want to try and/or use my skin or not. Really doesn't matter for me. Personally i still prefer using my own skin when using Poly-Ana.

It is more likely that this was my last post on this topic for a while...
Last edited by Ingonator on Thu Mar 16, 2017 2:16 pm, edited 1 time in total.
Ingo Weidner
Win 10 Home 64-bit / mobile i7-7700HQ 2.8 GHz / 16GB RAM //
Live 10 Suite / Cubase Pro 9.5 / Pro Tools Ultimate 2021 // NI Komplete Kontrol S61 Mk1

Post

Ingonator wrote:Back in 2015 at KVR i posted my own skin available in two sizes: 1512x801 and 1200x636 pixels

Both are available at the "Banks & Patches" page for Poly-Ana here at KVR:
http://www.kvraudio.com/product/poly-an ... /downloads

I just installed the bigger version as described there and it seems to work properly here in Windows 10 64-bit.

The skin uses my own design (also for the knobs) and arangement of the controls. It is called "Flatland" as it is a 2D skin without 3D effects.

There was a lot of trouble and/or bashing in that old thread where people including me posted and discussed their skins and finally it was closed (actually there semed to be more than one that was closed). Later it was forbidden to discuss Poly-Ana further at KVR (as was mentioend earlier here).
I really do not want to be involved in such discussions and/or bashing again. Either you want to try and/or use my skin or not. Really doesn't matter for me. Personally i still prefer using my own skin when using Poly-Ana.

It is more likely tat this was my last post on this topic for a while...
I just downloaded this and am willing to give it a try but I have absolutely no idea how to change the skins for this thing. I don't see any menu option on the synth that says load skin or anything like that.

So how exactly do I change it to this skin?

Post

whyterabbyt wrote:
fluffy_little_something wrote:For me personally the problem is that the bigger the monitor, the smaller the GUI.
The size of the monitor is only one factor. The resolution of the monitor is an equally important factor. As is the distance of the monitor from your eye.

The onscreen size of a UI is dependent on the ratio of the screen's resolution to its dimensions; dots per inch.

If you use a bigger monitor, with the same resolution the GUI will not be smaller, it will be the same physical size.

If you use a bigger monitor, with a lower resolution the GUI will be physically larger.

And of course, if you're going to talk about perceived size rather than the actual dimensions as displayed onscreen, desktop screens are typically further away than laptop screens, so UIs will appear smaller when they're not
Valid points there. Be that as it may, I have had several monitors over the years, they were always located at the same spot. I definitely noticed that the same old programs I have been using for like a decade have become smaller and smaller. I can't really mess around with the resolution a lot because using inferior resolutions leads to inferior image quality, which undoes any improvements due to mere size. With many resolutions a circle is not even a circle anymore :D
Nor is it very practical to switch between resolutions all the time because some user interfaces are much bigger than others. Ideally they would all work like Sylenth1's :) Then I could use the recommended resolution of the monitor and image quality would be perfect.

Anyway, in the case of PA, it is not only about size, but the whole default GUI is not ideal, there is something off-putting about it in my view. The exact opposite of Sylenth1, whose GUI invites me to use it.
Last edited by fluffy_little_something on Thu Mar 16, 2017 1:15 pm, edited 2 times in total.

Post Reply

Return to “Instruments”