That’s right.
You know I get so used to my Artist controller being able to make custom key commands I forget that you can’t do the same with the Cubase macro set.
I have a custom button my MC that I have named “toggle” that is programmed with Control+Tab, that cycles focus through all open windows.
I don’t understand this. How do you have an assignable button that you nave named “toggle” on your MC to cycle focus through all open windows? Alt+tab is not listed under Cubase key commands therefore to my knowledge it’s not possible to assign it to your MC.
What am I missing here? (I don’t use a MC, but I think the Icon uses MC protocol.)
MC as in Artist MC Control.
You can program windows key commands on the Artist MC for the touchscreen, (not just Cubase key commands) , you can name it what you want. I have this button in several locations on my custom touch screens to toggle window focus.
You can also program any combination of windows key commands, cubase commands and Eucon commands and even string them together for powerful macros.
For OSX that might be true, for Windows it’s a different story because the plugin editors hide behind the mix console when you focus on the mix console. Really annoying!
I agree but there are a lot of great features in the new console, enough for me to deal with the gymnastics involved.
I’m probably gaining more in terms of desk efficiency than I’m losing by the navigation.
But you would think that with all the squeezing and contracting we can do it wouldn’t be an issue, I guess that’s what they thought, but when you get into a mixer that has the channels squashed into an accordion, that, yeah asking too much.
But if no moron BUYS updates/new versions, the developers would have to work for free. Working for free doesn’t provide an incentive to fix major bugs.
So we should BUY updates and should NOT BUY updates. Outch! Help!
You talked about bug fixing for free, not about the non-controversial fact that we all paid for C7 / C7.5.
You implicitly stated the proposition: If one wants to get bugs fixed, one should increase the pressure by not buying any more products or updates from Steinberg. I personally think this is not constructive. Eventually, a company will not fix bugs but get bankrupt if no one pays for their products. Besides all this: They did fix bugs for free already.
Of course I would be happy to get a bug free product right from the start. Of course I know that this is only possible in utopia land.
Additionally, you called everyone a moron, who pays for new versions and updates. I paid for C7.
I don’t know if you can do the following on Windows, but what I do is enlarge the mix console to fill my screen (but not “full screen”) and set plug-in windows to “always on top”.
I dont mind paying for little bug fixes… but paying for HUGE bug fixes that should’nt have been there in the first place when I bought C7 (yes I’m a moron too) that’s what I have a problem with. All of us have been beta testers for version 7. And now as a thank you (and still not fixed) we can buy version 7.5.
But like I said who gives a beep, we are all going to enjoy the new colour scheme in version 8!!! Yeaaaaaaaaaaaahhhhhhhhh
You probably use 1 monitor. Try to have a lot of plugins open on 3 monitors. And then suddenly poof they are all gone, and you have to click to get EACH plugin back on the screen again. Do this 50 times a day…
There are bugs, and then there are things that simply are not well thought out or diligently tested in house by real users. I can appreciate bug testing, I did a lil HTML back in the day. But error, quality testing, workflow… hard to have an excuse.