azslow3

Thanks for correction, I have overseen that change! BTW is it also possible select "related" synth for current track? I am still using not always working "hack" for that in AZ Controller (which it turn is based on bug in instrument tracks...).

Intel is "stuck" with current technology for a while. Till your friend is going to use advantages of current top mobos immediately, I do not think it is wise to make investment into the "future" (the next generation can bring new USB/thunderbolt standards and current trend is making all new incompatible with "old"). There is some "basic" level of bios tuning which is nice to have for audio PC and exists on gaming boards (but not on "office" boards). Top end adds last percents in overclocking, multiple graphic cards compatibilities, third M2 (while even the second is already limited on 24 lines CPUs, so all current except X and server CPUs) and fancy light (with build-in LEDs and extenders). F.e. that can be effectively useless for a system with one M2, one graphic card and not overclocked (btw overclocking above automatic turbo mode is not really working on normal i9, it start consume above 200W under specific load just with default settings...). I have considered ~€200 Z390 MSI Mobo, i9 and middle range M2 (Evo Plus). I am happy so far, but I have not managed to tune it down to some (rumored?) system latency numbers. It works fine without any tuning under low load, with lowest settings my audio interfaces support (48 samples by 48kHz, 3.1ms RTL). In case of big real-time load and top end latency requirements (under 2ms) more effort should be made to select exact MoBo, Memory and all relevant settings. In such case simpler solution is contact Studiocat (Jim) and get proved as working for the purpose complete system. I do not need extra internal disk for the moment, but I will try to avoid any HDD inside my home computer in the future. I mean I prefer 3x 2TB SSD instead of one 6TB HDD, when possible. Price difference still exists, but it is no longer factor 10. SSD is silent, HDD is not. Do not forget about powerful while silent PSU and cooling. After many "iterations" (at work), I have considered PSU+Cooling approximately as expensive as MoBo+RAM for home.

If that is BM-800 which can be bought in Germany for €25 (€13 in China), including stand, pop filter, cables and USB audio "adapter" (or phantom power adapter)... you probably can get better result by using a mic in your mobile phone. My noob tip: record e-guitar instead. If not an option, use some acoustic guitar pickup. At least you do not need studio like environment in this case (== special room without noise and reflections) to get "studio like" sound.

Transport and faders should work in Mackie mode using Cakewalk Mackie surface module, set "Disable handshake" in the module configuration. Pads was thought more for performance, so can be used the same way as keys. Alternatively they can be assigned to mimic some Mackie buttons (on the keyboard side) or assigned to arbitrary DAW operations using ACT MIDI (Generic surface or AZ Controller).

VS-700. Original surface module. Device itself is discontinued and does not support Windows 10 (driver can be installed with tricky workarounds only). MCU Pro and complete clones (like Behringer X-Touch, big one). Cakewalk surface module (Mackie). Does not support Synth steering, Plug-in mapping in a dedicated text file (no ACT Learn). With feedback/faders touch/display support. Faderport Classic/Alphatrack/Roland MIDI keyboards/Nektar MIDI keyboard (except Panorama). All have original surface modules, but they was not updated for years and can be problematic. Behringer BCR2000 and X-Touch Mini. AZ Controller surface module. Almost on the limit what can be done theoretically with control surface in CbB using encoders and buttons (feedback, double-precision encoders, ACT Learn, jogging, etc.). Any simple controller with 8 faders, 8 knobs and 8+1 buttons. Cakewalk surface module (ACT MIDI). Easy and flexible in configuration. ---- That was more then three, but the list is almost complete

You can control FX bin and EQ/Compressor in ProChannel. Synth rack and other then EQ/Comp PC modules are not supported. The mapping can be defined in text file.

Banks is ACT MIDI are internal. So you can define buttons to switch them, but you can not use banks to assign more hardware controls. ACT MIDI supports exactly 8+8+8 + 1 controls. That is already insufficient just for one layer (encoders are pushable and there is one fader, so one layer is 8x2+8+8+1). ACT MIDI supports encoders, but you can not change sensitivity (the speed of parameter changes) ACT MIDI has no feedback. So, if you want all power of your controller, use AZ Controller with mentioned preset. You will have feedback, several logical layers, 2 banks for ACT and you still can tune everything to your taste.

