Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by azslow3

  1. Writing from memory (my... not RAM): computers are using numbers to report errors. And different libraries use the same numbers for own (so different) errors. If an error comes from one library but the text for it is asked using another, obviously the text has nothing to do with real problem. So, as I remember, standard code which corresponds to "not enough memory" is something like "device is busy" in one other library (I can't remember which exactly, I just remember the number clash). I will not go into details, but that particular case has no easy fix. That confusing message appears in many applications for many years...
  2. I am too young... My "computer operator" curse was already with disks, which had to be loaded into (wash-machine like) disk drive.
  3. In Cakewalk everything is processed in real-time. REAPER and some other DAWs have "precalculate" mode. So currently recorded or monitored tracks (including up-chain) are processed in real-time, all other (in fact all till you record or monitor something) are processed way more forgiving way. For that reason it is possible to have more plug-ins/tracks without problems even when audio buffer is small, no problem with recording into projects with PD plug-ins already inserted (till in the same chain as recorded track). But that comes with price... In REAPER PD is always rounded to the next buffer size, so if you record with a plug-in which has 1ms PD and the buffer is 3ms, that plug-ins adds 3ms. Two such plug-ins in the chain and you have 6ms. In Cakewalk you get exact PD or the sum of them, so 1ms and 2ms in the example. Also in some of my tests Cakewalk was able to drive more plug-ins in recording chain then REAPER, using the same buffer size. Note that any DAW has many obvious and not really obvious settings which significantly influence CPU load. BTW my upgrade 2 years ago was under 1k€, with i9, 32GB and 1TB fast M2 SSD. Note that in many (most?) cases only one M2 works as fast as possible (insufficient PCIe lines in desktop CPUs). Optimizing the computer for audio is the most challenging task, one single component or setting can render top configuration less usable for audio then 10 years old optimized system...
  4. ACT plug-in supports fixed number of conrols, 8 faders, 8 knobs and 8+1 buttons. So in the configuration there are 16 slots for buttons, 8 without shift and 8 with shift. What each control does is freely configurable, so you can assign Record to "B3" (without shift). BTW the documentation describes all that in details. If your controller is going to have feedback (LEDs, display, motorized faders) and/or has more then 8+8+8 controls, you better switch to AZ Controller right at the beginning. ACT and Generic Surface do not support feedback. The only alternative is mimic Mackie and use corresponding plug-in.
  5. Sorry for late reply. Just for clarification. As Mackie controllers, XTouch and XTender are completely independent on hardware side, they are "synced" inside end software, in this case Mackie plug-in. So it does not matter how they are connected to computer. When Xtender is connected to XTouch, XTouch is just USB hub.
  6. Just to make should you have tried right things... You need 2 control surfaces inserted, one is "Mackie Control" (pointing to X-Touch) and another is "Mackie Control XT" (pointing to XTender). If still no luck, cleanup MIDI devices in Windows (using Device Manager with disconnected devices shown throw an option in View menu). Delete AUD.INI. Enabled both devices in Cakewalk again, setup both surface plug-ins. In other words: while devices are physically completely independent, plug-ins "cooperate" them. Important to do this right, "MIDI busy loops" can be created otherwise. After dis/re-connecting MIDI devices, Cakewalk can be confused what is where. What is displayed then is not where signals are set, triggering the first problem while is the settings everything looks "right". PS. Configure surfaces without any project in Cakewalk. Till surface plug-ins "block" MIDI streams, something can be sent to devices and the input wrongly processed by Cakewalk, triggering the problem.
  7. I know only one modern solution which can survive offline as long as your Pentium4+XP+Home studio: RPi4/Intel i3+/AMD equivalent +SSD +Linux supported audio interface +REAPER 🙄 Otherwise any half way modern computer + SSD + Win10 + Cakewalk + any audio interface (with sufficient inputs) should do the trick. Just be prepared you have to go online periodically. Modern Windows and Cakewalk like be online, at least from time to time. I was keeping XP as long as I could. But that time is over. The same for Pentium4 and HDDs (except for backup or huge data).
  8. From my knowledge, I still have no fellows in cross DAW converters. So, it is possible convert projects from Cakewalk into REAPER only (free but in-official and incomplete, at least it tries convert audio+MIDI+FXes with reasonable success). For audio (no MIDI, no FXes) there is AATranslator which covers most DAWs. In practice, if projects are complicated and working with Bandlab is an option, that is most convenient approach.
  9. If MPK25 is not broken on hardware side, it is not worse than other controllers. And it is more capable then Mini. But with any generic controller, some time has to be invested into setup. In short: windows device manager should be used to cleanup all midi devices, specially duplicates (even they are not currently connected, any connection to different USB port creates new device) when in doubt, Cakewalk MIDI configuration INI file should be deleted (and later all used MIDI devices enabled again in Cakewalk preferences). the device should always be connected to the same USB port all devices should be connected before starting Cakewalk the device should be properly configured (see its Reference manual and configuration editor) All these topics (except the last one) was discussed on this forum, you can use Google to find related posts. BTW devices with special drivers can be worse then class compliant, f.e. when manufacturer "forget" update the driver rendering the device unusable with new Windows version. PS many troubles with audio/MIDI/other devices come from the cable or particular port/hub. Try to use another cable, connect to hub, etc. Note you need to repeat the first two listed operations after changing the port. PSPS for device configuration... note MPK25 is represented by 2 different MIDI devices (ports), current configuration tells which messages send to which device. Disabling external MIDI synchronization, configuring controls to use port A and set CC modes for knobs is a good start. When Cakewalk recognize MIDI device, you can see small icon in the Task bar. If you see "LED" on it blinking when you use controls, that is a good sign (doesn't mean they send what you want, but at least something...).
  10. If you mean "Dynamic plug-in mapping" (which is sometimes called ACT). Original Mackie plug-in was not supporting it. So till msmcleod has implemented parameters learning, particular plug-in configuration has to be defined in text file.
  11. Please write which X-Touch you have, there are 4 and they are different: X-Touch Universal (with 9 faders, jogger and displays) X-Touch Compact (with 9 faders, without jogger nor displays) X-Touch Mini (without faders) X-Touch One (with one fader) Note this thread was for X-Touch One, but it seems like you ask about X-Touch Universal. If you mean level LEDs and you use Cakewalk Mackie, you need enable level indication it Mackie configuration dialog.
  12. For X-Touch One, the last link from James has preset (for AZ Controller ) and PDF layout for its functionality (f.e. F3 for tracks/buses switch).
  13. In the first post you wrote you want fast way to switch buffers, since you do this all the time and that annoys you. We have tried to explain why other users rarely (if at all) forced to switch buffers. And why your audio interface is almost the worst possible for music recording. "Sound latency perception" is personal, absolute value in numbers is not. You are happy with "2ms" setting. Great. In practice that means you are happy with ~20ms key to sound latency (as most people do). That in turn means you can use any modern USB ASIO aware interface with "forgiving" buffer size on not death optimized system and probably eliminate any buffer switching. As you can read, you are not the only one who believed SB cards have lower latency since they are not USB, are good for music production since ADs claim so and have good drivers since Creative is the "marked leader". Most people are moved on, after realizing (technically and acoustically) that is not the case. And so we make the point (friendly). I think it is time to stop for me... 😏
  14. I have not found relevant data for this particular card, I mean real "analog to analog" latency. But you can easily do your "own scientific measurement", connect some output to input (do not forget disconnect or switch off all speakers/headphones/etc !!!) and run https://oblique-audio.com/rtl-utility.php There is more precise way, using any DAW. But you need more complicated cable connection. Achievable by particular interface lowest latency is only one of parameters. More interesting is what can work smooth under particular settings, in terms of soft synthes, FXes and the number of tracks. Sure, the computer and the software play significant role. People which test seriously do that with devices which can be considered as "music production audio interfaces". And Creative has never produced such (at least not with Sound Bluster label). Consequentially it is hard to find corresponding results. But so far every time someone tried (including myself) the results was confirming that Sound Blaster is not good for music production. Theoretically it can be ZxR is a revolutionary product in the line. But looking at your screenshots, where "ASIO reported latency" is strictly equal to the buffer size (physically impossible), that is unlikely 🙄 So my proposal is still the same: if you can, try some recent USB interface with dedicated ASIO drivers or even build-in Realtek (if computer is not older then ~4 years). It can happened you can find fixed buffer size with "not detectable delay" (for MIDI) and without problem when many VSTs are loaded. BTW 96kHZ is not good for that. Most interfaces have a bit better latency under higher sample rates, but double load on the system is normally not worse the advantage. If you need 96kHz in some particular plug-in(s), Cakewalk supports up-sampling. PS. I wish someone have tried to convince me to buy RME before I have tried (in chronological order): Sound Blaster (PCI), M-Audio (Firewire Audiophile and 410), Behringer Xenyx USB, Cakewalk VS-20, Phonic 808 (apart from not dedicated audio interfaces in e-drums and vocal processor, Relateks, etc.). That is the only reason I periodically try to convince other... EDIT: I have realized SB Z(x(R)) are 8 years old... so you almost certainly have more then 10ms RTL (I guess 16+ms).
  15. I think the first comment from John Vere, with fixed settings, is a good target to consider. If you don't play guitar softamps, especially in case you record MIDI only, you don't need top audio specialized PC nor top interface. Still, you need: relatively modern not "office" computer (if Intel, some i5 or better) moderately optimize it for audio (bring system latency down, no more then 1-2ms) use audio interface with stable drivers and decent latency. The last needs clarification (based on your comments). You need something under 10ms total latency, better under 6ms with the best settings, so you can used relaxed "fixed settings" and still be under or around 10ms. The interface does not have to be crazy expensive, in fact modern build-in Realtek chips (worse probably $1) do the trick. On budget, old Firewire interfaces also have reasonable (for MIDI) latency. Most modern USB interfaces also. But what is not working good for the purpose are SB cards. They never had "advertised" latency. Yes, the buffer size can be 2ms. But with such buffer PCI SBZ has more then 18ms latency (it can be PCIe SBZ is a bit better, but I doubt the difference is significant). In addition, SB drivers are traditionally bad (for music) and such setting are barely usable in practice, when the system is somehow loaded (that you observe). Also SB does not report latency correctly (that you probably also observe, when reported correctly Cakewalk automatically put recorded audio/MIDI to sync with already recorded material, when that is no the case the result is not in sync, especially when recording with big buffer sizes). There is no reason to fight for every ms in latency when dealing with MIDI. Hardware MIDI cable needs ~1ms to transfer one note, so 10 finger chord takes up to 10ms to transfer. USB connected keyboards/drums can do it faster, but that is rarely the case. But over 10ms RTL (5-6ms audio output) can be noticed, especially with e-drums. BTW e-drums with build-in interfaces (f.e. Roland) don't have market leading latency, but they assume you record using local sound and since they report latency correctly, DAWs usually put MIDI (more or less) at correct place (reporting/accounting MIDI latency is something not so advanced as reporting/accounting audio latency).
  16. At such moment I have visited the nearest music store to buy reasonable audio interface... Not that I no longer use other "devices" which can produce sounds from my computer (7), 3 are permanently connected. In critical situations I use the one I trust. But in practice cables, mixers and amps can start generate something without audio interface help. Big power button is the only ultimate solution against all possible problems of that kind (at home I use power sockets with remote control). From my personal experience, even in case you have big dedicated knobs for each stereo par, find the right one in multi-channel setup once something is really loud is hard 🙄
  17. If I understand correctly, your primary wish was physical controls for all outputs. But we are in Cakewalk by Bandlab forum. So, if controlling different outputs in CbB is sufficient, any Control Surface with multichannel audio interface will do the trick. The controller can be configured to change volumes in CbB rather flexible way. Sure, if software in question is not CbB (nor other DAW) or the sound does not come from software at all that approach is not going to work.
  18. To use channels from different devices in parallel, they have to be synced. If that happens on hardware level, some software solution can be written to make use of it. Otherwise audio stream manipulations are unavoidable. Such manipulations eat the spirit of ASIO, it make no sense then (except in case some software support ASIO only, so there is no other way). Hardware synchronization can be done: * generic way using World Clock, as dedicated wire or as a part of Digital Audio connections (S/PDIF, ADAT, etc.). Your interfaces don't have them. * proprietary way, somehow using existing USB/Firewire/PCI/etc. connections to the computer. I don't remember any entry level interfaces with multi-device ASIO drivers. And so aggregating your interfaces into one ASIO for software which supports other driver frameworks make no sense. Any approach (there are several) will either re-code audio stream to sync (void ASIO benefits) or produce audio glitches (makes the result unusable).
  19. Toontrack is one from a small set of companies which was friendly and ready to help with accessibility. That by itself move them to "customer friendly" category for me.
  20. CD, WAV or MP3, final customer never buy the content. The customer buy the right to use the content for limited purpose. If I remember correctly, in EU there is a simple rule: if you have bought something you can sell it. Explicit statements in contracts/licenses/etc. violating that rule are void (as usual when something violates laws). But some fee is allowed, to compensate addition costs (un/re-registration, etc.). I think license transfer fee under 10% of the price is reasonable for current crazy world, taking into account Google and Apple take 30% from all payments in all apps, just for the fact the app is commercial and works on corresponding platform...
  21. These are not "presets" only (configuration files), but plug-ins (programs). A-300 is Roland device, they was labeling some of them "Cakewalk" (when Cakewalk was owned by Roland). Cakewalk ownership was changed two times since then, but you still can download original software https://www.roland.com/de/products/a-300pro/downloads/ (look for "Control surface plug-in for SONAR"). The device is relatively old, and so software for it.
  22. I hope it will be not Sonar X2 style accessibility... May be you know, I have tried to make X3 at least somehow usable accessible way. So, accessible control surfaces setups for Cakewalk exists (generic and more flexible then NI solution). But there is no content API for surfaces (access to items, automations, takes, etc.) and that should not be forgotten. In practice even with accessible GUI the best solutions (Sonar 8, REAPER, Samplitude) could not be made without extra packages, and such packages prefer direct access to the DAW specific staff. Well, it can happened Cakewalk can construct reasonable object tree inside standard accessibility framework so such extra package is not required at all or can be constructed solely as a screen reader module. But from my knowledge probably it will ends as usual, with declared accessibility but almost or completely unusable.
  23. I have not checked for a while... but from what I know, if you use (or plan to use) control surfaces, AUX sends is not a good option...
  24. Just don't update right before critical work... By luck, we was visiting a friend when her Windows has decided to do major update and ended with continuous reboot... I was able to do "black magic" in console so it was working again in two hours. But I guess many people will be in trouble in such situation (it seems like corruption in distribution files has happened some time before the update, so "restoring from backup" was not a good option, update was stuck exactly the same way). Servers I administrate at work run without updates normally for 2+ years (except for exposed to Internet services). For home/hobby computers continuous updates are fine, for things which "should work" I avoid that. It is extremely rare when something is updated without side effects. Normally they are not important/not noticed, but I prefer to deal with bugs which I already know... I am Russian who does not like "Russian roulette" (may be something to do with 20+ years living in Germany ) 🙄
  • Create New...