Jump to content

David Pollock

Members
  • Posts

    86
  • Joined

  • Last visited

Posts posted by David Pollock

  1. 3 hours ago, John Vere said:

    You need to remove both of those  from your system, They are what is known as an invasive drivers and they will cause issues like this. No doubt even if you deselect it you will find it listed in the latency settings in Sync and Caching tab. Its bad news. 

    Remove it in the Reg Edit app as shown below.  Just choose delete.  You only want your Motu or any other proper audio interfaces,  see my ZoomL8 too,   listed here.  

    These drivers are installed with other software as alternatives to on board audio and are not needed even by that software. The realtek ASIO driver is totally not recommended by Cakewalk staff.  Windows now uses WASAPI mode. 

    If you follow my set up in this video you can use the Motu for everything and even multiple music apps can be used at the same time.   

    https://youtu.be/opDwsC4_llg

     

    Screenshot (436).png

    Thanks. I've done that. We'll see what happens.

  2. 13 minutes ago, 57Gregy said:

    Did you first deselect the generic driver? If possible.

    Installing Cubase was the thing that affected this. 

    Thanks. I did deselect it in the input area, but what I needed to do was deselect it in the output area to make it selectable in both locations. 

    • Like 1
  3. Suddenly the generic ASIO driver is loading, and I cannot select the MOTU driver installed in these setting(and I reinstalled it to be sure it was OK). The only thing I have changed lately was to install a trial of Cubase. Otherwise, I have not made any system changes that should affect this that I know of. What's happening?

    Win 10
    Cakewalk 2024.02

    image.thumb.png.f29d5ffef6f02fc15161115c2450c53f.png

     

  4. 3 hours ago, David Baay said:

    Omni is an Input setting; promidi's talking about the forced Output Channel setting that dynamically overwrites the embedded channel information in each event as it's transmitted. But I don't really think that's relevant to this issue. And I highly doubt the project is actually corrupted. Most often the "corruption" conclusion is just a failure to identify the root cause of unexpected behavior. I don't own anything from EastWEst, but if you can share a track that's misbehaving, and the cause isn't East West itself, I'm sure I can fix it. The crashing issue definitely sounds like it was a problem with EastWest. A quick Google found other reports of Reaper/Studio One/Finale crashing "after 10 minutes" using EastWest Play; sounds like a memory leak.

     

    OK, I'll DM you. But this is my seminal work that will establish my place as a musical legend, so don't share it with the world until it's finished. 

  5. 15 hours ago, Promidi said:

    One other thought.  Are all MIDI events on a given MIDI track set to the same MIDI Channel.  Are all MIDI tracks set to a specific MIDI channel rather than “none”?

    Personally I make sure all MIDI events on a given MIDI track set to the same MIDI Channel. 

    I also set all MIDI tracks set to a specific MIDI channel.

    I have also configured my Cakewalk so that when I bounce MIDI tracks, all MIDI channels that are in the resultant MIDI clips get re=channelled to the MIDI channel of the track containing those clips. 

    One other uncomfortable possibility is that you simply have a corrupt project.

    Currently, they are set to none, but previously, they were all Omni.  And yes, I had labeled the project as corrupt and likely unsalvageable a while back. But after spending hours on it, I was able to revive it enough to keep working on it. I am painfully close to finishing it. I'm just tweaking here and there. So I plan to just keep at it unless it totally implodes on me. Redoing it would be a huge undertaking.

  6. 5 minutes ago, David Baay said:

    Events can be hidden by slip-editing a clip boundary or splitting a clip with Non-destructive MIDI Editing enabled. You won't see the events in any view, but the Contoller Pane will continue to display a lane for them. Bounce to Clip(s) will permanently delete them so the superfluous lanes go away.

    Hmmm. That one is going to take me a while to process. Thanks.

  7. 32 minutes ago, Promidi said:

    Do you run any CAL scripts and then, immediately after, do a delete of events? (Using the “delete” button on your PC keyboard)

    I know, from actual, experience that that can cause unpredictable results in CbB (including adding CC events in other parts of the project).  In some circumstances immediate deletes after CAL scripts can crash CbB.

    In all of my projects, I use heaps of controllers and I have never had MIDI events just appear.  The only MIDI events in my projects are ones I have manually entered with the mouse and CAL scripts. Of course I am extremely careful not to run a CAL then immediately delete.

    Has turning off those MIDI outs in the VSTs and the MOTO M make a difference?

    I do not run CAL scripts. So far, turning off the MIDI outs and in MOTO have not fixed this last issue of random controllers showing up. I have not had time to test the other issues yet, but I will let you know when I do. Thanks for your help. 

  8. 6 minutes ago, David Pollock said:

    My MOTO M Series audio interface was set in CW preferences to enable midi out. I turned it off. We'll see what happens. Thanks.

    I should also have described this which I have only noticed in this one project. Controllers keep appearing in the controller area even when I have deleted them. Then if I click on another track and come back to this one, the controller reappears. It happens most often with the wheel, but also with a few others. What does that mean?

    cw.jpg

  9. 8 hours ago, David Baay said:

    Do you have any MIDI I/O devices available/enabled at all in Preferences? If you're not aware of ever having set up loopback, it's unlikely to be relevant. I was just mentioning it as one of the few ways I could imagine getting unexpected messages recorded with no controller connected.

    If I'm understanding correctly that you don't use any MIDI input devices, you can set the Input on all your MIDI/Instrument tracks to 'None', disable Always Echo Current MIDI Track in Preferences, and you shouldn't have any further issues. Or, alternatively, you can set all Inputs to CbB's Virtual Controller, and never open it.

     

    My MOTO M Series audio interface was set in CW preferences to enable midi out. I turned it off. We'll see what happens. Thanks.

  10. 45 minutes ago, Promidi said:

    Do any plugins (synth or effect) have MIDI out enabled?

    I found three out of 52 and turned them off. I will have to check if it helps when I have time later. Thanks.

  11. 1 hour ago, David Baay said:

    I have never seen an event recorded in CbB that didn't come from hardware or from a MIDI-generating plugin except in the unusual case that CbB was recording MIDI via hardware (or virtual MIDI cable) loopback and picking up messages sent at the start of playback/recording by enabled Volume, Pan or Patch widgets in a MIDI track. And I know of no circumstance in which CbB will spontaneously generate [Pitch] Wheel events in the absence of an automation envelope explicitly created to do it.

    Thanks, but I do not know what to do with that observation. There is no hardware attached, and as far as I know, no midi-generating plugin at play. How would I investigate the loopback possibility you described?

  12. I have revived a large (for me) orchestral project that appeared to be completely corrupt as described here:  Crashing problem solving - Q&A - Cakewalk Discuss | The Official Cakewalk by BandLab Forum and I am nearing the end of fine tuning and tweaking. One of the original problems was, it seemed, that my old keyboard was sending errant wheel signals causing some instruments to go out of tune. I have long disconnected that keyboard and not connected another. But I just noticed a wheel midi event on a channel where I have not added one, and I have no explanation for how it got there. Since I still have these random times when an instrument will go out of tune, I think this must be the cause, and I need to make sure they stop happening.

    What can cause these wheel events when there is no keyboard attached, and in fact, I have not added nor intentionally used wheel events anywhere in this project? 

  13. I have managed to get the project working again by painstakingly changing each of the 52 instruments to a different instrument patch and then back again to the correct patch. Once I did that, the crashing stopped--so far at least. Now I have a bizarre problem with the Play instruments going out of tune for no reason I can find. EastWest refuses to help since this is with Cakewalk, so it remains to be seen if I can actually finish this or not.

  14. I have reinstalled Cakewalk along with the entirety of my Play instruments. Still crashing. There's something in this project that is the problem, I think.. With 52 tracks, it takes a while to reload every time it crashes. So this is supposed to be fun, is it?

  15. 3 minutes ago, Wookiee said:

    @David Pollock do you FX in the tracks? You could try removing one at a time to see if that works. I can't remember but I think if you use mix recall it remembers FX so take a snapshot, remove an FX, I would save the FX settings as a preset so they are easily recalled.

    The other option is to use safe start and exculd a plugin at a time, lengthy I know. 

    Thanks, yes, I've started in safe mode without all fx. Still crashed. So those aren't the  issue.

  16. 18 minutes ago, Wookiee said:

    @David Pollock have you disabled USB power management? 

    I had not, but I did, then rebooted and relaunched. Still crashed. And I just discovered something I had not noted before. It was crashing at the same exact place in the section I was currently working on (but it also crashed in lots of other places, so it is not just this one place). It seems like I might be able to discover something from this. There are not that many instruments with notes at this point of the crash, and although there is some envelope activity on the tracks, there is nothing changing at the place of the crash. What else should I consider?

  17. 2 minutes ago, msmcleod said:

    Is it possible some audio related device is going to sleep?  This could cause a driver to crash, or Cakewalk to crash if it wasn't notified of it going away.

    Check your USB sleep settings just in case.

    Mmmm. Not that I can tell. There is only one device--a MOTU M2, and it's not sleeping.

  18. I know there are MANY posts about crashing, and I've read a bunch of them, but have yet to find a solution. I have a large project that has 52 tracks of nothing but EastWest Play instruments. All of a sudden, it is crashing ten minutes or so after opening it. A variety of things are happening at the moment it crashes: I've muted a track, dragged a track, edited an envelope, etc. I cannot determine a particular action causing it. I opened in Safe Mode with no effects as well as turned them off once opened. That makes no difference. I'm at a loss of what to do.

     

  19. 1 hour ago, JohnnyV said:

    Sorry my friend,  but it is a 99.5% probability that you did. 

    I hear you, but I guess we'll never know for sure. Given all the other odd things happening in this project, and the fact that this happened a lot in this project while never before being an issue for me, I do not believe I caused this. 

  20. Thanks for the selection/find suggestion. I will see if that will help. 

    I would have agreed that I must have done something wrong, but I have spent many hours in Cakewalk without this ever happening before, and it happens on different note numbers on different kinds of tracks. I don't think I did anything to cause this. 

  21. In a large and long orchestral project, I am suddenly finding tracks where notes have been shortened as you see in this screenshot. When it happens, it happens with a number of notes across many measures. And the shortened notes are so short that it is really difficult to be able to grab them and drag them back out. In other words, this is a major pain (and coming near the end of this thing I've worked on for months).

    I know that it is possible to accidentally select all the notes of a specific note in a track and accidentally change them while changing one of them in another place. But that is not what's happening here since there is suddenly so much of it and it is different notes here and there. I don't see anything in the archive about this. Any ideas?

    Win10 machine with latest Cakewalk.

    image.png.51412d701d2061f757283c4c7e9077f8.png

    image.png.38ff8ca175f6760fe6c053435a171c86.png

  22. I created a new project to further try and narrow down the issue. I created four simple instrument, softsynth tracks without the keyboard connected. It worked fine. Connected the keyboard and played around with it. Worked fine for a while, and then the key change stared. I looked at the events lists for all tracks. Nothing but notes. So the issue is apparently not the recording of such events. But yeah, still the keyboard in some way it seems.

×
×
  • Create New...