Don't remove Generic Remote, instead improve it? Or Improve MIDI-Remote to have same function

Cubase
, , ,
21

Is it possible to use both GR and MIDI Remote simultaneously?

I want to create a jog wheel control in TouchOSC

Would this be better done in MR or GR?

There was a thread talking about it in GR that sounded difficult, but it’s locked now.

assigning an endless rotary encoder to jog wheel - Cubase - Steinberg Forums

22

I know i’ll definitely not upgrade to the first Cubase version that completely removes Generic Remote in the future…

23

Before biting the bullet and learning how to program the MIDI Remote API, I ran the Generic Remote in parallel with the MiDI Remote for quite a long time.

see my reply in your other thread.

24

Cool good to know thanks.

25

I know i’ll definitely not upgrade to the first Cubase version that completely removes Generic Remote in the future…

Hopefully if they do that, they create 1:1 functionality and a way for that new functionality in MIDI Remote to just import and convert Generic Remote .xml files…

I don’t think it would be that hard to script… Generic Remote is a fairly simple point to point entity. AI could probably come up with a conversion script. (Calling back @Jochen_Trappe on this point, no need to reply, just saying hi again)

26

While I agree with you, I highly doubt the GR is going to vanish anytime soon. I think that wording, written since the creation of the Midi Remote, was to strongly point users to use the Midi Remote.

27

+1

I use MIDI remotes and even write my own custom scripts, but I still use generic remotes.

My biggest issue with MIDI remotes is that you are forced to assign a controller object as a middle man in order to control a parameter. This is not necessary when working with touchscreen solutions designed for advanced MIDI editing and causes many issues:

  • Certain commands are less responsive. I tried converting some generic remotes to MIDI remotes when MIDI remotes were first introduced and certain commands responded noticeably slower than via generic remotes. This makes some of my touchscreen functions unusable.
  • Session loading times are longer because MIDI remotes are much larger in size due to all the additional graphical information.
  • It greatly complicates the creation and maintenance of very complex remotes with hundreds of assignments.

If Steinberg really intends to discontinue generic remotes, they must ensure that:

  • Users can make assignments without creating objects.
  • All generic remote functions are available as MIDI remote functions.
  • The response is equal or faster than using generic remote.

If not possible, some users like myself will be royally screwed and forced to stick with older versions of Cubase, and Steinberg will end up losing money and damage their reputation.

I think it would be much safer to preserve generic remotes and for Steinberg to think of MIDI remotes not as a substitute for generic remotes, but a complimentary feature: MIDI remotes for simple physical controllers, generic remotes for complex touchscreen controllers.

28

Great points thanks for chiming in, some things I didn’t know about as well.

As long as Generic Remote is improved… It’s pretty painful to work in at the moment.

  • Popup menu instead of command/target browser.
  • Popup menus are too small/non-resizable.
  • Generic Remote display box is too small.
  • Being in Studio Setup window locks user out of Cubase which means they can’t test things as they assign them, which means they have to close Studio Setup window to test, then re-open it to work further but losing their place in the Generic Remote list.

It’s quite a conundrum for us users doing this type of work being stuck between an old abandoned Generic Remote trying to utilize it for complex modern touchscreen workflows, and the MIDI Remote with a more modern UI/UX but lacks the needed amenities of Generic Remote… Neither really feel like the lesser of two evils.

Hopefully this thread puts things into motion for development.

Would it be that difficult to create a non-graphical device in MR?

@Tublitha

Could you be more specific about which commands/types were noticeably slower and not useable via Touchscreen?

29

It’s been a while but I think the transport controls were causing trouble with some of my touchscreen functions because of slow response.

I remember doing a test but I’m not sure exactly what I did. I probably mapped a bidirectional function like track mute to 2 different buttons on my touchscreen using the GR & MR, then toggled mute on/off in Cubase and noticed the MR assigned button was responding noticeably slower.

I agree that the generic remote interface is horribly outdated and hopefully they’ll change direction and resume development, I wouldn’t hold my breath though.

In the meantime, consider using a script editor (Notepad++) to edit your generic remotes. It will allow you to:

  • Copy/paste/duplicate multiple lines.
  • Use the search function to find entries faster.
  • Use the replace function to edit multiple entries (Ex: Change MIDI channel).
  • Reorder lines easily.
30

Good tip, thanks

31

Amazing, thanks for chiming in! I’m not a coder myself but I really appreciate your scripting insights. Either way, here’s to hoping Steinberg keeps GR for a long foreseeable future, even if they’re not interested in updating it.

32

Maybe if we all hope at the same time?