User 905133

Not sure about bypassing the entire bin; now that you mention it, I am curious. Here are some background colors I had on file for individual FX and the FX bin bypassed. Thanks for pointing that out, Colin! (1) MNotepad - active; z3ta+ - bypassed; bin: active (2) Same as above but bin is bypassed ABOVE: Track View (1) (2) ABOVE: Inspector Strip/Console View

FOOTNOTES (probably Notes to self, unless someone else has been down this road before and/or is interested): Based on some personal explorations and several forum discussions over the past 6 months (esp. the last few days), I have begun exploring the midi data flow surrounding this issue, particularly as concerns the flow from external controllers via (1) track settings and controls (a) to the Inspector-based arpeggiator and (b) to a software synth (just because it is more handy than having to boot external sound modules) and (2) remote control midi [aka midi learn] (a) to the Inspector-based arpeggiator's virtual buttons and selectors but not (b) to the arpeggiator's functions themselves. (See also note 3.) So far I have ruled out some possibilities to explain the behavioral differences of the arpeggiator's handling of midi data. As of this morning, I have a new lead. Based on one test so far (more to follow) it seems that because the arpeggiator exposes its parameters to automation lanes, remote control of the arpeggiator's functionality must use automation lanes. So, for the moment this question is still open (unsolved) but I am actively engaged in answering it (See original question.) Based on more tests, (3) seems to be confirmed when (a) a specific Inspector-based Arpreggiator's parameter has been recorded [W = Write/Record external midi data/CCs.] and (b) it is played back [R = Read/play back recorded external midi data/CCs from the automation lane to the Inspector-based Arpreggiator]. Real-time monitoring of the affect of remote control midi might not be possible for all parameters. That is, it might require recording [automation lane = W] and playback [automation lane = R].

As someone who has good reason to dislike Cakewalk's shades of grey on other shades of grey motif (aging eyesight issues), I know what you mean. And somewhere I have some test Themes where I specifically played with the FX on/off button colors. I would also appreciate a guide to the multiple states images. I am pretty sure someone explained some of them in a post. Matthew's explanations here are excellent--very helpful! Thanks!! And thanks for raising this discussion!!!!! BTW: I am a big fan of using assorted colors to find where UI elements are, though so far almost all of my explorations have been with colors elements: One of my favorite uses of bright green [good to go] v. pink [wait!]:

Updates to my previous post: I was able to select loop construction after I highlighted a section of audio in an audio track. I was able to select step sequencer after I added a blank midi track or a soft synth / instrument track.

Since they are grayed out as opposed to missing, Step 1 might not be relevant. Maybe Step 2? What kind of track are you working on?

As I understand (as a user since the MS-DOS versions), when the Staff View was introduced, it was never intended to compete with $500+ full-featured staff editing software. It still doesn't compete because as some have noted (implicitly and/or explicitly), the markets that use music/staff notation have not been vigorously pursued. (Some people have phrased this idea as: the staff view has been neglected over the decades while other aspects of Cakewalk have been pursued.) JMO: This does not mean that Cakewalk's Staff View and Staff Printing capabilities couldn't pursue markets that use staff notation. Of course, being free software might be an issue--I am not sure. Pre-COVID, schools in the US still used staff notation. Not sure if the educational use of music notation has dried up. That being said, except for tweaks that seem to favor digital audio manipulation that messed up the use of the staff view, it still does (almost) as much as was originally intended (as I understand it).

I looked through some of the Theme Editor parameter tests I did several months ago. I didn't see any ones where I tweaked the text color for the section names, but evidently I did one test where I tweaked the background. (See below.) If something like this would help, I can look up the parameter I edited using the Theme Editor.** Or, you could look here. As for the Mute, Solo, and Record buttons, IIRC they are images. Full Themes done by others might have colors you like and you can "borrow" images from them and put them into your own custom Theme. **EDIT: Found it.

