OutrageProductions

Find the file in Windows Explorer, RMB to properties and see what the OS reports as duration.

Right Mouse Button

NOAA kinda messed up the forecast.

The options are available if you RMB in the Articulation lane or on any selected (set of) Articulation(s).

I went out on the deck late last night (I live in northern Puget Sound) and saw the strangest cloud striations ever... looked like a spider web with a center porthole, green & red. Turned to look north and saw the display. Very cool!

It's the top one "Bus Output Volume"

Select all notes that you want to effect in either TV or PRV and using the Event Viewer Module [on the Control Bar]; click in the <duration> field and enter 98% (or similar) to shorten all data by a few ticks. This works well for notes that are quantized and/or justified on the same number so they don't overlap each other.

Or take up a vocation that requires less stressful effort, like basketweaving or fingerpainting. Audio Engineering & Production may not be in your wheelhouse because of the required skill set.

CbB will throw up a warning against using 'fake' ASIO drivers like ASIO4ALL, Realtek, and other generic drivers that create more problems than they solve. Only use bona-fide genuine ASIO drivers from the I/O device manufacturer. For ex: some low end Behringer interfaces use ASIO4ALL claiming it as a true ASIO driver, when it is not.

When installed and set up correctly, Komplete Kontrol works perfectly in CbB. I use over 60 instances in most of my templates without any issues. You must have (as Glenn noted) something in the Prefs (Control Surfaces or Metronome section) that is triggering a false start.

Any recent DotNet or Security updates to the OS coordinate with this onset? [DotNet would have a large part in the way your slave VSL libraries are passed back to the master DAW]

Found this in the back of my High School yearbook: probably not playable anymore, but still...

If you RMB in the left side of the track view, the context menu has 'Insert Instrument'.

@Terry Kelley I have orchestration templates with up to 120 VST instances (each an individual articulation) [of NI, E/W, & Spitfire for example] running, usually, at ~10ms latency. After about a dozen 'live' tracks I will start to get some "popcorn" snits, and will either start freezing instruments that are (near) complete, or increase my buffers to about 20ms. I never have to go above 33ms, but have just developed a workflow that will freeze/thaw quite often as the composition progresses. Seems to work for me, as my machine has some pretty serious horsepower under the bonnet. I've never really had an issue with that process.

Less than the amount of time wasted on reading this thread.

You might want to read up on the "Auto Focus" & "Auto Lock" button functions in the top right corner of the PRV. I cannot recreate your issue when those are properly adhered to.

You're welcome! When we started the Control album with Janet Jackson, she was very timid and shy and always tried to sing with her head sunken into her chest. Made her sing up and out and now the album speaks for itself. Altho she still preferred being in a completely dark room for ambience. ?

While this is certainly a worthwhile suggestion, it is kind of a Windows Julian extension naming convention issue as well. If you name a directory as 'filename.pdf' or 'filename.exe', and then stuff an identically named file inside it, Windows will throw up in your lap during a search, and log some strange stuff in the admin events. It's much safer to realize that the VST's are easier to scan when they are at the expected nesting hierarchy.

I have quad monitors and know that I have to be smarter than the computer. It's not the job of the application to do your housekeeping work for you.

Whenever making a change to preferences, click the apply button... prefs window will disappear & reappear, then click on close. At least in my experience.

I didn't see you click the "APPLY" button in the "Manage Workspaces". Are you using only one active monitor? Have you tried to resize the app to see if PRV is floated & opening behind it?

IIRC; there are "Workspace Options" on the context menu... that allows inclusion/exclusion of certain modules & windows. Check there. PRV may be turned off. [EDIT] With a project open, go to the "Workspace" drop down menu, select "Manage Workspaces", in the "Show in GUI" box, expand "Views", and make sure that PRV is checked. Over the years, upon an update, I've found that sometimes things get reset in a strange way. Not a bug.

As a film composer, I would be lost without Eventide Blackhole. But it's not for everybody, nor is it cheap.

Details & explanation begins on page 1325 of the PDF manual, which can be DL'd from the first post in this THREAD.

CbB has had similar issues with other (but, strangely, not every) plug that gets installed into a nested folder with a vst[3] in the name, like Spitfire BBCSO Discovery and several others. Simplest solution is to move the plug executables up and out of named subdirectory, and delete the offending directory. FWIW; I've seen this same issue occurring in a Protools vst scan path as well, but not with AAX plugs. Stranger things... I've not seen this problem in my Cubase 13 or Nuendo 13, so I'm thinking that Steinberg has a secret that they aren't letting out to other developers about the way they parse naming conventions.