azslow3

Sorry of off-topic... I have high-pitch noise from my Z390. Not from fan (I have not found any), but still annoying (from googling that is common). And I wish my TDP 95W CPU consumed that 95W by default. My (middle size) air cooler was unable to keep CPU any cool when I was running my fist PRIME95 test... I was disappointed (by the cooler), till I have found that CPU power consumption is over 200W (with all BIOS "defaults"). I mean it seems like "TDP" has no meaning these days (my 9900K consumes from 10W to 250W at its own will, till limited explicitly).

MPK261 is a flexible device. You can configure what and how each control sends. There are predefined presets for different DAWs, controls are set to send different messages in each of these presets. For ACT MIDI configure (or find existing configuration) all controls for sending CC messages. For buttons use "momentary" mode. You can use "relative" mode for knobs, but you need to set parameters properly in ACT MIDI then (in addition to control learning), also they can appear "too slow" for you in that mode. ACT MIDI and Generic Surface do not show messages they receive. You can "record" controllers as normal MIDI clip and then check the recording in Events List mode. You can also use MIDI-OX (with Cakewalk stopped) or AZ Controller (inside Cakewalk) to monitor incoming messages "real time".

I have mentioned the whole known set of "supported" keyboard controllers: Roland A and Nektar Impact. Both are limited as hardware (f.e. no encoders) but the integration was provided by the companies. I write "was", Roland is no longer affiliated with Cakewalk and all Nektar's powerful controllers do not support Cakewalk. But MPK261 is not a bad choice for controlling Cakewalk. It has capable hardware. The only problem the solution is DIY. So you will need to invest a bit of time to make it work. Depending from what you are ready to sacrifice: you want transport buttons and 24 tracks (with ABC keyboard banks) Volume+Pan+One switch per strip (Mute OR Solo OR Arm, etc): setup Generic surface plug-in. you want overlay the right part section (8 encoders + 8 faders + 8 buttons, NO transport, NO ABC banks) for mixing, controlling plug-ins and executing commands: setup ACT MIDI plug-in. you want all controls, overlay functionality, LED feedback: you will need AZ Controller. First two options you can get up and running within an hour. Set MPK261 to Bitwig mode and follow Cakewalk PDF I have mentioned. For the third option you start with mentioned preset, that should work out of the box. To extend it or change the functionality you will need to spend significant time (days or even weeks) and without background in programming I would not recommend diving into complex modifications.

Original documentation describes both plug-ins (pages 1215-1228): https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf If in addition you want to know how all that works: http://www.azslow.com/index.php/topic,107.0.html Well... MPK261 does not "fit" into standard plug-ins functionality. M-Audio support some DAWs, but Cakewalk is not in the list (not a surprise, only Roland and some Naktar keyboards are Cakewalk aware). You can start with: http://www.azslow.com/index.php/topic,393.0.html as stated in that post, I do not remember which MPK261 mode should be used. If not Bitwig, that should be some other standard preset. And I do not remember what this preset does nor which MIDI IO should be set. But it definitively recognize ABC banks and most controls do something useful ? General installation you can find in "Manuals" section / Videos linked on top. (the preset was created long time ago and remotely... I have never touched real MPK261)

Great work! Special thanks for detailed information concerning fader calibration. I have made my preset strictly "remotely" (not seeing/touching the device), so I was not aware such problem exists The only general suggesting about functionality: original Mackie was using "direct" API for controlling plug-ins, there was no ProChannel but (fixed positioned) "effects". Cakewalk has switched to ACT mapping approach at VS-700 (and other Roland surfaces) time. There was nasty bug in maps saving for several years, but last Platinum and CbB do not have it. I mean uniform way to control Synth/FX/ProChannel and standard control learning procedure is better (AutoMap, NKS and VIP use the same idea for controlling).

It sounds more an more you simply have a problem with cooling. To rule out audio interfaces, Cakewalk, etc., you can try to run PRIME95 (I guess your system will shutdown within several seconds...). But better follow the advise from Slartabartfast, before doing any future tests. "Low multicore load" normally consumes less power then one core doing the whole job. That is why you could observe some difference after "balancing" the load using Cakewalk settings. But that is not a solution for your problem.

