Jump to content

Tez

Members
  • Content Count

    97
  • Joined

  • Last visited

Community Reputation

10 Good

Recent Profile Visitors

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

  1. Well, on an optimistic note just before crashing I decided to run my test one more time, only this time I checked the "Always Open All Devices" option, the performance module showed CbB happily bouncing though each logical core, and it ran for more than half an hour with no dropouts. The interesting thing was that LatencyMon showed a spike on a graphics related driver, issued it's red audio issue warning right in the middle of the test, but as stated CbB was unaffected 😁... So I can sleep a tad better tonight. But... I'll have to run it for longer tomorrow and hopefully with the same result. On my prior PCs all had third party sound cards installed as a build option, but not this one, and I'm not good at playing with a pc's innards, and external devices had their drawbacks back then. Anyhoo tomorrow's another day...
  2. Yup that's the ISR which I believe kicks off Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft and that's the spiking DPC. It turns out the latency issue with Wdf01000.sys is all over the web going way back and no solution that I can find, except to bypass windows drivers altogether and ASIO4ALL has been updated since 2017... So will keep looking for a solution...
  3. What were your dropout codes? Well, one and all thanks again for all your input! I have to remark that with 4.01GHz core and 32GB ram my system should be amply audio capable, and by and large it is. The test performed (described above) does nothing but stream audio silence to the FXs. LatencyMon shows several drivers with spiked DPC execute times, and these cause underruns resulting in an Audio Engine dropout 1. Namely the Kernel Mode Driver Framework Runtime, I believe triggered by the High Definition Audio Bus Driver and also the Port Class (Class Driver for Port/Miniport Devices) used by audio devices, and in this case both I believe are audio related, and last the NVIDIA Windows Kernel Mode Driver, which is up to date as is W10. This test was also done with no internet, no router and the AV off, same result. These sporadic spikes are the problem, the performance tweaks are in effect, so the question is what is causing them. If anyone has had this particular issue and has fixed it please let me know...
  4. So far, conducting multiple tests as described above: And using the settings described in the OP, the audio dropout 1 occurred after about 15 mins and LatencyMon showed a big spike in HDAudBus.sys driver. No event errors occurred during the tests, and the same result occurred for several test repetitions . Incidentally, running LatencyMon whilst writing this without CbB running, just the browser, the same spike occurred. The system is always up to date, so as to what this means I'm far from sure, is it the driver's poor performance or the task using it, CbB is using WASAPI, the browser isn't. Power throttling is disabled, no page faults occurred for CbB, and it seems this spike is the best candidate for the dropout, although other spikes possibly misleading, can show up. So I'm at a loss as to how to fix this. As to Realtek ASIO I share the opinion of Mr @scook ...
  5. @Prod.Lostboy Anything that might help, so thanks. Just about to embark on my own LatMon odyssey... Wish me luck 😵!
  6. Not as yet, just being cautious, but if as you say there's no down side, I'll see what relevant. The "power/USB management" did pique my interest as the midi input is via USB, but as I mentioned for the test above the midi was not active, and the dropout occurred regardless with no activity whatsoever. Other than the mouse as far as I'm aware, there's no other USB input I use for CbB. So I'm curious, in what way is it crucial, and am I missing something? Anyhow thanks for your help, much appreciated! Update: Just applied the power option tweaks, much of the others like "Privacy Options" were off or just don't apply to my system and for the moment deferring the optionals. I just realized that I can always revert to the previous "Preferred" plan if "High performance" has issues. So, will see if this improves dropout frequency first... Update: Just ran my test mentioned above, unfortunately despite the tweaks an Audio Engine dropout 1 occurred with no activity or midi input whatsoever. So, hopefully LatencyMon will reveal something...
  7. @JonD I just ran a test with a project where my synth is Pianoteq with Ozone 9 in the FX rack, and REmatrix in the prochannel of a bus. The midi input for the synth was set to none, the echo was off and the midi keyboard was switched off. I walked away for a while to see if a dropout might occur with no activity or midi input. Without fail it did, an Audio Engine dropout 1. My question is, if you might know, how would I use latencymon to track down the cause, as it seems to me for this scenario something might well be affecting CbB. I'm assuming that the "LatencyMon.exe" is a standalone app not an installer?
  8. Well, when I check the resource monitor all cores are active, if parked it should say so, no? I was under the impression that desktop w10 core parking was disabled... I'm not familiar with latencymon, something I'll have check out. For DAW tweaks I've got the pdf "Tweaking Windows 10 for Music Production" from Creative Source, some of it might be appropriate, but this is not a DAW dedicated machine, maybe one day I'll be able to afford one, meanwhile I have to exercise caution... Regardless, thanks guys for the input, if some process or another is the culprit, hopefully I can track it down, this might be the case as I've noticed dropouts on simply opening a minimalist project... 🙄
  9. Even on projects with a single synth and only a couple of FX plug ins, Audio engine dropouts keep occurring. These are the basic settings: WASAPI Exclusive, Buffer Size: 40.5 msecs, Multiprocessing Engine checked>Plugin Load Balancing checked, DropoutMsec: 1000, Midi Playback: 1000 msec buffers (the max allowed). I still get too many Audio Engine dropouts: mostly 1, occasionally 9 and even a 3. Dropout 1 often happens when nothing is going on, no activity, no midi input. I started using WASAPI hopefully to eliminate this plague of dropouts. If someone has any suggestions to fix this I’d be grateful... My system should be well able to handle CbB performance, basic specs can be found here:
  10. I think I've narrowed the issue a little . For a completely blank new project, no buses, no tracks, no vsts, the template generates all the buses present when initially saved. For my 5.1 speakers, using WASAPI exclusive, this was set to 3 hardware stereo outs, but the template in this case only shows the 1st hardware out, which maybe an old issue. For a new project template that has some of the buses included in the track template the existing buses will persist. Saving the template without the existing new project's buses and inserting it into new blank project as described in the OP, half the time there is no issue, the behavior is as expected, but sporadically it will shutdown cakewalk on project close. It seems there's a conflict with a new project's existing buses and the track template's version of the same, and probably something more. So, I think this is a bug...
  11. @Base 57 I'm not surprised you couldn't duplicate 2 & 3, it probably depends on the track template in my case the synth was pianoteq, the FX Ozone 7 and the audio out generates 3 buses, an input bus, a verb bus which uses Rematrix in the ProChannel and mix bus for the input & verb which sends to the pre-master. I also have a template that just generates the 3 buses mentioned using a blank audio track in the track pane, and guess what... Scenarios 2 & 3 don't happen. So, I'm speculating that it's an issue with how the FX and synth instances are being handled in the specific context in the OP. Now using the blank audio track bus template and independently inserting Pionoteq and the FX , for each new untitled project, scenarios 2 & 3 don't happen. Whatever's going on must be complicated 🙃 ... Update: It seems the issue resides with the track template used in the OP, namely just creating a new blank project as before an inserting the track template in question, on closing the untitled project without saving also closes Cakewalk, this should not happen, typically the Start Screen should be invoked. So now I'm really confused 🙄...
  12. I have a blank project template with an empty track pane and 2 buses, a pre-master with a send to the master which has all the sends to the hardware outs. Scenario 1. Create a new blank project, and immediately create a second new blank project. The window tab only shows the last blank project. An addition to the track pane of a project has to be made for a subsequent new project to appear in the window tab. Scenario 2. I have a vst3 synth track template, Midi source, Synth track folder and 1st audio out to a specific bus configuration and an audio FX in the rack. Create a new blank project, and insert the track template, create a second new blank project and insert the same track template. Close the first new project without saving and the Cakewalk app closes. Scenario3 Create new projects as per Scenario 2, and for each perform a “Save as” so now these are no longer untitled projects. Close the first project and the Cakewalk app closes. Last, since the projects were saved opening each one in the same cakewalk session, the behavior is as expected, namely closing one of them does not terminate Cakewalk and the other remains. This all seems a bit buggy to me...
  13. Make sure you delete the synths and the associated tracks from the Synth Rack view, then try, "Save As..." from the File Menu, and choose a different name, then close the project and open the newly named project. If the problem persists it maybe you don't have full administrator privileges, then try launching Cakewalk as an administrator, and see if that's the issue, on saving your modified project. These are just suggestions of things to try, otherwise it doesn't sound like a CbB issue perse...
  14. Silly question... Did you save the project before closing it?
×
×
  • Create New...