sjoens

Any users of Knobman know how to contact the author? I see no Contact links on his website. Problem: Since Windows 11, some fonts no longer show up in the jKnobman font list making a few of my knobs unusable.

Noticed the Demo Projects file info displayed in the Start Screen isn't consistent with actual file info. I have never opened or edited any of them yet it implies I did yesterday.

All Audio Tracks may be an alternative. Currently it seems Entire Mix is referring to the entire project length of all audio tracks within the project itself. It includes unfrozen synth/MIDI/instrument tracks and FX but no outboard sounds or outboard FX unless they are recorded onto a track 1st.

Make sure you installed the 64 bit version as most X series required separate 32 & 64 installs.

This normally works, but there are times when mystery phantom data lurks undetectably and the track or entire collection of clips has to be deleted to eradicate the free radicals.

I would assume this is intended - Start Screen follows the main GUI when opened. Another thing that happens is if an instance of Sonar is open before I open CbB, the CbB Start Screen will NOT open at all. So the two start screens are somehow interfering with, or sharing resources.

Yes. You can open CbB (or any program) by double clicking a file or project made by it. However, this method bypasses the Start Screen so it never even opens. Dragging a project to CbB when already open with Start Screen seems to ignore the Start Screen and it stays open.

Should it?

Those unfulfilled promises of a hover car?

I've never seen just the top lights (A) flashing. Normally the meters also show activity. I once reported on a bizarre instance where all the meters were bouncing up & down when the transport was stopped. It was a project glitch that hasn't happened since.

Thanks. Forgot I recently selected Generate Scan Log in Preferences. Makes sense this one waits for you to close it.

Lately VST Scan Toast messages haven't been closing after showing. They remain indefinitely. Preferences Timeout is 2 sec.

No. Colored but not color coded. Someone posted in Feedback Forum requesting it, tho.

I have Sonar 8.3 on this system so I'll have to compare it with CbB. Edit: Took 5 sec to Process>Length 200% the same 6 min clip here, as opposed to 8 sec with CbB. So CbB is slower than old Sonar, but I think it uses a different process.

Outrage out times me, but he has better system specs. Mine: Win 11 laptop Intel i7 12700H 2.3GHz 16GB ram

I repeated your scenario with a 6 min mono audio clip using Elastic Pro and it took 8 sec. However, for some reason when I tried to bounce the processed clip I got a "Catastrophic failure" error. "Process>Length" may not need to be bounced but it shouldn't flash an error either. So I slip-stretched it 200% and bounced it... took 10 sec. These times may be slower than Reaper but not unreasonable IMO. (worth about -0.2¢) There's no doubt "newer" DAWs are more efficient at handling certain tasks, but the times I'm seeing in this thread are far from normal for Sonar/CbB. Are you running Reaper and CbB at the same time? Try closing all other programs, including antivirus, before processing or exporting.

I'm curious as I haven't experienced slow behavior. Just bounced a single 5 min audio clip in less than 2 sec. Then I Exported a 6 min song with 8 audio tracks and NO plugins in less than 4 sec. Result was a 100 MB wave file. Then I Exported a similar 6 min song with 7 unrendered softsynths and 3 plugins in less than 1 min. All @48/24. Same song Exported to highest quality mp3 took 1:15 min to make a 13 MB file. Rendering, Freezing and Bouncing individual clips/tracks & plugins 1st should speed up the Export process. There may also be other background processes going on affecting the slow down.

see page 2 post 4

.

Save template with a different name. Then reinstall latest update.

Good plan. Might work if it reads the offending plugin.

32 bit Sonar scans different folders, so that could be a factor. They each hang so sporadically that there could be hardware issues to blame as well. Sometimes I have to reboot the system several times before everything plays right together.

No doubt. In this case Sonar is the victim, as I go b&f between 32 bit Sonar & CbB for older project migration and Melodyne 4 usage. (Melodyne 4 won't run under 64 bit Win11 & Melodyne 5 has no 32 bit version.) Both have "Automatic Background Scan" checked, but of course, Sonar does not have "Generate Scan Log".

At least one reason for Sonar is upon initial startup when the VST Scan "Toast" message gets toasted & stops responding and hangs indefinitely for some reason.

The Console strip Patch menu needs attention as well. It gets cut off at the bottom.