Colin Nicholls

Something strange is happening in my project when I add an instrument (split) to a folder. The tracks appear at the bottom of the track view, indented but NOT IN A FOLDER. When I scroll up to the folder I expect to see the new tracks in, they are not visible. Scroll down - they've vanished from the bottom of the list also. The Track Manager thinks the tracks exist, in the intended folder. The soft synth does appear in the Synth Rack. The new tracks are not visible in the Track View. I am going to try and capture this, it's so weird. Observe: I select a track in the target folder, "Drums B".' I insert an instrument/split The new tracks appear at the bottom of the track view, indented but not in a folder When I manipulate the track view (open, close folders) the new tracks have vanished The new tracks show in the Track Manager as being in the target folder (but they aren't there) (The VST did get added to the Synth Rack) When I save the project, close Cakewalk, and then re-open the project, the two new tracks are now visible in the track view - AT THE BOTTOM, INDENTED, BUT NOT IN A FOLDER. They only show up if the target folder is open: I don't know why the "Guitars" folder has moved in the track list order 😕

@scook deserves some kind of award for the patience and detail of his messages. I have five new shillings I can contribute to the fund. It would have to be a platinum-plated shelf widget of some kind. Suggestions below.

2021.04 PSA: I had some custom themes (Polar Blue, SteamPunk) that did not have any customizations in elements affected by 2021.04, yet cause the "Theme Compatibility" warning to be displayed. I solved this by editing each of the tab button images, and saving over the top of the defaults. I then re-edited the themes to remove the custom images (even though there were no effective visual differences) and then re-saved. So theoretically we're back where we started, yet the themes no longer receive the compatibility warning dialog upon use in Cakewalk. FYI.

FYI: When I "edit" each of the Inspector Tab images and then save back over the default into to the theme (but without making any image changes), and then save the theme, I can now open the theme without seeing the Compatibility Warning. Huh: If I then re-edit the them and remove my "custom" yet un-altered images, and re-save the theme, I can now use the them without getting the compatibility warning.

Two of my custom themes are getting reported as having a "Custom Theme Incompatibility" despite containing no changes to the default Inspector Tab button images. Is there any chance of a "Show details" report that could tell me what has been found as incompatible?

Good catch! Was that even mentioned in the release notes? I see an under-stated note about Plug-in menu enhancements, this must be it.

I didn't think this feature would be for me but I realized that I often record vocal ideas or rhythms using the Voice Recorder app on my iPhone. Last time I tried to export from the iPhone and import them into Cakewalk, the sample rate was strangely out of sync. I don't know if BandLab would allow me to record audio fragments on my iPhone and then import them into Cakewalk without this audio syncing issue but it seems like something I will investigate.

Release 1 of this theme is honorably discharged from the force, and is no longer included in the ZIP. Release 2 is the current maintained version. Updated for 2021.04 with revised Inspector tab buttons.

ZIP updated with 1.0.6 with 2021.04 changes to Inspector Tab buttons, including new Tempo Track.

Not my theme. I've already adopted Blue Aston, I can't feed any more

Updated for 2021.04. (Also fixed the PRV AutoFocus button while I was at it)

Question: How do I hide the tempo track once I've made it visible?

That's very interesting. Thanks for drawing my attention to the .04 EA release. I can't believe I missed the announcement.

@Nilrik, I don't know about Blueprint but I highly recommend you watch Creative Sauce's latest tut on SI Drums, all the way through.

I use my ears /snark

This has kind of happened to me, (I think my audio card is playing back at 48kHz but Cakewalk thinks it is 44.1) but definitely does not persist after a system re-start. I'm not sure if this is helpful for you. MORE INFORMATION: Typically this happened to me again shortly after I posted this. In addition to my PCI/ASIO audio interface that I use with Cakewalk, my DAW has on-board audio (device manager has it identified as "Headphone Audio (High Definition Audio Device)". I have a lightweight set of headphones plugged in to the front panel headphone output on my Dell workstation. I use it for Windows System Audio, Youtube, VLC playback, etc. What happens is that Windows 10 can tell when the headphone jack is unplugged and (I think) tries to switch System Audio from the onboard headphone to the ASIO audio. It's not successful if Cakewalk is running, but it seems to have the effect of upsetting the driver into going to 48kHz. If I go into Cakewalk Preferences and toggle the audio recording frequency from 44.1 to 48 and then back again, all is well. This would not be nearly a problem except that my darn cat LOVES to go up to my computer and pull out the headphone plug when he wants attention.

This is "Comp" behavior. The Smart tool will include these actions unless you disable them. I find it handy to alter the "smart" tool so that the comping behavior doesn't kick in. Right-click on the Smart Tool to get the available actions:

I think you need to install the Studio Instruments add-on from the BandLab Assistant.

ZIP updated with 1.0.5 with changes to the Control Bar Tools module, including the Pattern, Mute, Sine, Square, Triangle, Line, etc, tools that were missing from previous releases. The Tool module is now complete!

I use a MidiSport 2x2 USB with Cakewalk and my computer and have never had a problem. As @Giorgio Gabriel says, try moving it to a different USB port to see if you experience a difference. You say "at a certain point", can you expand on that? Do you mean "random" or is it always after the same series of notes or in a particular phrase? Are Note Off messages being missed in the recorded MIDI data?

That's a nice look. I really appreciate the different angle you've taken here, with the round Tool and Track buttons. That's a lot of work; well done. I hope you manage to finish it to your satisfaction, I'm looking forward to giving it a spin eventually.

Alas, currently these colors can not be changed, not even with the Theme Editor. Best you can do is increase the vertical zoom and the text gets larger.

There's nothing stopping you editing the name of those tracks to remove the "(3)" suffixes, but I'm curious as to how they got there in the first place. I suspect something about your workflow is outside what we would consider "normal". How and why are you bouncing tracks? What destination do you specify and why?

Not meaning to be patronizing but do you understand the differences between a MIDI track, an Audio Track, and an Instrument Track (kind of a mash-up of the other two)? Are you recording MIDI okay but want to save/render the output of the virtual instrument as audio?

oh ho ho Tempo Track Incoming 😉