Zoom In/Out, Scroll In/Out using single controller...

[Captain Caveman]

Hi

Just a tip of the day here. Seeing as the Generic Remote doesn't have seperate functions available for In and Outs of the Zoom and Scroll commands etc, the workaround is.....

1. Program your endless rotaries on your controller to use RPN Inc/Dec (151), since NRPN isn't recognised, program them all for RPN, but on different MIDI channels.

2. In Devices/Device Setup/Generic Remote, MIDI Learn (eg) Zoom In and rotate counterclockwise and Out clockwise.

3. Repeat as necessary.

Viola, up to 16 dual functioning endless rotaries.

:eek:

[Animus]

Cool trick!

[Captain Caveman]

If there was such a thing as Scroll In/Out it certainly would be!! I'll edit the post to not bring down the tone of the forum.

:)

[messianic]

This is what I'd like to do with my Fader Port pan-pot controller, except it is seen as controller "unknown".

[Captain Caveman]

It has let me change the title, but it still appears as In/Out in the list of threads.

Oh well, that's the bug reported - I'll start a timer now.....

0 years 0 months 0 weeks 0 days 0 hours 0 minutes 1 second

since "thread list and topic title edit sync bug" reported.

:D

[Captain Caveman]

This is what I'd like to do with my Fader Port pan-pot controller, except it is seen as controller "unknown".

I have just read the Fader Port manual, and it doesn't mention the ability to change the functions of stuff that aren't the user buttons.

If you really wanted to do this, you could use MIDI OX to convert the pan controller to RPN and use a MIDI Yoke input for the controller instead of the Presonus one.

Either that, or you could use a button for Zoom to Selection and one to trigger a macro that Selects All then Zoom to Selection so that you can do the moving about with the swipe of a mouse and the press of a button.

I've set up a couple of keycommands for these, the only PITA being that the original small track sizes are sometimes lost (seems to be mainly with the track that was last touched/had an event selected in it).

[Animus]

It has let me change the title, but it still appears as In/Out in the list of threads.

Oh well, that's the bug reported - I'll start a timer now.....

0 years 0 months 0 weeks 0 days 0 hours 0 minutes 1 second

since "thread list and topic title edit sync bug" reported.

:D

Maybe it was a caching issue? it all works here! Must be your machine. lol :-)

[messianic]

Thanks for that advice.

All the buttons and controls send information which is good I can see that in MIDI-OX and I also was able to change the data from pitch bend to something else.

All of the controls are recognised by MIDI OX which kind of leaves me wondering why Cubase can't see what's going on. The Pan control comes up as a Pitch Wheel which I don't fully grasp as I thought they weren't endless controls.

My understanding of MIDI Yoke is that it is a kernel mode driver. I will look into all this some more and will report back my findings.

Thanks for your information and for letting me post in your thread.

Best regards

P.S. I've uploaded the XML file (in txt format) which I produced from assigning whatever controllers are allowed in cubase bar the pan control. I am still at a loss as to why it is recognised by MIDI OX but not cubase, anyone have any ideas?

[Captain Caveman]

.... I am still at a loss as to why it is recognised by MIDI OX but not cubase, anyone have any ideas?

That'll probably just be because Cubase filters it out in the Generic Remote section to avoid confusing us simpletons and having us deleting stuff via the shaky pitch bend wheel of our keyboards. If Presonus can get it to work though then it must be allowed for manufacturers.

Having said that, it could be quite handy....



Pitch Bend
The pitch bend wheel is also a continuous controller on many MIDI keyboards. Possibly, the Pitch Bend message is in its own category because it is something likely to be done frequently. The two bytes of the pitch bend message form a 14 bit number, 0 to 16383. The value 8192 (sent, LSB first, as 0x00 0x40), is centered, or "no pitch bend." The value 0 (0x00 0x00) means, "bend as low as possible," and, similarly, 16383 (0x7F 0x7F) is to "bend as high as possible." The exact range of the pitch bend is specific to the synthesizer.

So you could forget about RNP and just re-assign value 0 - 62 to one controller and 66 - 127 (MIDI OX works from 0-127 and it's probably best to leave a buffer so that if the pan knob is sensitive it won't trigger commands) to another and Cubase will recognise either direction of the Pan as seperate commands.