I knew this, but thank you for reminding me/[us]; I have been trying (again) to try to figure out why I cannot get remote control midi to work with the inspector-based arpeggiator. Yesterday I figured out that while note data goes to the arpeggiator based on the track's echo status, CCs change the status of the virtual buttons and selectors (but not the underlying functionality) whether track's midi echo is on or off. Upon making the observation, I immediately thought of this thread re: the Step Sequencer channel issue and wondered "How does the arpeggiator route midi control data--even if they are being routed into a blackhole?" I have been using CCs to try to change arpeggiator functions. Your comment suggests to me I should test to see if there is a difference between CCs and notes; although it could be that note data is routed to the arpeggiator and CCs are just thrown away. NOTE: Not trying to hijack this thread; was going to do more testing and either add to an existing thread on this problem or add yet another one. Just wanted to TY for the note v. CC insight and to flag the issue here as possibly related. Also TY to @msmcleod for his limitation v. bug comments as those observations might (or might not?) be related to the remote control/arp issue as well. UPDATE: The note v. CC distinction appears to be a dead end in terms of the disconnect between the arpeggiator's virtual buttons / selectors and the underlying functionality. It was worth looking into and ruling out. However, @msmcleod's comments re: bug v. limitation might be relevant (see both above and below) because the arpeggiator's channel(s) setting (1) seems to be for both input and output and (2) allows for multiple outputs. There is a major difference, though. In the case of the arpeggiator notes might be routed (or not) to the arpeggiator based on the (a) the echo status of the track [on/off], (b) the track's input setting, (c) the controller's sending channel, (d) the arpeggiator's I+O channel(s) setting and maybe (e) other settings. However, in terms of remote control midi, both CCs and notes seem to be routed only to the virtual buttons and selectors but not the underlying functionality. This bug/limitation is only tangentially related to the drum map bug/limitation at best but was worth looking into.

I can relate--not that it is counter-intuitive, but more that it is not what I have been used to; so, for me the learning curve is steeper than things I am familiar with. However, having started with a few personal favorites from the free collection and "graduated" to the licensed version of the free collection and then to several of the weekly 50% off plug-ins, I have found the transition to plug-ins that used the same UI features was easier. With plug-in features that vary from what I have taught myself, the learning curve remains on the steep side. For example, after using the free convolution plug-in, I opted for the Multi-Band version on one of the sales. So, having learned how the basic convolution plug-in UI worked, it was pretty much one step to learn the MB feature--which I can apply to some of the other MB plug-ins. I remember the struggles I had a few decades ago trying to teach my mother how to used a cassette tape recorder. It's not that the technology was counter-intuitive, but she had a super steep learning curve because so many aspects of the technology were not part of her prior experience. Similarly, I had the benefit of learning synths on a Moog at my college. So for me hardware and software synths that use features, methods, etc. that I learned ages ago come far more naturally to me than newer ones. Also, like the PRV and the Step Sequencer, the learning curves are rather steep for me, though I know many to many other Cakewalk users, the learning curves are either very minimal or nonexistant. I have seen others be frustrated, angry, dismissive, insulting, etc. but I think your are right on with making the time to tackle the learning curve . +1,000,000 [me, too] Thanks for contacting them on this and for sharing the news!!!

Looks like D# to me, too. If the PRV calls it Eb, that's a different issue.

Sorry; my post was about using close then Alt+ [number] and getting full screen panes; not about "folds"; ergo non-responsive to the double-clicking and folds issue.

Thanks for the confirmation. I understand about personal workflows--for me setting CCs on my controllers and mapping them to my preferred parameters doesn't require any retraining, though I confess, I tend to use the same CCs for parameters and also have 3 x 5 index cards handy!! Also thanks for mentioning the use of automation and midi tracks. As a test, I split the instrument track and tried remote midi on the midi track. Unfortunately, it didn't make a difference, but I can rule that out as a possible reason why remote midi doesn't work.

Is it safe to assume "they seem to be working as expected" only refers to your use of automation lanes, not to the use of remote control /midi learn from an external midi controller? If you have had success with remote control midi from a controller to change the arpeggiator parameters, I would be very interested in that. Thanks.

Several months ago (as you noticed) I observed a disconnect between (1) the remote control of the virtual buttons and drop-down selectors in the Inspector-based Argpeggiator and (2) the underlying functionality of those virtual buttons. For example, a remote CC (1) can make the latch button light up but (2) the latch function does not turn on. The last time I checked, if I had the virtual latch button lit without the underlying function being on and then clicked the button with the mouse, the button went unlit and the latch function turned on. (See update.**) I tried different settings to try to make the remote control work in the arpeggiator without any success. In other places (such as track echo on/off) remote control worked properly. 100% pure speculation: perhaps the disconnect is related to Cakewalk's automation features. Its very simple to re-test--just assign any midi data to any arp function. I will try again this afternoon. UPDATE: Just did a simple retest with SI-Bass and latch on/off via midi learn/remote midi. As before the CC turns the virtual button on and off and has no effect on the function itself. **With the quick test, I was unable to replicate the virtual-button-being-out-of-sync-flip-flop effect. Nevertheless, it is still possible to turn the Latch virtual button off (for example) via midi remote control leaving the function on, while the button shows it off. As I recall, this was true of any of the arp buttons/selectors and their underlying functionality.

