Jump to content

razor7music

Members
  • Posts

    774
  • Joined

  • Last visited

Everything posted by razor7music

  1. @scook So, you mean go into my bios and reenable my integrated sound, then select that as my audio device in CW and see if I get the dropouts?
  2. Hey All - @scook @Noel BorthwickBorthwick @Robert Bone At this point I'm just trying to do all I can to determine if my issues are audio interface related. The last thing I want to do is buy a new interface and have the dropout issue remain. Can you please think of anything else I can do to at least determine if it's my audio device? I posted another question to people with my same device and on W10 and theirs seems to be fine. Thanks!
  3. More great information. I admit, I'm ignorant when it comes to the config. I'll try to adjust this setting up and report back. Thanks! -EDIT- NI = Negative Impact. I set the DropoutMsec from 250, to 275, to 350. I set the ThreadSchedulingModel to 3. I also tested the other project that was completed without issue in W7 and now won't play at all in W10 without bypassing the FX. NI there too. 😞
  4. Hello Thanks so much to you and @scook Sadly, changing it to 2 had no effect on the audio dropouts. I was limited on time so I didn't test my other project after the change, but I will. I think I'll try 3 just to rule it out as well.
  5. Hello @Robert Bone I guess I didn't understand the question when this info was being asked for. I'm at thread scheduling 1. Should I be at 2? Either this changed when I upgraded to W10 (doubtful) or it's the same as I had with W7 when CW was rock solid stable. CC; @Noel Borthwick
  6. Well, on the bright side, at least Microsoft isn't installing an update it knows or thinks isn't compatible with your system.
  7. Thanks, me too. I had the Layla 24/96 before the 3G. It just started having major static in the headphone volume pot but everything else was great. The reason I started with the Layla was because Cakewalk recommended it on their list, long, long ago.
  8. Well, I'm getting the same message that my device isn't ready, and I'm kind of glad it isn't. I just upgraded to W10 and am still trying to diagnose my new dropout issues. The last thing I need are BSOD from an update. Do we know if the issues with ver 2004 are related to DAW hardware or CW?
  9. Get a bare minimum GPU that will work for CW but not good enough for gaming and you'll spend more time making music and less time gaming! 😉
  10. So that's where all my Blue Tubes plug-ins came from! If I'm not mistaken, they're abbreviated as BT in the plug-in manager. I've got to check those out again!
  11. Yes, I turned off all the background stuff. I did an in-place upgrade. A fresh install was not an option for me. I did all my homework prior to the upgrade, but something fishy is going on because although I get project load toast messages, I don't get dropout toast messages. I've posted about that a couple times and it remains a mystery. The last thing I want to do is buy a new interface and still have the same issues, so I'm in research mode until it's diagnosed.
  12. Thanks for the insight. My day job is IT and I hate legacy equipment or technology to hold up advancements and improvements in the form of upgrades in other areas. That's what I'm thinking is going on with me hanging onto my Echo audio interface. I procrastinated upgrading to W10 so I could keep my outdated audio interface. I just want to be 100% sure (or close to) that is my dropout issue before I buy a new interface and decommission my second Echo Layla.
  13. Hello This post is merely me trying to poll the group since I upgraded to W10 and am having issues that might have to do with the Echo drivers. I postponed my W10 upgrade for a long time thinking that the non-existant W10 drivers might be a problem with CW. I heard from several of you that there were no issues, so I took the plunge. Unfortunately, I'm having issues with fx plugins and virtual midi instruments causing dropouts, and since I heard that there were no issues from some of you so long ago, I thought I'd check again. Please let me know if you're on W10 and have the Echo Layla 3G if you have any performance issues with CW or not. I'm trying to decide if it's time to get a new audio interface and money is an issue at this time.
  14. Where? On the Celemony site upgrading to 5 Editor from any previous version is $99 US. I just checked again since I'm waiting for the usual sale that comes out a while after a release, but it seems a little early for that. We're you thinking of Essentials?
  15. Be really careful with the app. If you don't configure it correctly, it could crash you computer.
  16. @Noel BorthwickI always have virtual instruments because I always have drums in all of my projects. I'm going to create an audio only test project and post back my findings. EDIT: @Noel BorthwickI am running my audio interface in ASIO. I followed all of the tips from this forum on what to do after upgrading to W10. Disable fast start, no AV scanning of music related files, no indexing either, etc. I do get a drop out on another project that can be worked around if I bypass all of my FX, and then it acts the same as this new, small project in that it dropped out the first couple times, then it's fine. That's the other video sample I linked to. TESTED - I copied the new (problem) project and completely removed the drum sampler (kontakt) and there was no dropout. I closed CW and reopened and loaded my problem project that has a sampler (kontakt) and the dropout happened again, as usual. Do you know of any settings in CW that can help with the virtual instrument issue, or is that my audio interface drivers not playing nice with W10? There are several users in this forum that have the Echo Layla 3G with W10 and CW and said they have no issues--but it is an oldie. Thanks! EDIT 2: Just updated CW to the most current version. No effect. Issue remains.
  17. I used to use this app Speed Fan for fan speed noise. It's been many years, so do your homework. Thoughts?
  18. Hey @Noel BorthwickBorthwick Let me test your questions and get back to you. Wavelab and Sound Forge both work flawlessly, but they don't have virtual instruments. Thanks
  19. Hey @Noel BorthwickBorthwick Just wondering if you've had a chance to look at my reply to your troubleshooting questions?
  20. Hello @Noel Borthwick Here is the build I'm running. Just to be clear, the only change between CW being stable and how it is now is upgrading to W10. Windows says I can't capture video with my DAW (HW not acceptable) and I can't make the video files small enough to post here--so please use this link to view the examples. This first example "1" is new project. One effect, hardly any tracks. It will stop playing as soon as the midi drums start, but only the first 2 or three tries. After that, it works. Once it works, it takes a reboot to get it to do that dropout thing again. The 2nd example "2" is of a finished project. I waited to upgrade to W10 until this project was done (gratefully). With the update to W10, it will not play at all (dropouts) unless I bypass all fx. Then it acts like the new project in the 1st vid. It will only dropout 2 or three times, and then it will play. In any case, no matter why I get a dropout, there are no toast messages. I get project load toast messages, just no dropout messages.
  21. Hey @Noel Borthwick I'll be back in studio tonight and will provide those answers. All these issues started when I upgraded to W10. In fact, I have dropouts on a finished project that had no problems with W7--now I can't even play one measure in W10--no toast message there either. Thanks!
  22. Although your tales of trouble concern me, I looked at the features of v5 and $100 US is a little steep for me now. I'll wait (a long time) for a sale.
×
×
  • Create New...