azslow3

There is no separate monitoring level inside Cakewalk. Recorded level is solely controlled by your interface. Then it goes throw "Input Gain" -> FX -> (Pre Sends to buses) -> Track Fader -> (Post Sends to buses) -> Track Output. Live processing is the same as playback processing.

You first have to found what is loud, then you can adjust volume of it... 1) open "Views"/"Console View", check in "Strips" "Hardware outputs" are selected. Adjust the size of "Console" to see faders and meters. 2) move faders of Hardware Outputs all the way down. Play guitar. If you still hear it, the sound comes not from the DAW. Check direct monitoring / mixing matrix levels in your UA interface panel. If you don't here the guitar, move the faders back to unity (double click) and 2) without starting playback, play your guitar again. Check where you see meters moving. It can happened your have: 2.a) more then one track with input from guitar and input echo enabled 2.b) "pre." sends from your guitar track to bus (so track fader is not changing sends level)

"Target audio" (mp3) as well as "Source Audio" have tempo 89BPM (precisely, so not 90). MIDI file has tempo 178 BPM, so double of 89. MIDI file also include tempo, f.e. if you open it "as a project" in Cakewalk, it will set 178. If you want project in 89 BPM, you should stretch MIDI clip (not the same as trim it). Note that MIDI always follows tempo since Notes are specified in "beats", audio is seconds based and it doesn't follow the tempo. So normally when aligning MIDI to audio you start with audio, find its (precise!) tempo (can be variable, but not in this case) and then MIDI is automatically aligned. In this case, for unknown reason, MIDI was created using double tempo and so has to be stretched (precisely). PS audio can follow tempo when you mark the clip as grooved and set its originally tempo correctly. But that feature is not for your case.

This text is set by plug-in, in this case by Nektar. But I have never tried to use it with international characters. So, if you expect ASCII (english) there, it is Nektar bug. If your track names are localized, that can be encoding issue. Whatever I was displaying as status many years, as long as that was in english, it was displayed correctly. -- The only big difference in handling controllers by Cakewalk is that handling is officially documented in public (GitHub). "Most DAWs" hide it, so those who have access to it (f.e. Nektar) can write anything to users, users can't check the claim... At least in DAWs for which handling is known (Ableton, Bitwig, REAPER), the handling is similar. Nektar is controller producer which hide protocols. For Impact there is nothing they can really hide, but for "smart" controllers like Panorama that prevents 3d party developers using controllers. Even for NI controllers (which publish no technical details in public) it is possible to get the documentation. Other companies have it in open or don't prevent RE documentation spread in the Internet. I mean it is not wise accept as trues everything Nektar writes to you. They know you can't check.

May be not relevant comment, but who knows... There was CbB versions (I mean I am not sure that was fixed) where what was visible in Control Surfaces preferences was not the reality. I mean MIDI ports assignments was already broken, but preferences was still showing everything is fine. Changing port to something (+"Apply") and then changing to desired values (+"Apply"), so visible results are the same as before, was solving the problem. Also periodically checking "hidden" ports in the Windows Device Manager is a good idea. F.e. connecting device to different USB port produce "a clone", which persists till manually removed. Unfortunately devices like MIDI don't have unique IDs. The system can't be sure the same device is "moved" or new device appears when something is different (f.e. another USB port). The same for DAWs. Some software guess mapping of MIDI devices better then other, but there is no perfect solution.

PRV must be lanes aware to conveniently use lanes with MIDI. PRV in Cakewalk is not. May be some day they implement that in Sonar...

If you see "VST3", that most probably will not work. You need VST2. The problem is that Amplitube VST3 is not reacting on PC (at least for me, and as you can find in the Internet for other as well...) and Amplitube can only change to arbitrary preset using PCs. That is not Cakewalk specific. But if you want "Next/Previous" preset, that can be done by CCs (and so it works with VST3). PS. In general, changing presets "on the fly" is rarely perfect approach. That only works without glitches in case plug-in can change presets "instantly", so when there are just several parameters and everything is already in RAM. That is not the case with most plug-ins since they need to load something on preset change. And the result can be "old preset still works for a while after preset switch", clicks/pops or other glitches in sound and in some cases audio drop... So, if switch should be reliable during performance, it is better choose other approaches. One is make a preset which includes required variations and then control these variations. F.e. just some parameter. If you use completely different presets, you can have more then one instance of plug-in, each with static preset. And then you change routing on the fly, switching which instance get input at particular time. Note that consumes more RAM and CPU.

When someone has defined something which potentially can do things faster or with reduced latency, that doesn't mean everything is magically faster and has reduced latency... USB, especially USB 2+, is not limiting factor for MIDI size/speed data. Are there real tests with "USB-IF MIDI 2.0" which prove it has less latency with the same hardware? MIDI 1.0 has hardware protocol, which is slow. The throughput is limited to ~1 event per mSec, so 8 finger chord + wheel can take up to 10ms to transfer. MIDI 2.0 has no special hardware. So the difference is in "USB-IF MIDI" 2.0 vs 1.0 ( proprietary "USB MIDI" drivers could and was better then generic). All (modern) computer external communications are serial, technically all transfers are "one bit at a time". "Multiplexed MIDI stream" is defined by USB-IF for MIDI 1.0 (from 1999). Primary difference of "USB-IF MIDI 2.0" is support of "Universal MIDI packets" (UMP), which can be 4 times bigger then MIDI 1.0 packet (32bit only). 2.0 also has sections which try to address hi-speed and jitter. But as I have written at the beginning, someone has to implement all that and have a prove it "works better" in practice. Only then we can write "new MIDI has..."

