Jump to content

Terry Kelley

Members
  • Posts

    902
  • Joined

  • Last visited

Posts posted by Terry Kelley

  1. I turn off all effects (highlight FX), turn on PDC (highlighted) and set the buffer down to 128 or 256. At that point the delay is not noticeable but my system sometimes starts going static at 128. 256 is good enough for me.

    Considering how slow MIDI really is, it's disappointing that you have to defeat so many thing to get it to pass from the keyboard/controller to Cakewalk without taking seconds (ok, it's less than a second with effects turned on. no PDC and a larger buffer.) It's a Windows issue. DOS didn't have this issue even with the generally slow MIDI data rate and opto-isolater delays.

  2. 18 hours ago, Kalle Rantaaho said:

    Would you elaborate a little, please.

    I don't understand the question. Malformed how? Random forms which don't match the audio?

    When I open certain files, a box pops up with the message. I close it and the file opens. It appears that resaving fixes it.

     

      

    6 hours ago, Jonathan Sasor said:

    if the audio plays fine, then it might just be a picture cache issue. You could try right-clicking and going to Associated Audio Files, then recompute picture. Or just delete the contents of Picture Cache in your Cakewalk Projects folder before opening the project.

    I'll give this a try. I can't really predict or associate it with anything specific.

  3. I've learn something about TTS and V-Vocal. Add TTS early in the project and as many instances as you think you will need and do your V-Vocal tweaks before you start building up the track with effects. Otherwise, it's crash city with no fix in sight. I've learn - don't expect to add TTS or use V-Vocal late in the project. Grief will ensue.

    If I have a project that I've built up with a lot of tracks and effects, I have to copy the audio to a new project to get V-Vocal to not crash. I usually copy one instrument track with the audio so I have a pitch reference. 

    I've spent countless hours with problem projects trying to figure out what is going on. I've started deleting effects, freezing tracks, merging tracks and nothing works. I've play with just about every setting, switched audio interfaces, different PC's, slaughtered a goat, nothing works. Once either TTS or V-Vocal decide to not work, they will never work in that project no matter how much you delete/remove/change/pray/dance ...

     

  4. I originally posted this in the Early Access 05/20 thread since I first saw it after I installed it but after rolling it back, the issue is still here. It's not related to EA05.

    I can't change the CPU Meter Option in the Performance module. I can right click on the module, go to the CPU Meter pull-down and see all threee options (Audio/System/Overall) but selecting System or Overall doesn't. Audio Processing stays checked.

    Is there some other setting that can lock the CPU Meter option?

    On a side note, I also lost the Audio Processing/Engine Load/Later Buffers dialog when you hover over the Performance module but determined it went away because I de-selected Tool Tips in the Preferences (weird, but it does that.) Tool Tips must be selected to see that dialog.

  5. Not sure if this is related to the 05 EA but I can't change the Performance/CPU meter settings. It's always stuck on Audio Processing. I can't select Overall or App. Also. The drop-down shows them but no matter what I select it stays on Audio Processing.  I also don't see the dropout information if I hover over the CPU meter.

    Did I lock these settings somewhere?

    Edit: I rolled back and it still doesn't work so it's not EA 05.

    Edit 2: Changing the CPU meeting setting still doesn't work but I found Tool Tips needs to be enabled to get the Audio Processing, Engine Load, Buffer bubble to show up. It's shouldn't work that way. There is nothing intuitive between Tool Tips and the Performance bubble. 

  6. 9 hours ago, pwalpwal said:

    they're both DX instruments, if that helps troubleshoot

    Hi Pwalpwal,

    I've done a lot of testing around TSS and V-Vocal problems. About the only conclusive thing I can say it that if you plan on using either, use them early in the project because at some point they will stop working. I've tried everything suggested in the last decade and nothing conclusively works.  Maybe Direct X changes, maybe they were never stable in the first place (that sounds true for V-Vocal), maybe other changes exposed their issues ... who knows.

    V-Vocal hates effects. If you installed any effects (like compressors, eq, etc.) it will likely crash on one of them while creating the region. Remove them all and it will crash on Cronus. Open a new instance in CbB and copy over the audio and you have a better than 50-50 chance V-Vocal will work. Again, this is a function of using it early in the project with no other plugins. But be prepared to have to close CbB completely, then open it with your temporary audio file and for god-sakes don't add any plug-in. Don't. Don't even think about. Oh, and just to give you hope it will work with lots of plug-ins, being used later in the project and without rendering immediately to make you think you have it fixed. Fool.

    TTS is similar. Add it early in the project. Adding it later risks it not wanting to insert or play anything without a crash. Too bad because it is a very decent synth.

    The crashes are access violations. That can be caused by many things in Windows. It's not practical for the average Joe to follow it through memory and see where it's jumping out.

    I've figured out some work arounds in case I need to use either but I do what I can to avoid them. I also don't report the issues anymore. :)

  7. The issue for me is that if CbB decides to do something funky, troubleshooting it pretty much impossible. Yes, there is always someone that will post that they have  been using it since 1956 without any problems but there are many people that have it go totally goofy without any obvious changes.  Just when I think I have it dialed in, it decides to go south. I decided that constantly posting with the latest weirdness just isn't worth it.

    I get that the team is at the mercy of the shoddy plug-ins we want to load and can't deal with every corner case. Got it. But it's pretty unpredictable if today is the day it decides to close without warning, fail to export without hanging, needs a system reboot or crashes on TTS or V-Vocal ...

    It could be better.

×
×
  • Create New...