Colin Nicholls

I've updated the PDF document to the latest version, 0.9.3. It includes several changes including a new section at the end for Case Studies, in which I discuss customizing the Control Bar modules.

I run a 4K monitor (3840 x 2160) at 125% and although Cakewalk is not as "crisp" and pixel perfect as it is at 100%, it is more than just "ok". It is very usable. You're asking the impossible for a non-vector based graphics application to look perfect at anything other than 100% or integer multiples of same.

Steve - Thanks for your comments and observations. I'll respond in one reply Re: Logos - I don't think the ASIO Panel is furnished by the Cakewalk application. At least, my ASIO Panel shows an ECHO logo which isn't one of the ones in Global | About Box. But, good thinking... Re: Input(etc) control icons - Nice graphic! I'll just include your image verbatim in the doc if that's OK with you. Re: Control Bar Background (collapsed) - I just double-checked this. I'm not sure what I used when I tested earlier, but this time I replaced the graphic with an empty rectangle flood-filled with yellow with an alpha transparency value at ~50% and this is what I see: So the customized graphic is overlaying the original. There may be places in the UI where an alpha-channel is respected, or not, and I guess this is a place where it IS respected. I'm not planning on testing this everywhere! Re: "I should probably wait until you are done; would save me some time!" - Well, I had planned to stop working on the doc for a while. As long as I was working on a new custom theme, it seemed reasonable to log my findings, but I think I need to take a break. That said, I'll add your input control icon image as the first change to go into v.0.9.3. Any other updates - from you or anyone, either posted here or as a PM - I will integrate into the document to be included into the next release.

The most recent version of the document is v.0.9.2 and it is available at the URL above. I have paused working on it as of a few days ago, so I expect this is a stable version if you want to download it for easy access.

Thanks, guys. The title is a riff on Neal Stephenson's "The Diamond Age: Or, A Young Lady's Illustrated Primer" which is a pretty cool SF book; recommended. It seemed to be a good time to prepare the document, as it is clear that the Theme Editor is pretty stable in the development cycle. The bugs and inconsistencies aren't going to be worth the time the skeleton dev group would need to spend, so documenting seems reasonable. I'm not expecting anyone to go through this line by line looking for errors; and there's definitely more useful stuff that could be added. All suggestions welcome! If you have any theme-ing tips or tricks that you know of, let me know and I'll add them in. I'd like to make this a community effort and of course I'll adjust the credits to suit.