I also recommend to read http://www.azslow.com/index.php/topic,107.0.html That is in depth manual for ACT MIDI, apart from step by step guide how to "recreate" ACT MIDI inside AZ Controller. PS. If you do not understand Russian humor, please skip the subject and the text before "smile" (some people was confused).

Do not mix "MIDI learn" with "ACT learn". Also both are for steering plug-ins, not Cakewalk itself, they work completely different way. "MIDI learn" inside "ACT Midi" is yet another type of "learn". That is for learning the controller. Confusing, I know... For "Undo" in "ACT MIDI", in the Options tab (of ACT MIDI) select "Bank1" "B1" (or other) in the Buttons row and find "Edit|Undo" in the list. If you want a dedicated undo button in the CbB GUI, enable "Custom" module in the Control Bar and select Edit/Undo for one of its buttons. BTW in AZ Controller you can construct context sensitive custom action, f.e. Undo with transport stop as normal undo but "Stop->Undo->Record again" when you press it during recording. That is not strait forward to configure, but such (and more) examples exist on my site.

For transport and undo, ACT MIDI will do the trick. You will need to configure it a bit, there are many instructions/videos. If you want more you can try this: http://www.azslow.com/index.php/topic,247.0.html Depending from the version of your keyboard, you will need to re-learn controls.

(a) You try to use X-Touch Mini from 2 (or more) applications in parallel. That is not supported by Windows standard MIDI drivers. It is not Cakewalk specific not X-Touch specific. The message is misleading, but it comes from Windows (it has many device related misleading diagnostic). Check you do not have MIDI-OX, other DAWs, Behringer editor, etc. running when you start Cakewalk. Also check you are not using some plug-ins which try to work with MIDI devices directly (rare but exist, f.e. Ctrlr) (b) you have started Cakewalk with X-Touch or any other MIDI device disconnected / connected to other port, etc. Under some conditions, Cakewalk is confused and theoretically can try to open the device twice (not that I have seen that). Delete corresponding ini files for Cakewalk, it will regenerate them. (c) your device/cable/connection is unstable. That can produce all sort of errors. That is not unusual with Mini, my periodically fail to initialize or crash after closing DAWs, when connected throw 10m USB hub and I forget to switch on extra power for it. Try another port and cable. (d) set UWP mode for MIDI in Cakewalk. UWP supports device "sharing" (unlike MME).

It should work with ACT MIDI (there is no dedicated module). Or you can use this: http://www.azslow.com/index.php/topic,377.0.html

I am not sure you mean that, but there is one bug with "presets" and just one ACT mapping per plug-in. If you have 2 ACT MIDI (or Generic, or any other) instances, they share the same ACT plug-in mapping table ("ACT Learn"). They both show the same "preset name". But you can use them with different presets, just be careful when saving and never save preset when both GUIs are open.

Overclocking by itself should not produce any issues in the DAW. But overclocking recent CPUs hit throttling rather quick. Check with some utility (f.e. TrottleStop) that you do not have such problem. Note that throttling can be from several parameters: temperature, short term power consumption, long term power consumption and current.

I do not have NI keyboard, but I have seen several such questions. Without good solution. Just some background: * first NI keyboards was supporting Mackie Transport. Early Komplete Kontrol was locking in DAW instance switching. So, transport was working and Komplete Kontrol steering with manual instance switching. Nothing else was foreseen and nothing could be implemented. * in the second NI keyboards generation they have removed Mackie Transport (and controlling MIDI) support. Komplete Kontrol was still the same, so transport functionality could be done with OSC only (my no one from my knowledge has done that for Cakewalk) * recent Komplete Kontrol has returned MIDI steering, using documented (not in public) protocol. And it covers not only transport but also other DAW parameters. They have also unlocked instance switching. And so, it is THEORETICALLY possible to make recent S and A keyboards work in Cakewalk with full integration. But that is not done yet...

