OutrageProductions

FYI; the only version that will still authorize is 2023.09.075 AFAIK. The auth servers for previous versions have been taken offline. If your Win7 is x64bit version, you may be able to upgrade and run the last version.

Unless I'm totally mistaken, the MIDI channel Input Gain knob is (sort of) unique to the DAW and does not have the availability to be assigned or automated by a MIDI CC#. Same thing with an Audio channel Input Gain knob. This may explain why they are trimmed in bipolar values. Generally they are set for gain staging and left in static mode. They may have some undocumented control available using CC 96-101, which translate RPN data to NRPN controls, but I can't find any detailed info on that. Probably only the Bakers know the bit/byte data stream for those encoders. The Buss input gain & pan DO have automation CC's available in addition to the output fader & pan.

Ah yes... signal convolution and the pan laws.

Test it either way. I always have mine <unchecked> so that it will always pick up LFO mods exactly where they are set upon playback. Or if any CC is only written starting well into the cue, it can think that CC is at zero from the beginning and really mess things up. Although it can have strange effects on any synth patch that is an evolving or self modulating soundscape like Reaktor or Pandora. YMMV. It's not out of the realm of possibility that it truly was just a glitch. But now if it happens again, document & reproduce if you can.

@David Baay Velocity (as with all MIDI CC) has a 0-127 range. If you dbl-clik on a MIDI vol fader it will reset to 101. If you dbl-clik on an audio fader it will reset to 0dB. Only RPN/NRPN values have bipolar values (-8192 to +8192, zero null) like pitch wheel.

MIDI reset has never affected my volume fader levels. Check the setting in <Preferences><Project><MIDI><Zero Controllers When Play Stops>

That is totally dependent on the VSTi plugin, it has nothing to do with the DAW. Some plugins can be resaved in their initial state with an instrument/preset initiated, but a smarter way to do it in CbB is to save an instrument track with a VSTi loaded into it as a track template and load it instead.

The secret is to have your download folder location open alongside NA when running the DL/Install procedure and catch the ISO file just after the DL completes and during the install operation and quickly grab and copy it to another folder or drive. I have the installers for every NI instrument that I've ever DL'd using NA saved on an external drive.

Well... back in the prehistoric era, those of us that make a living at this stuff... discovered these things referred to as "pencil" and "paper".

It's definitely not a bug(!) or the rest of us that use it every day would be going bonkers. 2023.09.075 is the latest (and final free) build, released early October, '23. Many of us got a renewal authorization prompt in the first week of January, usually with no issues. Most likely you have some trash in your registry. Try to clean it out and see if the problem resolves on your system. Also check for maybe a few too many ShadowCopies (Windows Restore Points) and eliminate all but the latest 2 or 3.

Redacted (duplicate)

FYI; the only version that will still authorize is 2023.09.075 AFAIK. The auth servers for previous versions have been taken offline.

I had the activation toast pop up yesterday, it said "activation complete" and faded out in about 5 seconds.

It's Mackie MCU compatible under Windows, so install it as a control surface using the Mackie template.

We're in the midst of the sixth mass extinction on the planet... why sweat the small stuff??

You asked about the pad sound on the fade-up intro to "Another Day in Paradise", just before the stick cliks enter.

On the original album release and support tour, one of the pads (they are layered) just before the sticks start the click were done on a 1990 tour with an Oberheim OB-8. (I knew the keyboard tech from those days.) That airy pad is pretty easy to emulate with any other modern synth.

Try it with and without the "Disable Handshake" setting ticked in the Mackie Control preferences page (as posted above).

I rarely have anything 'hang', but if you have clean memory, Kontakt/UVI/VSL Syncron/Komplete Kontrol can take a few (5-15) seconds to load and initialize without any instruments loaded on a new project, but reloading the same project or even a new project is inevitably faster because they are already cached. Never bothers me, cuz I know what is in ram at the time. If I'm changing from one huge project to another in the same studio date, I will flush my ram between sessions with a batch file, and I always expect the load to take maybe 20-30 seconds anyway. No biggie in my world.

<Preferences><Audio><Devices> needs to have both an INPUT device selected and an OUTPUT device selected. The preferred device needs to be set as the timing masters in <Preferences><Audio><Driver Settings> as Playback/Record Timing Masters.

Check in <Preferences><Customization><Editing> that all the settings are as you desire. Also check the status of <Ripple All> command in the upper right corner of the Track View. Explanations for these settings/functions are covered in the Help system or the PDF Manual.

Without at least one autosave version available, you are probably out of luck. I've only had that happen a few times in 30 years, and never got the files back from the original.

Here's an old article written by one of our own bakers; https://noelborthwick.com/2017/04/20/wireless-audio-and-midi-in-sonar/ It gets pretty deep into the weeds, but may supply some information for you. It appears as though UWP was built mostly to bridge Bluetooth devices to the Win kernal so that they could be used in a DAW as a native device. MME is legacy, but if your MIDI devices operate correctly using it, then don't worry too much.

These screenshots clearly show that your MIDI driver is set to MME, and your Audio Driver is using ASIO. They are two completely different things. Nothing to worry about.

I was an adjunct marketing advisor for NI in 2017/18 on the development of the S series Mk2 keyboards (before the Venture Capital buyout) and I could forsee then that they were about to completely diverge from the direction that was common amongst their users. Real pity, they were really a stong market leader for a decade. When I got the preview of LoRes, I thought it was grossly underwhelming for a 70Gb library.