So I just had a glance at your homepage as well as the github profile but I am not sure: does this mean I can run the server on mixed platforms (e.g. one Mac, one Windows machine) and use those on a Mac DAW with the plugin? Like having a "Windows Outboard" in a Mac (or Linux for that matter) DAW?
When I realized that SoundGrid system was only proprietary at the software level and that the machines were just custom made intel workstations, I became most excited about the prospect of building out my own DSP network. However, I was shocked that there wasn't any soundgrid alternatives commercially available, but a double shocker once I tracked down AudioGribber discussions deep into a pc audio forum where they speak so technical, It might as well be klingon!
I am most thankful for this being opensourced as this will enable so many within the music creator community access to a tool and solution to overcome the financial barrier to acquiring current industry grade workstations. i APPLAUD this effort!.
just discovered this awesome tool. quite stable (only a few GUI things depending on the VST used) but nothing serious.
thanks for your time and effort to offer this for free.
will definitely donate as long as I use it.
will there maybe be an option (if the Server is not available) to load the actual VST in the plugin, to not be always relying on an available server? Also it would be possible to host the Server on a multi core machine on the same computer (maybe in a VM) to offload processing from the DAW's threads.
I have a 16 core CPU and my DAW can't (or won't) use all cores by itself. Usually because of sidechaining only 2 cores can be used by the DAW itself.
When I now use another core which is free on the same machine (by affinity) I can run bigger sessions. Of course a bit of latency is introduced, but that's no problem for me in mixing/mastering.
I don't get it why DAWs still don't allow to process a track on more than one core. Probably the synchronization of data across cores is hard to implement, but this would be the solution for so many problems in these times where core counts are getting higher but not IPC.
I also noticed when hosting plugins on AG on the same machine, I can have way more instances than in Reaper (DAW) itself. I tested this mostly with plugins in series, because that's where dropouts usually happen at some point. AG seems to be able to handle way more plugins without dropouts than Reaper, perhaps because it can be set to greater buffer sizes? Bit I distributed the plugins by 8 plugin instances per AudioGridder Plugin. I didn't put AudioGridder Server on a virtual Machine, I accessed it by typing in 127.0.0.1 as the server address in the AG plugin.
I just successfully switched an AG instance between local server and another machine. Seems no problem as long as the plugin name and format is the same on the other machine.
It would be great to be able to perhaps set some sort of rule how to search for different versions of the plugin on different machines. Let's say I have VST versions on one machine, but Audiounit versions on the other, AG could load the AU version on this particular machine. Would be a great feature for cross platform compatibility etc.
Thanks apohl79 for your awesome program! I've discovered it not so long and in my tests and it works really good! I have some minors issues and it will be could if you can look into them for your future releases:
- i'm using it on Local mode (version 1.1.1) on win 7 64-bit, and the position of the inserted plugins in AGridder is never remembered (always opens on the left corner of the screen).
- plugins inserted on AGridder don't stay on top of the other windows, when using them as soon as i click somewhere else on my DAW there dissapear and go to the bottom of the openned windows.
- when reoppening a session that had AGridder, Algouth the loaded plugins are remembered and work fine, AGridder is blank like when you first start it without plugins. And if i close it's window and reoppen it now it shows the loaded plugins correctly.
- the loaded plugins steal focus of the keyboard, so pressing the spacebar don't start playing the DAW.
All these tests concern mostly the VST format(DAW used was Fl Studio 20) and the results were the same with Protools 12 but after having load AGridder in a very heavy Protools session with a very CPU heavy plugin that session won't load anymore, so will report perhaps later if needed for the aax format.
Thanks again for this awesome solution given freely, tha'ts very generous.
This tool is awesome!!! I'm just trying it these days and if it works as it seems i will donate to the project with great pleasure!!! Guys remember to donate if you use it, it's a great way to support the development in both economical and morally way.
I just have a question. I noticed on Fl Studio if i make automations they are not compensated as it should, so in example the automation start and end little before than it should. If i export the project the automations doesn't work as they should, i.e. if i start a low pass filter to go from 10% to 100% (where 100% is no filtering at all) it happen the WAV to be strucked for the rest of the song at 70% i.e. so it seems to skip some automation points.
I hope you can fix it. I'm using the latest version (beta 15).