Jump to content

Terry Kelley

Members
  • Posts

    902
  • Joined

  • Last visited

Posts posted by Terry Kelley

  1. 2 hours ago, gmp said:

    Good post, Terry. I did forget to say that I always work with small clips, one or two  vocal phrases and I immediately "bounce to clip". Then move to the next spot. I, as a habit, only have 1 project open at a time. I assume most V-Vocal users are already doing this.

    I'm a pianist so my template always has Ivory, Superior Drums and Kontakt synths connected. So my RAM is about 3.5 gigs. About a month ago I did forget to close and reopen CbB and I got a crash right away - oops. My method has been working 100% for a year or 2. 

    Hi gmp,

    If the project is really simple (less than 4-5 tracks), V-Vocal behaves well. Unfortunately I am a track and effect pig so it makes things worse for me. I am surprised Cakewalk keeps up with 40+ tracks with many having 3-4 effects. But damn ... it does. It's voodoo.

  2.  

    At some it would be good to collect together the various actions we try to get V-Vocal to work once it decides to go south. I'd love to hear other's tricks. And yes,  we have beat the Melodyne option horse to death. This is about working around V-Vocals short comings.

    For me, I try one or more of the following in this order.

    1. Disable all effects. Strangely this works enough times to give it a try.

    2. Bounce the clip. Try bouncing by itself, then try bouncing with adjacent clips, then give up and move to option 3.

    3. Bounce to stereo then open V-Vocal. If it fails, convert to stereo and back to mono (if that is where you started.) Then try 4.

    4. Close the program and restart. It rarely works but sometimes ....

    5. Reduce the size of the clip to as short as possible and still be able to make the changes I want. It could be as small as 1 second. This is one of those solutions that makes me think V-Vocal is running into some other chunk of memory Cakewalk is using. Hence the C0000005 (you ain't supposed to be in here.)

    6. Copy the track/clip to a new project but I almost always have to close the other project where the crash occurs or the new project will crash too. Make the changes and copy it back into the original project. I often copy an instrument track with the clip to help identify the pitch changes I want, but I add that with no effects. Either way, editing in a new project almost always works. I'd say 95%+.

    7. If I get the empty V-Vocal window, I bounce the clip which works and/or convert to stereo and back to mono. but I usually have to close the project and restart. If Cronus or Vpenc don't decide to crash, the wave is usually there. If it crashes, I will be forced to option 6.

    8. If the volume of the clip is low enough, you might find notes where you don't get the initial yellow pitch line. The waveform is there but no yellow level/pitch line. Exit V-Vocal and raise the gain of the clip 6db (or more) until you get the yellow line across the complete note. Edit the clip, render and then reduce the gain by that same amount. I see this at the end of long notes where there isn't enough signal for V-Vocal to follow it as the note decays. The line will end before the note actually does.

    Most crashes are in Cronus and Vpenc. Once in awhile, Cakewalk will just close. I never see a VPSoloDec crash.

    The reliable option 6 is a bit of a pain but once you start doing it you get pretty quick and it's faster than trying the other options first.  Just accept your destiny.

    To gmp, your suggestions are exactly what I see but pretty much head for option 6. Moving the clip in memory seems to make it work again.

  3. No doubt. It appears the equivalent is Assistant for $300. Just from my comparison. Is 5 more stable than the previous versions?

    In the meantime some of us will share our V-Vocal workarounds.

    • Like 1
  4. It appears Tempo nodes are being (randomly/arbitrarily) added past the intended end of the project causing it to continue past that expected end. Chris.r and I have both noticed it. Maybe we are fumble-fingering something but we don't recall doing anything that should add a node. Once it's deleted the project will end as expected.

    One  project I was working on ended normally at 5:16 but with either the 4.1 or 4.0 update, I noticed it ending at 7:44. Out there is this Tempo node.

    If it's us, let us know so we stop doing it. :)

    • Like 2
  5. 53 minutes ago, chris.r said:

    I've noticed that since the new Tempo Track a tempo node is added at the end of the project every time I right click>'Reset Tempo Map' or 'Clear All' in the Tempo Track assuming there's none already. It's a little bit puzzling.

    I'll post it in the 2021.4 thread. Maybe something is amiss. Thanks for the followup Chris.

    • Like 1
  6. 22 hours ago, Terry Kelley said:

    This is interesting. I never thought of this and tried it on a 5:16 song. Ctrl-End took me to 7:44. There is nothing out there or past 5:16. But you would think it would take you to the last bit of data.

    I looked into this more and it turns out there was a Tempo node out at 7:44. I am not sure why since I didn't intentionally add it. I deleted it and it stops correctly and CTRL-End is at the correct spot.

  7. 5 hours ago, abacab said:

    5 or 7 frets? I don't understand...

    E1 to C5 works here. And it appears to include 20 frets. 😉

     

    Ample Guitar M II LITE capture.JPG

    On the freebee? That's what I have. On mine, I can't play anything above the 4th fret on all but the high E on the fret-board.  On the keyboard I can play all the way up but if you watch, it only plays in the 1-4 fret range until it gets to the high E. That will go all the way to the top of the neck.

    Maybe there is a magic setting to go higher? It's not like I read the book ...

  8. I think in one way or another each of us have expressed our reasons for liking and wanting to use TTS-1. It's not a one-off by some internet random. Old, oh yeah, but when functional, it's extremely useful. But to your other point, yes, many of us have learned it's limitations and don't expect it to fill every need.

    I do agree with your point about (generally) avoiding the myriad of one-off VSTs floating around. But I don't see TTS-1 as one of them.

    • Like 1
  9. Did you insert the TTS-1 with the Instrument Track per Output checked in the Insert Soft Synth Options? When you do, it creates 4 tracks for each output. Then you go into the TTS-1 settings and assign each "Part" to an output. You then route those 4 to some master or main output. You can insert audio effects on each track but you are stuck with any/all Parts sent to that output going through the same effects. You can alternately, assign each midi track to an output one by one, freeze it, copy that to a new track and keep going until each one has it's own track and therefore can have it's own audio effect.

    Your questions imply you missed a step somewhere.

    • Great Idea 1
  10. 24 minutes ago, User 905133 said:

    Please notice what I wrote: esp. "for some of us."  I did not say "for everyone." 

    Please understand that not everyone has the same experiences. 

    You can contradict me, but that doesn't make you right. 

    Also, doing an internet search and finding "people battling it as far back as 2006" does not disprove that, "TTS-1 has worked flawlessly as intended for some of us over the years."

    I have seen people talk about issues with TTS-1.  I never doubted their experiences.  We all have different experiences. We all have different preferences. We all have different workflows.

    Obviously my experiences are not the same as yours.

    I stand by what I wrote.

     

    Ok.

    • Thanks 1
×
×
  • Create New...