User 905133

5.11.1.6049 now includes support for Pigments 6 (among other changes). This means we can access the Modal synth engine, including editing presets that use the Modal engine. Use ASC to update.

Since I haven't played with Cakewalk Next in a while, I am not sure I can help other than to suggest contacting support for Cakewalk Next if what you want is not covered in the manual or the Help Webpages. Moreover, when I read your post I thought it was not clear what you were trying to do, and I thought maybe someone in the User Community who uses Next might be able to help if you were clear about what you are trying to do. So far as I can tell, you have some pads and knobs somewhere and you seem to want to be able to assign them to specific drum instruments in a drum kit track you have inserted into a project. But that's just a guess. I booted Next and it seems that the kit I tried is already mapped to my usb keyboard and the built-in Virtual Controller. Maybe you are talking about using the built-in pad controller? If so, you might want to search the User Manual (accessed through the Help tab) for "pad controller."

What do you mean? "Map a MIDI?" A MIDI what? MIDI Data, a MIDI Controller? Also, Cakewalk Next has support staff.

I am not familiar with the newer products; My most recent Rolands are from the 1990s. Maybe you know: Is the FA-06 in any way related to the Fantom line? I ask because I do have two files for the Roland Fantom XR: Roland Fantom XR.ins and a separate one called Roland Fantom XR Drum Kits.ins. Not sure where I got them from. Below are the initial file comments for the first file.

Assuming you are talking about a Roland product in their FA line, I looked in my Roland.ins files and didn't see any *.ins files for any in the FA series. Not sure if it was ever "built in." Evidently it wasn't supplied in any of the Cakewalk Instrument Definition Files I downloaded. Maybe another user has one.

Yes. Get a file finder tool.

I thought this was resolved 8 months ago. I have been using Cakewalk since the days of MS-DOS. Maybe you and I are in the same age range. If so, I understand forgetfulness, preferences for avoiding change simply for the sake of change, etc. But to me, Workspaces is an amazing feature. In fact, several years ago I created a customized workspace specifically for creating piecemeal tunes using the staff view and MIDI data. The layout was simplified to have distractions out of the way. I could enter phrases one at a time via my usb midi keyboard and edit them as needed in either staff view or the event list (or re-record them). I am sure I had the sysex view enabled. Also, I had the track view header just with the MIDI parameters I needed, the Control Bar was customized to show me just the tools I needed, with the most important ones expanded, others collapsed, etc. , and the Multidock setup just the way I needed for creating tunes using my really ancient workflow augmented by a few new features, including a console set up to my liking with narrow strips to easily balance my MIDI tracks. Or create your own Custom Workspace so you have just the tools you need setup the way you want. While it might take some time to learn how to create and use customized Workspaces, I would encourage you to spend the time to learn how to create one that meets your needs. You can have all your favorite views and features available and others excluded so they aren't even shown.

This looks very familiar. Except that I thought the glitch was for the full version and the upgrade for $29.99 was not a glitch.

Thanks for clarifying this ^^^^. I just opened about 15-20 pure midi files with the MIDI Device Preferences as noted above. They all played on my M-GS64 and TTS-1 didn't show up in the project. The files range from the 1993 classic canyon.mid, to some of my own files, to commercially sold songs (Led Zeppelin), to video game tunes my kids downloaded from the internet a decade or two ago, etc. My XMidi interface is an older class compliant usb device that supports 2 MIDI Ins and 2 MIDI Outs (5 pin DIN). I do not have my iConnect MIDI interfaces set up, so I can't test them. UPDATE: I just struck out the long shot speculative ideas after trying all sorts of things--using UWP MIDI Mode, having all MIDI Outputs enabled, adding an audio/MIDI plug-in, etc. After each change, I loaded (1) canyon.mid or (2) a project from today that contained canyon.mid. In any of the test cases, TTS-1 did not suddenly show up. In the immortal words of one of Gilda Radner's classic characters, "Never mind!" I notice that your outputs show: . Is there any chance that the drivers for some of those ports/devices are not pure external MIDI devices that might be causing something in the connected those devices to be reported as virtual MIDI devices? Just wondering out loud since I am totally unfamiliar with those devices. Also, I know for my legacy external MIDI gear, I need to use the MME MIDI Driver Mode. Long shot: do you use UWP and if so, could that be making some non-legacy gear appear to Windows and hence CbB as non-external MIDI hardware devices? I discovered that with my gear UWP messes things up, so I absolutely never use it. Again, this is a long shot and I would defer to others here who know more about UWP MIDI Driver Mode v. MME MIDI Driver Mode. All I can say that my tests today are consistent with what I described in 2024 WRT not having TTS-1 show up when I am using MIDI Devices as described. Not doubting that you are getting TTS-1 to show up when unwanted; just trying to offer what little I know in case it helps sort the issue out. A few weeks ago, I did have a case where TTS-1 showed up when I was trying to do something with external MIDI gear, but IIRC the project already had at least one soft synth in it (or something else such as an Audio/MIDI plug-in that might have told CbB I was using virtual/internal MIDI). If I can reconstruct what I was doing, I'll give that a try.

