Jump to content

Search the Community

Showing results for tags 'control surface'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News & Announcements
    • Product Release Info
    • Frequently Asked Questions
  • Cakewalk Products
    • Cakewalk by BandLab
    • Instruments & Effects
    • Feedback Loop
  • Community
    • Tutorials
    • Songs
    • UI Themes
    • The Coffee House v2.0

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 6 results

  1. I wanted something to do during the lockdown so I started looking at the Cakewalk control surface SDK. I own a Behringer X-Touch Compact and only meant to put a few tweaks in the Mackie Control plug-in specifically for it, but then mission creep took over in a big way and I ended up with something that’s more like a separate plug-in in its own right. I also wrote a program called XTCview, which is an enhanced version of BCFview (the program that went with the older BCF2000 control surface to emulate the Mackie Control’s display) because using a control surface without a display is pretty challenging once you get into plug-ins and all the various shift states. If anyone’s interested, I’ve attached an introduction and an almost-completed quick reference guide. I’m really happy with the way it’s turned out, but like most things it’s a question of balancing many different conflicting requirements so you may not be so happy with my choices. Let me know if you might have considered using it but for something that really annoys you because at this stage I might still be open to suggestions. And as you’ll see, there are still some open slots in the M1/M2 shift matrix on page 2 of the guide so I’m taking requests for those too. I’ve tested with Cakewalk by BandLab on Windows 7/64 and 10/64 and Sonar Platinum on Windows 7/64. I have also built 32-bit versions but have not been able to test them on a 32-bit OS. I will open-source it eventually, but for now if anyone wants the plug-in with XTCview and/or the source code then just ask and I’ll gladly send it to you once I’ve finished up a few final things and I’m completely satisfied with the way it’s working (probably a week or so). I’m also planning on doing a complete revision of the help file but that will have to come later. About me: I’m a retired software professional with 35 years of experience in C/C++, although I did spend the later years of my career working more with C# so my C/Win32 is a bit rusty and that probably shows in my code. Introduction to the Behringer X-Touch Compact Control Surface Plug-In.pdf Quick Reference Guide.pdf
  2. A few weeks back, before we had this shiny new forum, I posted over on the old Cakewalk forum asking if anyone could tell me how well an Icon QCon Pro X control surface would work with CbB. I got a good number of helpful responses, some of which recommended the Behringer XTouch. Someone also mentioned the Icon QCon Pro G2, which unlike the Pro X, officially supports CbB (though they still call it Sonar on the Icon website). Long story short, I ended up getting a G2, and wanted to post back on how well it's been working, as no one in the previous discussion had tried one. And... it works very well! It even allows navigation into the FX bins to any plug-in, which I call out specifically because I think I remember reading that there was a point in the recent past where one could not navigate past the first plug-in with the MCU and/or XTouch. In fact, the G2 has so far successfully controlled every parameter of every plug-in I’ve tried it with (about 6 or 7 plugs so far). As I've never used an MCU or an XTouch (or any dedicated surface), and the G2 didn’t come with any DAW-specific documentation (and I couldn’t find any online for using it with CbB), I had to go through the MCU .chm help file (found in the same directory as the Mackie Control DLL) to figure out how to use everything. This was difficult because the G2 has different button names as well as a few differences in available buttons as compared to the MCU. These differences meant that, in some cases, I was reduced to just stabbing random buttons to see if I could get the G2 to do something described in the help file. But I’ve now gone through the whole help file and tried 99% of the functionality described therein. The results? The G2 can do just about everything the original MCU can do. I found only a handful of functions referenced in the help that either don’t work on the G2 or work slightly differently, though some of that may be due to me not finding the right button combo, bugs in CbB or the Mackie Control DLL, or to changes in CbB since the help file was written (examples of that last category are: the duplicate track function opens the Duplicate dialog instead of directly duplicating a track and one of the hide track functions opens the Track Manager). Really, though, all the discrepancies I found were quite minor IMO. Anyway, because it took so long to figure out the G2’s functionality, I decided to make a spreadsheet that includes most the functions I tested (I left most of the really obvious ones out, and didn’t bother mussing much with entering digits into text fields… because that’s what keyboards are for) and the G2 button combos required to execute them, as well as a list of the functions that didn’t work. I'm going to post it here in case it may help someone with a new G2 (or in case anyone is curious). Before I do that – and keeping in mind that I’ve never used an MCU – here are the biggest downsides of the G2 as compared to the MCU (and I think the XTouch would not suffer from these, but this is based only on viewing photos of it). There is no 2-character "Assignment" display. On the MCU (and, from pictures, on the XTouch as well), this tells you what state the device is in. However, this isn’t that big a deal, as the G2 indicates some of the info that would otherwise be displayed on the Assignment display in other ways (e.g. via lighted buttons or by what’s displayed on the scribble strip). Still, there are a few states that are maybe not obvious, which can lead you to think you're in a state that you're not. But I've not been much hampered by this. Back on the MCU (and, I assume, on the XTouch) one could easily switch with a single button whether the channel/bank change buttons would change the track/bus assignments or instead change the parameters assigned to the encoders (or, if working in the FX bin, the plug-in whose parameters are available for assignment). Further, I think which of those states you were in was clearly indicated by the Assignment display or by an LED or button backlight. On the G2, though, you must be in a toggled shift mode (Layer 2) and then hit a completely non-obvious button to toggle between these two sets of channel/bank change button functionality. The button differences aren't the problem, though - the real issue comes from the fact that there is zero indication of which mode you’re in until you try to change the channel assignments, only to have the parameter assignments change instead, or vice versa. With that said, as soon as it happens you know due to the scribble strip changing or fader movement, at which point you can easily recover by hitting the opposite bank/channel change button to get back to where you were. On the positive side, here is an important advantage that I think the G2 has over the XTouch: the scribble strip info is presented on a large, upright, bright and easy-to-read display, while the XTouch's strips are claimed to be, per several reviews I read, hard to read (they appear to be small and are laid flat on the device such that they are far from perpendicular to your eyes). This was one of the main reasons I went for the G2 over the XTouch (again, though, keep in mind I’ve never tried the XTouch). Okay, that’s it – I hope the spreadsheet* is useful to someone. Also, if anyone is thinking of getting one of these, I'd be happy to answer some questions. Oh, I should also state that I’m using a Mackie DLL modded and compiled by msmcleod; to get it, go to the post I linked to in the first paragraph and search for his username – he gave a link to the DLL in response to my OP. I think you can also get the compiled DLL on github, and I think I saw him post here on the new forums that he’s made further changes (though that might be a different user). *Note that the spreadsheet is something I threw together quickly, and I’ve not yet proofread it or edited it for brevity/clarity (and it could use some of the latter). Icon QCon G2 Pro Control Map3.xlsx
  3. Good day Looking for some insight. I'm using my Touchmix as an input / output device. Multitrack recording and mix down. Cakewalk see's 16 odd ch# inputs 1L/1R/Stereo; 3L/3R etc. Typical with Sonar/Cakewalk since mutli channel input devices were incarnated. The even channels are the R inputs of the odd number channels. Whats odd is it only presents 16 odd ch mono outputs. a bit of a pain with the limited control surface real estate of the touchmix to use every other slider control. Other DAW software sees the Touchmix as CH 1-16 inputs and outputs. So this seems a behavior Cakewalk and not driver related. Thoughts ? Cakewalk team .. REALLY appreciate you keeping the product alive and continuing development. Would you have a look at this ???
  4. 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).
  5. I have an Alesis DM-10X e-drum set set connected to my DAW for recording drum parts in KbB via Addictive Drums 2. The physical connection is a USB cable from the DM10 module to a USB port on my computer. I have the MD10 module set to send MIDI data in omni mode. Everything has always worked perfectly with the DM10 module. No problems at all. However, I recently got a Behringer X-Touch Universal Control Surface. It too connects to my computer via USB. When doing the initial setup, there did not seem to be any way to specify a MIDI channel, or even omni mode, for the X-Touch. When I was setting up the X-Touch, the DM10 module was off and the X-Touch worked perfectly. But when I turned on the DM10 module, the X-touch disconnected from the DAW and became unresponsive. Does anyone have any ideas why the two USB MIDI devices are conflicting, or know how to resolve the issue? I read somewhere that the X-touch was incompatible with USB 3, so I move it to a USB 2.0 port and still have the same problem. Could it be something as simple as a bad MIDI cable? Or could it be software related in some way, maybe some kind of MIDI conflict? BTW, I could connect the X-touch using an Ethernet connection, but I would rather not have an active NIC port on my DAW if I can avoid that. If possible, I would prefer to have the two USB MIDI devices work happily together. any suggestions would be greatly appreciated. --Jay
  6. 😎 Please enjoy this video tutorial about Automation and Control Surfaces within Cakewalk by BandLab. [tube]
×
×
  • Create New...