@Thurisaz.
StudioOne has a ton of presets in the Theme area to change the colors as you say.
With Cubase you have to dink around with it to get it close to what you want.
I have no need to have Cubase look like Protools here if you will
What presets. I am not seeing any here.
All I see is one slider a couple of other things on that settings page.
Studio One has those NOT Cubase. That was my point. S1 gives you a bunch of presets even though they are just color and contrast variations
Iām talking about Studio One 5 Professional. I have that, too.
Cubase has fairly extensive color customization in the settings. I am aware of thatā¦
S1 has HUE, Contrast and Luminance. What more do you need to get it there?
Works fine for me. Cubase color section is lacking ANY starting point for a preset is my point. I have and USE both apps here. Its not an issue unless you want it to be one.
See that box that says load PRESET???
Will be great to have RENDER IN PLACE with Side Chain
- Multi-core CPU optimization. Find a way where if a long signal chain does not have to rely on 1 core, rendering the rest of the cores useless.
- Ability to link parameters in any VST or effect to automate them together seamlessly. Quick control is fine for people who use external controllers, but we need a vst to do this that is seperate.
- Ability to upsample any factory cubase vst or effect.
- Upgrade or introduce a sampler and step sequencer similar to fruity loops. This would absolutely crush it.
- Ability to select any effect and upsample it.
- Ability to produce a track in 48khz and export it at a higher sample rate (like convert the files and export the higher quality sounds, not just make a higher sample rate file).
- Ability to change the tune of an entire project (ie, A @ 432)
- Create a āmix engineer modeā which creates large latency but also allows to take further advantage of modern cpus. Basically improve asio guard and enhance it.
- Optimize cubase to be more efficient with cpus (same as 1).
.
Cubas has better granular configuration of colors in settings. Complaining because of the lack of presets is curious. What if you donāt like the presets? Digital Performer has tons of presets, but 90% of them are so awful they mind as well not be there.
I donāt need presets. I need better granular control, not just some Luminance/Contrast/Saturation sliders.
And the DAW should just ship with decent settings for Light and Dark Mode, anyways.
-
Agreed, DAW should ship with decent settings for Light and Dark Mode. This reminds me of the 200 or so chitty presets you get on a guitar modeler.
-
The preset is a good starting point for editing it to your liking which is all I need here.
Im not editing VIDEO with Cubase here. Not everyone wants to dink around with granular settings all day. Most of us want to do music. This is why I HATE Reaper. -
DP sucks all the way around, itās horrid IMO let alone viewable.
-
You should not use S1 do to these color palette limitations you feel are stopping you from making great music.
-
The Preset is a starting point, but there isnāt enough wiggle room for editing it to suit you. This is why granular settings are good. You can share Cubase GUI settings, as well. Cubase is generally better in this area. Cubase is not a video editor. No one edits video with Cubase⦠Weird statementā¦
Dark GUIs became popular because of graphics design and Video Editing/Motion Graphics/VFX Software that people often use in darker rooms so that ambient lighting doesnāt bias color perception. Every other software type jumped on the bandwagon because āDark Modeā became a fad.
-
If DP11 werenāt so buggy with VST Plug-ins and ASIO drivers on Windows, Iād have dropped Cubase for it with the quickness. I actually bought a cross grade, but ended up getting a refund. The issues with ASIO (which I fixed by getting a new interface - I liked it that much) and VST plug-ins were really the only showstoppers. Itās totally viewable. The only things that seemed problematic were the stock virtual instruments that I would pretty much never use, anywaysā¦
-
This sentence makes literally no sense whatsoever. Not sure how to respond to that.
I only use Studio One as a backup on my laptop when traveling, when I donāt feel like bringing a dongle with me. Once Cubase 12 releases, itās getting deleted. Some of the things I expected to be there, but arenāt, surprised me; as I just didnāt expect a v5 DAW to be missing some of that stuff (MIDI List Editor, Per-Note Channel Assignment, Ability to Round Trip with an External Audio Editor, etc.).
The only reason why Iām willing to deal with that is because it was always intended to be an ephemeral solution. I donāt actually use it āthat much,ā especially considering the whole COVID situation over the past two yearsā¦
-
Makes perfect sense. Donāt be daft on purpose
I donāt need all the extra stuff to make the DAW look how I want it color, shade, gradients etc. You may, I donāt. Im not that picky. Dark mode sucks IMO and I agree that this convention follows the Video NLEās
-
The font size is so small in DP it hurts my brain. Ive tried the DEMO here
-
You act as if S1 is limiting you due to the lack of color palette/gradients/ granular things etc.
IF it bothers you that bad you should NOT use it . Simple. Thatās what Im saying. I have no issue with it. I simply adjust a couple things and off I go to make that masterpiece no one will buy and Spotify gives .07 for a play. (Thank you record labels)
I agree, S1 NEEDS to have a MIDI List Editor. This seems like a simple thing to add but NO, we NEED that SHOW PAGE that no one wanted.
I use REAPER here when doing live recordings due to the dongle BS with Cubase. It is more stable for live than S1 IMO. Once C12 is released I will simply wait a year till all the license mess that will happen gets fixed.
Cubase has way more bells and whistle and we all know that in comparison to S1. Im DAW agnostic here. I dig them both
My ephemeral solution is to move on from this thread. Carry on
You can make a midi track and send midi from that track to any plugin that accepts it, you can also assign automation this way. And then draw in what you want in the midi track. When midi 2.0 comes along, (presumably in 12), this will have much greater granularity.
There is also this.
This works: Blue Cat's Remote Control - virtual MIDI Control Surface (VST, AU, VST3, AAX)
This company has some tools I have tried recently because of a suggestion on another thread. The Connector worked, but there were issues outside of the tool itself. Havenāt tried the remote control, but it looks like a possible solution for you.
While their are algorithms to do something like this, in much the same way as anti-aliasing. Upscaling can not do so without introducing transients that were not desired. This would be very advanced, as each formant structure would have to be filled-in in a different way. There are multiple points of NPC in the process of performing the transformation. (multiple times when it would be necessary for a human to make a decision). If automated, what would result would likely sound worse than if you just added in the extra bits in between generically, which you can already do.
Some use of AI may advance this in the future.
Hello @Matthias_Quellmann,
Great to finally see a serious amount of work in the wright direction! Many features that had to be in Cubase a decade, or more, ago are in version 12.
Thank you very much for the hard work!
Still two things that I (and probably many others) find very important are still not there:
- Event Volume Envelope Line at 0dB it should be at the center of the Event, just like the Clip Gain in Pro Tools (with an option to show and hide it)
- A way to invoke Automations directly over the Event (again a Pro Tools feature). This will save vertical screen space in case we need to keep more Automation Lanes opened.
⦠and please, think about an advanced tool like Beat Detective! It keeps everything quantizing , crossfading, event slicing, hitpoint creating⦠etc, in one place. We really miss such powerful tool in Cubase Pro. In Cubase most of these features are separate and placed in different places.
I hope you would think about the thing Iāve mentioned in this comment!
Thank you in advance!
Best wishes,
Thurisaz
Font size in DP was made adjustable in DP11. The only small fonts are on some of the stock VST Instruments, and you will probably never want to use the affected ones, anyways.
Iāve run this DAW on my system. You speak as if you havenāt bothered to run a trial version of itā¦
Contrary to popular belief, things can and often do change.
S1ās configuration in this department is completely inadequate for me.
In any case, Iāve upgraded to Cubase 12 and deleted S1 from my systems. It is no longer needed, so I wonāt torture myself with it any longer. It was always only a temporary solution, but frankly I ended up not even using it that much. Iād just use my old copy of Samplitude Pro X4 Suite instead, due to some of the surprising feature ommissions in Studio One that had fairly massive effect on workflow (or ability to perform some tasks efficiently).
Cubase 12 doesnāt have a dongle. Weāve known this was coming for months. Not sure why you were still talking about it.
Bye. (Interesting use of the word āephemeral,ā btwā¦)