Xoo

This is a good article (I think) about the why's and wherefore's of SMT/HT: https://bitsum.com/tips-and-tweaks/why-you-should-not-disable-hyper-threading-or-why-you-should/ Scheduler and architecture has changed: previously, Windows had a "habit" of using logical cores on the same physical core rather than spreading threads out over logical cores across physical dies.

That's true but within a CPU with HT on, the 2 "cores" are sharing the same hardware.

But there is no physical core (as opposed to logical) as such - a physical core has 1 or more logical cores. All logical cores on one physical core share the same physical hardware, registers etc and to communicate to the outside world.

Citation for this? From a Windows perspective (slight simplification), there are just cores, not virtual (logical) and physical, so it can't assign a thread to a physical core as there's no such thing. A bit old, but clear: https://techgearoid.com/articles/difference-between-physical-cores-and-logical-processors/

There's a phrase for people like you who have studios like that... ?

That is exactly what Freeze does (although on a track, not a clip) - it converts the MIDI+softsynth into audio.

From memory, it's a permissions issue with UAC, because the files are saved in a Program Files subfolder. You either need to run as admin (try not to!) or use the drop-down menu at the top of the window to save presets.

If you have changed the default double-click option for MIDI *clips*, the double click on a blank area of track doesn't work to open PRV:

I'd definitely agree with this.

Ah - the old IBM Manual feature.

Given that clip automation does do gain automation, I'm finding it hard to understand what you're after. Can you expand?

At that (high) buffer size, I wonder if it's a case where CbB needs more memory allocated - there's an aud.ini setting that changes this for plug-ins, but I forget the details (ExtraPluginBufs - default 0, I believe). Might be worth digging into that?

No error code, it just (still) says it's not suitable for 2004.

And no PACE driver on my Melodyne 5 machine.

Under 2 seconds here for the CbB 16 track template. AMD Ryzen 5 2600 (6 core/12 threads), stock speed (3.4GHz, but it boosts itself to ~3.75GHz all the time), 32GB RAM, NVMe Windows/application disk, SSD (Samsung 860 EVO 250GB) data drive, 2GB nVidia GT 1030 video card. So nothing that special (for 2020!). Windows Defender realtime scanning disabled completely.

Did you hear about the man who had his house made backwards so he could watch TV?

And, from memory, you can change the filter on multiple tracks using quick grouping.

My bad terminology - I don't mean driver interfaces, I meant using different "driver" APIs (sure, they're not all drivers in terms of pure Windows nomenclature). Rather than having to interface to ASIO, WDM, DirectX, MME, WASAPI, just write an ASIO interface layer and pass the buck to an off-the-shelf translation layer for non-ASIO soundcards.

Do you mean this setting in aud.ini? AutomationDecimationMsec=50

Saves them having to write multiple driver interfaces - they just write an ASIO interface and let ASIO4All etc handle the wrapping if a real ASIO driver doesn't exist. Makes a lot of sense from a coding perspective (especially if you're primarily aiming at "pro" users).

There is a hacky way round this now (although manually entering is a good idea) that may work: Change the project tempo to what you want the clip to be at (let's say 100bpm) AudioSnap the clip Open the AudioSnap Palette Select From Project - tempo set at 100bpm Change project tempo back to what it should be Note that tempo stays at 100bpm in AudioSnap Palette

Check that your Workspace (Lens) does not exclude video view.

*Vice* President, surely?

Agreed - just pointing it out for a quick (if not free) fix.

Ah - I was referring to plugins. Fair enough.