User 905133

@Astra-Ios Several months ago I explored the Inspector-based Arpeggiator. I really liked it a lot and was building a custom template. Unfortunately, I was never able to get midi learn to work the way I wanted. (I am still not sure if it is a bug or just user error.) Depending on what you want to do, it might meet your needs. In my experience, if you don't mind using a mouse for turning the arps on and off, latching them and un-latching them, etc. they seemed to work fine. The problem I had was that via remote midi, the virtual buttons changed (lit/unlit), but the functions did not change based on remote midi commands. Other than that, I thought they were quite flexible. http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Recording.17.html

I see that there used to be skins for z3ta+ 1.5 on the internet, but I can't find any links for skins that still work. My guess is that the one in the video (and posted above) is a skin. (I like it, too; so, I looked for it but couldn't find it.)

Another thread on SoundFonts:

Is this from Z3t+ 1.5 or a newer version (or an earlier version)? Perhaps they are the initials of the sound developer? (Just a guess.) In 1.5 there is a bank that says . Maybe BT stands for BigTone? Speculation verified by Canopus. See below.

Interesting idea. I thought resizing images would cause problems for the UI's stability so I never tried it. But as my eyes continue to age I might explore expanding the size of frequently used / hard to read elements. More research needed. Intuitively I suspect that trying to enlarge the buttons so they match the double sized icons won't work, but based on your suggestion its worth it to me to try. EDIT: Suspicion confirmed:

If the goal is to have an element browser from which we can put check marks next to elements and the press "OK" so that all of the checked elements override the theme currently in the Theme Editor, I think I'd use that, too! At present I override elements (as noted above) by using saved sets--such as my "Scrabble for Juniors" style midi track control icons [I, O, C, P, B] set.

I just dabble with the theme editor, so I will defer to the experts. However, with my limited experience, I did something that >>might<< fit what you describe, but only (1) if you are talking about exporting some elements from one or more themes and then importing them into another theme and (2) if the elements are compatible (e.g., the same dimensions). You could also be trying to do something totally different; I'm not sure. For example, I have some customized themes that only over ride some elements of a factory theme. So, when the Arranger track came out (which changed the size/layout) of a number of elements, I was able to import my tweaks onto the new factory theme because there were no size/dimension incompatibilities. Another example I haven't tried yet: I like some elements others have in their themes--so I plan to try to borrow those and build my own set of overrides so I can apply them to other themes.

I don't use TH3, but I tested it and was able to click on some knobs in the TH3 modules and do either midi learn, or assignment to automation slots. The power button on this module (AQTX Spring Reverb) seems to be assignable.

I agree with (b) as I suggested previously. We can scroll with the mouse wheel while reading, but once we go to edit, we have to use up/down buttons. Personal preference, but I would like the mouse wheel for both, not a scroll bar for reading and mouse control for editing. EDIT: There is a scroll bar for read mode.

I first heard about it from this (in the thread I linked above): I don't have anything that runs OSX, so I have to assume that's where its coming from. I have no idea if there are massive amounts of *.midi files available on the internet. I will defer to others who have used OSX.

Thanks for the heads up about "fast startup." I have an older version of Windows 10, so perhaps I don't have a setting for that. Not sure its related, but I did find my Power Options > High Performance was set to Allow Hybrid Sleep = On. Not sure what that does (more research needed).

Out of curiosity, are *.midi files standard midi files? I renamed my *.smf with a *.midi extension and evidently I already had another *.midi file from somewhere. Both open up in Cakewalk from "Everything" - a file searching/listing tool I have used for a while. I understand the issues you raise, @Robert Bone --esp. the suggestion that other extensions should be accessible via Cakewalk itself. I totally get that!!! I also get that renaming file extensions is not necessarily anyone's first choice. With that in mind, this is just another possible work-around for opening the files without having to rename them--for the time being. Personally, I think that if the developers decide to allow for other extensions to be seen and opened from within Cakewalk, perhaps there could be something in Preferences so users can choose which extensions they want Cakewalk to see and access. We all have personal workflows. For example, I like being able to have file filters for various things, including different types of Cakewalk files. There are probably other tools that do the same thing, too. for example: Not trying to distract from the suggestion; just offering some ideas on work-arounds.

I know I had this working a few days ago since I posted some images of some of the hot spots for dragging tracks. Here's a hot spot for dragging folders. I will test it again. Yup--they move.

I have not started using the new Arranger Track yet, but your suggestions sounds like something I could use, too (when I get back into some of my note-on-staves projects). I see that we can have the staff view open and by pressing A, I get the Arranger Track at the top of the Track View. Also, I can open the Arranger in the Inspector. I don't know what we can and can't do with the staff view open, so I am asking for clarification of your idea. Thanks.

