Xoo

I get this error (0xc1900223) on trying to run the update - after running through the "getting ready" phase, which seems to mean "nothing wrong, try again later".   Helpful, eh?

But on re-opening the Update settings tab, I now get the same as Erik above with a nice little picture.  How cute.

Sure.  Just wanted to flag to (new?) users it's partially doable at least now.

You can revert fader changes to the previous value (right click on fader in track view at least).

Yes!

20 hours ago, Robert Bone said:

I haven't run into any UAC issues with my J-Bridged 32-bit plugins living in a sub folder to VST32, which is in C:\Program Files (x86). I have set that hierarchy up on multiple computers for years and years, with no issues.

 

I have - and I wish I could remember which plug-ins.  SynthEdit ones perhaps (since they "unzip" SEM modules into subfolders on first run)?

I'd also strongly advise your 32 bit VST2 folder to be outside Program Files (x86) - say C:\VST (x86) - so you don't run into UAC/permissions issues for "bad" old plug-ins.

However, updating 4 to 5 trashes the 32 bit install of 4 if that is important to you.

Yeah - 105 <<<<< 280!

Quiet Threadripper?

+1.

Bites me all the time (I position lock clips as a matter of course after recording to avoid accidents - I wish there was an option for this to happen automatically).

Add a new bus, select that bus for browser output and adjust volume of the bus to taste.

Core Audio?

Try setting the below in aud.ini:

[Video] 
VideoEngine=0

Or change to 1 if already at 0.

5 hours ago, John K said:

Probably missing a lot, but same thing became apparent as I went into a dead end feast amassing my gigabytes collection of reverb convolution IR's.  Got to a point where I realized that they all sound the same, just a difference in short or long.

You too then?  🙂

Actually, I do notice some difference, but usually very little (especially between IRs just differing in distance from cone, for example).

I wonder if it's down to Windows 10 no longer supporting mpeg2 (vs Windows 7) due to licensing costs?

Isn't it free anyway so this is just for amp models etc, right?

Changing the latency for ASIO drivers using the slider is a relatively new development and doesn't work with all ASIO drivers.  Click on the ASIO Panel button instead and change the latency there (it'll be reflected on the preferences page and with the slider).

There's a setting that disables IM except when recording - try that?

UPDATE: "Disable Input Monitoring During Playback"

It looks like you've got a more fundamental problem if none of these install for you.  How are you trying to install them?

Those plugins do run on 64 bit Windows within 32 bit SONAR (you'll just need to install a 32 bit version).

It's a pity CbB doesn't include a DirectX BitBridge as there are still some good 32 bit DX effects (like these) which would be nice to access, plus it would make migration easier.

Ignite do a good one (I forget the name offhand).

AMD's implementation is essentially the same.  My 6 core Ryzen can run 12 threads (and appears as 12 in Windows task manager).  From Windows' perspective, AMD' and Intel's CPUs are in this respect indistinguishable.

Yes, but it still does some funky stuff.

13 hours ago, Starise said:

I did some investigation into the way that AMD and Intel process thread information. Hyper Threading was a term coined before multi core chips were all the rage and since it was a proprietary technology AMD couldn't use it, so they use something called  multi threading instead . It is important to note that the two don't work exactly the same. Otherwise it would have been an infringement on  the Intel patents.  To be clear, this idea focuses more on the way physical cores are dealt with and not so much the the physical cores themselves. 

The fact that a cpu has lots of cores doesn't mean much if the way they are used is less efficient. Hyper threading works with a firm connection between the hardware and the software. The software has to be written to take advantage of it. While multi threading  has a similar outcome the two don't work the same from the inside.  The OS and software must be written to take advantage of whatever hardware chip /MOBO configurations are there. In the case of Intel Hyper threading I think this is a MOBO /cpu dependent thing from the get go. I'm not sure about multi threading as used in AMD architecture. It isn't the same thing.

An article I found on it HERE

 

I 

Both AMD and Intel (as do other CPU vendors like IBM) now use a form of Simultaneous Multithreading (SMT).  Hyperthreading is just an Intel trademark, hence why AMD couldn't  use it explicitly.  The silicon implementation will be different, but from the OS' point of view, they are essentially identical.

That article is somewhat confused (the comments are much more accurate!).

Press scroll lock key.  Does this do what you want (disables scrolling and then re-enables)?