Promidi

I only have bank - 0 in the drop down as well. However, you can just manually type the bank number in the field.

I just tried it here with Arturia B3 (VST2 and VST3) and it does indeed respond to patch change events. To get Arturia synths to respond to Banks and Program chance messages you need to create a as least one Playlist. Bank MSB selects your Playlist Bank LSB Selects your Song Preset Selects Preset To work out what to put in the bank field, It's Playlist x 128 + Song If you only have one playlist and one song, then Bank is 0 and just choose the preset from 0 to 127 (which is Preset 1 to 128). Remember, in the preset field, 0 is preset 1, 1 is preset 2 and so on. See: https://support.arturia.com/hc/en-us/articles/5392397216284-Program-Changes-in-V-Collection-9

Massive X updated to 1.50. Update via Native Access Release notes 1.5.0 - 2025-03-27 ADDED New Multi Compressor effect in the Stereo Effects section for multi band upward and downward compression ADDED 60 new presets (please update the Massive X Factory Library via Native Access) FIXED Browser view scrolling to incorrect column or scrolling back and forth FIXED Rare crash with Logic Pro on Intel Mac when recalling projects with certain presets loaded FIXED Multiple sound type selections disappear when selecting preset in browser FIXED UI controls sometimes not reacting to user input after host automation assigned to a Macro on Intel Macs

Some of those CPUs kick some serious derriere, and even they are having issues with Serum 2. Don't XREF have a BETA program that should have picked up these issues?

Yeah that is a bit of a bummer.... Well this is the first release of version 2. Maybe XREF will get the memo and refine the engine....

Pitch bends applied to various synths using MIDI WHEEL Events freeze fine here. Which specific synth and preset and pitch bend range are you using? Also, as above, are you using MIDI WHEEL Events using the PRV controller lane or are you using Automation to perform the pitch bend?

I tried the trial of Serum 2 here and it glitched badly here as well. I put it down to my older PC - even though, UVI Falcon 3.1.1 , Latest AAS synths (including the known CPU hog, Chromophone 3), Eastwest Opus, Kontakt 7 Full, all Arturia synths, IKM Sampletank 4....... well you get the picture.... all work well on my old rig. ..... ok, so maybe Serum 2 is a major CPU hog. I uninstalled Serum 2 trial.

Select all, then refine the selection by moving the start marker (which is called From) to where you want your song to end. Enable Ripple Edit. Edit > Delete Special and select all items, except “Shift by Whole Measures” and click OK Disable Ripple Edit.

You also might want to add a 1TB hard drive to your shopping list.

I gave the trial of Serum 2 a go and loaded PD Amazon Souls. On my antiquated 4th gen i5 3.4 ghz CPU (which can handle Chromophone 3 - another known CPU hog), PD Amazon Souls crackles badly... they will really have to work on that CPU hit. Uninstalled Note: I have Msoundfactory 17.04, UVI Falcon 3.1.1 and Pigments 6 - All of which my PC handles well. I don’t think I will be spending $AU300.00 (or AU397.00 after June 1) on Serum 2 any time soon - even if they get that CPU hit under control.

That's what I am thinking. If that's the case, keep an eye on your vouchers. BBA2 owners might be in for an upgrade price.

You sure about that? WS4 (now updated to WS4.01) has been out for a couple of weeks now....

As above. This file stores the settings configured in Preferences - MIDI - Instruments I know hardware synths are a relic of the past. However, I suspect there are still people who do use them. I believe these people would find it handy if the Instrument definitions to MIDI output/Channel configuration in Preferences - MIDI - Instruments was saved when one backs up Sonar configuration using Preferences - Customisation - Backup/Restore Settings. The “INSTRMAP.INI” file is not included when you back up settings.

The need for for hard drive space...?

Run the XLN Online installer and check activation status.

Yes, I paid $US49 for the upgrade from Blackhole to Blackhole Immersive.

I guarantee you, no one has (or should have) ever paid $US199.00 for Eventide Blackhole.

Yeah, I could have done the loopback recording of the MIDI test. However, as soon as I saw the +10 change to the +50 between CbB and Sonar, I stopped the video. As long as it's just a display issue, and even then only if not using 960 PPQ (which I have not done since 2017), I am not going to lose sleep over this one. It'll be fixed when it’s fixed.

Here is a shot video showing this issue. https://drive.google.com/file/d/1_vsRPeXIpHICjZ8cfmiJewZK-ZfYw4M5/view?usp=sharing

Preferences - Customisation - Display > Base Octave for Pitches. I use Yamaha devices, so mine is set to -2 See: http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B06

My suggestion is valid. Perhaps I was using some common DAW terminology that you may be unfamiliar with? PRV = Piano Roll View. CC = Continuous Controllers - MIDI events that do things , like adjust volume, pan, etc. Controller lane - Part of the PRV where you can enter Continuous Controllers. (Cakewalk’s user manual is your friend) Velocity - how hard (or fast) a note is played on a keyboard. This is one of the MIDI Note event parameters. The other being duration.

Confirmed here as well. I saved a 192ppq CWB file with a single MIDI track with an offset of +10 ticks in CbB. I loaded the same file in Sonar 2025. The MIDI track offset does indeed become +50 ticks. I confirmed the clock opened as 192 ppq in Sonar 2025 (as expected due to clock being per project). I opened the test file again in CbB, changed the clock to 960 and resaved. When I opened the file in Sonar 2025, the offset still changed to +50. I confirmed for this instance of the file, the clock was set to 960 ppq in Sonar 2025. Looks like Sonar 2025 can indeed change the MIDI track offset of older projects where those clock are set to a value less than 960 ppq. The reason I never saw this situation arise is that since the Platinum days, I am always used a clock of 960ppq. I do use time offsets, but when I open older projects in Sonar 2025, MIDI track offsets did not change for me.

I was thinking this as well, but then I realised this is a per project setting - this clock setting gets saved with the CWP file. Even if you save as a MIDI file, this click setting is embedded in the file as part of the MIDI spec.

This is still the stuff you will need to learn if you want to do things like this.

Please have on your agenda to one day purchase a proper audio interface that comes with Native ASIO drivers. Then you can uninstall the Magic Low Latency 2016 driver. This is not a true ASIO driver but is a wrapper that makes your non ASIO audio device present to your DAW as a an ASIO driver. Cakewalk does not like any form of ASIO wrapper software. An example of such an audio interface that comes with Native ASIO drivers is the Focusrite Scarlett Solo. https://focusrite.com/products/scarlett-solo