Plugin vs DirectWave Render

Discuss & Share DirectWave content here

Return to “Direct Wave - Presets & Programming”

[You can only see part of this thread as you are not logged in to the forums]
Jonathanese
Sun Dec 17, 2017 1:48 am

0 x

Plugin vs DirectWave Render

I recently got EastWest Symphonic Orchestra Gold. As nice as it sounds, FL studio adds about 3GB of RAM usage the moment the plugin is loaded (no samples loaded yet), and a full orchestra runs upwards of 11GB in FL despite system reporting 5GB in use. EW only reports 1GB of actual usage. The CPU reports 70% usage without doing anything. So something between EW and FL is running like complete and total garbage.

Then there's the fact that things like slides and such don't work. But adjusting control channels works so I can work with that.

But I'm wondering if it would be worth it to instead do a render of all the instruments into directwave (like 2 notes per sample and 4 velocities), or if I would see a loss in quality or just a waste of time. Like something about it feels like a bad practice, but I need the CPU and RAM where I can get it.


So what do you think. VST plugin or Directwave render?

Or if you have experience with sample plugins like this, maybe you could give me some advice.

Thanks in advance!

sql_error_uname
Tue Dec 19, 2017 1:11 pm

0 x

Re: Plugin vs DirectWave Render

i prefer vsts but sometimes it is almost imposs...

Jonathanese
Tue Dec 19, 2017 6:00 pm

0 x

Re: Plugin vs DirectWave Render

Disk space is generally not much of a concern f...


Return to “Direct Wave - Presets & Programming”