"Open CbB" is too complex operation for computer, to get reasonable advise you need to localize the source: Open CbB with EMPTY project. Turn off audio engine. Minimize it to the tray. Any CPU use from it? Step by step, checking significant CPU load increase: Maximize CbB Add several audio tracks without plug-ins, up to your usual number of tracks in the project Start audio engine (if not started by tracks) Add some audio clips Start playback Add plug-ins Load your usual project Once you notice CPU load, independent on which step, try minimize CbB and then change audio device to build-in. That should point which part of the system/CbB triggers high temperature: plug-in(s), graphics, audio interface. Sorry for repeat, but from all your previous observations it seems like your system is "fine tuned" for low multi-core load only. I mean if full powered single core overheat, full powered all cores will switch your system off instantly. Can you run PRIME95 for a half an hour? I guess not, and that is looking for troubles. FX-8350 is an "old world" AMD CPU. Every surface micrometer has to carry the heat out from TDP 125W to keep "max temp" under 61C. May be it is time to re-mount the cooling head. For comparison: modern AMD CPUs have TDP 105W (real ~150W) and "max temp" 95C. That is obviously way simpler to keep under control. My own system is Intel based, ~40C idle. It runs ~70C when "test loaded" under TDP (95W), I can keep it under 85C with power limit 170W. Without limits it can consume up to 250W and my "small" air cooler is unable to deal with that (I have only one case fan). All that without any "manual overclocking", modern CPUs overclock themselves by default...

Is that happens with or without plug-ins? Can it be you had some changes in plug-ins you use (updates or simply changing settings)? As correctly was mentioned by Oleg, CPU consumes different power based on activity. In my case (i9), "100%" CPU tests can consume from around 90 up to 250W (if not limited...), depending from what these tests do. Since you mention some interference with graphics, check/update your graphic card driver. F.e. graphics can switch into "software" mode with bad drivers. In any case, if your system can hit thermal limit something is designed/set/assembled incorrectly or broken. No software activity should be able to overheat correctly build system.

As long as you wrap plug-ins in question into NKS, I think you can control parameters using Komplete Kontrol native methods. If I remember correctly, there is still no "deep integration" for these keyboards into Cakewalk (so there will be no "automatic track following"), but it should work for the purpose. In MIDI mode you can use Cakewalk feature called "ACT" ("Plug-in dynamic mapping"). It is available in "ACT MIDI" and "Generic Surface". "ACT" term is also used for surface API in general, so a bit confusing (but "ACT" button on top of plug-ins is for "Plug-in dynamic mapping"). You can easily find many guides in the Internet (and that feature is described in the standard documentation). Plug-in dynamic mapping works for any plug-in in focus (FX, Synth, ProChannel). Finally you can use ACT map in AZ Controller. You will find many posts that "ACT does not work", "my mappings are not remembered", etc. But that is more for older versions of Cakewalk (there was one nasty bug for several years). And you can move to the "safe side" by using "AZ ACT Fix" (usable with all surface plug-ins) in case you still hit some problems with mappings (or just for convenience... there is no build-in feature to "clean" automatically created and hardly unusable maps, with that utility you can clean, reorganize, backup and one click restore).

They are remembering current strips. Let say you are working with several not consequent tracks and need to switch between them. You can temporary reorder them, but that can be annoying. With F buttons you can remember up to 4 strips and switch with one button press. Note that strips can be tracks and buses. That was default behavior in the original plug-in, not my idea. I have just reproduced it in the preset.

Track/buses should switch by pressing left encoder (in plug-in/EQ mode works with Shift only, in all other modes with and without shift). That is mentioned in the documentation (and differences list for the preset). F1-F8 have "default" behavior from the documentation (save/recall current strip). F1-F4 are recall, F5-F8 (so F1-F4 with Shift) are save.

msmcleod still updating MCU and partially HUI compatibility. Except for Softube Console 1, I can not remember any new device got Cakewalk support from Cakewalk or device producer last 5 (or even more) years. That is about the hope it "will be supported soon"... Novation is publishing all technical documentation (not many companies do). Cakewalk has public surface API (not many DAWs have that). So THEORETICALLY anyone can write reasonable integration (including LEDs, display, colors and device specific controls). In practice only several new devices got reasonable integration, using AZ Controller platform. But that is DIY solution. Not many people was ready to invest significant time and effort to create deep integration. I have written the platform and created several big presets. But I no longer ready to create presets for devices I do not have.

Crashed DAW just because of some MIDI device internal mode is not expected result. It can be you have some "MIDI loop" inside your project, during surface (and other MIDI devices) setup it is better have black project loaded (without any MIDI tracks). Other reason can be some Control Surfaces in Cakewalk preferences (Cakewalk tend to mess with MIDI IO assignments when new devices are added). Finally "starting from scratch" is also an option, after cleaning all MIDI devices in Windows Device Manager and removing Cakewalk MIDI related INI files. But in case you prefer out of the box solutions, I agree that FaderPort V2 is not the device to use with Cakewalk. At least till someone make working preset and write/record installation instructions.

Classic had specialized plug-in for Cakewalk. V2 does not have such plug-in and it can not mimic Classic. There is no published preset for V2 (at least I have not seen it), but in case you put V2 into some "native" mode (so its controls just send what user is doing, without attempt to be "smart"), you can MIDI re-learn the preset for Classic using V2. That should work, except feedback (Classic designers have made a... mistake... so feedback to buttons does not match commands from these buttons. I think "Use Ctrl" instead of exact MIDI messages in the Feedback section should work for V2.) So, definitively manageable (with device in hands) but a bit of DIY. If you have no time nor willing to invest it, I can not help.

