User 905133

Thanks for chiming in on this, Bassman! I will look to see how I set it up based on your comments. I believe I am using the same preset within AZController. Also, as MIDI-OX shows, the CCs are the same. Here I just moved slider 1 a little on each. Port 1 is nanoK # 1; Port 2 is nanoK # 2. Thanks for the link to the preset on AZSLow's site; I will take a look at it. EDIT [20 Jul 2020]: Oh--that thread/preset is for nanoKrontrol2. From what little I have read, version 1 and version 2 are very different. UPDATE:

OK--I am going to try what it says here (setting the WAI for different tracks in hopes that one nanoK controls one track and the other one controls a different track). Nope; I cannot make it happen; need someone who has had success with this before. No matter what I tried, I get both nanoKs controlling the Console sliders for both tracks 1 and 2. This kind of thing might be why I went with AZController instead of ACT. I will try the AZController to see if that will enable the two nanoKs to be independent. [Image from Cakewalk using ACT removed--it didn't work] UPDATE: (1) There's got to be an easier way! (2) I will return to this tomorrow, but I did set up the faders on one nanoK to affect Console faders 1 - 9 using AZController and following this video step-by-step. I will try setting up the second nanoK to affect Console faders 11-19 tomorrow (unless someone has an easier way to do it with ACT). New UPDATE: Set up second NanoK to work with Console faders 11-19. It works. ? Again, this is with 2 version 1 nanoKONTROLS. From what I have seen in the Forum, version 2 has a Control Surface mode. There might be easier ways than programming it with AZController, but if not, following AZ's video works. I just mapped 9 faders for this proof-of-concept. Buttons could be mapped such as to Mute/Solo. I only used Scene 1 on both nanoKs. I suppose with scenes 2, 3 and 4 on each, I could map more console sliders. But so far, I tend to use the nanoK for FX plug-in controls. PS: These remain as before:

Anything in these thread that might help with trying to find a solution or shed insights on the problem?

I have two of the original nanoKONTROLS, but I tend to use them as midi controllers, not as control surfaces to change Cakewalk itself. I did test some control surface capabilities, but I used AZController, not ACT itself. I have not tried to use both simultaneously as control surfaces, but if no one knows the answer, I could do some trial-and-error testing. As MIDI controllers, they work because they are on different ports. One question I'd look into if I were to try this is: How can I (if its even possible) route controllers on different ports to different parts of the Cakewalk UI? Again, I hope someone else can help, but if not, I could try as it might benefit me somewhere down the road. EDIT: FWIW, I just set this up; maybe I will explore it later today (unless someone else can help).

Long shot, but easy to check just in case: Did your MIDI Driver Mode change (MME v. UWP)? I had something similar with nanoKontrols not being seen in Cakewalk after I had switched to UWP. Hope your solution is that simple to fix.

Possibly related threads:

Thanks for the historical clarification!! Though I have X1 and X3, at that time I was doing more with a hardware sequencer and just exploring soft synths in X1 / X3 as an alternative. Not sure if I noticed it. Glad Cakewalk by Bandlab had the wisdom to add them back!!! Maybe they will also add the tools back into the Staff View Pane. (I did notice those were gone from CbB.) From X3 (looks a bit "sparse").

Help me out, how does the new feature differ from the old buttons? From SONAR 3.

working on testing this. So far as I can tell, clicking on an existing note on the staff with either the smart tool or the edit tool does not change the note-value button in the Staff View Pane.

Just did a very quick test as follows (v. 2020.05 build 39). Verified "Last Touched" was checked in the Control Bar's Tool Module. On a single staff from a project in progress from a few months ago: Selected 1/2 note from the note-value tool in the Staff View Pane, Placed a 1/2 note on the staff, Checked the duration by right clicking on note head. Repeated the steps for a whole note, a quarter note, and a 16th note. For all 4 tests, the duration was as expected--2 beats for 1/2 note, 4 beats for whole note, 1 beat for quarter note, 480 ticks for 16th note. ----------------------------------------- oops--part 2 got put into a new post instead of going here.

I just tested some pre-Arranger Track Themes and the folder was there. Setting my windows scaling to 150% also allows the folder to be seen (though the UI took a very long time to display/open the project). Also, tried some of my custom Workspaces, with pre-Arranger Track Themes at 150% Windows Scaling. Could it be related to some display specific settings?

I started to reply, but I am only familiar with that setting as it pertains to bank switching methods and decided that was probably not what you were talking about (since you didn't say anything about bank switching). If you were, then the way you phrased the question definitely caused me not to reply. Also, I am a novice when it comes to using the Prochannel, I didn't see anything to change from Controller0 to Normal there, and assumed that someone who uses ProChannel Tools might know what the reference was to. Ohhhhh. Just found it at the bottom of the Inspector: And it looks like you were talking about bank switching method. Sec. I will try to reconstruct what I started to test back when I first saw the Q. UPDATE: Just did a quick test and it worked for me. Let me test again. Basically here's what I did: FWIW, there's this in the Instrument Definition wizard: I never defined my instruments this way; I just edited *.ins files directly. But maybe you can tweak all of your Instrument definitions in this dialog, or create/tweak a "NEW" Definition with Bank Selection = Normal and just assign that Definition to all channels. PS: I cannot speak to why others didn't reply, but your lack of referencing Bank Switching dissuaded me from replying. I had started to explore this when I first saw your post. Also, your reference to ProChannel distracted me from looking in the Inspector. Anyhow, hope this helps.

Oh!!!! Are you using Bandlab--the web-browser based, social networking oriented app? or Cakewalk? I had assumed you were talking about Cakewalk because (1) this is the Cakewalk Forum and (2) everyone else seemed to be replying as if you were talking about Cakewalk. However, after your most recent post, I went back to the beginning and it is totally unclear. If you mentioned Cakewalk, I didn't see it. Everyone else replied re: Cakewalk. So maybe that's why their suggestions do not make any sense. If so, its not a can of worms, just a classic case of miscommunication.

This is interesting--something that sounds like it should be simple to do evidently isn't. I have never had to do this, but someday I might; so I am trying to understand. If I play a part and save it as a *.mid file, Cakewalk saves the part as a MIDI file. So I guess from what people are saying, if there are other tracks in the Cakewalk Project, somehow the keyboard track needs to be isolated and saved as a midi file. Evidently, exporting a single midi track doesn't work. (Not sure why not, but I don't do a lot of exporting.) Could you just make a copy of the project, delete all the other tracks from it, and then save it as a *.mid file?

Its needed for a second or third or fourth monitor (however many your PC can support) that might be at a lower resolution than 3440x1440 px. ? My second monitor is 1600 x 900, so I don't have the problem you do. If I did have a larger resolution, I can easily see how the extra space strip could get used by sends, FX, etc. Its not in my budget, but now that I see the potential, it is now on my list of things to save up for. So, thanks for the suggestion.

Thanks for sharing the tune and for the details on your technical and compositional strategies. I am very new to using Voltage Modular, but I find it to be extremely intuitive (probably based on my experiences from long ago). I will have to see if I have this module. As for the "rabbit hole," I know what you mean!! In fact this week I have been reliving memories from the day the synth rep gave a demo at my undergraduate college and two of us stayed to explore and were surprised when the janitor came in to clean the synth room the next morning. We had no idea it was that late--errr, early.

Thanks for posting new screen shot. It confirms what I thought--that the audio you heard came from the Microsoft Synth which was serving as the default midi device to play the audio. Track two shows the Output [O] Track Control Widget is routing the midi data to "1McrsftG..." which is the Microsoft GS Wavetable Synth. As Nigel pointed out, to have the midi data sent to the SI-Electric Piano software synth, you need to route the output of that track to the SI-Electric Piano. There are a number of ways to do that. ----------------------------------------------- P[references]:

I asked because I have never had a midi track generate sound unless the midi data was routed to a sound source that plays midi data. Maybe by default it is pointed to the MS sound source. Can you post a screen shot that shows the midi widgets for each track? [I, O, C, B, P]

Track 2 is a midi track. Are you routing Track 2 to a software synthesizer or an external sound module?

As I understand it, Move in Staff View worked properly from Sonar 3 through Sonar X3. After that it seems to have gotten changed and the new behavior got passed on to Cakewalk by Bandlab.

The other day, I only tested one software synth I have and was able to export two arps. I have not yet tested any others, but while it could be a midi routing issue with/within Cakewalk, it could be a function of (a) a specific software synth, (b) what a specific software synth "exposes", and/or (c) how Cakewalk treats those parameters, among other related issues. Not disagreeing that it must be a midi routing issue, just trying to identify possible sources for the problem. Over the past six or seven months I have been trying (without success) to get Cakewalk's Inspector-based Arpeggiator to do what I want and only recently discovered that there appears to have been some midi routing decisions made that impact where remote control midi data [aka midi learn data] gets sent (or not sent). So far I have not been able to find a midi routing/signal map/flow chart comparable to the level of the audio signal flow chart. Something like that might help many people sort out midi-related issues, including those related to automation.

Step 1: Step 2:

@Colin Nicholls Do you also get the anomaly I get here (upper right-Inspector Strip Tab Bar)? I have been using this (1) for the sake of variety and (2) to see if there are any color combinations I like and want to borrow. I had the Inspector collapsed on the right* and wanted to move it to the left but couldn't because of the layout issue. Also, I switched from a "None" Workspace to one where the Inspector is on the left and the display issue occurs there too. However, once I collapsed and reopened it, I got more evidence that some images (tabs) are amiss.** Also, for me the floating/undocked strip is problematic.*** Not sure if its me or an incompatibility with recent display element changes. If it is an incompatibility issue, it shouldn't be too hard to tweak if someone wants to use this theme. Any idea who designed it? Thanks. *Docked at right: **Docked at left: ***Floating/Undocked: Hmmmm. If this is indeed the minor incompatibility I suspect, it might make an excellent example to demonstrate step-by-step how to override a new Cakewalk theme format with a set of parameters of other theme parameters. UPDATE: Simple import-on-top method seems to work partially, but some other minor tweaks are evidently needed: UPDATE: Found what appears to be the original posting of the theme.

Are you talking about the awkwardness issue discussed in the thread that includes this?