I see that as the only and artificial problem. Back in time, they had high granularity in monitor/tv native resolution. So there was 800x600, 1024x768, 1440x900, 1680x1050, 1920x1080 etc. monitors. Smart people cood choose "optimal" for own perception and desired size resolution, so apps are looking good without doing anything. F.e. I had 19' 3x4 monitor with 1024x768, 19' 16x9 with 1440 and 24' with 1680. At some point, apps have moved toward "native" FHD wide screen design. That is working well, from 14' on notebook up to 27' on desktop, without any scaling (at least for most people). They have now "jumped" 2x in resolution (fixed), but not so in size. 4K on 14' is an overkill and 55' you are not going to use from 30cm distance. It can all be good for video, 60' TV looks a tick better in 4K then in FHD from several meters (but effect of frame interpolation and HDR is way more visible). But for monitors that is almost pointless. After disaster with 3D, they have decided to go "safe way" in marketing: 4K, big size, curved. Just to sell something "new", not because it make sense. In such discussions I always remember my good friend. We have bought Panasonic plasma TVs at the same time, he took FHD and I HDReady (the price difference was almost 50%). 5 years later we have bought our first BluRays, so he could finally use the advantage... But for the price difference I could get new projector with 3m screen. Way more enjoyable with movies.

Hi, 150% zoom means 1.5 pixels pro one. So such scale will be fuzzy by definition. 100%, 200%,400% are fine. HDPI aware apps just calculate everything themselves, obviously avoiding not even graphic scaling and rendering fonts and other vector graphics in native DPI and desired size. Another approach is declare the interface HDPI aware, but scale the picture at constant 2x. Such apps are not really HDPI, but kind of trick OS and so avoid 150% PS. @bassman. I have seen your BCR2000 preset, but I have not checked it yet. Sorry.

lol... why people still fall into the same trap? Next will be 16k.... Are you still going to buy it for 10' tablets? I understand there can be some advantages for photo processing (but I guess HDR bring more here). Who professionally works with 4K Video also obviously need 4K screen. But why have pixels which is impossible to use 1x1? Yes, everything can be a tick smoother, with 4x processing power or 4x picture size. I am still happy with HD Ready TV for TV (42') and FHD 24'' monitor. I use 100% on FHD 15' notebook monitor as weöö, so I guess I will use 100% on 32'' 4K in case I buy it. And I wish me a new projector in 4K, since I have 3m screen. But when someone needs scaling to work normally, it simply make no sense.

What you mean by "/24" ? Normally "<frequency>/24" means ASIO buffer size is 24 samples. But I am not sure in your case (24 is very small buffer, supported by some relatively expensive interfaces with top computers). All current interfaces can work in 24bit mode and 32bit mode is hardware-wise not possible. DAWs process in 64bit FP (at least 32bit FP). So the "sample size" 24bit is normally assumed as the only option and so omitted. 48/<n samples> has less latency then 44.1/<n samples>. Less latency in addition to more samples per second is more system demanding. In case the system is on limit with 44.1 it can not handle 48, at least not with the same buffer setting. Sonic difference is small and CbB supports upsampling for plug-ins. That is audible for many plug-ins, it make them run on double frequency. So (IMHO): to be on the "safe side" in all audiophile discussions you need 96kHz, on powerful system with top interface it can be possible to have less latency with 48 then with 44.1 (on a weak system with low/mid interface it make sense upgrade the interface first, in case latency matters ) , has no difference otherwise.

When almost unused they normally produce zero noise. My is in silent mode most of the time (including small 3D editing and old games). It depends how much power particular job needs, is the card in "gaming mode" (over/under clocking/voltage settings) and how good is the cooling system when passive. So that can be a good point for OP: low profile can be problematic from the noise point of view. If the case allows, normal profile is safer.

I have opted for 2x16GB. I know my needs at home (at work decisions are in different size and price range...). GPU can outperform CPU in some tasks. But that is the task and GPU dependent. By 1050Ti can not outperform i9 in Blender rendering.