I can select types and presets in demo... I have Windows 10.

I could only test demo version and it has MIDI steering disabled...

May be I do not understand what was your problem... But Cakewalk support MIDI input for FXes directly (till some Sonar X the way was a bit "hacky", but since that time it just works). You need to "Enable MIDI Input" in the "VST2" menu (plug-in window top controls). The plug-in is then visible in the Synth rack and MIDI track output can be routed to it.

I have replied you on my site... I guess meet online and make corresponding preset(s) is the simplest solution for both of us.

ACT Dynamic Mapping is the only plug-ins control approach supported by Generic Surface. And it is focus oriented. There is different way, but it is supported by Mackie Control only. Sure, AZ Controller support both. If you do not need feedback (Generic Surface does not support it at all), following "Quick start" will take ~5min (including installation), pressing "Dup" in Options tab and MIDI learning additional controls ~10sec per control. Changing Volume to another parameter or inserting "Filter" Action between track and value yet another ~15sec per control. In total, it does not require any programming skills nor more time then Generic Surface to do what you describe. AZ Controller is way more powerful then Generic Surface, but no one force you to use that extra power ?.

I think he is using the latest CbB. And I think only people which are using REAC can say something. PS. Note that original message "style" is a kind of "Russian technical spoken dialect", that is why automatic google translation has quite strange sentences. @Анатолий Семенов Пожалуйста напишите конкретную версию Windows, REAC (и других аудио драйверов) и CbB. И пожалуйста используйте обычный лексикон, Гугл с Вашими "косяками и шляпами" не справляется. Если у Сонара когда-то были рускоговорящие разработчики, то их много лет там нет. Кроме того REAC от Роланда, они Cakewalk давно продали и соответствующую поддержку устройств закрыли (до выхода Windows 8). Так что шансов на успех мало, но кто знает...

The only important part is written in English, the man has problems with REAC in the latest CbB version. I think it is also not correct to claim that "nobody knows" the language of the largest country in the world ? Yes, it is not in the list of official languages of current "Cakewalk home". But since "Cakewalk country" has 4 official languages, I think it is ok to use different languages in this forum, no?

I think the simplest way is to use: (its 'multiple independent groups of devices' feature) With drum controllers I can not advise anything (I use e-drums as "drums MIDI controller).

Once installed, it has 6 months run time. When people "update", this period is reset. It is possible "re-activate" without update, but that is only true for Cakewalk itself. Bandlab Assistant has to be updated to "re-activate" Cakewalk. At no time this process was painless for me, automatic update of assistant was producing errors. Update Cakewalk from assistant also.... I mean in a class environment it is not a matter of seconds to "re-activate" using some low band connection (f.e. mobile). It will be quite some work.

I have touched 3 DAWs. 2 of them have no Musicradar "review", one of them was not mentioned at all (Tracktion, I still believe it is the simplest for beginners and they have free version too). Some "pro" and "cons" are questionable: Ableton has NO cons? really?; "does not come with loads of plugins", first that is not right (this does not comes with soft synthes, but the number of plugins is not small, especially when someone knows that JS is plug-in format), second they write best DAWs not best Bundles; "Mac only"/"No Mac version"... where is "no Linux version"? I do not think someone on Mac care about Windows and reversed. For 2 DAWs I know good, the "text" is useless. For Cakewalk they write nothing about DAW at all. For REAPER they mention questionable points: the interface has responsiveness problems at the moment (in "high" display) and the reason is deep in design. And it is not "most affordable" DAW: it is not free, commercial price (they mention "From ...") is relatively high. I understand finding deep technical advantages and disadvantages is not easy. But in any serious ranking there must be at least some meaningful information. So in case someone ask "should I check Musicradar when searching for a DAW?" I will answer using original words they write about Cakewalk: "you've got literally nothing to lose by..." reading it. And I will add "but you will learn almost nothing".

If you need "the first" controller, get Behringer X-Touch Mini. If will work out of the box with AZ Controller plug-in. From your list X Touch (big one, with displays) is exact copy of Mackie in functionality (not in controls quality), it will work as desired. Faderport V1 (old one) has special plug-in, but not V2. X Touch One will work more or less ok. They try to mimic Mackie, but since the DAW does not know it has just one fader, it is not working exactly as Mackie. Nanocontrol will also work. But it is "nano"... If you primary need buttons or your projects are no more then 8 tracks, it can be almost as good as Mackie. But at the time you load new project, shift to different tracks in the same project or try to control FX, you will need to bring knobs/faders "in position". Nektar P1, when ingegrated, has guides for faders and endless knobs. So it is way less work to shift tracks and no work for knobs. With nanocontrol it is different. Back to X-Touch Mini. It has encoders (as its big brothers) and a set of buttons. The functionality is listed there: http://www.azslow.com/index.php/topic,377.0.html