KVR Audio

nix808 · Post by **nix808** » Tue Nov 18, 2014 4:56 pm

Thanks!
With the RAM,
once you have deleted the instances you don't need,
you can save and reload the project.
This will free any hung-up memory.
So- actually I think I will work on this today after all hehe,
maybe I can push it through to ver.1 within a week.

I will keep a close eye on the RAM when I write the next Orion song,
to make sure it is just a loading, deleting thing ie. that it does not climb.
It really shouldn't, all the mems have fixed lengths, which are loaded at plugin load.

idfpower · Post by **idfpower** » Tue Nov 18, 2014 8:03 pm

I see... well thing is that it seems to increase in CPU consumption also when tested it in a single instance session... just browsing through presets will trigger the CPU build up and soon it drives FL into CPU overload. I don't know if it's just a particular condition due to my PC settings or maybe something to do with FL itself...

nix808 · Post by **nix808** » Tue Nov 18, 2014 8:09 pm

Oh damn man,
will write in Fruity now-
r u using the version with vector graphics?

Maybe it has a denormal somewhere- now testing and sorry

idfpower · Post by **idfpower** » Tue Nov 18, 2014 8:43 pm

No, just FL Studio 11 (11.1.0). And ASIO4ALL v.2.12. I think there may be something in the build of the program... for ex (on certain synths) when you use multiple instances of the same synth in a session and then "freeze" the tracks, if you load a new instance of the same synth, although the others are "disabled" it still "sees" them as active and adds them to the CPU load (well at least that's how it behaves on my PC). So maybe it's something particular just to FL...

nix808 · Post by **nix808** » Tue Nov 18, 2014 8:57 pm

hmm,
I dunno what's happening,
will try freeze now.
I have 7 instances running at 20% FL dsp monitor,
they are not climbing,
after loading or just letting it run.
It is the vector beta 11.5.13

Will keep Fruity testing mate, hope u can bear with me

Also it's interesting to see how it performs as FL FlowStone
it's using a slightly oscillating 754mb Ram

edit-it's running good here with the 7 instances.
There's some preset switching UI glitch, will look at it today

idfpower · Post by **idfpower** » Tue Nov 18, 2014 9:21 pm

nix808 wrote:There's some preset switching UI glitch, will look at it today

Yeah, that's kind of "normal behaviour", heh

Same thing happens with Vaccin and other synths as well. Sometimes the UI itself will make it stutter bit if it's on display.

Maybe it's worth mentioning that my PC is really ancient (P4 dual core @3Ghz)

it adds to the list of possible issues I'm afraid

No problem, take your time

Thanks for being so understanding & responsive so far

EDIT: ok I've downloaded again the latest version of the plugin and so far no more CPU build-up (at least not in single instance session)

nix808 · Post by **nix808** » Wed Nov 19, 2014 9:57 am

Oh good!
Yeah, the s&h execution order was wrong I think,
but I wrote it again and saved CPU by just making the counter for it free or retrigging,
while there is just one hold.
It was the S&H IMO.

This preset changing thing in FL is really annoying,
and there is no easy fix-
looks like it is somewhat cumulative ie. in degrees of noticeability,
depending on which modules are in the schematic.

I am aware that the draw LFO is not working in the current version, will up another soon.

idfpower · Post by **idfpower** » Wed Nov 19, 2014 12:51 pm

nix808 wrote: This preset changing thing in FL is really annoying,
and there is no easy fix-
looks like it is somewhat cumulative ie. in degrees of noticeability,
depending on which modules are in the schematic.

Heh, tell me about it

I've been really struggling with some newer synths... it seems they've reached a point at which the program got too bloated and all sort of issues start to surface...

nix808 · Post by **nix808** » Wed Nov 19, 2014 7:48 pm

I have found a way around it-
unfortunately I think this setting cannot be made global.
Like I say, I am running the latest beta-
which allows in the plugin's individual settings to uncheck in GUI group 'Check properties on display change',
this stops the glitching.
I suggest we petition to make this default, or possible to set once globally.

Let me know any other issues you experience with Flowstone,
or FL generally if you'd like.
I'm going to wait until this beta goes full, then I will set up my FL environment again,
after 8 years of absence.

idfpower · Post by **idfpower** » Wed Nov 19, 2014 8:02 pm

Oh, I see

On a different note (and with the risk of becoming annoying, heh): if you like the symbol overlay that much, can you please crop it so it wouldn't overlap the synth's central display? And also, why not moving the name of the synth in the middle of the UI, instead of the "ATTACK"?

Nitpicking, I know

Tricky-Loops · Post by **Tricky-Loops** » Wed Nov 19, 2014 8:05 pm

Phenome looks much better than Entrancer!

nix808 · Post by **nix808** » Wed Nov 19, 2014 8:31 pm

Thanks Tricky!
Entrancer is due for a UI overhaul for sure.

I made those mods pretty much Mr.Power,
the Attack in the middle matches the look of Entrancer,
so I left it there.
The file is in the first post.

I get very particular too,
one of my recent issues is that you cannot rename the plugin window in MAX/msp-
it's driving me to distraction
I hope you like those little mods, let me know what else u want done to it

idfpower · Post by **idfpower** » Thu Nov 20, 2014 7:38 am

Oh, wow, the modified UI looks very cool

I'm very impressed that you've actually taken the time to do it - much appreciated

nix808 · Post by **nix808** » Fri Nov 21, 2014 8:11 am

I'm happy to do things like that, that are easy to do in the build.
I have one knobstrip .png, and the overlay just needs to be hidden.

The destinations etc. will be more time consuming,
but I'll get around to it. Just playing with my drum synth DrumRoll-
it's going to be a lot better ie. the graphical envelopes will be much improved.

Just wanted to say nice one to the community, the latest version before IDF's
has had 414 downloads.

Xenos · Post by **Xenos** » Fri Nov 21, 2014 5:21 pm

Bug report: Patches saved often dont sound correctly when reloaded. The filter resonance and keyfollow knobs seem to load in random settings rather than the exact settings they were saved at.

I will wait on submitting my patches until the synth is more finished.

Btw, serial routing for the 2 filters would be a major improvement...being able to have the output of filter 1 run through filter 2. You'd get some nice vocalesque sounds as well as a few other tricks.

Attack Phenomen, x64!