Stratisound
New Member
I am curious about the Waves Rack plugin...Within VE Pro, When I click and open it I see the "sys" preset and there is actually nothing in there plugin-wise. Is there meant to be plugins in there?
Yes there should. Please send me a support mail with a screenshot and the template version details here:I am curious about the Waves Rack plugin...Within VE Pro, When I click and open it I see the "sys" preset and there is actually nothing in there plugin-wise. Is there meant to be plugins in there?
Hi Bensmir!Is it possible to import the tracks from this project to our personal template and still retain all the template important settings ?
importing my template in project colossal is actually quite cleverHi Bensmir!
This is definitely possible. Its important to keep the original routing so the sound is correct. That being said, the expansion only runs in VEP. So no track import is possible there since VEP already works like track import with their workflow.I'd recommend opening the original template first to check how it's setup to see how the track import in your personal template can be done best. Or even the opposite: import your template in Project Colossal!
Hope that helps!
Best,
Rico
+1So I got it and it’s great but wound it be possible to have a “lite” version where it’s one instrument=one library and have the mic position setup there etc? Instead of three?
It won’t sound the same of course but for convenience sake.
Mainly css without vep.
So I got it and it’s great but wound it be possible to have a “lite” version where it’s one instrument=one library and have the mic position setup there etc? Instead of three?
It won’t sound the same of course but for convenience sake.
Mainly css without vep.
Hey hey!+1
Having 1 track per instr. and articulation would be very appealing
I can’t stand midi tracks too
I think the core idea behind your template does not fit the single track indeed because it's tailored around CSS and the mic positions.Hey hey!
I did test this and did choose not to. The reason was to avoid having 3 mics per instance of every articulation. So now for example the 4 horns have just 3 outputs. Even for the split patch version. Instead of 33 or even 36. Wich means you would have 264 mixer tracks only to have separate kontakts for the brass section. Imagine the loading and saving times now...
Then the mix mic...
The whole idea is to use all mics to be able to do some close mic automation and sculpt the sound very specifically. This is simply not doable in the mix mics, and not in line with what to me was the idea of Project Colossal. That being said, I'll consider doing a 'lite' version in VEP as another expansion since it would definitely be helpful to lighter systems.
Best
R
Yes and no, I did split the mics out for flexibility for sound. But if you want a more intimate sound i would not do that with automation. Simply a fixed change so to speak. But specifically for brass and woodwinds a bit of close mic automation can help tremendously. I think boosting that in context sound better than simply boosting the decca and rooms too. That would unbalance the section too much if overdone. Check out Star Wars Episode III music for example. You REALLY can hear the section/close mic automation on the trumpets. Not everywhere is this pointy detail. So yes its intended for sound purposes, but specific ones i would say.I think the core idea behind your template does not fit the single track indeed because it's tailored around CSS and the mic positions.
Excuse me if it sounds obvious but why do you emphasis the close mic automation ? Is it to make the template more flexible depending on what type of sound you want to get ? Is it specific to CSS or would you have done the same if your template was based around another multi mic library ?
Doesn't Kontakt have internal EQs compressors etc that can be used (in addition to the fabfilter/etc afterwards) or will these not save with the template?Hey hey!
I did test this and did choose not to. The reason was to avoid having 3 mics per instance of every articulation. So now for example the 4 horns have just 3 outputs. Even for the split patch version. Instead of 33 or even 36. Wich means you would have 264 mixer tracks only to have separate kontakts for the brass section. Imagine the loading and saving times now...
Then the mix mic...
The whole idea is to use all mics to be able to do some close mic automation and sculpt the sound very specifically. This is simply not doable in the mix mics, and not in line with what to me was the idea of Project Colossal. That being said, I'll consider doing a 'lite' version in VEP as another expansion since it would definitely be helpful to lighter systems.
Best
R
Sure you can. I find the FFproq3 just more user friendly and quicker to use. But you can definitely use those and resave a copy. You always can download a fresh copy from the access link anyway!Doesn't Kontakt have internal EQs compressors etc that can be used (in addition to the fabfilter/etc afterwards) or will these not save with the template?
Im releasing something else I've been working on for almost a year now first. Hope to share more on that very soon!@ricoderks, Will you be releasing an update for Colossal with an expansion anytime soon?
Thanks so much! I think it could be a version problem. Pro R2 came out today too! haha!@ricoderks
Jumped on the train this night and must say: great work rico
Everything is running fine. Only "Pro-R" I had to open manually and choose your preset. It was marked as not found in the slot - maybe a new version? (I use V1.15 64bit VST3 from March 2023).
Now I wait for "Gullfoss"- and "Soothe 2"-Sales and then its complete. But already such a huge improvement in sound! Its so nice and fun to work with "Project Colossal" -just start composing without thinking about sound, eq´s, reverbs, etc.
Now its time for the release of CSS Percussion
Yeah - but R2 is a separate plugin. R1 stays with itThanks so much! I think it could be a version problem. Pro R2 came out today too! haha!
I'm eager to work on the perc as well! Next year I hope!
Cheers!
Glad it was solved by re-loading the preset! Im not using R2 anytime soon in Colossal i think.Yeah - but R2 is a separate plugin. R1 stays with it
No prob - it was just a free grace period upgrade or better "free R2"-pluginGlad it was solved by re-loading the preset! Im not using R2 anytime soon in Colossal i think.
Happy Composing!