David Baay

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.

Assuming you use Always Echo Current MIDI Track, it's not a good idea to change tracks while performing because the synth on the track you're "leaving" can be left with stuck notes due to missed note offs or pedal-up controllers. That said, I can repro that more than the currently active track can sound when switching Instrument tracks while performing. Probably also affects separate MIDI and synth tracks but I didn't check that or MIDI to hardware synths. Also reproducible in the last release of SONAR Platinum.

Drag the MIDI file into the original project to bring the tracks in. Then either drag the MIDI clips to the appropriate track (holding Shift to preserve the start timing) or change the output assignments of the new tracks to the appropriate synth.

I find Zipping up the project folder to be preferable to a bundle file. Then post it on a sharing site and post the link here. I can PM an e-mail address if you don't want to share it with everyone. But I'll probably be going offline soon, and anyone of the regulars can probably figure it out. I'll wager it's due to project configuration and reproduceable on other systems.

I can't repro anything like this. Can you share a sample project that's doing it relatively consistently? P.S. With all due respect to my fiend, Promidi, I consider the "start at measure 2" recommendation to be largely unnecessary. Certainly not necessary for audio tracks, and generally only necessary for MIDI when sending patch changes or initial controller values to hardware modules. Like audio, soft synth output gets 'buffered up' in advance.

Possibly you're having an issue with Workspaces overriding per-project settings. I don't use Workspaces, and am not seeing any issues. Here's a quick overview of the relevant features: Comping is both a recording mode and an editing tool. Setting the record mode to Sound on Sound has no effect on the availability of the Comping tool. The recording mode is per-project and I'm not seeing any problem with having other modes persist on re-opening different projects. Having the editing tool available as part of the Smart tool is optional (right-click the Smart tool in the Tools Module of the Control Bar) and applies to all projects. When it's enabled as part of the Smart tool, it's only active when clicking in the bottom half of a lane. It's also a mode of the Edit tool, and a quick check shows the Edit tool defaults back to Edit mode when closing/re-opening a projects (the same goes for mode of the Draw and Erase tools). The recording mode is per-project and I'm not seeing any problem with having other modes persist on re-opening different projects.

As noted in the other thread, it appears the issue is at least partially that Groove Clips are "transient-aware". I believe Audiosnap Autostretch tends to work better when doing a proportional stretch at a constant tempo, regardless of the algorithm, because it just stretches the whole clip uniformly without regard to transient locations. And, of course, it allows you to use whichever algorithm works best for a particular type of material. I would just use whatever method works best in a given situation. I would, however, like to see more resolution allowed in specifying a stretch percentage (the same goes double for Process > Length which doesn't even support tenths of a percent).

"Zeroing" Modulation causes trouble with a lot of synths/patches, including hardware, because it's often used for some sort of tonal or FX control, yielding a 'nominal' sound somewhere around 64. I understand that you wouldn't want to send hundreds of individual messages to reset everything. I'm thinking that you might have just a few radio options like "All", which would still use CC121 - Reset Controllers, and then some individual ones like "Sustain Only" or maybe checkboxes for a few key ones that could be combined when "All" is disabled (not sure offhand what else might be useful). Alternatively, it occurs ot me this might be solved by doing the Searchback on Stop instead of - or in addition to - on Start. I haven't thought through all the implications of that; just "spitballing" as they say. Just having the "Sustain Only" option would suite my needs.

Two possibilities: 1. You have inadvertently enabled punch-recording of a range later in the project. 2. CbB will show "confidence recording" of events arriving on other ports/channels than the one you've assigned as Input to the track so make sure the Input assignment is matching your controller. I consider this a bug. CORRECTION: The first possibility won't be applicable in this case; it will prevent recording, but you won't see "confidence recording" events until you get to the punch region. I'm pretty sure #2 is your issue.

Just to clarify a bit: All Notes Off used to be sent by default; having it off by default with an option to enable it is new behavior. Also note that in a synth with a proper MIDI implementation, a pedal down (CC64 > 63) message will override All Notes Off (CC123 = 127) so you additionally need to have Zero Controllers When Play Stops enabled when working with tracks that use sustain. (the one exception I know of is TruePianos which does not honor the standard and will not keep sustaining when it gets All Notes Off). Also I should mention that a common casue of stuck notes in CW/CbB historically is having the VSTi inserted in the FX Bin instead of in the Synth Rack. Using the FX bin to get the synth audio into the track is supported for compatibility with projects that used that legacy configuration but is not the preferred setup. And, finally, since @msmcleod is watching, I'll re-iterate my longstanding request to be able to enable Zero Controllers selectively - e.g. only for Sustain - so that synths that use Modulation and Expression controllers for volume control (e.g. Garritan JABB/GPO) don't go silent on Stop. Having appropriate controllers for Searchback to find helps on restarting playback but it doesn't address the need to be able to rehearse with the tranport stopped. The only option in that case is to disable Zero Controllers.

Your slashes are slanting the wrong way.

https://www.bozdigitallabs.com/plugins/ Love my T-Bone.

It's part of the Notes tab in the Browser now.