David Baay

I'm curious what the use case is for this.

The display of the "Comp" clip in the parent of an audio track is optimized for Comping where the signal from only one lane is unmuted in any given area, and the muting/unmuting is controlled by "promotion" with the Comp tool as reginaldStjohn suggested. In your case, the clips aren't "Comped"; they're 'layered' in sound-on-sound mode. In that case, the clips are shown layered in the parent; it can be a little unpredictable which layer is on top, but in my experience, the clip in T1 tends to take precedence. If you were to swap the clips between lanes, you would see the muted section in the parent track.

Hmmm... Okay, yes I can replicate that. I was not aware of Ctrl+Alt+Spacebar.

Are you playing the keyboard using Local Control or by echoing MIDI through a track in CbB back to the keyboard? If the latter, raise the MIDI Volume to 127 to ensure CbB isn't lowering the volume via CC7 messages. Then check what the track meters and numeric indicators show for peak level when the track is armed to record and you play some big, high-velocity chords with a piano sound. You should be able to clip the signal. But if you reset the meters and play a quiet, monophonic line it may well be down around -18dB or less. It's possible to zoom out the scaling such that a lower level signal like that will be nearly flatlined. Double-click the dB scale between the track and clips panes to reset it to default.

I kind of like this idea except that it violates the convention that a grayed-out object isn't available and can't be changed, which could be confusing to to noobs. The parens around the value are enough for me but need be replicated in the Inspector.

I'm not seeing that. Just to clarify... Shift+Spacebar (not Ctrl+Alt+Spacebar) is the default binding for Audition, and it depends on having some selection made - usually a measure or more in my workflow. Alt-Tabbing away from CbB is not causing the selection to be lost in my case so Audition still works when I come back to it. Are you generally seeing selections lost when you Alt-Tab away?

I agree although I saw another post recently requesting that Delete not be at the top of the FX bin context menu, so different users have different opinions about this.

I mostly use keyboard shortcuts for these operations in CbB, but so far as I know, this change in Windows Explorer does not affect context menus within CbB or other applications...?

Oops. You've reminded me that a change was made some time ago that broke/eliminated the previously default bindings of Tab and Shift+Tab. To have this work now, you have to custom bind Tab to 'Audiosnap Go to Next' and Shift+Tab to 'Audiosnap Go to Previous' in the Global context. This works in the PRV as well, incidentally which is where I use it most. And if you don't select a note, Tab and Shift+Tab will still move the Now time, but won't audition the the note.

I'm a pretty old dog, and I pretty rapidly got used to the new cut/copy/paste/rename/share/delete icons.

It doesn't really make sense to create and Aux track with nothing routed to it. To me it makes perfect sense to create it by assigning a send or output from a track to a New Aux Track. I'm not really sure what you meant about having to do a lot of scrolling...? EDIT: Ah, I see you're talking about scrolling through the list of existing buses and aux tracks to get to New Aux Track. Seems putting the New options at the top of the list would solve the problem.

I'm not immediately finding the thread reference, but I recall something like this being reported about TTS-1 in the past. You might try increasing/decreasing your MIDI Prepare Using buffer. I believe the default is 50ms and both too low or excessively high can cause issues. And be sure to insert TTS-1 in the Synth Rack rather than in the FX bin of an audio track. Not many users doing the latter any more, but I mention it because it can also cause issues like this.

My Chrome browser is up to date but does not have anything like this path in Settings. After much poking around, I found the following: Settings > Privacy and security > Site settings > Additional permissions > MIDI devices > Don't allow sites to connect to MIDI devices

In any case CbB should always detect the driver coming and going from Windows Device Manager and prompt you to switch to another device (if available) when it goes away or re-add it when it comes back. If it doesn't, and the above recommendations don't fix the root cause of it going away in the first place, you might be able to reset by disabling/enabling the driver in Device Manager.

I agree the font-switching is troublesome, but if it's not going to switch I'd like to be able to set a slightly larger font size for my old eyes, especially when working on the laptop.

Click at the far left of an event to select it (black block in the first column), then Tab to step-play notes one at a time or Shift+Tab to step backwards.

Other deals available at PluginFox as well but this is the one that brought me there - $130. A highly rated pianist's piano, prized for its "intimate" sound and low noise vs. its primary competitor, the Garritan Abbey Road Studios CFX ($159 at Sweetwater) which I also considered. Just over 18 hour left as I write. I bought it based on reviews but have not yet had a chance to load it up and check it out. https://pluginfox.com/products/vi-labs-ravenscroft-275

I’m just telling you nothing is likely to come of come of such an amorphous request, and you need to clarify the steps to reproduce specific issues. It’s up to you to do it or don’t do it.

I suspect a good number of editing errors like this might be due to corruption of the undo stack. Unfortunately this can make it extremely difficult to reproduce the full sequence of steps to demonstrate the issue and the bakers are unlikely to find the root cause without it. “Overhauling” is not really applicable to software. You either make a targeted fix or you re-write from the ground up which is likely to result in more bugs than it fixes.

Sounds like you might have set a non-zero value for fade on start in preferences.

Check your MIDI Prepare Using Buffer (Preferences > MIDI > Playback and Recording). Default is 50ms IIRC. Lower can be problematic and higher may be necessary for some synths in some projects.

One nice thing about Modartt is that the additional cost of an upgrade is just the difference between the two versions so it costs you nothing to start basic and upgrade later. But the current sale prices are better than during last Summer's so you might have to wait a while to get to upgrade at the same total cost. The added flexibiity of Standard is quite desirable in my view and it can import modified "FXP" patch files developed by other users in the Pro version that Stage cannot. I bought a license for v7 Standard from the original owner for a little less than the current sale price. I upgraded to Pro in the Summer through JRR for the same $100 it would cost now, and because I did that within the last 12 months, I got the upgrade to 8 for free. Modartt's pricing and license transer policies are are very fair compared to some.

Not that this is any kind of an overall solution, but you might save yourself some grief in the short term by Edit > History > Clear after adding SpectaLayers so it won't be removed by Undo.

The 'A' in the icon indicates 'Always Echo Current MIDI Track' is enabled in Preferences. To my mind, it's expected behavior in that case that you can force Echo On but you can't turn it Off on the currently focused track. However, I'm seeing that you can turn it off in the Console view and that will persist until you move focus to another track and back. I would say it's actually a bug that you can override Always Echo in the Console view and turn it off. I checked the 17.10 release of SONAR, and the behaivor was the same there. I think this inconsistency has been brought up before, but I'd have to search.

Any .MID file you drag and drop into an open CbB project (from Windows Explorer or the Media Browser within CbB) will yield a new MIDI track for each track in the file (assuming a Type 1 MIDI file). If you have hardware MIDI ports in the system (including a "GS Wavetable" synth if enabled in Preference > MIDI > Devices), the output of the new tracks will default to the first hardware MIDI OUT. If you have only virtual ports presented by soft synths, the track outputs will default to the first soft synth. Based on everything you've said, it sounds like maybe you were using your soundcard's wavetable synth for output before which should have worked fine. Really I can't think of anything that would make only the drums go silent. If it were a channel problem you would typically hear the drum MIDI rendered by some other instrument sound. In any case, it sounds like you are now understanding MIDI and synth I/O routing and have it working.