I bought Loupedeck CT and want to use it in combination with CB13 pro. I can’t get the dial for scrolling working. I see in mac texteditor that the loupdeck is sending - and+ when scrolling dial, but when i use it with CB when i turn the dial i get sound from speaker that looks if it is a wrong command for CB. When i use an external numpad and use - and + cubase cursor is scrolling.
Any one who works with Loupedeck and Cubase, have some suggestions??
Kind Regards Leon
Maybe the assignments you see are not for the numeric +/- (i.e. those seen in the numeric side of the keyboard) but for the ones we see on the qwerty side of the keyboard? I think that these are not assigned to commands by default and you can give a try assigning them to Forward/Rewind.
Hi,
This device is sending dedicated commands, based on the Application on top, if I’m not mistaken. So it seems other data if you use TextEdit or Cubase.
Hello,
Is there someone who uses Loupedeck in combination with mac? I am wondering if this combination works.
Kind Regards Leon
Hi, after lot of testing and contact with Loupedeck support, we found out that Loupedeck cubase plugin does not work as should be. Loupedeck software department is now looking what is wrong…
Leon
Loupedecks work great with Cubase - been running a CT for a few years now!
I’m using a custom mix of commands - some from the built in collections and some self programmed.
You’re gonna need to use a custom key command set in Cubase. A bug in Cubase means the editor never re-loads the current key set so you need to be careful when building it that you’re updating the correct set!
And the Loupedeck software couldn’t be more un-intuitive if it tried, it takes a lot to get your head around it.
But it all works well.
Cool! I’ve received a loupedeck ct today, and I saw that you can also configure it to send midi messages. This can be a solution to some issues, if you engage it with midi remote.
Hi,
Do you use windows or MAC?
I got mail from Loupedeck today that their software team is working for a cubase plugin update. When i want to give big Loupedeck dial FF and REW transport keycommands, nothing happens with cubase.When i do the same keycommands with streamdeck this works perfect in Cubase.
Both.
Sorry, I haven’t yet got into setting it up inside Cubase. The setup I’m going to prepare involves mostly MIDI. This means, that no matter how Mac (I think you’re referring to this OS) treats shortcuts now or in the future, I will be, at least so I hope, at the safe side of MIDI.
Hi,
With Midi remote you can not make horizontal cursor scrolling, and with midi remote all buttons have toggle mode. I let you know when loupdeck / steinberg plugin is correctly working.
By using the assistant, this is correct. I’m using scripting so it works as expected. Just to be clear, I didn’t buy this device, a friend sent it to me, to program it for using with Cubase in the alternative way of the MIDI Remote.
Not sure I understand this. Even when using the assistant, you can setup your buttons to either toggle or gate.
But yeah, using shortcuts is the most straight forward thing to do, so you really should wait for the fix, especially if you don’t plan to use the 6 knobs for altering plugin parameters etc, in the DAW.
I just tried this and you are correct, something is wrong somewhere - you can see the rewind and forward buttons lighting up in the transport section but flickering, not steadily lit like when holding down the + or - buttons on the number keypad.
I found out that when i use nudge cursor left and nudge cursor right in combination with the loupedeck dial everything works ok. You have also set GRID# to adapt to zoom.
The loupedeck software department made aready 3 updates and problems with loupedeck software are getting worse and worse…I think streamdeck would be a better choice.
Hi there,
this has also been a point of much frustration for me with several of my non-midi style controllers such as the colour play and the Logitech MX console dial pad.
The other day I had a breakthrough however when I just simply started using it without thinking ( unmapped, no controller etc) All these devices I’m talking about are seen by the Mac as a mouse, that should be the first thing to point out.,
Now, it seems if you hover your mouse over the top of any thing that moves in Cubase and then turn the wheel on that device it will move it. It’s like an automatic A.I. knob and if you think about it that’s what the scroll wheel on your mouse does so if it’s not a scroll wheel or if Mac doesn’t think it’s a scroll wheel, make sure it does and then
give it a go. You’ll see what I mean. It’s fantastic now I don’t have to. I’ve abandoned all plans I had for mapping and all these other sorts of complicated fixes for just simply using it as a Mac device
like any other.
.
My Logitech console doe# that too, have you got the trigger as a hold down nor a press?