Jump to content

Andres Medina

Members
  • Posts

    646
  • Joined

  • Last visited

Everything posted by Andres Medina

  1. I agree. Just duplicate the track (without the midi data), and record over the section you want to update. This is my preferred workflow, because you just get rid of punching in, etc. You can build a consolidate midi track later or just leave the multiple tracks as they are.
  2. Mhhh, perhaps this is the explanation (and workaround) for this related problem I had:
  3. Also, double check that you didn't accidentally hit the "Pause/Inter" key on your PC keyboard. This disables certain graphic movements.
  4. Yes, I do often find this same problem, that appears randomly: I think it happens because Melodyne does not always auto select the track you already selected for editing. If you click in the select track (orange icon) inside Melodyne, you get the blops displayed.
  5. It's very easy in fact: Select the whole track you want to edit in Melodyne (it can be even a comp track including the selected clips, if your workflow includes it) Apply effect region Melodyne creates a composite region track of all clips (first it will bounce all audio in the background) Edit your vocal (if you want-need), just erase the silent spaces or noises in between When you are done, render the whole track fx region
  6. I understand. Thanks! Good to know. Hope I will solve it, though!
  7. Thanks for the feedback! I found that the crash happens only on the first attempt to create a Melodyne region in the project, AND applying it to several tracks at once. If I already have a Melodyne region active, there is no crash at all ... Celemony team seem to have a trace of what's going on, and will let me know.
  8. Narrowing down my previous post, I am getting continuous crashes when applying Melodyne to audio tracks. It seems that it only happens when applying the plugin to at least 3 contiguous audio tracks. The crash occured in the process of "Initializing Regions", according to the state bar. There is no minidump created, even when ExceptionHandlingSeverity is set to 7. I'm able to reproduce it by following this steps: Insert 3 adjacent audio tracks Record some material Select the 3 tracks at once Apply Melodyne from the Right Click context menu Crash Anyone having the same problem? PD: I'm updating Melodyne team with this new information, that they are already addressing.
  9. My guess is that you can't split unless the region fx is rendered... don't know the technical reasons, thought.
  10. Update: CW not crashing anymore. I reinstalled Melodyne from scratch, AND wiped all traces of melodyne from my project. Then re-applied Melodyne to pertinent tracks and it's working fine - at least until now! I guess, as msmcleod pointed out, the compatibility issue between versions of Melodyne may be at play, as this started to fail after updating to latest Melodyne release. And I will follow John's advise to render Melodyne after finishing editing, to avoid this kind of trouble. Still, I'll follow up Celemony support response, to be 100% sure Melodyne will continue to be as reliable as always has been within CW.
  11. I see. So, for an ongoing project, as long as I use the same Melodyne version, I'll be fine keeping the Melodyne tracks unrendered, but should make sure to render when I'm done. I'll stick to it. Quote: "Nowadays I always copy the track and archive the original, then render any Melodyne edits to the copy. If I'm 100% happy with the edited track, I'll delete the original." - Got it. Safe workflow. Thanks -
  12. Update: Still getting crashes. This time CW crashed at the moment I created a new region efx in a track. So, there seems to be a problem with the new version of Melodyne, at least in my system.
  13. Thanks - I already placed a ticket at Celemony. Let's see what they find. Regarding active region effects: I wasn't aware that you are supposed to render region effects before closing a project... I did have unrendered regions, but never had a problem before. Anyway, I uninstalled - reinstalled Melodyne from scratch, and it seems that the crashes are gone... let's try a bit more. I first pdated Melodyne from the pop up window. This time I did directly from the Celemony site, with CW closed. Let's see -
  14. Thanks! yes, it seems a Melodyne issue then. I'll do.
  15. Hi, I'm getting continuous crashes when opening projects. Recently I installed MODO drum, and a Melodyne update. The project opens fine, but upon finishing the loading of the track view, it crashes with no warnings, and the program closes. I did delete MODO DRum plugin to see if it made a difference, but still CW is crashing. Then I uninstalled MODO Drum completely, to no avail. Still crashing. Then I increased the ExceptionHandlingSeverity to 7, and now I'm getting the crash window. I can see that the faulty module appears to be Melodyne... I will reinstall Melodyne and see what happens. The corresponding minidump files are enclosed. I'll appreciate support help. Thanks! --- MiniDumps.zip
  16. It doesn't help when the tone of the communication is belligerent. I know how stressful is to have a problem and not getting a solution, but never forget that most people here is genuinely trying to help - for free.
  17. It appears, based on your other post, that your VST's are not properly installed?
  18. Here, all my VST3 works just fine. May be you need to re-scan the VST plugins and make sure first that they are properly installed.
  19. I agree. My workflow is the same: work audio inside CW, export the audio (either Wav or Broadcast Wave), then use a video editor to assemble whatever you need. Is really straightforward and easy. I'm not familiar with other DAWs, and of course it would be nice to select audio in your timeline and choose to export video at the same time, but not sure if it's easy to make it work for the developers, as it involves editing video capabilities.
  20. I see. Good to know. Thanks! Still I can use the main menu, so no big deal!
  21. Somehow, my track templates folders are not updating inside CW, in this specific scenario: Id I add a new folder or change the content in nested folders, they are not updated in the "Insert from Track Template" menu that pops when right clicking an empty space in the track pane. Not even after restarting CW. BUT they are correctly updated when using "Insert/Track Template" from the top menu. May be this a bug? (the number of subfolders inside my track template folder is greater than 24: there is a limitation on this count?)
  22. Yes, you are right- no toggle, it just cancel all write enables. My mistake.
  23. The crossed button toggles between "automation write" enabled/disabled on all tracks. It means that if you want to write automation in real time as you play your song, the envelopes are written as you move the controls, as lomg as your W in the track bus is enabled. See pics and video. Video 1.mp4
  24. Can you post a pic of the line? The diagonal direction seems to be a drawing in the automation line, but, who knows...
×
×
  • Create New...