Hope this helps.

:)

[messianic]

I will try all this, some very interesting information there.

I've now gone and mapped up some MIDI drum triggers via a trigger converter (DTXPlorer) and put them into the free version of BFD2 which was quite fun however my current interface (GO-44) was pretty poor on playback, with clicks and pops but it is promising because I was able to learn something and this MIDI OX program is interesting as well.

Even though I watched the tutorial at bfd.com it was only when I looked at the information coming through that I realised some things about MIDI in general, so I will need to spend more time on this in order to understand properly.

Your last quote about the pitch wheel, I will need to look at it some more in MIDI ox and report back again.

Thanks very much for your discussion and information.

[RSE]

This is what I'd like to do with my Fader Port pan-pot controller, except it is seen as controller "unknown".

Here's another one for programming buttons, and also for using different menu commands (which are set automatically to 'push button' mode by Cubendo):

On the controller side:
Assign a controller to a button (e.g. CC#1), choose toggle mode with specific minimum and maximum values (e.g. val 1, 127, or e.g. val 63, 64).

On the Generic Remote side:
Add two controllers (top pane):

1. A JL-Cooper controller with CC# = the max value of the button (i.e. 127), and with max value = the max value of the button (i.e. 127).

2. A standard controller (e.g. CC#1) with max value = the MINIMUM value of the button (i.e. 1).

...

********************************************
Make sure that the JL-Cooper controller comes first (upper line), before the standard controller.
********************************************

Assign (bottom pane) different menu commands for the two controllers.

That's it.

:-)

---

It works because:

JL-Cooper controllers are 'reversed', they switch the value and CC# bytes - this way the GR is expecting a 'reversed' CC#127.

The controller's 'button on' command transmits max. value (e.g. CC#1 val.127), so the first ('upper' JL-Cooper) GR controller responds, because for JL-Cooper controllers Val(127) means CC#127 and CC#1 means max value of 1.

Obviously, the standard controller would respond too but at least on my system (N4) it's overridden by the 'first in line' (the 'upper' JL-Cooper) controller.

The controller's 'button off' command transmits min. value (e.g. CC#1 val.1), so the JL-Cooper controller would not respond this time, since it's waiting for a CC#127 command, not a CC#1 one.

However the second ('standard') controller would respond to the standard command (i.e. CC#1) with 'push button on', since Val(1) is its maximum value.

---

Programming the JL-Cooper controller with CC# = the MINIMUM value of the button would reverse the GR response (i.e. the JL-Cooper controller now responds to 'button off', the standard controller now responds to 'button on').

128 buttons per midi channel are availeable for this (128 CC#s with specific max and min values).

On my system (N4, BCR2000) I programmed a button to operate 'Zoom Selected' and 'Undo Zoom' -

I'd love to hear more useful ideas.

---

Btw:



Program your endless rotaries on your controller to use RPN Inc/Dec (151), since NRPN isn't recognized

NRPN is recognized by the GR, but not by the (buggy, STILL buggy...) GR export and learn commands.

You can get NRPN controllers if you edit the XML file manually, and change the specific controller's 'flags' value to 19.

...

RSE

[honeydont]

Hi

Just a tip of the day here. Seeing as the Generic Remote doesn't have seperate functions available for In and Outs of the Zoom and Scroll commands etc, the workaround is.....

1. Program your endless rotaries on your controller to use RPN Inc/Dec (151), since NRPN isn't recognised, program them all for RPN, but on different MIDI channels.

2. In Devices/Device Setup/Generic Remote, MIDI Learn (eg) Zoom In and rotate counterclockwise and Out clockwise.

3. Repeat as necessary.

Great f*@ck1ng tip! I was struggling for months with my axiom 49, using one rotary to zoom in and another one to zoom out! Thanks a lot!:D

[Stevie]

I'd be happy if it was just possible to zoom with the mousewheel, as in every other DAW, too :(

[ROCKINROG]

I'd be happy if it was just possible to zoom with the mousewheel, as in every other DAW, too :(

I know eh. It really is quite pathetic. Hello Steinberg...is anybody home:smash: