User 905133

---removed---

I suspect that there might be different reasons why BandLab Assistant fails to update and that different solutions might work for different people. However, I have found that going into Task Manager and killing the leftover processes helped solve it again for me when I had trouble updating to v.5.1.1 last night Please note: I deliberately left Cakewalk running to make sure that wasn't the problem. For me, it didn't prevent me from updating BandLab Assistant.

-- removed --

This is great to know! Based on Bob's experiences as reported over the past few months here and now your experience, it sounds like an excellent habit to develop.

I agree--excellent call!! I have long been a fan of Screensets and I have been coming to greatly appreciate Lenses since the summer (when I stumbled onto the new and improved Cakewalk), but I had never locked (or unlocked) Screensets. For me this adds another dimension to the complex yet flexible interactions between screensets (for project layout saving and recalling) and lenses (for overall/global workflow/preferences/etc.).

They seem to be in the Roland.ins file. [RD-700GX GM2 Capital] [RD-700GX BRASS/WINDS] etc.

HUH?????? Two new threads about an issue raised in May in a totally different thread? I had no idea that the recent posts were evidently tied to one from May.

Chuck, in another post, @tdehan asked how to use an airturn bluetooth pedal to get Cakewalk to start/stop. I suspect this question here might be related, but not 100% sure. I am just guessing.

I have something that superficially looks like what you have, but the only way I was able to do this is by creating buses named "Short Delay," "Plate," and "Room." That takes me back to "Question: Is "Modulation" the name of one of your buses? If not, what is it?" If I know the sends in that section are buses and not audio fx sends, that would help me to look for the elements to colorize. Someone who has designed full themes (or has done extensive colorizing) can probably just tell you which element you need to adjust in less time than it would take for me to teach myself. Below is a theme I tweaked slightly a few months ago with the three buses added in as sends (the image on the left). It is based on M. Titanium by @Matthew White . Perhaps he can tell you. Notice that in M. Titanium the parameters in the Inspector/Track section seem to be a similar shade of green to "Short Delay," "Plate," and "Room" (the image on the the right). Perhaps it is the same element. If not, finding the elements that use that color would be one way I'd look for it. However, maybe Matthew White knows which element it is off the top of his head. I will probably continue looking for color elements myself, but it will no doubt take me some time. Hope this helps. Steve

I have been looking for elements trying to find one that matched your screen shot. When I tried to insert something into that specific location in one of my projects, I had things like buses, patch points, aux tracks, etc. I did not have FX plug-ins in that location. That's why I asked what kind of a send it was. When I drag Audio FX to that location, they go into the FX Sends, not the location where you have "Modulation." I have been working on my own color schemes and I thought looking for the element you are interested in would help both of us, but I think you need someone who can look at your screen shot and tell you the name of that specific element. I tried. Sorry I couldn't answer your question.

