We are working together to make custom Agent presets that will be able to load with any Nebula and Agent user. Thus making an Acqua like plugin within Agent possible with just a preset. This would give us Nebula sound quality with an Acqua type workflow, and everyone would be compatible with each other. So my Alex B PoolTeQ and your Alex B PoolTeQ would be the same, using one preset.
It is a 2 step process to make this work. We've had success in testing so it should work 100%. Step one is a custom Nebula Setup with skin. Step two is a custom Agent preset and skin. Will be around 20MB in size.
We are looking for feedback about the Nebula setups part, but open to any thoughts in general.
Should we use the default OVERWRITEME.N2S skin for every setup, making it easily compatible with every user? Or should we assign a different skin with every Setup, helping to make a standard where anybody who uses them would get the Agent preset but also compatibility with other Nebula users studio's using the setups we are making..... thus providing true session compatibility between any studio's using our Nebula Setups a reality.
It will be a simple, place the right files in the right folders, and you load up the Alex B PoolTeQ, or Blue 1102, or MFQ.... as long as you own the libraries, Nebula and Agent. We're pretty far along in our testing and we've got it working, we just want your feedback.
If you are not sure of what we are talking about with Agent, look here.
+1 for the default skin. One less thing for everyone to think about.
I wouldn't try too hard to keep compatibility across plain Nebula Setups workflows and Agent workflows. It's just going to lead to more headaches eventually. I feel like end users are going to have quite a lot of disparity among their Setups configurations / preferences anyway.
And proper thanks to you both for taking the initiative to make the UX better for everyone!
This seems really cool! I only just started using Agent, and it's made me fall in love with some older EQ libraries that I've been neglecting recently. And the CPU saving is freaking voodoo as far as I'm concerned!
Personally, I would much rather see dedicated skins and setups where possible instead of OVERWRITEME and a non-Nebula Setups version. I have a LOT of Nebula libraries that I've built up over the years and have made lots of Nebula Setups to combat loading times of sessions and Nebula itself. Because of that, I obviously started using dedicated skins for libraries when they were available.
Basically, I don't want to wait 10mins for a session to load just because there are possibly 100's of instances of Nebula within different Agents... all taking forever to load because they are loading ALL my libraries...
Hope I didn't misinterpret/misrepresent what you were saying Will, but those are my opinions
Hi! Very good initiative! I vote for standard Nebula overwriteme skin, one less thing to worry about.
Main thing in my opinion: I really miss bigger and better fonts in Agent. The Aqcua plugins have become much better in this department recently. So if you can speak directly to the developer of Nyrv Agent, it would be a huge improvement.
I have made some Agent instances, and it's great to load AlexB's S*L 4k EQ with all bands available - but it take a lot of time to make one such instance, so I really applaud your effort and initiative - thanks again
One idea: JPN has contributed a lot to this community by giving us very nice skins. Perhaps he would be willing to contribute to this project too? Just a thought!