Here is the URL of the latest version of my Visual Guide to creating Cakewalk Themes. (The title is a reference to Neal Stephenson's excellent SCI-FI Novel "The Diamond Age".) The document is a work-in-progress, and will contain areas where incomplete information is provided. If you identify an area that could use additional content to help your Theme creation, please let me know and I'll look at enhancing those sections. Have at it! A Young Lady's Illustrated Primer to Theming Cakewalk.pdf

STEAMPUNK Slate. Bronze. Oiled Leather, amber, and hints of turquoise.... Clarity, consistency, medium-brightness. A smooth mouth-feel. You don't have to be a Victorian Gentleman of Learning to appreciate... SteamPunk. Update April 2020: I've validated that this theme works fine in the new 2020.04 EA release. Feel free to use. Update September 2020: Includes Markers view Lock indicator icon. Update January 2021: Control Bar Select Module Update April 2021: No actual image changes but theme was re-saved to eliminate the erroneous "theme compatibility warning" in release 2021.04. Update July 2021: Very minor change, Browser Media Tab and Track View Menu Bar Background. Hardly worth updating Update December 2021: No actual image changes but theme was re-saved to eliminate the erroneous "theme compatibility warning" in release 2021.12. GET IT HERE: SteamPunk.zip

Scroll down to "The editions compared", review the chart, and decide for yourself. https://www.celemony.com/en/melodyne/editions-and-technical-matters

I'm working on a comprehensive visual reference for color items in the Theme Editor. Would some kind Theme Author like to review it? It's not complete (yet) and I'm not looking for comments on style or content at this stage. - I have a number of entries for which I can only put "Not yet identified in UI" and although I suspect they are obsolete or unused, I would like to make sure I haven't missed anything obvious. Let me know and I'll PM you a work-in-progress copy.

Christian, you can swipe to select them just like any other CC value - then use Shift- to lock the mouse drag the selected values into a horizontal or vertical movement. It takes some practice. Zooming in horizontally may help with this process. Also, for simple On-Off, note that you can get the value anywhere above or below the center line to act as an on or off. < 64 is UP/SUSTAIN OFF, >64 is DOWN/SUSTAIN ON.

Totally can do this. Go into the PRV and add a controller lane for Control: 64-Pedal (sustain). Then you can edit them like any other CC value.

Both. Audio and VSTi's. Fairly big project. Despite my best efforts, I could not reproduce it, today. I'll post back with more info if it happens.

I'm experiencing a problem with playback (and recording). When I start the transport (either playback or record) I hear a sharp transient and then nothing. Stopping and restarting just produces the same transient, followed by no sound. The current song position increments steadily as though it were playing back, but no sound is heard. The only way to recover from this is to go into the ASIO panel and change the buffer size, either up or down. Then it works as expected for a few minutes more. Note that "recycling the audio engine" by clicking on the icons in the transport module in Cakewalk is not sufficient. I need to change buffer size in the ASIO panel. Here's the kicker: This has happened with both my ECHO Layla 3G PCI and also my Focusrite 6i6 (2nd Gen) USB. I realize that I need to repro this behavior with the Focusrite exclusively, and demonstrate that it worked better in 2019.09 than in 2019.11, before I have a legit claim that some change in .11 has been detrimental, but I thought I'd post here. I'll be running more tests today.

Just watched this all the way through. Nice work!

I'm an ardent user of V-Vocal, going the extra mile to ensure it is installed in my DAW environments. The version of Melodyne Essential included with SONAR Platinum and CWBB was not usable, in my view. (The opposite of "essential"). However, I took advantage of the recent Black Friday deal to upgrade to Melodyne Assistant (MA), which according to the feature comparison, seems to be a more 1:1 match with V-Vocal. My first impression is that MA is much, much slower that V-Vocal to bring up the editor. I think there may be a bug in that the editor comes up with no content (no "blobs" visible) and I had to exit and re-open the editor to see the clip contents. So I thought I'd start this thread as a place for us V-Vocal fans to share our experiences evaluating Melodyne Assistant. Any tips or tricks that will help us V-Vocal die-hards to enjoy and leverage MA ?

I've been running the hotfix since Friday and haven't noticed any problems. That said, my audio interface runs great until it doesn't, so perhaps this is premature, but add the data point anyway.

fjord perfect Thanks in advance

In Track View, Shift+LeftArrow or Shift+RightArrow will cycle through the Track Control Visibility presets. I had no idea about this. Cool. I can definitely see setting up some optimized views and switching between them.

It's not a bug so much as it is the Sonitus Suite not keeping up with "improved" security constraints in later versions of Windows.

I bet if you run Cakewalk as Administrator, you can save the presets you want. Then they are available in later sessions without Admin privileges. There's a hack you can do to lower the privilege level required to write to the specific ini file used by Sonitus, if this is a convenience you want. See scook's post below.

>> Any chance they're being overidden at the Colors level? Hi @malborinatiro, welcome to the forum. If you read your quoted text carefully, you'll see that this, indeed, was the case!

Glad to help!

Does Addictive Keys respond to CC:7:-Volume ? I checked the manual and it indicates that : AUTOMATION: The following parameters can be automated in Addicitve Keys: Channel Volume (Instrument Ch 1, 2 and 3, FX1, FX2, Master) FX Sends 1 and 2 for each Instrument Channel Master Channel Filter (Hi/Lo) ... So it might be that it expects you to explicitly assign a CC to a specific instrument channel to automate volume. I'm not a AK user, so I could be off-base.

Choose "custom installation" and de-select the bits you don't want. But to be safe, I recommend installing the whole thing. Then re-install Cakewalk By Bandlab.

I've never ever used controller 7 (MIDI volume) in my projects, so just for kicks I created a new project and dropped in an instance of Pianoteq. I then recorded some notes and opened the PRV, and added the CC : 7-Volume controller and drew some values. What I see is shown here: (animated gif removed to free up space and because it was no longer useful. Sorry!) You can see the notes I've created, and the CC:7 values I added, first with Snap quantizing and then with Snap disabled (smooth curve). Then I scroll to the left outside the borders of the current clip, and add some addditional controller events. Then I use Right-Click-Drag to select the events. Does this help? >> I'm trying to "paint" a line and it won't paint it, the way I'm used to seeing it do this. Instead as I drag my mouse, it generates a green rectangle, which does nothing --- or at least nothing I care about. Check Snap settings, just in case >> Near as I can figure, Velocity controls the volume at the mixing console whereas Volume controls the volume of the instrument itself. That's not how I would describe it. Velocity has nothing to do with Mixing Consoles, and everything to do with a binary value describing the attribute of an individual note - and how it is respected (or interpreted) is up to the module responding to the information stream. (MIDI controlled lights, anyone?)