Based on that, I assume you can if they have been saved as *.mid files. If they have been saved in a proprietary file format and/or have extensive commands that are unique to MOTIF, extra work might be needed beyond just opening up a *.mid file. I will defer to others who might be familiar with MOTIF and other hardware sequencer file formats. My experience has been mostly with E-Mu gear sequencer files--which are backed up as *.mid files and can be easily opened in Cakewalk. (Also I had some experience with very old software that used *.smf files and ancient Casio CZ-5000 sequencer files.) Just out of curiosity: If they are stored as *.mid files, does Cakewalk open them and show you the tracks? If so, have you tried assigning them to a multi-timbral soft synth (such as TTS-1) or other external multi-timbral gear? ADDENDUM: I was curious about the file format and found this. So maybe you did export them as standard midi files. Also, I found an old [1995] *.smf and it opens in Cakewalk.

I remember a previous discussion. Not sure your question is answered here (I haven't looked for it yet), but it might have some overlap with your question.

I agree--once I stumbled onto the mini track pane, I found it very convenient and started using it for some work flows.

Never mind; i figured it out: "to switch tracks on/off" = "to show or not show staves within tracks" (as in eye = show/don't show. Just a thought: It might be nice to have selectable elements to show--like the track control manager lets us show which widgets get shown in the main track pane (e.g., a mini track pane manager or a column in the current track pane manager). Thus, we could have different workspaces which show different configurations of staff/prv views and the mini track pane controls.

I am glad you mentioned this--I just typed CAL in the forum search and it works! ? Handy feature!

Nice tune! The conceptual interplay between the text ("paradigm shift") and shifting phrase lengths is a cool feature--lyrics and music playing off each other with multiple meanings! Excellent!

There are often multiple methods for doing things. My personal work flow for some projects is to use split instrument tracks--where the combined instrument track is split (separated) into an audio track and a midi track. Sometimes I will leave the instrument track with both audio and midi together and will create a separate midi track and point it to the soft synth. Below you can see that the output of several midi tracks are all pointed to the same instance of TTS-1 [O = 3-TTS-1 1]. However, the midi data for tracks 10 and 11 are forced to different midi channels [C=14CkwlkT...] and [C=15CkwlkT...]. These are just some personal options, but I hope it shows one of the missing pieces to understanding midi routing. If you don't have the I, O, C, B, and P track control widgets visible, switch the track control preset to "All." Hope this helps. [UPDATE: The presets for the track control widgets can be selected from the little arrow next to where it says "All" in the following image. You can also create your own widget configurations by choosing "Track Control Manager..." from the drop down menu. Apologies for not putting a box around it; I grabbed a picture from a few months ago.]

When I started testing this early access release, it seemed to me that the UI stabilized more quickly than previously (1) upon opening a project and (2) when switching Workspaces. I was very glad to see I wasn't imaging it and that it is indeed an improvement. Thanks!!!!!!!!!

Glad to hear this works!!! Actually, I set my PC to open *.ins files in Notepad as the default. Almost all of my hardware modules have Preset User Banks and I edit the names in my tweaked *.ins file using Notepad. Super easy! I think I also use the "Normal" bank switching method for my gear. I will check that out and also look at the Korg file to see if its different. UPDATE (revised): Bank lists like [Korg Pa4X Bank 00 GM/XG] and [Korg Pa4X User2] define the banks by enumerating the names of the presets in those banks. In a later section, the bank switching values themselves are listed under the name the Instrument Name: 15488 / 128 = 121 - So, the bank switching MSB = 121 and the LSB = 0. 15489 / 128 = 121 with a remainder of 1 - So, MSB = 121, LSB = 1. The CC0 value is the MSB number and the CC32 value is the LSB number for bank switching. HOWEVER: If you have the correct *.ins file installed correctly (and it is set up correctly--lined up on a per port / per-channel basis), you shouldn't need to figure out the CC0 and CC32 Bank switching values. For example: Here I have port 1 channel 1 set up to look at one of my E-Mu *.ins files. Specifically, it is looking at one of the Instrument Definitions for a Sound ROM I have installed [Module: Virtuoso 2000; Bank 1280]. I think the Korg *.ins file should work the same way. Hope this helps explain the relationship between the CC0 and CC32 values as listed in the Korg User Manual and how to select specific banks based on the *.ins file.

It depends on work flow. Some projects I have done just use the initial synth patch/preset as set in the track widgets. In those cases I wouldn't insert a program change in the middle just for the heck of it. However, sometimes I have changed presets on a track in the middle after the fact. I might insert a program change via the Event List in those cases. Sometimes I will insert a program change from a keyboard but will later either want to remove it, or change the bank/patch. I used to sometimes use a separate track for controllers. When I did that, I might have also used that track for program changes in some projects. (This was before automation lanes, though.) I have some synth module templates that use a similar approach. Every channel (up to 32 midi channels on several modules) are there, color coded by module, in per-module track folders. With this approach, it makes little sense to me to insert program changes in the middle of a track. However, after working with the massive orchestration template, often I just want to create music as I go (at least for the initial stages, to get the ideas down) and might have an initial patch on each track, but will insert back/program command at the beginning. With this work flow method, I retain the initial patch I used and can also try some other patches--from the start or in certain sections. Not saying one work flow is absolutely preferable; just enumerating different possible work flows.