This relates to the initial quandary I had when I saw the original post. Thank you for articulating it so well! http://recherche.ircam.fr/equipes/salles/WFS_WEBSITE/Index_wfs_site.htm

Amazing detective work here!!! It would be great if someone else can confirm this. I will see what I can do as it will be a great learning experience for me, but it would be better to have others who are more experienced than I am with the step sequencer and with drum maps. Update: Thanks for chiming in on this, Mark.

I am going to have to defer to others with more experience, problem-solving skills, and maybe insider knowledge. To be clear, I believe you are describing the Browser (the one window with all the plugins). If I understand correctly, you solved the problem of docking it on the left. You then re-saved that Workspace with the "Window Layout" Load from Workspace option checked. But when you re-opened the project or switched Workspaces and tried to return to the Workspace you want (with the expanded Browser docked on the left), that Workspace didn't load. I tried a number of things with the Browser (including a several personal Workspaces) and wasn't able to recreate the issue. (I did not try using Screensets.) Maybe some other users or staff have some ideas.

I would agree that this is one of several improvements that could be made to the Event List. If we can do this at the start of the song (in either the track pane or the inspector), why not in the middle via the Event List? The name isn't correct because its not in the *.ins file, but you are right--we know what we are doing.

Yeah, that's the way bank switching on my gear works. For example, [Advanced Orchestra ROM] Patch[8448]=Proteus 2000 Siedlaczek 0 Patch[8449]=Proteus 2000 Siedlaczek 1 8449 / 128 = 66 with a remainder of 1, so CC0 = 66 and CC32 = 1 https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Instrument_Defs.07.html#1117553 ADDENDUM [2020-06-21]: Just to be clear, a program change with bank switching works on my gear if CC0 and CC32 are inserted before the program change.

Bank Switching CCs: CC0 and CC32 + Program change, IIRC.

I am not sure what Cakewalk assumes regarding *.ins files. I thought the original ones were created by users of the gear, but I really don't know that; it was an assumption based on the "Contributed by . . . " comments in the original Master.ins files. From those, I made my own. Also, I have seen patch editors that will create *.ins files, but that is only because the software developer put that in there. This threw me off. It seemed like you were saying there was a problem using external/hardware gear. I see now that your issue is that evidently no one has spent the time to create an *.ins file for your piece of gear. Now I am really curious about this "bug." I think the earliest Windows Version I currently have installed on a PC is either SONAR 3 or SONAR 5.

Did you save the new Workspace (or re-save it with the same name) with the proper save and restore options (such as "Window Layout" in the "Load from Workspace" section with the Workspace Manager? http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x23EFB

I used the event list in Cakewalk with external gear before soft synths. It worked then and I just assumed it still worked. I have *.ins files for my gear. It seems to work with them. If I can figure out how, I will try doing this without an *.ins file. I will try to understand your list of steps. Interesting: I used a *.midi file and the synth wasn't even selected as an output. Yet, the *.ins file was there!!! I didn't expect that. I will have to enable the synth so I can unlink the *.ins. OK: I enabled a device for Output 2 and changed it to "Default." Evidently, since there are no banks defined, we are unable to choose banks. As you did, I also tried 1024 and Cakewalk didn't accept that. I tried the dragging method--but only went to 131--too crazy to try for 1024 that way! Sure enough the 131 replaced the --. Personally, I like having *.ins files with banks and patches defined. You have my curiosity, now. I will try this under SONAR X1 on my XPSP3 PC. After XP SP3 SONAR X1 test: It seems to work the same for me. If the instrument assigned to the port & channel doesn't have banks, -- does the same thing as above. However, when I assign an instrument that banks, I can select them. I don't current have my E-Mu *.ins files installed in my SONAR X1 path, so I used a generic Roland bank to test. Hope this helps.

"True Stereo Panning" caught my eye because I had no idea what that could possibly mean. But rather than ask, I looked it up. As best as I can tell, it refers to the ability to put an audio source any place between 100%Left/0%Right and 0%Left/100%RIght. Evidently if the source is stereo, balance becomes something like % of the left-side signal being routed to the left output [or bus] v. % of the right-side signal being routed to the right output [or bus]. Just trying to understand here. Do I have it right?

So far as I have seen they might also be affected by color settings, but the colors of the plug-in names can be changed using the Theme Editor. The colors of the icon images can also be changed, but need to be re-painted. Or, if a Theme Maker has already colorized them in a theme, you can grab those images and assign them to your own theme. If you just want to display the VST2 and the VST3 plug-ins separately you can select Sort by Type. (Note: I was almost done with this when Canopus replied, but we are saying similar things. Maybe the pix help?) Here you can see how MarianoGF colorized icons in Boston Flowers.