azslow3

For that money, they had to do something "special" 😏 Merging knows how to do that type of equipment, but "USB part" is hacked in by someone else. That is the first (and the only) interface from Neumann, also I don't know if Sennheiser ever had a company with experience in normal USB interfaces. What I think is "special" in the class of "notebook capable" audio interfaces with small number of IO is... fan... reviews mention it is not really silent... 🤔 Also build-in effects are not stochastic, no reason to record wet. I think many DMs and "DM like" audio interfaces can. DMs effects can be stochastic, so that can make sense. Recording digital EQ and Compressor (f.e. in RME) has questionable value.

Aux Tracks was introduced exactly for that purpose (a possibility to use them as buses, to visually interleave "buses" with tracks, was a side effect...). Many synths and effects produce significantly different result every time you play the track. During performing, people "adopt" to currently produced sound. F.e. all effects with slow continuous (in world time) modulation. There are DAWs in which there is a special "FX bin" which should be applied before writing track data to the disk (useful for audio and MIDI).

"Edit Node" is editing Automation Nodes. The "Level" is the value, in corresponding parameter units. Normally these parameters are not (!) MIDI. They have usual float numbers precision (way more then 100000 possible values...). For MIDI possible values are integers, 0...127 (except for Wheel). There is no hint Sonar supports CC14. But in practice CC14 is a sequence of 2 CC7. So Sonar will work fine with them, there is just no convenient way to edit the data. And the number of CC14 per channel is small. While (N)RPN will use twice number of CC messages in comparison to CC14, that is not important till you transfer that throw hardware MIDI cable. >16k of (N)RPNs are available per channel and Sonar supports them.

CWP is Cakewalk proprietary format. There is no documentation. That is one of the reasons my utilities are not open source (even so developing them for the purpose they are developed from my knowledge is allowed in EU). Note I don't recommend mention other DAWs and my related utilities on this forum... Discussing utilities useful for/in Sonar was (and I think still is) ok.

For 20+ years Cakewalk has not updated the set of "core" plug-ins. Now they are updating them. Note that some related DXes from what I remember are used in Style Dials. In the future they can consider updating "extra" plug-ins, proper locking for particular purpose (f.e. Premium or Style Dials only). I mean most old users have "normal" versions and new users better know the procedure with internal plug-ins is "a trick" which can stop working without warning in any update. It can happened it will work another 10 years, it can happened it stop working in a month. We don't know. The point these internal plug-ins are not in the official list and so can be removed/locked at will.

Style Dial knobs are normal FX Chains which use these plug-ins. For whatever reason Cakewalk has decided not expose these plug-ins directly in all bundles with Style Dial knobs. In other words, they have to have them but don't want they are exposed as "normal" plug-ins (till installed separately). It seems like "Internal" copy is the way the concept is implemented... These are "normal" plug-ins, installed separately. They can be installed from any bundle, including pre-platinum, but the user obviously has to have related license (has payed for 8.x - X3 - SPlat bundle with these plug-ins included). VX-64 Vocal Strip (only) is mentioned in the "new" Sonar changelog, so it is probably installed/installable without prior versions. I guess using "internal" versions is not a good idea, even in case that is somehow possible at the moment, the "backdoor" can be closed in any future update.

Note that in your screenshot there is a track "Kontakt 1 Main" and "Plug-Ins" list doesn't include Kontakt... So you have found tracks which mentioned Kontakt, not Kontakt in the synth list. Depending how someone defines track names that can be close to the same. Some users name tracks based on sound kind, not plug-in type. Also if the goal is find all synths, searching particular one doesn't help.

I don't know if A-Pro source code is available (not in standard Cakewalk repository), so I can just guess. Most probably A-Pro surface plug-in switch the device to control map 0 during initialization. That make sense, to avoid support busy with questions like "I set up how I want it to control Sonar, but it doesn't work" The plug-in is hard-coded to work with particular MIDI messages from all controls, when user change something that can break the logic. If the source code is available (Mark probably knows), it is possible to avoid Control Map switch. Otherwise the only way is change corresponding byte(s) in the binary, but I can't found any MIDI protocol specification for A-Pro and I don't have the controller to find corresponding command (plug-in sends a bunch of CCs and SysEx at startup, I guess one of them is switching the Map).

https://www.azslow.com/index.php?action=downloads;sa=downfile&id=104 Command line tool, for one file. But example BAT to scan current directory included. The result can be redirected to file, f.e. cwpsynth_dir.bat > all_synth.txt

I will try... may be tomorrow, but that is not hard deadline 😏

I have just tried and it couldn't find Kontakt, at least it was not listed in plug-ins. While I am not going to re-create that tool, if you write what you really want and implementing that is relatively simple (for me), I may consider to write that. F.e. a command line tool which list all synths in specified project (can be saved into file, run from a batch script which search CWP files, etc.) is not a big problem. Project management with sophisticated GUI is problematic...

I guess the confusion comes from existence of: "revived" plug-ins: info about VX-64 in Sonar 2024/2025 Revived plug-ins are Sonar/subscription locked VST3 (original are unlocked). VX-64 is not in the list (at least not yet). Original VX-64 plug-ins are from pre-platinum time. They can be (I have not checked recently, but there is no reason that no longer work) installed offline, in case the user has corresponding license and installation files (8.5 - X3).

You need to check Focusrite Loopback is enabled. In Windows 11: 1) right click the speaker icon, select "Sound settings" ("Soundeinstellungen") 2) in appeared panel select "More sound settings" ("Weitere Soundeinstellungen"). 3) in appeared panel select "Recording" tab ("Aufnahme"). Try to find something like "Focusrite feedback". If not there, right click on any and select "Show deactivated devices" ("Deaktivierte Geräte anzeigen"). Right click on Focusrite feedback (I guess it should be there), select "Activate" ("Aktivieren") (obviously in case it is deactivated). 4) you should be able to select it as input in Audacity and other programs. And hopefully it can record Sonar then. PS. You could record in Sonar because it is in the set of ASIO input channels, unrelated to windows settings.

Have you followed all steps in my last link? I mean "Expose / Hide Windows Channels" "Lautsprecher (loopback)" input in Audacity is not Focusrite loop-back input (it is WASAPI output, the feature I have mentioned before, it can loop-back record the system + apps which use WASAPI, but not ASIO). As a check, you can use steps described later, so set Input of some program in Windows audio settings to "Loopback".

It can be Will is right and you can, at least there is one report of success: But he doesn't mention if he was using ASIO in Cakewalk. I suggest you try. If that doesn't works, try disable Loopback input in Cakewalk and try again. Sure that is not going to work with two ASIO applications, they can't run in parallel with Focusrite.