Jump to content

Glenn Stanton

Members
  • Content Count

    344
  • Joined

  • Last visited

Community Reputation

178 Excellent

Recent Profile Visitors

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

  1. i have several "stem" busses which all feed a master buss. i only export by selecting only the master buss when i want the single combined output, or i can export all of the stem busses (low, vocals, instruments, solos, drums) in a single go by simply selecting those busses.
  2. hey @Noel Borthwick here's the exact testing setup. note i'm using the laptop rig shown in my sig and profile. the device is a Behringer Q802USB mixer - limited to 16-bit and running at 48Khz. the only changes are the drivers selected: ASIO4ALL (there is no specific ASIO driver for this device) WASAPI Exclusive (WASAPI E) WASAPI Shared (WASAPI S) MME (32-bit) WDM/KS the "defaults" provided by each selection (ASIO = 512 samples, WASAPI 480, etc) all roughly 10-12ms loopback USB Codec (the default clever name...) Ctrl Out Left -> Ch4 Left In note: the second ASIO is the MAGIX Low Latency (ha ha) driver which is the (same as the?) ASIO4ALL driver under another name, and i chose not to use that one since in testing earlier it was identical to the ASIO4ALL results. as my previous note, when i select the 512 samples in the RTL under the Windows Audio Exclusive it glitches, but works fine on the 480 - hence my suggestion there is a bug in the RTL (still a beta product...) CbB does not glitch until i set the slider (on any of the drivers) to 32 or less samples 🙂 (that's good and it's working well). however, there is definitely some delay compensation need with this setup. i'll be home in a week or two and i'll try to get my home rig up and running enough to test (although i'm in the porocess of moving so it may take longer). the home rig is the UMC1820 with ASIO drivers (and generally has always worked as expected).
  3. @Noel Borthwick RTL for the WASAPI (Exclusive) was 2384. manual offsets didn't change the offsets in the recordings. if i changed it via the slider, then there was a small change - see pics. it's interesting that the RTL see 480 samples but the driver appears to be set using the previous 512 samples of the ASIO driver. when trying this using the RTL 512 sample setting it glitches out saying too short, increase samples, but going back to 480 then works fine... may be a bug there... no difference setting the manual offset move slider (bottom track):
  4. yes, the loopback testing with RTL showed up as longer (1968) than the reported amount to CbB (1568) by ASIO4ALL. i noticed that the ASIO4ALL and MME were pretty close in terms latency, only off by the 32 samples shown in the ASIO4ALL control panel.
  5. and if it's still problematic, run the installer locally as administrator.
  6. i found on one of my USB interfaces, that it liked the longer older USB (steel braid shielded, heavy duty) over the short one supplied with it. we had someone here in the past 6 months who experienced an issue with their USB cable being old and too long (...no jokes please...) and replacing it with the newer heavier one "fixed" the problem. i'm guessing that as these devices get faster and more powerful (higher current levels for example in USB3) that the capacitance and induction of the wiring etc can impact it's sensitivity to EMI and race conditions (...the electronic kind...).
  7. i just look at the big red button up top - if it's dimmed, nothing is armed, if it is lit up, then i have one or more tracks armed. in the latter case, i push it and it disarms all the tracks, on the other, if i press record and nothing happens, it's a "Doh!" moment and i try not to repeat it too many times before arming a track 🙂
  8. the hmmm wasn't to condescend, i fully empathize with your situation. it was more a pause to consider that in the year since it went unsupport that perhaps some of the libraries which are required may have been updated or in some cases as i noted, confused in their stacking which has caused crashing or inoperation on my systems as well. cheers and hopefully this will be resolved.
  9. i did some testing on my "away" system - laptop, Q802USB (16bit 48K), and using ASIO4ALL (only ASIO for this older device), MME, WASAPI Exclusive/ Shared, and WDM/KS. not surprising that the MME and ASIO4ALL are only about 32 samples apart (same as the ASIO control panel latency settings of 32 samples). on my system the WDM was closest with WASAPI (either mode) showing the worst. note - PDC was engaged (no plugins anywhere), ASIO reported 1568 samples. RTL reported 1968 with the loopback test on ASIO, 2231 for Windows Sound Exclusive, 7000+ for Direct Sound and Windows Sound Shared.
  10. hmmm. Microsoft announced that Windows 7 support ends on January 14th 2020. On this date, Intune also retires support for devices running Windows 7. For more information, see Intune plan for change: end of support for Windows 7. Microsoft Intune will retire support for the Silverlight-based Intune console on October 15, 2020. https://www.microsoft.com/en-US/windows/windows-7-end-of-life-support-information in theory, Windows 7 should still work even though the last updates to the OS were at least a year ago. i'm guessing though that in short order not just security updates will be unavailable but many of the system components will as well. not sure why Edge components would be installed by CbB or even needed. there may be C++ libraries which are common to both which would be necessary... weird that the projects would not be accessible unless the installer overwrote your project directories and/or changed permissions. are you saying the project files are no longer accessible because they've been deleted or permissions changed to an account you have no access? or you just cannot open the projects because CbB failed during installation? if the latter, i'd try out Teegarden's recommendations. if the former, hopefully you have a good practice of backing up the projects that you can recover from.
  11. Windows does not have a native ASIO driver. what IO are you using? did you install the product ASIO drivers? if you recently did an update, did you reinstall the drivers? as a note, i find myself periodically reinstalling some of my drivers after a large Windows update and that has generally taken care of the problems related to ASIO driver behaving oddly (or not at all). i'm guessing sometimes the stack of SDK related bits installed gets confused and some of the winapi get used as the wrong version for some software etc... backwards compatibility not withstanding...
  12. very nice work! couple of thoughts: 1) ASIO4ALL - maybe tweak this video or add an appendix video to showing how ASIO4ALL isn't really ASIO so it's fixed in peoples minds... 2) WASAPI is "was-A.P.I." or "W.A.S.A.P.I" not "was-sappy" 🙂 like ASIO is not "ah-see-oh" 😉
  13. not all plugins install where the app manager can perform an uninstall, and many don't have an easy uninstall option either (esp if the plugin is installed as part of another software package). using the plugin manager you can see the location of the plugin file and the file name, then simply (using the File Explorer) click on the file, click again (now it's going to let you edit the name), use CRTL+-> or CTRL+END and type ! (so it's now .dll! or vst3!, etc), hit enter to close the edit, and say Yes to window warning you the file may not function... if you have a bulk renamer (i use StEx) you can select all the files you want to drop from the scans, and use the replace .dll with .dll! (or .vst3 with .vst3!). if the plugins have an associated folder, you can do the same thing, just add a ! at the end. then rescan. you should find all the files you appended with the ! are no longer showing up, and yet, if you decide to "restore" the plugin, just remove the ! from the file (and associated directory).
  14. yeah, like HP PC of yore, a number of interfaces need their own ASIO drivers to function. Windows will recognize them in the Device Manager as Audio Interface, etc but only the IO device drivers will work. usually they make a WASAPI driver for general Windows usage, and an ASIO "equiv" for "power users"... not sure how much ASIO is there when they do this. to wit: newer UMC series by Behringer, M-Audio, Focusrite, Avid, etc. many seem to adopt the old "we don't need to use no stinkin' class compliant device drivers" that HP used to do to us, because, ya know? then again, if it's well made device with great features, ok then...
  15. yeah, it would be nice to have the full latency total for a given track and by plugin in a small display or metric popup... hmmmm
×
×
  • Create New...