Jump to content

jono grant

Members
  • Posts

    607
  • Joined

  • Last visited

Posts posted by jono grant

  1. Hi, I'm trying to select multiple tracks and export them using "Tracks though entire mix" so that each track goes through the bus processing I have on the master bus. It goes through each track, exporting slowly because of the processing. But then, it only makes one exported track, after all that!

    What am I doing wrong? I've done this before but not sure why it's not working now. It should be making multiple exports of each track I have selected.

    Do I have to create a task or something? Kind of confusing. Any help appreciated.

    Thanks

     

  2. Thanks but that method is absolutely ridiculous. No one is expecting CW to be a video editor, just simply render out a small clip of a project with the video included. It says "Export to video" in the file menu, then it should do that. 

    People that want to do this are not editing video. They are scoring music to picture, and when working on a 2 hour film, constantly going to other programs to do a simple task like this is not something a composer has time for. 

    Cakewalk's dealing with video has been such a joke.  The folks updating the program should really look at decade old problems rather than redesigning the parts of the program that already work. 

    "Select all, highlight a region and export to video file" that is how simple it should be. 

  3. Hi, I have a video in cakewalk that I'm doing some music on.

    I wanted to export a short region of it as a video/audio file.

    I select a region and export the video. It exports the entire video though, not the region I selected!  (I say select all, then chose the region, even tried turning on loop. It doesn't render the full audio, it renders what I selected, but not the video.

    How do I do this?

  4. 14 hours ago, Andres Medina said:

    Mhhh, perhaps this is the explanation (and workaround)  for this related problem I had:

     

    Tried it again this morning, the multiple tracks brought into melodyne seemed okay, but there were some tiny glitches, very hard to detect but there. Back to bringing them in individually! My friend doesn't have this issue in Cubase.

    • Like 1
  5. I've found the solution to this issue. In Cakewalk, if you have clips that have been slip-edited or have fades on them, and you choose multiple tracks like this and try to bring into melodyne region effects, they get all garbled up and glitched.

    However; if you bounce the files to clips first, it works fine to import multiple clips.

    Perhaps people not having this issue were simply bringing in clips that were not edited/faded etc. (I think?)

    The weird thing is, if I have a single track with edits and fades, it works fine, only happens on multiple track/clips

     

    Anyhow, it works if you bounce to clips first. Cheers

    Jono

    • Thanks 1
  6. On 5/27/2022 at 5:40 PM, marled said:

    Sometimes me too! But in other situations, especially for non-drums instruments I prefer using AudioSnap, because it does stretch the audio between transients.

    If you want a proper result, then the speed is not that much better IMO! But the difference is the stretching. 

    Ya, the manual method is best but you end up spending time filling gaps that AS would just stretch...

  7. On 5/27/2022 at 7:55 PM, Lord Tim said:

    The MultiResolution algorithm is definitely the most accurate when it comes to detecting transients, much better than the original 2 algorithms, but AS in general still struggles when there's any kind of noise between hits, and will often see notes without a definite start as having different transient points and will put multiple markers in.

    Once you clean up the noise between hits, AS is excellent once you learn the way around how it wants you to work. But that's where I think AS needs the most improvement in the next iteration: better control over what it "hears" - high and low pass filters, gating, masking decay on each hit... if it gets cleaned up like that before it hits the detector, you'd rarely run into these kind of issues if you configure it well, I think.

    I've certainly put my laundry list of things I'd like to see in the next version in, and I'd say this is on a very long to-do list somewhere!

    I think the take away here is to gate the heck out of everything before creating a mix to add to the clip pool. And yes, the Radius mix algo is best for this. 

  8. Hi, question regarding Audio Snap:

    I have a live drum kit, I turn off any effects and bounce all the tracks to a single track, I apply audio snap to that mixdown in order to add the clip to the pool and then I can apply those markers to my individual drums tracks. 

    In the attached image, you'll see that audio snap will sometimes add double transients to a single drum hit. I have to go through and delete the unwanted transient markers.

    My question is, why does it do that?

    and also, which marker is best to delete? The one sitting right on the drum hit or the doubled marker that is either before or after the hit.

    This is such a powerful feature, it would be great if it was more consistent in tracking.

    Any info appreciated, thanks!

    Jono

    Audio snap.jpg

  9. 20 year CW user, for sure I know where all the settings are. It's ignoring them. I have zero changes set and it will still save every time I push stop it seems. Only on a heavy file with lots in it but still , it's weird. 

    Also, if I ever crash, it's usually at the exact same time as an auto save is being created. 

  10. Hi, I've been getting issue where I bounce down a mix, I am using an external insert on a drum buss. When the bounce is finished, there's only about half a bar of audio.

    I've tried different buffer sizes and rendering in real time with and without audible mixdown. 

    I assume it has something to do with the external insert but not sure. I've only been seeing this since they upgraded the export window.

    Anyone else having an issue like this?

    Thanks, Jono

  11. On 2/22/2022 at 4:51 AM, msmcleod said:

    If you're working in the PRV, this can generate a lot of changes as IIRC a lot of operations are done on an individual note by note basis  ( as opposed to the clips view, where operations are done on a clip by clip basis ).

    The best thing to do when you're still at the stage of editing events/clips is to set your auto-save to be time based.

    I set it to 10 minute autosave only. There is no value set for amount of changes. Yet, it saves all the time! This is on files that have a fair bit going on, but still, why is it saving so much if set to 10 minutes?

    Also, if I ever crash, it is always at the same time as an autosave... 

  12. It's also worth noting that any time I have a crash in CW, it is at the exact same time as an autosave occurs. 100% of the time. I've raised this issue for years and years. CW autosave is messed up. It doesn't respect anything you have set in the preferences as far as zero changes, or setting a time limit. It simply doesn't work. I wish CW would look at these issues that have been present for ages.

    JG

×
×
  • Create New...