Keni

Thanks Starship! That was some good info and observations. I didn't know about Cherry's association with Acoustica. Not that it would have mattered to me as I have no 1st hand experience with them... The dll location is of little importance to me between the vst2/vst3 systems and with what you said about the sidechaining not being restricted to vst3, what then is the point of the vst3 "update"?

just an immediate thought is that no demand when audio not passing may save something, but that doesn't mean the plugin will perform better. Needing to constantly turn on/off may have it's own issues. All the calls needed to do this may actually increase the system demands. But I'm not a programmer. I don't know... What I do know is that repeatedly if I replace my vst3 devices with vst2 equivalents, My system runs leaner/better...

Yeah... I hear you! I too use direct monitoring when recording via mics, but I now use virtual guitar/bass amps which lay in the demands and increases latency. I've often wondered about what changes there are between vst2/vst3. The only feature I know of is side-chaining which is something I rarely do these days. I don’t remember the last time I did. So what else fhanged causing them to be so much more resource hungry? I've switched back to all vst2 except the few items that now are vst3 only.

Interesting... My usage meters hardly light yet I get problems relieved only by increasing the latency. I'm running 12 cores with multi-threading which Cake shows as 24 cores. Mine barely show any height. A nudge up from none. So it's not my processor having the difficulty. I'm believing it's the audio interface itself. Mine is somewhat old, but claims a latency of 5ms peak. I can run very little at 64 but run normally at 128 for most things. Some of the new Synths coming out are proving to be very vst3 resource hungry so that's changing things. I'm very happy with running the vst2 versions instead where available. I have no known need of the vst3 features such as side-chaining very often if ever... I freeze all my tracks prior to mixing so I mix most of my stuff at 128 as well. Only some of these new issues spoken of have begun upsetting that but now knowing to default to vst2 when possible, I should do better... I hope. This latency dancing is just too much constant fidgeting!

We already KNOW what a great DAW it is! ...simply finding it's way back into the mainstream. ......but Ai, Ai, Ai! It's all too much!

OK... Blindsided me... I thought about it on occasion but somehow let it pass... It seems there's a huge difference in resource demands of VST3 and VST2 plugins. For a long time I've been having a lot of trouble with a number of plugins resource hunger and others tell me they aren't seeing that... I don't know if this is the reason, but I just realized that when I upgraded to this win10 (from win8.1) system I decided to start using vst3 versions of everything when available. Not for need, only to be more current... Now I'm discovering many, if not all vst2 versions operate much more efficiently... MUCH more. Previously work running Cherry Audio's VST3 Memorymode I was forced to 512 or 1024 latency for even simple operation all by itself. Just now I loaded the vst2 version into a song with Session Drummer 3 (active) and 4 frozen tracks (still live feeding some bus fx etc.) and I can cleanly play most of it's presets at 128! The light is finally on in my brain again? Addendum... Just found that monophonics play fine at 128 in above scenario, but polyphonic reqiores changing that to 256. Not fabulous, but way better than the vst3 version!

I was thinking along those lines as well... I even tried some of the temporary forums setup during the Gibson dumping. Of course long closed down... I left a post of the Cakewalk Community page on Discord, but ...

Ah. Now I understand.

"Add page"? What did I miss? I don’t see such...

Yup... I guess many of us were thinking/wishing/hoping this was the case. Now it’s just gonna be another sad Monday tomorrow...

......Simply keeping the dream alive!

Wow! Amazing that’s still online!

Thanks. I'll remember that if a need for the vst3 arises. As far as I remember, the only really significant difference is the side chaining which I rarely use.

Absolutely! I love it! (The response) As for the software? I’m not a big user of sample libraries these days.

Good one John... I'm gonna change the thread title right now! 😉

Yeah, I'm learning this with Little Plate too... I've gotta increase the latency more than ever before to use this plugin... I'm gonna look/see if I have both vst2/3 and try the vst2 if it's there as I typically defer to the vst3... Maybe that'll be a little better? Edit: Wow! Massive difference. Switching to the vst2 version instead of vst3 and my system is back to normal able to run clean at 128! I have no particular need of the vst3 version to begin with! Thanks for the tip! Edit 2: With this thought in mind, I just tried this same "trick" on one of my most resourse hungry plugins... Cherry Audio's Memorymode... Running the vst2 instead of the vst3 again totally change the situation and the plugin runs clean as a whistle at 128! I think I'm swearing off on all vst3 versions of plugins for the time being. I see very little need for the vst3 versions (for me)

Not sure if this matters to anyone, but I just stumbled upon this. A product called Sonar (not related)... https://audioplugin.deals/product/sonar-pings-and-signatures-by-fallout-music-group/?utm_source=APD+Subscribers&utm_campaign=57c9ccceb1-Blog_IK_Multimedia_MixBox&utm_medium=email&utm_term=0_766211a9e5-57c9ccceb1-39509537&ct=t(Blog_IK_Multimedia_MixBox)&goal=0_766211a9e5-57c9ccceb1-39509537&mc_cid=57c9ccceb1&mc_eid=22fd0c11f1 Any problems arising?

Yeah, a trashcan gift. I really never use the Mac side. My previous machine (I still have) is also a Mac Pro dual xeon 6 core with 64G. Also a beauty. Each of these machines was over $10k!

Wish I could afford to... but a dual xeon 12core with the trimmings is over $10k away...

No. If you download from the web page, you get the full installer.

It seems to me that more plugins are turning up with heavy resource demands these days. Most fx are reasonable, but Instruments are another story. Often hard to work if more than one virtual instrument is active (frozen not an issue). So constant freeze/unfreeze/clean drive required. ...and I’ve got a reasonably powerful machine (xeon 12-core multithreaded, 128G) The anti is raised again!

Yup. I ran into that with Amplitube 5 crashing CbB at 512 but fine at 128/256...

I’ve always followed that idea, but never before actually needed it! My difficulty frequently arises when I need to record guitar using a virtual amp etc. but even then I’ve never before been forced to do these things. The Little Plate being the first to put me in this position. Though the Cherry Audio excellent synths frequently give me grief too! 👀

Thanks David... That's what I have been believing... and experiencing. But wanted a firmer grasp on what's involved and going on. I had the understanding that without the immediacy of live playback, the pc was afforded the necessary resources to accomplish more than the live play... Yesterday I played safe so that I didn't feel I needed to scrutinize for such errors (though of course I did anyway) I simply opened the latency all the way to 2048 to be safe! 😉

Thanks John I think you addressed my question towards the end of that. When rendering an output mix, the latency settings do not affect the outcome...