nice...looking forward to the update..
i'll update my bidule patch now with locks on the release params and let you know how i get on.
Poly-Ana 1.0 New VA softsynth. 1 week full functioning demo
-
- KVRian
- 540 posts since 7 Jul, 2004 from Skopje
-
funkychickendance funkychickendance https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=78609
- KVRAF
- 2097 posts since 19 Aug, 2005 from Where Sheep May Safely Graze & They're Using A Chicken 2 Measure It
I'm pretty much on the ball with this one, thanks! 
v0.30 seems to be it, contra-intuitive though that may seem from all the devs who go to v0.997.4.009.199, and so one...
Not a bad price, when all's said and done, but fearsomely complex.
Though of course, that's the idea: no one will be left craving knobs, bells or whistles on this gizmo 
/funxi
who is, believe it on not, 'all synthed out' for a while
v0.30 seems to be it, contra-intuitive though that may seem from all the devs who go to v0.997.4.009.199, and so one...
Not a bad price, when all's said and done, but fearsomely complex.
Though of course, that's the idea: no one will be left craving knobs, bells or whistles on this gizmo /funxi
who is, believe it on not, 'all synthed out' for a while
Every Potemkin village needs its idiot savant
-
- KVRist
- 441 posts since 30 Nov, 2002 from Sweden
Boulotaur2024 wrote:I made a more 'melodic' demo a while ago when v0.10 was released, you can check it out for yourself here :
http://www.s146380088.onlinehome.fr/Muz ... _Impro.mp3
it's played live so it has a number of mistakes and clipping but the sound of the synth is something I've never heard before, believe me : )
Also at the time I couldn't run more than 8 voices of polyphony but I guess it has improved a lot with the optimisations AQ brought (but my eval period's been over for ages now).
Oh, and btw, is PA optimised for dualcore ? ('dont think so but that would be a great idea)
Very nice demo!
-
funkychickendance funkychickendance https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=78609
- KVRAF
- 2097 posts since 19 Aug, 2005 from Where Sheep May Safely Graze & They're Using A Chicken 2 Measure It
Hey, give an old geezer a break, dude...Improv wrote:I forgot-up to speed once a year, whether you need be or not, right?funkychickendance wrote:I'm pretty much on the ball with this one, thanks!
It's hard work being the uncrowned king of the faux naif question...the only other place I know where "0.3" means 'about ready' is on the side of my electric toaster... /funxi
Who is still wondering WTF happened to Ethnotronic?
Every Potemkin village needs its idiot savant
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- Topic Starter
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
Let me clarify about the version numbering.
The first number left of the decimal point is the major version number. It's 0.x now because it's in Beta, it's not the full blown product yet, so people shouldn't have the same expectations they would of a complete product (i.e. docs not yet complete, some possibility things might change, etc.)
As soon as the coming soon list reaches zero items, it will become 0.90. And the 0.9x series will be the "release candidates". This will also be the first release to include the effect version so if you need to see that working before buying, hang on a few more weeks. 0.90 is not far off.
So understand that it might very well jump from 0.40 to 0.90 in a single release, depending on how many major features I add for the next-next one. (I expect there'll probably be a 0.50 though, but if I happen to get it all done in the next 2 weeks it'll jump straight to 0.90)
The one coming in a few days is 0.40. It has MIDI Guitar support (I think, still testing), has further improved CPU performance, and I believe there's also a fix or two. If I do a small release like just a bug fix or optimization, that becomes the third digit. i.e. 0.11
But when I say it's "out" now. It is out. The product works, is useful, is real, you can buy your 1.x license now (at considerable discount), there's just going to be MORE before it's "done-done". (And even after that there'll be more, but the promises will stop.
) I feel it's better to get it out there asap rather than hold it off for months waiting to get the perfect documentation (etc) done, when again, most people only glimps that. And that WILL come too, but because people want it now, because I need a certain number out there in use being tested, it's available now. This also lets people get input and there have actually been several features suggested (or demanded ) by users that have been added since the original Beta release back in October.
So, we're almost done Beta, I think it'll be to version 0.90 in about a month (but if it takes a big longer, that's because its getting even better.) Still, it's a perfectly functioning softsynth right now. Buy it!
Thanks!
The first number left of the decimal point is the major version number. It's 0.x now because it's in Beta, it's not the full blown product yet, so people shouldn't have the same expectations they would of a complete product (i.e. docs not yet complete, some possibility things might change, etc.)
As soon as the coming soon list reaches zero items, it will become 0.90. And the 0.9x series will be the "release candidates". This will also be the first release to include the effect version so if you need to see that working before buying, hang on a few more weeks. 0.90 is not far off.
So understand that it might very well jump from 0.40 to 0.90 in a single release, depending on how many major features I add for the next-next one. (I expect there'll probably be a 0.50 though, but if I happen to get it all done in the next 2 weeks it'll jump straight to 0.90)
The one coming in a few days is 0.40. It has MIDI Guitar support (I think, still testing), has further improved CPU performance, and I believe there's also a fix or two. If I do a small release like just a bug fix or optimization, that becomes the third digit. i.e. 0.11
But when I say it's "out" now. It is out. The product works, is useful, is real, you can buy your 1.x license now (at considerable discount), there's just going to be MORE before it's "done-done". (And even after that there'll be more, but the promises will stop.
) I feel it's better to get it out there asap rather than hold it off for months waiting to get the perfect documentation (etc) done, when again, most people only glimps that. And that WILL come too, but because people want it now, because I need a certain number out there in use being tested, it's available now. This also lets people get input and there have actually been several features suggested (or demanded ) by users that have been added since the original Beta release back in October.So, we're almost done Beta, I think it'll be to version 0.90 in about a month (but if it takes a big longer, that's because its getting even better.) Still, it's a perfectly functioning softsynth right now. Buy it!
Thanks!
-
- KVRian
- 533 posts since 16 Jan, 2006 from France
Excellent news : )AdmiralQuality wrote:Among other improvements, it's now using approximately half the CPU power that version 0.10 required! And there's still lots more places to make performance optimizations so expect it to continue to get faster throughout the 1.x product lifetime.
I'm on the verge of being tempted...
-
- KVRAF
- 1891 posts since 9 Oct, 2004 from Columbus,Ohio
Hi!
Well, I love the sound and design of this thing, it seems like it can make some interesting sounds. Howevever, unfortunately, when I go to play every other patch, the CPU usage spikes to about 80% and then freezes altogether.
I'm using Windows XP, Toby bear's minihost, on a HP AMD Athlon XP Processer 3000+ with 512 MB RAM.
Edit: I should say though that i'm sure once you are out of beta, and all is optimized and well, that it will be hell of a synthesizer.
Well, I love the sound and design of this thing, it seems like it can make some interesting sounds. Howevever, unfortunately, when I go to play every other patch, the CPU usage spikes to about 80% and then freezes altogether.
I'm using Windows XP, Toby bear's minihost, on a HP AMD Athlon XP Processer 3000+ with 512 MB RAM.
Edit: I should say though that i'm sure once you are out of beta, and all is optimized and well, that it will be hell of a synthesizer.
"You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live."
-
- KVRian
- 540 posts since 7 Jul, 2004 from Skopje
some good news, locking the release parameters appears to have done the trick and im not getting any high-cpu lockups.
i just have a question or two about the modulation mixers and env-3 in particular.
I've setup a basic patch where the cutoff of filter 1 is modulated by mod mix 1.
In mod mix 1 the first dial is set to lfo - 1. I can adjust the level here and it does what i expect.
Now, what is confusing me is if I switch the mod type to multiply, surely there should be no modulation as anything times zero is zero, but i still get full modulation.
If i then setup the second mod source as env 2, which is just set to A:0, D:0, S:Full,R:0 and adjust the amount for env2, nothing changes. But if then change the sustain level of env2 to zero then the mod-amount setting for env2 does make a difference, but not at all what i expect.
At full (or 10 as it says on the UI) i get what appears to be a normal multiplication (i.e. zero modulation). At zero I get the full LFO modulation, and at -10 I get what sounds like double the LFO modulation.
Just to add to the confusion, I repeated this with env-3 and get completely different results. Basically if mod-amount 2 is full then it seems as if a sustain level of '5' on env-3 is a zero setting.
If you want me to go into more excruciating detail about what happens at different settings just ask
So is the current setup broken? or does it just need explaining clearly?
i just have a question or two about the modulation mixers and env-3 in particular.
I've setup a basic patch where the cutoff of filter 1 is modulated by mod mix 1.
In mod mix 1 the first dial is set to lfo - 1. I can adjust the level here and it does what i expect.
Now, what is confusing me is if I switch the mod type to multiply, surely there should be no modulation as anything times zero is zero, but i still get full modulation.
If i then setup the second mod source as env 2, which is just set to A:0, D:0, S:Full,R:0 and adjust the amount for env2, nothing changes. But if then change the sustain level of env2 to zero then the mod-amount setting for env2 does make a difference, but not at all what i expect.
At full (or 10 as it says on the UI) i get what appears to be a normal multiplication (i.e. zero modulation). At zero I get the full LFO modulation, and at -10 I get what sounds like double the LFO modulation.
Just to add to the confusion, I repeated this with env-3 and get completely different results. Basically if mod-amount 2 is full then it seems as if a sustain level of '5' on env-3 is a zero setting.
If you want me to go into more excruciating detail about what happens at different settings just ask
So is the current setup broken? or does it just need explaining clearly?
-
- KVRian
- 533 posts since 16 Jan, 2006 from France
Ok, I bought it, I couldn't resist more : )
And I'm already creating what I like doing most : stringsynth patches.
I'll probably provide some soundclips if it turns out any good.
And I'm already creating what I like doing most : stringsynth patches.
I'll probably provide some soundclips if it turns out any good.
-
- KVRAF
- 1927 posts since 30 Oct, 2003 from Frolicking in Dirac's Ocean
First off...I love this synth. It's like buttah...big, fat juicy sounds. A couple of questions...
1) I realize this is not an emulation but I was wondering whether this harkens to any hardware synth in architecture or sound;
2) I run this in Sonar with a VST wrapper. So the whole synth doesn't quite fit - due to the wrapper. The very last row of wheels, keys and controls is very hard to get to as a result of the wrapper. I was wondering whether there was any way to add those window sliders that would allow for me to scroll down and access the area...
Anyhow...great work. This thing is a monster.
1) I realize this is not an emulation but I was wondering whether this harkens to any hardware synth in architecture or sound;
2) I run this in Sonar with a VST wrapper. So the whole synth doesn't quite fit - due to the wrapper. The very last row of wheels, keys and controls is very hard to get to as a result of the wrapper. I was wondering whether there was any way to add those window sliders that would allow for me to scroll down and access the area...
Anyhow...great work. This thing is a monster.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- Topic Starter
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
mayan: Thank you and to answer your questions...
1. Yes, merged the best features of my favorite classics and added a few new ideas but nothing that couldn't have been achieved with mid-70s analog electronics.
2. I've heard about the Sonar VST wrapper issue before. Will look into this for you guys. What screen res do you run?
Boulotaut2024: Thank you and welcome to the club! Let me know if there's anything I can do to help.
marvotron: The zero position on the mod mixers when in multiply mode mean no effect. As you turn it more towards +10 the preceding signal will be more and more attenuated by the selected modulator -- it's attenuating because while multiplying, its not usually by more than 1.0 (Envs work on 0.0 to 1.0 range, LFOs are either 0.0 to 1.0, or -1.0 to 1.0). So that's normal. The negative range has the same effect, just with inverted polarity of your modulator. However you're right, there IS something weird going on with Env3. I'll get this fixed for the 0.4 release (probably still a couple of days away but this new fix will be in it.)
Thanks for the great testing!
1. Yes, merged the best features of my favorite classics and added a few new ideas but nothing that couldn't have been achieved with mid-70s analog electronics.
2. I've heard about the Sonar VST wrapper issue before. Will look into this for you guys. What screen res do you run?
Boulotaut2024: Thank you and welcome to the club! Let me know if there's anything I can do to help.
marvotron: The zero position on the mod mixers when in multiply mode mean no effect. As you turn it more towards +10 the preceding signal will be more and more attenuated by the selected modulator -- it's attenuating because while multiplying, its not usually by more than 1.0 (Envs work on 0.0 to 1.0 range, LFOs are either 0.0 to 1.0, or -1.0 to 1.0). So that's normal. The negative range has the same effect, just with inverted polarity of your modulator. However you're right, there IS something weird going on with Env3. I'll get this fixed for the 0.4 release (probably still a couple of days away but this new fix will be in it.)
Thanks for the great testing!
-
- KVRAF
- 1927 posts since 30 Oct, 2003 from Frolicking in Dirac's Ocean
Thanks, AQ. You may have heard about the issue from me...I e-mailed you about it a coupla months ago. I run 1024X768 on a 19-inch flat screen. If I could lose the wrapper frame, I'd be set...barely. I realize why you don't want to make the GUI smaller...it's gorgeous and there's so many controls. That's why I though the scroll bar might help.
-
- KVRist
- 64 posts since 18 Jul, 2004 from KOREA
Hi, AQ,
Today I just bought Poly-Ana and played in my host program, Orion Platinum. I found some problem with Orion Platinum. When I play Poly-Ana, especially with the preset, '106-uni Bass', CPU goes up to 100% then It stops. With some other presets, it goes same. I don't know why. However other case it works fine and it sounds great.
You can test it with demo-version of Orion Platinum at http://www.synapse-audio.com
Thanks in advance
Today I just bought Poly-Ana and played in my host program, Orion Platinum. I found some problem with Orion Platinum. When I play Poly-Ana, especially with the preset, '106-uni Bass', CPU goes up to 100% then It stops. With some other presets, it goes same. I don't know why. However other case it works fine and it sounds great.
You can test it with demo-version of Orion Platinum at http://www.synapse-audio.com
Thanks in advance
Last edited by brouculy on Thu Jan 04, 2007 6:50 am, edited 1 time in total.
Viper, Nordlead 2X, Moog Little Phatty Stage II, Synapse Orion Platinum