Search the Community
Showing results for tags 'transport'.
Found 3 results
Hi there, I just purchased a new Nektar Impact LX49+ MIDI controller to use with my Cakewalk by Bandlab DAW. Nektar works as a basic MIDI instrument (I can play my VST synths and occasionally map the knobs successfully depending on the VSTi) However when I try to use the DAW Transport controls (Play/Stop etc.) or use the sliders to control the volume in Cakewalk’s mixer, I have absolutely no response. I’ve downloaded all the necessary setup files for Cakewalk SONAR via the Nektar Impact website as a registered user and installed on my Windows 10 machine, and still nothing. I’ve also set up the Nektar Impact correctly as an ACT Controller in Cakewalk settings. Has anyone with a Nektar Impact been able to successfully get it ‘talking’ to Cakewalk and use it to control the DAW transport and volume sliders? It’s been very discouraging thusfar. Really appreciate your time and assistance! cheers
Hello i succesfully connect Cakewalk to Jack_router. My Cakewalk can receive inputs from Jack_router and send ouputs to Jack_router. But i don't find how to trigger Cakewalk Transport when launching Transport in Jack (via Qjackctl). Does anybody have an idea on how to do this? I only see that is possible to trigger Cakewalk with MMC but it's not what i am looking for for my project. Thanks.
Hey all, this is Andy. Please allow for a hopefully simple question regarding automation of real time controls via the AZ Controller control surface. First of all, I was able to setup remote control for CC MIDI messages and SysEx messages (master fader) for a CME UF6 master keyboard. I am struggling with transport control, because the SysEx commands seem to be filtered out through CbB. Internally generated MIDI RT events work as expected. A MIDI monitor shows that the commands are sent by the keyboard and received through the interface. In general one can allow SysEx data to be recorded through the CbB preferences (Edit > Preferences > MIDI - Playback and Recording > Record / System Exclusive). This setting is important for the control surface (AZ Controller) to be able to listen to SysEx events. For some reason however this does not include real time SysEx events (such events that do not start with F0). What could be the reason that events like "Play" (FA 00 00*) and "Stop" (FC 00 00*) are not passed through to the AZ Controller control surface? Is there another setting in CbB that filters these events out? Your help would be much appreciated! Update after further research * MIDI Monitor may display the bytes of the MMC real time messages in a different order than these are sent, and may also omit an information (Device ID). The displayed command codes FA/FC seem to be non standard. Because of this it is now no longer clear to me if the sent messages are compatible to AZ Controller's MIDI RT entries. It is however confirmed that CbB understands the real time messages in MMC sync mode (set as slave device with the keyboard as master).