It sounds to me like you are wanting a super high-end recording studio server to integrate / manage all aspects of professional recording with a dedicated Operating System. I guess that addresses my post: So, I defer to the others in the forum who might benefit from the kind of high-end recording server you seem to be wanting. I have no idea how much a fast-food management system (hardware+software) costs or how much a fully integrated hardware+software recording studio system costs. Several years ago, I did look into a company that was developing some high-end audio software to revolutionize things, but that was over my head, way beyond my needs, and definitely out of my budget. For a while I followed some of the discussion on their Discord channel, but there was way too much in-group thinking/discussing for me. I have my own methods for my madness--or should I say, my own madnesses for my methods. 😜 I'll leave this discussion of high-end recording studio servers (with a dedicated OS) to others.

I cannot answer your question; just trying to clarify: by "pure MIDI files" are you talking about (1) opening a standard MIDI file in a new project? (2) a project that only has MIDI tracks (that is, no instrument tracks at all)? (3) something different? In my own usage, I haven't looked at the issue of when TTS-1 gets added and when it doesn't. I have seen difference, but recently if it happens when I am intending to do a project purely on external MIDI sound-producing hardware, I just delete it. At some point I might want to sort this out for my own needs, but I think by "pure MIDI files" you mean new projects being set up to only send MIDI data to external MIDI sound-producing hardware. IIRC the last time I did this, I wanted to look at someone's MIDI file (probably *.mid) and play it a Roland M-GS64. Anyhow, it might be clear to others, but I'd like to try to figure this out for myself sometime and wanted the clarification in case you are talking about something different. I still have plans to some day set up some hardware and use only those in projects (no in-the-box software instruments). Thanks. ADDENDUM: LOL@Self. I should have tried a simple test BEFORE replying. Here's what worked for me: Booted CbB. Powered up my M-GS64. which was already connected to a MIDI Interface port. In Preferences > MIDI Devices changed the devices from to since the M-GS is connected to port 2 of my Xmidi 2x2 Loaded a *.mid file that someone posted in the forum Results: 6 MIDI tracks loaded into the new project. No software instruments loaded. i.e., TTS-1 didn't load. Since I changed Preferences > MIDI Devices all tracks were pointing to the M-GS64 port. Note: The first time I tried, I had left the Layla MIDI port selected and all MIDI Tracks pointed to that device. That would have required all 6 MIDI tracks to be rerouted from the Layla Port to the Xmidi port, so I did the change in Preferences. In either case, I didn't get TTS-1 added to the project The project played the pure MIDI file on my M-GS64. I hope this helps.

You seem to be advocating something based on this ^^^^. If I understand you correctly, you seem to be drawing a parallel between the use of timers at fast food restaurants and the use of timers for processing audio data and MIDI communication--as if to say, "Since greater stabilization can be achieved with a specialized OS by making the fast food restaurant process more efficient as regards timing / handling the process components, greater stabilization can be achieved with a specialized DAW OS that makes audio and midi processing more efficient as regards timing / handling DAW process components instead of using any services, features, components, etc. of Windows' services, features, components, etc." Just wondering if I understand where you are coming from.

I have nanoKontrol [1]. The Korg Editor allows me to set the settings of the knobs, buttons, and sliders. If a VST has Remote Control / MIDI Learn, I can use that to tell the VST how to use the outgoing MIDI data the Korg sends (aka Mapping). I have also used the nanoKontrol sometimes as a Control Surface to control the Cakewalk UI. You can use the forum's search tool to look up "nanoKontrol" to get more posts. I am sure others have already discussed using the nanoKontrol 2. Here's a search link for "nanoKontrol." to get you started until others with the nanoKontrol 2 chime in here. Hope this helps.

Interesting question. I have no idea, but I can only assume if you have a controller that sends out CC88 data and a synth that interprets it as extended range velocity information, playing back the recorded MIDI data should allow the synth to do what you want. Again, I have no idea, but I like the question. [EDIT OUT based on David Baay's explanation of the CC88 data.] If you (or anyone else), has some note data that has the CC88 velocity extended range, I'd be interested to see what it looks like and play around with it to see what I might want to map the CC88 data to (purely as a hobbyist).

Thanks for confirming this. I assumed this was the case based on your prior reference to "the CC88 implementation" but the clarification is good to know.