People, have you ever tried to CHECK which latency compensation is applied? I mean the one you see when you open the dialog (so just randomly the first interface in the system) or the one for currently active interface? You don't even need precise loop-back test, just set huge different values so you can notice the effect easily. I don't advise keeping disturbing drivers in the system. Some are well known for influencing other drivers (especially ASIO4ALL). But many users have many interfaces and so they are all installed. And MY observation is that dialog in question always shows the same interface, independent from currently active one. And that is not a problem. May be the behavior on your system is different, but that conclusion should be from real observation... Only then there is a chance Cakewalk will try to pin and solve the bug. So far (and there was many threads about that particular setting) there was not a single evidence there are problems with it.

This particular setting is just displayed confusing way. It is technically a table with all interfaces, so you can set custom latency for any. You probably see the same list as in Audio/Devices. The dialog starts with "the first interface", even when it is not active.

I will try to extend the answer from @pwalpwal The problem is that "user preset" content is not something standard. It is up to particular plug-in to define what it is and how to use that. The problem is even more complicated since there can be several ways to save "preset", even for the same plug-in. most "compatible" way is to use plug-ins own export/import, when it has it. But there is no warranty everything will be included, some parts (f.e. samples) can be somewhere in the system and so not included into such preset. Plug-in on the same computer will (should...) be able to use the preset in another DAW. Note some plug-ins can't load preset saved in VST2 into VST3 (and some DAWs no longer allow both formats working in parallel). Still, when that method doesn't work, other will most probably fail as well. DAWs have own functionality exposed to users to "save/load preset". In standard formats (.fxp/.fxb for VST2, .vstpreset for VST3). Sometimes the first options doesn't exist, than this one can be tried. obviously DAWs save "preset" into projects. But here the fun begin. It seems like the way particular DAW does that can be sufficiently different between DAWs and even from exposed to the user "save/load preset" in the same DAW. I mean resulting "preset" can be different, even when format is the same. When the result of Cakewalk way is "compatible" with format expected by another DAW, CWP2Song will give you usable presets (yet, it is on my site). As usual, the evil is in details. F.e. some DAWs just have bugs in preset saving, so what they produce can't be used in other DAWs (I have reported one such bug with .vstpreset in REAPER, and it can happened it is still there). Also when DAW can load preset "from project", that doesn't mean it will be able to load it with "save/load preset" (I remember there was at least one plug-in which was happy loading saved by Cakewalk preset from .song, but was unable to use it when loading explicitly). When the number of VSTs you use is limited, just check what is working for each of them. BTW you can estimate what is included by the size of preset file. F.e. if you know you use custom samples in your preset and preset file is just several bytes, these samples are obviously not included.

As you know, many details are lost during that procedure. Just to mention some: clips boundaries / names / looping / fades (for audio) take lanes automations routing (buses and everything related) instruments and effects settings Yes, you can save separate clips manually and make screenshots of VSTs. But restoring settings from screenshots can be long and error prone. And you still have to record on which track/bus it was, in terms which track/bus was sending there and with which level. And all that can be affected by automations. Sure, since your DAW project is created "manually" it is possible write down all settings and then manually restore them. But lets face it, for any serious project that is ridiculously ineffective process. PS CWP2Song can be useful even in case you use manual conversion to unrelated DAW: it has an option to save tempo map and separate MIDI clips (structured as in the original project) as well as effects and instruments presets. If preset loading is working fine (some VSTs or VST+DAW combinations are a kind of "buggy" and can't restored such presets correctly), that is way faster then restoring settings from screenshot.

DAWproject format is not a way to get in touch with someone... Badly documented and with several general problems, it is more or less supported just by one DAW (Bitwig). The second DAW mentioned in the "official" support (Studio One) has rudimentary, almost unusable implementation. "Community" implementation in REAPER is in the same boat - that DAW ideology "doesn't fit" into format which has to be called "Bitwig project LE". I have implemented R&D quality converter from Cakewalk into DAWproject before coming to that conclusion. Into 2 of them you can convert Cakewalk projects. Not absolutely everything, but way more then DAWproject supported features. There is no "way back". But that is up to Cakewalk 😏

Have you seen Cakewalk in the Faderport v2 user manual? It is not there. Normally at that point you should extra check for compatibility. Good idea for MIDI controllers, computer components, auto accessories and everything else which potentially can be incompatible 🤪 But your controller is compatible. ------------------------------------- You have 2 options: The first is MCU and HUI modes on controller with Mackie Cakewalk surface plug-in. If you try HUI, don't forget to set corresponding option in the plug-in (and unset it otherwise). "Disable handshake" is probably also required. Not everything will work as labeled and you can't change the functionality. But till the goal is not to make "every labeled button work as labeled", that can be sufficient solution. The second is using native mode with AZ Controller: https://www.azslow.com/index.php/topic,444.0.html (note I have forgot that preset when posting into this thread 4 years ago... sorry, I never had this controller and I don't remember for which controllers I or someone else have created some preset already). In this case you can modify the functionality at your wish.

Control surface integrations are designed to send some MIDI depending from DAW status (f.e. to sync LEDs under transport buttons). Works not time accurate, but may be sufficient (default "delay" is up to 75ms, can be reduced to 25ms). If you can't program in C++ (using Cakewalk API), you can use AZ Controller (www.azslow.com). If you go this way, I can write an example configuration.