i agree.
i only recently started to explore all this stuff and i've had this in my plugins for a few years now.
it's very well laid out, more than any other vsti i can think off...
i agree.
there's no demo, it's free nowadays.
Thanks.
thanks heaps! this was really informative. i have tried a homebuilt "newest version" and with Circus2 +Logic Pro X + AU I was not able to get the clicks to appear. I am familiar with the clicks, however, i know what you're talking about. there was a ticket about it, and it got fixed and closed. now with Circus 2 + Renoise + VST2, I'm not getting clicks to appear when playing multiple (4-6) notes at the same time.Spitfire31 wrote: ↑Sun Jan 06, 2019 3:09 am So far, I've found this 'unintended behaviour' on the following presets.
Category: Keyboard
Circus 2 (but not Circus)
Organ 3 (but not Organ 1 or 2)
Category: Monosynth
Cell
I noticed the 'strangeness' first when playing 'Circus 2', which is polyphonic. I got sharp, digital clicks when playing legato. Later, I instead got 'squeaks' and exploring further, I got all kinds of funny sounds when playing two notes simultaneous – for example, an overlaid tone that kept on rising, like a signal generator. Playing 'Circus 2' monophonically and detached sounds normal.
'Organ 3' displayed similar unexpected antics and 'Cell', although monophonic, produced intermittent clicks, like those I first noticed with 'Circus 2'.
It would be interesting to know if somebody else has found something similar. I haven't tested the AU version yet, since I'm using FCP on the same machine and am keeping its AU arsenal at a minimum.
/Joachim
this is similar to the aMUSEd error, and an error i have been having when binding parameters into DAW from Surge, where twiddling a knob in Surge will result in two automation knob binds in DAW. it is being looked at currently.
are you able to see this issue happen still, and could you point to a specific two presets that, when loaded, cause a crash? that does sound pretty horrible. but Bass, Keys and Atmospheres are huge!Saukar30 wrote: ↑Fri Jan 04, 2019 3:29 am Im wayyyy late to the party on this (i have the 2nd version of Surge that was uploaded on Github and haven't kept up with the changes), and I dont know if its still an issue or not, but when browsing through the presets one by one starting from the 1st category, there were about 5 or 6 presets that caused my DAWs to crash. I checked in Reaper, FLStudio, Cakewalk, Reason, AKAI MPC, Orion; 32 & 64 bit, same presets. They were different presets in I believe the Bass, Keys & Atmosphere categories (if not those, then definitely whichever the 1st 3 are). There could be more but I ran out of time to test. I didn't see anything familiar about the presets such as which wavetable, filters, or parameters that were in common. Again, this was with the 2nd build of Surge as open source and I uavent touched it since then.
If these have been addressed, I apologize for bringing it up and the vague information regarding it. My hard drive crashed on New Yeras and I just got it back up and running again
Can ya be more specific.. which operating system, which DAW.
can ya try the 11th january 2019 (or newer) build at https://kzantow.github.io/surge/ and see if it still happens?
This issue was resolved with one of the 1.6 builds.esaruoho wrote: ↑Fri Jan 11, 2019 7:05 pmcan ya try the 11th january 2019 (or newer) build at https://kzantow.github.io/surge/ and see if it still happens?
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement