Promidi

I use patch change events all the time for my outboard Yamaha gear (SW1000XG). The majority of my client projects are saved as MIDI file (can be type 0 or 1) I never have any issues with Patch change Events in MIDI files with Sonar. I make sure any MIDI tracks have the initial patch set in the MIDI track’s inspector. Any subsequent patch changes are in the track itself (if required). When a MIDI file is loaded into Sonar, it processes each MIDI track as follows. The first Patch Change event encountered in a given track gets placed into the MIDI track’s inspector and removed from the track. Any subsequent Patch Change events in the MIDI track does not change. This occurs for type 0 and type 1 MIDI files. (I tested this).

It does. I use Workspaces and screensets. My screensets are always locked. For all Workspaces I use ,I configured them not to saved screen layouts. That way, the windows layouts present in Screensets prevails. My big time always displays at the size I want. If I ever want to change the the size of the 'Big Time' view, I would · Resize the 'Big Time' window. · do a quick Unlock and relock of the Screenset. · Save the project (or Project Template).

However, with software, I am ok with paying a reasonable price for the R&D that goes into creating new features for the next version (EG LL EP4 to LL EP5)

It's a bit like inkjet printers. They pretty much give you the printer - but charge an arm and a leg (and sometimes the odd kidney) for the inks.

At least AAS have decent discounts for their expansions. I have many AAS expansions, and I have only grabbed them when they have been on sale (even cheaper at JRRSHOP with the GROUP or FORUM code)

I know this sort of thing has been brought up before, but this makes me wonder, who would ever pay $US179.00 for this when it goes for $US30.07. One can for forgiven for thinking that the $US30.07 is the actual intended price.

I suspect that CV-3 will be later than 3.0.0 (It might even be up to v3.3.0)

As that after collating and reinstalling your products. Remember, for some of my synths, the downloaded versions were later than what was stated on the website.....

According Sonar’s local Help, Sonar “is compatible with ARA 2 plug-ins”. See Sonar’s local help > search for ARA under the “Search tab” (Web help does not mention ARA2, local help does) As well as writing to Prism's developers you might also want to drop a note to Sonar support. https://help.cakewalk.com/hc/en-us/requests/new

BBC Symphony Orchestra has been updated to version 1.11.6 Open the Spitfire Audio App and use the Repair function to update your library. Changelog BBCSO Plugin v1.11.6: Fixes: Fixed an issue in settings menu where items would be cut off Fixed an issue where Error #3 would appear when loading a plugin or project with Rent-To-Own Fixed an issue where the Technique Editor would crash saving twice in the same session Fixed an issue where Techniques would not visually be recalled when loading user presets Improvements: UI loading and general speed Audio Mixer performance to prevent any freezing or sluggishness when moving the slider General quality of life improvements Important note: Users will need to repair their library in order to apply this update - please ensure you repair all installed sections of your BBCSO product in the same repair session (incl Piano if you have purchased this) to ensure they all show up correctly: See: https://support.spitfireaudio.com/en/articles/13169200-bbc-symphony-orchestra-plugin-v1-11-6-changelog

Some Applied Acoustic System synths have been updated. Some Applied Acoustic System synths were updated to versions than what the website states exists. I just downloaded the installer file for all off my products from my Applied Acoustic System user page (I used the single installer for all). Here is a list of the synths I own licences for and what versions they were updated to. Chromaphone 3 v3.2.0 Lounge Lizard EP-4 v4.4.4 Lounge Lizard EP-5 v5.1.1 String Studio VS-3 v3.3.0 Strum GS-2 v2.4.4 Ultra Analog VA-3 v3.3.0 Objeq Delay v1.3.4 I am not sure about CV-1, CV-2, CV-3 You can download the installer file for all off your products from here: (Of course, logon is required) https://www.applied-acoustics.com/portal/products/

Yeah, I was going to do that, but I thought copying the files manually would be easier (which it was). I'm so lazy.....

