Image Line

tony tony chopper · Post by **tony tony chopper** » Sun Jul 02, 2006 12:50 pm

Ok.. now you can either try the FL version in FL, or Fred will take care of this when he's back (couple of weeks).

If it's not the bandlimit then I have no idea right now. Could be something in the VSTi itself.

Edit: here I can play 36 voices of the default synth string patch at the same time, with a 9ms (x-fi asio) latency, using the FL version in FL, AND using the VSTi version in FL.
So it's probably a host conflict, and Fred will take care of it.

reflex · Post by **reflex** » Mon Jul 17, 2006 12:39 pm

Arksun: can you send me the simplest Cubase file that demonstrates this problem? My email address is frederic@flstudio.com.

Arksun · Post by **Arksun** » Mon Jul 17, 2006 1:45 pm

Ok frederic, I'll take it on email from here.

BTW my systems changed now from Intel to AMD and from SX2 to SX3, going to see how the behaviour has changed if at all and report to you ala email.

reflex · Post by **reflex** » Mon Jul 17, 2006 1:52 pm

I haven't got SX2, so maybe it's that. On the other hand, I've got a new test version of Sytrus that might work better. I'll send it to you by email once you've sent me the Cubase file (don't know if I've still got your email address).

woodie · Post by **woodie** » Mon Jul 17, 2006 2:06 pm

Hey fellas...I'm using Sytrus 2.1.0.1 over here and Live 5.2.

When playing around with various patches, I can confirm ALOT of movement on the CPU bar in Live...much more so than a couple of other VST's I use. On patches like the first one..the Synth Orchestra one...yeah...it spikes up about double and then back down and on every note there's alot of CPU movement back and forth (playing chords). I don't know if that's the way it's implemented "behind the scenes", but as in another sampler/synth VST that I use (used actual samples)...the CPU jumps up to a certain point and stays there when pounding away chords.

I played around with dropping the Unison and on/off on the B.Limit...and hardly see any difference in whatever patch.

I already got rid of any previous versions I had of Sytrus, so I can't compare with an older version.

Anyway, for what's it's worth...that's what's happening on my side!

Arksun · Post by **Arksun** » Mon Jul 17, 2006 2:25 pm

holymoly wrote:Hey fellas...I'm using Sytrus 2.1.0.1 over here and Live 5.2.

When playing around with various patches, I can confirm ALOT of movement on the CPU bar in Live...much more so than a couple of other VST's I use. On patches like the first one..the Synth Orchestra one...yeah...it spikes up about double and then back down and on every note there's alot of CPU movement back and forth (playing chords). I don't know if that's the way it's implemented "behind the scenes", but as in another sampler/synth VST that I use (used actual samples)...the CPU jumps up to a certain point and stays there when pounding away chords.

I played around with dropping the Unison and on/off on the B.Limit...and hardly see any difference in whatever patch.

I already got rid of any previous versions I had of Sytrus, so I can't compare with an older version.

Anyway, for what's it's worth...that's what's happening on my side!

I hope Image Line don't mind, I've uploaded an older version here (the one I still use), for you to grab and test on your Live setup:

http://www.musicprogressive.com/sytrus/

That's a 2.0.6 version. There's still some initial spike up on note plays, but nothing like the cpu maxout I was getting with 2.1 when playing 4 or more notes simultaneously (irrespective of preset type and settings)

But like I say, that's what I was experiencing on my older P4 3.2 with SX2, will test both versions for comparison on my new DAW later today.

tony tony chopper · Post by **tony tony chopper** » Mon Jul 17, 2006 3:03 pm

What I need to know (since no one here can reproduce anything strange) is if you see anything wrong with the Fruity version of the plugin (in FL itself).
I think the latest VSTi is the closest to the FL version that's in the latest FL beta (6.1, from our web site).
It would help as we don't know if it's on my side (the plugin itself) or Fred's side (VSTi).

If there's no difference between bandlimit on & off, at least that excludes what I thought it was.

woodie · Post by **woodie** » Mon Jul 17, 2006 3:18 pm

one problem though, gol, and I think Arksun's in the same boat....we don't own FL

Unless of course...this Sytrus version you're talking about comes in the demo version, then would that be sufficient for feedback? (using the demo version?)

Arksun · Post by **Arksun** » Mon Jul 17, 2006 3:33 pm

tony tony chopper wrote:What I need to know (since no one here can reproduce anything strange) is if you see anything wrong with the Fruity version of the plugin (in FL itself).
I think the latest VSTi is the closest to the FL version that's in the latest FL beta (6.1, from our web site).
It would help as we don't know if it's on my side (the plugin itself) or Fred's side (VSTi).

If there's no difference between bandlimit on & off, at least that excludes what I thought it was.

If you read all my previous posts on this thread regarding testing in fruity and bandlimit on/off that should already answer your question there

holymoly: read previous posts covering fruity use too, I do have fruity installed as well.

woodie · Post by **woodie** » Mon Jul 17, 2006 3:38 pm

ok my bad, arksun....yeah, I remember now reading that you had it.

odo · Post by **odo** » Mon Jul 17, 2006 3:41 pm

theres a update :\
didn't get any mail

tony tony chopper · Post by **tony tony chopper** » Mon Jul 17, 2006 3:57 pm

Yes you told about the FL version, but we have an FL 6.1 beta from our web site, and normally the Sytrus (FL version) that comes with it should be closer to the latest VSTi.

adam standring · Post by **adam standring** » Tue Jul 25, 2006 10:43 am

The CPU spiking issue was something I noticed happens with dual core processors. I had a similar issue with Pentium 3.2Ghz dual core chip in my Dell 9800 laptop and also with old drivers for my Athlon X2. New drivers and a microsoft patch sorted the issues which are with processor scheduling, when the software tries to spread the processing load between two cores.

tony tony chopper · Post by **tony tony chopper** » Tue Jul 25, 2006 10:48 am

Fred has fixed it (he had left file logging stuff in the release).

Arksun · Post by **Arksun** » Tue Jul 25, 2006 1:04 pm

Yup, I can confirm the latest updates really helped.

adam: wasn't just dual cores I had it something cronic on my previous Pentium 4 3.2HT (though I guess it could have been HT related, multithreading that way)

With the AMD X2 the problem wasn't that noticable, but with the latest version the prob seems to have gone altogether. Good stuff guys

Arksun

Image Line

KVR Audio

CPU Spiking issues with Sytrus 2.1