Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

47 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Not only network related drivers give a bit too high numbers, especially in case you work with low buffer size. Check with ThrottleStop (it is a tiny utility without installer) that your CPU is in performance mode. To check what is behind Wdf0100.sys, use Windows performance toolkit. You will see real driver then.
  2. I have recently return to the topic how to debug latency issues... In attempt to understand a problem on a friend's computer (kind of solved, but still no optimal, work in progress) and my own DELL XPS (here the conclusion is simple... DELL XPS (from the Inet ALL of them) are disaster for audio. But at least I have learned how to use already known for me and yet new tools: * Latency Monitor and In Depth Latency test. Detects general system CPU/MB glitches, shows latency spikes and detect some bad drivers * ThrottleStop. Shows thermal situation of CPU/GPU, the distribution of C states, accurate CPU load and frequency. Also allows to change many power management parameters on the fly. * Windows Performance Toolkit from Microsoft (a part of ATK). Shows precise graphs of all timings, down to concrete drivers ISR/DPC (Latency Monitor can not distinguish drivers behind "frameworks"). Finally, REAPER performance monitor displays precise real-time processing length (not the same as real-time CPU load, but it is also shows). Sonar/CbB has no that kind of diagnostic. My comments about all that you can find here: http://www.azslow.com/index.php/topic,395.0.html. Open spoiler near "Latency Monitor" and REAPER. Another generic check I started to use recently is https://cpu.userbenchmark.com/. After quick test, it display how good/bad your computer components perform in comparison with other users computers with the same components. PS. I am not convinced I can find all possible origins of latency problems. But I am convinced using mentioned tools I can find concrete numbers and graphs describing such problems.
  3. Unfortunately after Sonar X3 Cakewalk has introduced online authorization. I still have X3 installed, also that is the last version which I have manage to run under Wine (I develop under Linux, with cross compiling). And now there is one single DAW which still use completely offline authorization (apart from Ardour, which is not universal). All other want authorization, including free Cakewalk and Traktion. Fortunately, this DAW is multi-platform (Linux version is still "beta", but I have found it way more stable than Waveform "releases"). And it took the lead as an accessible DAW (sharing that with Samplitude and ProTools on Apple, many years Sonar 8.5 had this position... lost with switching to X1 GUI). I in fact had no choice, taking my wished into account 😉 I still launching Sonar or CbB when I want my control surfaces do what I want them to do. And will continue at least till AZ Controller 2 is ready...
  4. Till it is broken/stolen/forgotten... Sure, not as bad as iLok could, which can be down for a day, without excuse, explanation or reply from support. For dongle methods, I think Waves is reasonable: no need for dedicated dongle, lost/forgot USB stick - no problem, once per year restore all licenses in 1 minute. Remembered where this USB is? No problem! Reset "once per year" counter in 1 minute. But I will try to continue selecting my "goto DAW" with completely offline key authorization. Fortunately that is still possible.
  5. "My" copy of 2019.9 is 600MB... User friendly products with fixed activation time I have used can display expiration time... I know, running Assistant periodically is possible, but... I had 2019.3. So assistant need to be updated. assistant can not update itself ("something went wrong") downloaded and installed assistant manually 50MB. Well... tee, cigarette... downloaded. In case of update: "Update available", update button pressed playing piano... having dinner... (takes more then 1 hour for me in case my daughter is watching Netflix) "Update available" (no errors, nothing, like I have never pressed update button before and I have not seen slowly progressing download) 🙀 update button pressed... (waiting another 30 minutes - no one was using Internet at all this time) "Update available" (no errors, nothing, like I have never pressed update button before and I have not seen slowly progressing download) 🙀🙀🙀 ok... I am smart... I have found downloaded file and run it manually, installed without problem 😉
  6. You send the heartbeat (PingHuiIfRequired) from RefreshSurface only. Bad idea... Refresh Surface is not called when some CW dialogs are open (till they are closed), can happened some other GUI elements prevent updates as well. MIDI prepare buffer "magic size" is the time based length of DX plug-ins playback window. I doubt it is used for anything related to the number of queued MIDI messages. But Noel can correct me, that is just a guess (in the part it is not used for something else...).
  7. After reading post from Marco about D8b, I have just googled... There is a preset for Platform M+ http://www.azslow.com/index.php?topic=386.0 "ACT" (Dynamic Mapping) mode allows control plug-ins (including synth and ProChannel). I do not see controls to select the plug-in, you will need to do this by mouse or extend the preset with selection controls. I have no idea how good the preset is working, Hermu has made the preset without me 😉 In the comments he writes D2 shows something. So yes, that is possible.
  8. Some features are implemented in the BCR2000, referenced in the previous post. Syncing FXes is a documented action. Stop on marker is "Presets which work without surfaces". If you can not find something particular, I can find that for you...
  9. ACT is Cakewalk API for Control Surfaces. MackieControl.dll is also ACT based. They label "ACT" Plug-in Dynamic Mapping, which is a part of ACT API. And they call "ACT MIDI" one of DLLs. A bit confusing... AZ Controller should work correctly with any resolution up to 14bits. By "correctly" I mean careful precision auto-detection, including 7bit transmitted over 14bit messages (most "Mackie compatible" devices which do not claim high resolution explicitly). Exotic value ranges (some iCon devices used that) are also supported. 7bit controls apply special (non linear but invertible) mapping, so pan center can be set exactly. Touch sensitivity and feedback are supported. Too good to be true? Yes... Unlike "plug-and-play" MackieControl.dll and simple to configure ACT MIDI, AZ Controller is a DIY platform 😉
  10. There are several way with a game controller. Interesting that people do not like "simple" solutions. My "Not a..." extension for REAPER does not attract people. While it is definitively the winner as a transport controller, in terms of price and size. The extension makes any mouse a dedicated MIDI controller from the DAW perspective (the mouse no longer works as a normal mouse, but buttons/combinations can be assigned and the wheel works as a pushable encoder ). Plus a dedicated 100+ buttons MIDI controller from any computer keyboard, as a bonus 😉 But I think OP can fix IP addresses for devices inside local router configuration and that will make network based solutions stable. To press "Record", this toy http://www.azslow.com/index.php/topic,288.0.htm should do the trick, as long as IP address of computer running CbB is fixes. TouchDAW involves extra service, this one http://www.azslow.com/index.php/topic,295.0.html has no external dependencies. But again, stable IP is a must.
  11. I do not see any reason... There are "normal" gamepad controllers, which are already supported. Yet after 3 (!) years this relatively complicated preset exists, I have not spotted a second person which use it. The person for which I have written that preset originally was using it on stage, some people was wondering in which game he plays, in parallel with drumming 😉 The preset has an extra features, using second sound card (Windows sounds) it audition all operations. Up to the level it was possible control Sonar/CbB without monitor. Really control, with adding/removing effects, sends, detecting clipping, etc.
  12. Big X-Touch (with displays) in MCU mode has exactly the same controls as MCU. Original HUI is different, X-Touch does not have related (physical) controls. I have not heard about color displays in HUI. X-Touch color is an extension, it works in MIDI mode (when it is connected with MIDI cable) and throw Ethernet, when the device thinks it talks with Behringer mixers. I have not found the way to change colors when it is connected with USB.
  13. If controls are sending the signal throw MIDI (different), you can "Forget all assignments" in the Options tab and then in the Hardware tab assign actual values.
  14. I will try to explain the question, but I am not sure I have undersood it correctly. In short, try USB hub. I know at most places it is suggested to plug an audio interface directly without any hub. There is even a rumor that slow USB device connected to a hub slow the whole port. All that is not always true. If the hub is implemented according to the USB specification, everything should work just fine. Especially with low IO interfaces like UR44, the bandwidth is sufficient and USB was specially designed to share connections. F.e. I have an USB hub with 10m cable and 8x8 interface, DP and surface coexist on it without difference from direct connection. Now the answer. MIDI cable support just one "connection", while USB can carry many MIDI connections. That is why connected by MIDI your keyboard does not operate the same way as connected by USB. You can reconfigure your keyboard so it sends all controls to MIDI, then reconfigure AZ Controller preset to react on that messages. But without such modifications there are no signals or they are different.
  15. My whole site is about what you can do with AZ Controller... What you expect people write here? 😀 You can assign whatever ever was possible to do with controllers in Sonar/CbB. And till some degree you can implement what was never supported in CbB. F.e. tempo change with knob, use your nanoKontrol knobs and faders in "instant" or "endless imitation" modes, make CbB speak what it is doing, up to the level it is usable with switched off monitor (except the content editing), combine different devices into one controller (f.e. make android tablet/phone be a display for your nanoKontrol). And there are unusual features: f.e. you can sync settings in one plug-in instance with another, do something when time pass particular markers, control your digital mixer or interface with digital gain using knobs of dummy FX chain, etc.
  • Create New...