+ I means asking someone to do his usual job for free is a bit unfair, no? So, comments from me (I have recently upgraded to almost identical system, except I put MSI MB/GPU and populated 2 RAM slots only): * no overkill in your configuration * "overclocked i9-9900K" is not the term it was before. Without any "overclocking", this CPU in "standard" turbo mode can (will) throttle under some conditions. With all threads CPU intensive load (and MB auto overclocking settings) it consumes 230W+. I have opted for 12A because of Noctua recommendation. It can handle 180W limit, probably a bit more (and probably with less aggressive voltage tweaking CPU can do more job from the same power). 12S is less performing. Common option is not even 14. For this CPU it is dual tower 15. The case should be chosen correctly and access to RAM slots will be limited, but that is more safe way to go. * from my knowledge there is no benefit from populating all 4 RAM slots, but the first two slots can be especially tricky to access with a big cooler. * you can set "all cores 5GHZ" to get under 10% theoretical computation power more. And hope the load is not too hight (so you do no use the whole computational power, not even close). A bit counterintuitive, but has some theoretical benefits. * Desktop CPUs have limited number of PCI-E lines (not PCI-E slots related). Your MB has 2 M2 slots and only one is "primary". Also note the second M2 disable a part of SATA connections. So "3 M.2" and "5-6 HDD" is not realistic. Put bigger M.2 if you need more space (f.e 1-2TB M.2 are not significantly more expensive when calculated pro GB). * the system will be quite, in case you do not put any HDD. But under low load only. As you can guess, once something is consuming 300-400W in total, all that is converted into heat. And this heat need to be moved out. Noctua and other have many differently sized case fans. Modern PSU and MB have special connections and steering for these extra fans, so they will be quite till they are required. "Stress loaded" air cooled CPU+GPU are helicopter like, no workarounds... * if you plan any GPU intensive tasks, opt for better GPU. If you do not have GPU tasks at all, CPU build-in GPU can do the job. I have 1050ti because I also play relatively old games on FHD monitor, that is sufficient, smooth and quite. Also 3D editing is smoother and quite. But 3D rendering is way faster on CPU then on this GPU. * I have 650W, no problem in that configuration. But if you plan more powerful GPU (alone or SLI), that can be problematic. Note that PSU total power is just a "label", look at concrete lines max currents to get the idea from where the problem comes, even in case total consumption from all components is under total limit.

I do not know how Presonus drivers work, but your first graph is definitively not from 96kHz sampling hardware. Can it be it shows 96kHz, while in fact doing that is software? Not sure it is possible with Presonus (possible with my M-Audio), does it work with ASIO and WDM at the same time? I mean check that Windows is not configured to use it for something, in 44.1/48kHz mode (the only way I know to convince Windows it to have another interface for it... when there is only one, Windows try to grab it). My interfaces report correctly - when the interface is used for Windows / other app, its ASIO frequency can not be changed. But I do not have Presonus, they f.e. could "trick" by letting frequency change in software while still locking hardware. Other possible way is checking Windows settings. In the Control Panel (old one) / Hardware and Sound / Sound. In playback and recording, right-click on each device, Properties / Advanced. Check everywhere is 96kHz, at least for all IO of FirePod.

Another term is "Slip stretching" (f.e. ctrl+shift dragging clip border). That allows make clip length what it should be, f.e. align clips recorded at different hardware clock. Note that is the subject of complex algo, you can set it in Preferences, separately for "preview" and "rendering", the quality can be significantly different.

This graph shows that your interface, at the moment of the test, physically works in 48kHz mode. Check its own control panel (if it has one). At least check that RMMA is in ASIO. In MME it WILL NOT switch the interface, so the interface continue to work in the last mode it was asked to work. From where the garbage comes I have no idea, on my interfaces the part up to 24kHz has the same general shape, but the upper part is zero (I mean when hardware is in 48kHZ, RMMA in MME with 96kHz). Can it be some "windows audio improvement" or some other software "effect"? (I do not have FirePod, but when I had SoundBlaster it has tried to "improve" my sound internally). I ask because even up to 20kHz part is horrible. Sure, I do not expect it is as flat as for top current interfaces. But even my M-audio Fireware (without pre-amps) looks way better (it falls after 20kHz in 48kHz mode). If that garbage has found its way into your recording, there is nothing you can improve there. But at least it should be possible to switch your interface into real 96kHz for future recordings.