Jump to content

Jerry Gerber

Members
  • Posts

    636
  • Joined

  • Last visited

Everything posted by Jerry Gerber

  1. Hey Bristol, You solved it for me! Thanks. I don't use screensets anymore as I prefer workspaces. But the files I was having this issue on had screensets hidden on the Control Bar locked. As soon as I unhid them and unlocked all of them, the Hide Tracks function works again. Best., Jerry
  2. I'm running the newest version of CW and have seen this issue in previous versions. I have a file with 33 MIDI tracks. After composition is complete I insert an audio track and render to the piece to audio. If I am satisfied with the recording, I mute, archive and hide all of the MIDI files so I can focus on post-production issues and wave file enhancements. When I save the file and re-open it, all of the hidden tracks, except the last one (#33) are visible. It doesn't matter whether I use a Workspace or not. CW doesn't remember that the tracks are hidden. It also doesn't matter whether the tracks are muted or archived. I've tried this on two machines, getting the same result. CW doesn't remember hidden tracks anymore. I've also tried this with several different .cwp files and they have the same issue. Might someone know what's causing this? I have all CW folders, including all audio and midi drivers, excluded from my anti-virus software. Thanks, Jerry
  3. Hmm, I wonder what's causing this. I'll contact CW tech support. Thanks for replying..
  4. I'm running the newest version of CW and have seen this issue in previous versions. I have a file with 33 MIDI tracks. After composition is complete I insert an audio track and render to the piece to audio. If I am satisfied with the recording, I mute, archive and hide all of the MIDI files so I can focus on post-production issues and wave file enhancements. When I save the file and re-open it, all of the hidden tracks, except the last one (#33) are visible. It doesn't matter whether I use a Workspace or not. CW doesn't remember that the tracks are hidden. It also doesn't matter whether the tracks are muted or archived. I've tried this on two machines, getting the same result. CW doesn't remember hidden tracks anymore. Thanks, Jerry
  5. Thanks Bitflipper for the successful solution to CW crashing upon closing. I put the 4 MOTU audio and MIDI drivers in /windows/system32/drivers in the exclusion list of Windows Anti-Virus (Defender) and now I cannot get CW to crash. Even if I close it with the file I saved without closing the file, it still won't crash. Wonderful!! Jerry
  6. Is there any particular reason to do that? Yeah, I've excluded all CW folders as well.
  7. Yep! Now I am 99.9% certain that the issue has been resolved by excluding the 4 MOTU drivers in Windows/System32/Drivers from being scanned by Window's Defender. Yay! I wish I had known sooner. I cannot get CW to hang after closing, wonderful! Also, if anyone is having trouble opening the Theme option in Preferences/Themes (it takes a long time), do the same thing; exclude C:\Cakewalk Content (where themes are located) from Windows Defender. This resolves that issue as well. Jerry
  8. Hi Bitflipper, I think you may have solved this for me. I placed all 4 MOTU drivers (Audio, USB, MIDI and, I think a system driver) that reside in Windows/System32/Drivers) into the Windows Defender Anti-Virus Exclusion area (whitelisted), so they are now not being scanned or monitored. So far I haven't been able to get CW to stick in memory. So, I am giving it a few days and I'll let you know for sure, but I think this has resolved the problem! I hope! Best, Jerry
  9. Not really. I am pretty sure the MIDI interface is involved in this because if I shut it off before closing CW, either it hangs windows or it shuts down Cakewalk after I try booting CW from memory. Since I am never sure what it will do if if shut down the MIDI interface first, I just wait a few minutes before closing CW and that does the trick. I'd still like to know what's causing it, but composition is always the #1 priority and I've already spent too much time on this.. Thanks! Jerry
  10. The only solution I have found that always works is to simply wait a few minutes after closing a file to close Cakewalk. When I do this, Cakewalk leaves memory as expected and I can shut down the computer. I am about 80% sure it has to do with the MIDI interface but other than continue to keep drivers updated, as I always do, I don't know what else to try.. Thanks! Jerry
  11. Hey Noynekker, It seems to happen on every project. I have numerous startup templates, not sure if any of those wouldn't have this issue. I'll try what you suggest, opening the default normal template, type in a few midi notes and close CW right away. Thanks, J
  12. Good idea. I'm running CW on an i7 Windows 10 machine with 32 GB RAM, 2 SSD drives and with a MOTU 1248 audio interface and a MOTU MicroLite MIDI interface. The MIDI interface is definitely the culprit because if I turn it off after closing CW it often causes the BSOD and the kernal corruption message. Both the audio and MIDI drivers are fully up-to-date and the latest that MOTU has posted on their website. I also updated the NVIDIA video driver but I don't think that's related to this problem. If I close a CW file and wait 3 or 4 minutes before closing CW, the issue doesn't happen. Thanks, Jerry
  13. Thanks! I hope the Resource Monitor will give me a bit more information as to what's going on. If I wait a few minutes after closing a file before closing CW, I don't have this issue, so something must be slow to leave memory..
  14. When I close CW sometimes it doesn't leave memory. If I turn off my MIDI interface I get the BSOD, a kernel level corruption occurs. I've updated my graphics driver and don't know what is causing this. Any suggestions? If I close a file and wait 5 minutes and then close CW, it works without issue. Thanks, Jerry
  15. I don't have time to scroll through all the puns to see if this one has already been posted, but here it is: My psychiatrist told me today that I am suffering from kleptomania. But don't' worry, I am taking something for it.
  16. With further investigation, I've narrowed down this bug in the Find-Change dialogue box: When converting C#s to D-flats using find/change, using the question mark to have the conversion affect all octaves of C# will not work. With this particular enharmonic conversion, you must designate the actual octave, so inputting C#5 to D-flat5 or C#3 to D-flat3 will work successfully. This is the only enharmonic equivalent that I have found that has this bug. Even going from D-flat? to C#? will work, just not in the opposite direction. This bug has existed since Sonar, but I, and perhaps others, have neglected to report it until now. Thanks, Jerry
  17. There's a bug in Cakewalk that's existed for quite a long time. When changing all C#s to D-flats using Find/Change, the change fails. With every other enharmonic equivalent it works fine. Even going from D-flat to C# works as does A# to B-flat, F#-G-flat, etc. But C#?-to D-flat? does not. Thanks, Jerry
  18. Thank you David! Glad you enjoyed listening. Jerry
  19. Hi Andy, Thanks for listening and commenting! Best, Jerry
  20. Thank you for listening and commenting Wookiee! Jerry
  21. Glad to hear it! Thanks Tom! Jerry
  22. Hi Bjorn, No, I've never in my life used the piano roll view for composition. I compose in the staff view, and make use of the event list and the controllers view often. Thank you for listening and commenting, glad you enjoyed the movement! Jerry
  23. Hi! Does anyone have experience using the Tascam CG-1000 master clock? I am particularly interested in how it compares to the Antelope OCX-HD master clock. Thanks! Jerry
×
×
  • Create New...