I have found two ways to change some of the various text colors (1) using the theme editor and (2) using Preferences > Colors. The trick is to find the right parameter. I will look this afternoon. Here are some sample text color changes I have done in the track view. I have done some in the console view. If you like any of the colors I have here, I have the codes written down. Question: Is "Modulation" the name of one of your buses? If not, what is it? PS: color changes are not always immediate [from another thread:

Have you tried lowering the volume(s) of the tracks? If using softsynths, maybe splitting the instrument track into the audio and midi components might help give control over the levels?

Sometimes switching screensets can help locate things that are hidden. Maybe add that to the list of thin gs to try after using the menu version of the same command. Optional: Set it up as a button in a collapsed Custom module.

We all have preferred settings/configurations to help focus our attention; so, this is more of a footnote for an option others might want to consider. (I am assuming you don't want to change what already works for you.) It is possible (using Theme Editor) to set the text color for the names of audio, midi, and instrument tracks (a) in the Track View and (b) in the Console View*. [*For some reason, my console track name text colors aren't showing up.] And I agree, being able to hide types of tracks in the Console View is handy! Oh, and I looked up to see if empty tracks could have their own text and background colors [think "greyed out"]; unfortunately, there aren't corresponding colors for empty tracks.

Have you considered using a wave editing software and abutting the "clips" at zero-crossings?

(1) Do you have a bus named "Master?" (2) If so, can you expand it and post a screen shot of it? I am thinking maybe you are doing something like I sometimes do, but you left the "Master" bus in even though you are not using it. Just a guess. I believe this is why Promidi asked for a screenshot showing the bus settings. It is possible that you don't realize you can grab the divider that separates the tracks from the buses, so you can see the buses.

The last time I tried to use Jack for Windows it didn't work. Admittedly this was ages ago. Does it work flawlessly in Windows 10 and not get messed up when Windows does an update? For me, Jack for Windows was such a huge waste of time, I vowed never to spend another minute looking into it as an option. Maybe someone made it work flawlessly? If so, maybe it would be worth looking into again.

Is it safe to assume you are not using the bus named "Master" to route audio to your audio device? Also, is it safe to assume that the bus named "Master" is not routed to a valid audio output?

Not sure that I would use the Iowa Piano, but I tried it. It works. I used the link posted above, unzipped it, pointed the vst scanner to the path . . . /downloads/iowa_piano_-_64, did a manual rescan and it showed up. Note: I do not have it in either of the Windows Programs folders. I downloaded it to my Downloads folder and uncompressed it there. I then added that path to my vst scan path list. Maybe someone who is an expert on Windows can tell you if having the *.mse file in a Programs folder is part of the problem. Anyhow, hope this helps.

Thanks for detailing the debugging process!!!! You are right, any unwanted audio artifact could be coming from a least-suspected source--even ones we don't use. Clarification: I wrote the above praise before the prior post was edited to include the checklist. So, I was referring to the narrative, which to me (based on my learning style) was more helpful than checklists which people often give in lieu of the running narrative. So, thanks for leaving in the narrative and not getting rid of it in favor of the checklist. ?

"Easy" in terms of what? using as a GM/GS kits? convenience of clicking a minimal amount of buttons and getting something useful? tweaking/customizing patterns? adding loop packs? adding personal/custom patterns? adding samples from other places? tweaking samples? availability/convenience of support files (e.g., drum maps) etc. Please note: I am asking not just for clarification, but because I have started to use "automatic" drummers and am very interested in things like importing patterns from hardware/my own patterns, importing drums (samples/kits) from samplers (hardware/software), etc. BTW, you mention "midi and wav percussion loops from the ancient drag and drop desk." Are you aware that you can drop and drag audio and midi loops directly from BandLab? Thanks for raising this question; hope I'm not piggy-backing too much onto your basic question. It does seem to fit the topic, though, and if others will be commenting, it might be nice to have some of these features addressed in addition to the concerns you raised.

Also: https://www.soundonsound.com/techniques/programming-sonar-5s-pentagon-i-soft-synth. Note: the manuals I have say midi learn = shift+left click, but it is indeed shift+right click as in the SoS article.

Now you tell me. ? Seriously, not sure I stumbled onto this particular setting (Valleys), but I discovered a number of other (possibly related) issues about 4-5 hours ago--super hot resonance in spots, varied loudness from patch to patch, changes from an other versions not reflected in manuals or release notes, etc. Fortunately, almost every time a patch/setting pinned Cakewalk's virtual LEDs miles above the top, it must have been above my ears' cutoff frequency. I did hear a few, though. I think Cakewalk's audio reset button cleared the peaked meters. Also, I learned not to change patches until the sound of the current patch was quite low. BTW, when looking for a manual online that matched my Pentagon I, I stumbled onto an old trick I had read and tested ages ago--using Pentagon I as a Vocoder. On the positive side, some of the patches made me not "hear" my tinnitus--perfect for some projects I had been thinking about.

Yup. Setting the permissions in regedit did the trick. Thanks!