Seems to be the Arturia way when things like this get released.

Just a quick question. Did everyone’s Pigments 7 VST3 and DLL file get copied the their respective VST folders correctly? Mine didn’t, and I had to copy mine respective files manually from the Arturia resource folder. No biggie - just wondering if it happened here only.....

Something else must be going on there. Just tried Pigments 7 in Sonar. It adds 542148 byes to the memory footprint.

Addictive Drums 2 updated to Version 2.8.9 Update via xln audio | Online Installer Release Notes · Fixed a graphics-related performance regression on Windows · Fixed a bug that made Lock Tempo stick to 120 bpm in Standalone mode · Fixed a bug in the interaction between FX Trig Gate and Delay Tempo Sync

Do you outboard MIDI gear, use MIDI notes for your Metronome and you have no audio tracks present in your project? If all of the above is true, then the audio engine should even need to run. That is how I edit MIDI files in Sonar and the audio engine is not running. Unless you are using VST synths.

@jkoseattleDo you ever use CAL scripts that modify MIDI events?

Maybe use a ForEachEvent Loop do delete just CC12 events. (forEachEvent (if (&& (== Event.Kind CONTROL) (== Control.Num 12)) (delete))) For the whole fade out thing, I just use a script I have written that creates a fade out by progressively reducing the controller values of selected controllers while keeping the relative dynamics. This effects all selected controller and aftertouch event though, but I am sure it can be modified to just effect CC11 events. I think the lines you would need to change is: (if (|| (|| (== Event.Kind CONTROL) (== Event.Kind CHANAFT)) (== Event.Kind KEYAFT)) to (if (&& (== Event.Kind CONTROL) (== Control.Num 11)) You could probably think of ways to trim this script even further. Fade Out Controllers.CAL

I'm stumped. Other than the following: Try another audio interface if possible? Try another Windows User profile. A full uninstall and reinstall of your RME RayDat drivers. A full uninstall and reinstall of Sonar. See: https://help.cakewalk.com/hc/en-us/articles/40752689912601-Clean-Install-Cakewalk-Sonar I am out of ideas. You might also want to drop a note to Sonar Support. Mention everything you have tried so far. Be prepared for them to ask you to do the full uninstall and reinstall of Sonar. https://help.cakewalk.com/hc/en-us/requests/new

Maybe your Cakewalk downloads folder contains your older installers. %USERPROFILE%\downloads\Cakewalk An installer you are after will be over 340 meg. Any installer with a filesize of around 64meg will need a previous version of Sonar installed to update from. I am going to assume you are using version 1.1.0.004 of the Cakewalk Project Centre

Next thing I would try is, with Sonar closed, rename your AUD.INI file. It will be rebuilt next time you start Sonar. This file is in the following folder: (Make sure you configure Windows to show file extensions) %AppData%\Cakewalk\sonar\

That small number on the top left of a clip means that the clip is part of a Clip Selection Group. See: (Or Search "Clip Selection Group" in Sonar’s Help( http://legacy.cakewalk.com/Documentation?product=CakewalkSonar&language=3&help=Arranging.34.html

Is the RME RayDat the only audio driver installed and enabled on your system? Did Cubase install any audio driver (like Steinberg's universal ASIO driver) Is the RME RayDat driver a true ASIO driver and not a wrapper (or an ASIO4ALL like variant?) The way to tell if you are using native ASIO: While playing an audio Sonar project inside Sonar, adjust the Windows volume (via windows taskbar volume). If the volume does NOT change, then you are very likely using native ASIO. I am going to assume that you have uninstlalled and reinstalled the RME RayDat drivers (update if necessary).

I have not had any issues with Native Access for a while now. Is the NTKDaemonService service running? Are you on the latest version? (Native Access 3.21.1) The latest Native Access can be downloaded from here: https://www.native-instruments.com/en/specials/native-access/