So, this is what I can get following previously mentioned method.

 

Hi Cherry,
You are assuming that all our usernames are "admin", is that correct? We therefore need to edit the respective .cmd files to include the correct paths?

 

Same here Vst2 in Studio One 5 and Fl studio 20.Can't even change track name in Vst3.

 

I apologize. This is my mistake. I'll fix it soon and throw off the working method.

 

I apologize. This is my mistake. I'll fix it soon and throw off the working method.

 

Do someone can share reaper presets?

 

Here is a corrected version:

You still need to turn off the DAW before changing the strip, because Consol does not release some files for writing. I have in Reaper so. I left the cmd window so that I could see the result of writing files.

 

Last edited: Jan 9, 2021

Thanks for the updated file, sadly I cannot get it to work on Studio One 5. I can see the window when renaming but then it closes when pressing enter.

 

There are so many other plugins why would you want to bother

 

Don't press Enter. Leave the OSD window open and unload Console, and load the plugin Console again.

 

Because that is how it supposed to work you are not missing out on any features without that window

 

Thanks Cherry , will try it this way.

Does anyone know if the console 1 hardware works with the recent releases from the sister site?

 

Wrong activate.cmd, errors on all lines for 9000!
"The system cannot find the file specified."
======================================
Sorry, my fault
First you must manually copy all files to %appdata%\roaming\Softube\Console 1\Presets\Channel Strip\

 

Last edited: Jan 10, 2021

If you are having the issue where the OSD window closes after renaming the track or hitting cancel, OR to make VST3 version work like VST2 version heres what you can do:

- Load up the VST3 Console 1
- Go into the settings
- Disable Use DAW Track Selection, Use DAW Track Name, Use DAW Track Number (I also disabled Use DAW Control, so you might need to disable that one too)
- Restart DAW and Console 1 OSD

- Load up a new instance of Console 1 VST3
- Now click on track name, and when OSD window pops up asking for track name, don't click ok/cancel or anything.
- Instead remove the plugin from your plugin chain (you'll notice the OSD window stays but the name track window dissapears)
- Then load up a new instance of console 1 and you should be all set.

Now after having done all that work, was it worth it?

 

On Studio One 5 open Console 1 VST2, not VST3, or uncheck Use DAW Track Names in Console 1 plugin settings. If ask for track names, not close this windows, but exit Console 1 plugin then reopen it again.
You can see only one OSD window, can't change anything in this window.
You can close it only globaly in Windows Task Manager.
And reopen this task with "Console 1 On-Screen display" in Windows Start Menu.

 

Last edited: Jan 10, 2021

TLDR; out of interest, can you use Console 1 hardware with the latest RtooR releases?

 

that softube hardware is really good, btw.

 

That also worked with Fl STUDIO.

Thank You!!!

 

All Cs1 Extensions Work Fine in @Cherry Method

 

cherry Method
In Studio One
Manually Save as store Preset one by one Cherry method to Studio One Presets
Workout>>>
put Vst2 version Of Console 1in first Channel
Then put Vst3 in other Channel
Next Reopen Vst2 instance Click <change name> now You can see the oBs(here:dont click Enter or Cancel in this step)
Then Reclick the vst 3 Channel
Now you can use all extension as Studio One Preset