Shattered Glass Audio - Code Red Free (Console Emulation)

[Ultrasonic]

[quote="tunca"]I made video for you.But i said that "nothing about quality,it's about taste!".Thanks for plugin.

Of course its about quality. Saying otherwise is just a cop-out for inability to deliver quality.

If its not about the quality, then theres no reason to be here, soaking up information or trying new plugins.

[tunca]

I made video for you.But i said that "nothing about quality,it's about taste!".Thanks for plugin.

Of course its about quality. Saying otherwise is just a cop-out for inability to deliver quality.

If its not about the quality, then theres no reason to be here, soaking up information or trying new plugins.

My aim is not showing quality difference.

[LAGinz]

For some reason the vst3, but not the vst2 dil , shows up in Studio One Pro. V2. Double checked and the vst dil is in the right place- just not recognized.

[Compyfox]

Could be a very simple ID issue.
Both Cubase and StudioOne tend to "remove" either the VST2 or VST3 version if the ID's of the plugins are the same.

I have several plugins on my HDD where that happens.
Just to be sure, temporarily remove either of these plugins from their folder. Then relaunch your host. If the plugins show up each time, then it's an ID thing. If they don't, then something else is wrong.


And tunca:
I've watched your video.

It's good that you used the WAVES REDD.37/51 as comparison, but why did you leave the WAVES plugin in .37 mode if the SGA preamp is actually modeled after the .47, which later turned into the .51? At the beginning of your video, the sound difference of the preamp alone is more than apparent.

[tunca]

Could be a very simple ID issue.
Both Cubase and StudioOne tend to "remove" either the VST2 or VST3 version if the ID's of the plugins are the same.

I have several plugins on my HDD where that happens.
Just to be sure, temporarily remove either of these plugins from their folder. Then relaunch your host. If the plugins show up each time, then it's an ID thing. If they don't, then something else is wrong.


And tunca:
I've watched your video.

It's good that you used the WAVES REDD.37/51 as comparison, but why did you leave the WAVES plugin in .37 mode if the SGA preamp is actually modeled after the .47, which later turned into the .51? At the beginning of your video, the sound difference of the preamp alone is more than apparent.

Actually i was thinking to make with all models but i have no time to do this for now.

[lingyai]

Really enjoying using this -- thanks very much !

One small niggle, though -- in Sonar Platinum, I've tweaked some parameters and saved them as a preset. The preset is loaded when I close and save the project. But when I reopen it, the preset is not loaded; instead, all parameters revert to the default settings. I have to then reload the preset. I don't think this is a Sonar issue no other VST fx plugs behave this way there, at least not on my W7, 64 bit PC. Anyone else seeing this? Any ideas re a solution?

[planetearth]

Really enjoying using this -- thanks very much !

One small niggle, though -- in Sonar Platinum, I've tweaked some parameters and saved them as a preset. The preset is loaded when I close and save the project. But when I reopen it, the preset is not loaded; instead, all parameters revert to the default settings. I have to then reload the preset. I don't think this is a Sonar issue no other VST fx plugs behave this way there, at least not on my W7, 64 bit PC. Anyone else seeing this? Any ideas re a solution?

I have Sonar X3e on Win 7 x64, and it loads the plug-in just as it was when I saved it.

Are you using the VST2 or VST3 version? My test was with the VST3 version.

Steve

[lingyai]

Really enjoying using this -- thanks very much !

One small niggle, though -- in Sonar Platinum, I've tweaked some parameters and saved them as a preset. The preset is loaded when I close and save the project. But when I reopen it, the preset is not loaded; instead, all parameters revert to the default settings. I have to then reload the preset. I don't think this is a Sonar issue no other VST fx plugs behave this way there, at least not on my W7, 64 bit PC. Anyone else seeing this? Any ideas re a solution?

I have Sonar X3e on Win 7 x64, and it loads the plug-in just as it was when I saved it.

Are you using the VST2 or VST3 version? My test was with the VST3 version.

Steve

Good tip, thanks! I was using the VST2. Tried the VST3, and that initially crashed Sonar (!) but since reopening the project all has been good.

[planetearth]

Really enjoying using this -- thanks very much !

One small niggle, though -- in Sonar Platinum, I've tweaked some parameters and saved them as a preset. The preset is loaded when I close and save the project. But when I reopen it, the preset is not loaded; instead, all parameters revert to the default settings. I have to then reload the preset. I don't think this is a Sonar issue no other VST fx plugs behave this way there, at least not on my W7, 64 bit PC. Anyone else seeing this? Any ideas re a solution?

I have Sonar X3e on Win 7 x64, and it loads the plug-in just as it was when I saved it.

Are you using the VST2 or VST3 version? My test was with the VST3 version.

Steve

Good tip, thanks! I was using the VST2. Tried the VST3, and that initially crashed Sonar (!) but since reopening the project all has been good.

Glad it worked!

I installed both (I don't remember having a choice otherwise), but Sonar is supposed to automatically replace VST2 plug-ins with the VST3 versions, if you have them installed. (It's an option in the Plug-in Mangler.)

The problem is that Sonar also doesn't usually handle VST3 plug-ins very well!

Steve

[lingyai]

Sonar's VST3 foibles were supposed to have been patched in Platinum. By the way, Sonar does give you now t an explicit choice, when adding a plug, which version to use.

I'm actually not sure whether the VST3 version is better for me; since I last posted, I had several almost immediate crashes when adding it or specifying a preset. I saved before the last crash, reopened, and now it seems stable, but ... I might just go back to using the VST2 version, living with the fact that I have to manually load in a preset when I open a project. Not the end of the world -- worth it, given the sound of the plug itself.

Still, I'd wonder if anyone else has had this problem. Perhepsthe developer might chime in when he or she reads this.

[planetearth]

Sonar's VST3 foibles were supposed to have been patched in Platinum. By the way, Sonar does give you now t an explicit choice, when adding a plug, which version to use.

I'm actually not sure whether the VST3 version is better for me; since I last posted, I had several almost immediate crashes when adding it or specifying a preset. I saved before the last crash, reopened, and now it seems stable, but ... I might just go back to using the VST2 version, living with the fact that I have to manually load in a preset when I open a project. Not the end of the world -- worth it, given the sound of the plug itself.

Still, I'd wonder if anyone else has had this problem. Perhepsthe developer might chime in when he or she reads this.

You'd probably have better luck posting this in the Sonar forum, unless this is the only VST3 plug-in you're having a problem with.

And I haven't tried saving presets with this plug-in. I noticed the presets that came with it are in the .XML format, which isn't standard for presets (as far as I've seen). I doubt this has any effect on your situation. It's just something to think about when you go to save the preset, since it won't have the "standard" file name extension.

Does this happen in every project in Sonar--even new, "blank" ones?

Steve

[v1o]

Hows the paid for version compare to the Waves Redd?

[Tappistry]

A 4 year old thread?!

I swear this forum does more necrobumping than a zombie Thriller flash mob.

[martinjuenke]

Who is necrophilic: raise your arm stump, you bloody zombies

[Tappistry]

Who is necrophilic: raise your arm stump, you bloody zombies

I almost made a similar joke but was afraid I'd get banned for poor taste.