I posted something about this prior, but not this specific question, which some might find intriguing.
This is regarding @Andrew_Scheps 's insanely useful plugin 'Melodyne Helpers', specifically the prep tool (what saves me the most time). However, I find myself using a little bit of a different approach to using Melodyne....
Let's just say I have a background vocal, and want to Melodyne it. I've already comped, and stripped the silence (kudos to Andrew, Mark, and Christian on that innovation too!). What I usually do, is only tune the selected region, not the whole file. Meaning, I DON'T use the 'commit' and delete trick, I actually sit there and wait for it to process. Boring, I know, but for me, the benefits outweigh the cost.
The reason I do this is, say I actually found that something doesn't sound natural, or I hear some BS in the take, and just want to use a completely different take. This is easy, as I can delete the blobs, of just THAT part up to the silence. (In Melodyne, maybe it's just me, but whenever I take a full audio file, sometimes there is an overlap or it cuts out some of the important information before/after the silence...)
So, as silly as it may seem, is there a simpler version that I could use that would ONLY prep it, up to the time it comes to commit/delete the track?
...OR! Is it possible to do all the wonderful things that Melodyne Prep is set to do, but do JUST selected regions? Maybe even a macro to JUST transfer in, the old school way, without having to press transfer, hide the window, etc.
Just some food for thought! I also put my ideas in the mid / end of this 7min video. I love this community already. What a damn genius workspace. Much love to all!
J
Andrew Scheps @Andrew_SchepsHey Jordan,
Glad you figured out the issue with Keyboard Maestro interfering with the script.
The plugin menu breaking is a known Pro Tools bug. It doesn't just happen with SoundFlow, but anything that uses accessibility to access Pro Tools. Hopefully they'll sort that out. A 'workaround' is instead of selecting 'search..' with the mouse, when you open the menu you can type 's return' and then you will be able to just start typing. It sucks but you get used to it.
I'm publishing a new version of the Melodyne Helper package. The first change is that the Melodyne Prep Template now has a choice for Edit Selection or Selected Tracks.
There is also a new script that will let you quickly add the selected audio on a track to an existing Melodyne instantiation.
Thanks for all the feedback,
Andrew
Jordan Pascual @Jordan_PascualHey Andrew,
Thanks so much for responding! Regarding search functionality... since that video, I actually have utilized Chris Shaw's Search/Add Insert function, and find it even better to be honest haha. Just a bit adapting to use 'control x' instead of clicking on the insert, but once you get used to it, it's fantastic!
Just checked out the update! Man oh man! Super appreciate it! I just tried it and can't even believe how cool this is! The edit selection and Add selected audio is a game changer for me
One quick bug I think I may have found though... I've posted a short video to explain... Essentially, Melodyne strangely only picks up on ONE audio clip/region OR it goes to a 'random' point and the blobs stop... meaning if I have a comp of 10 vocals from different takes on the top playlist, it will only take the first part. My guess is that it has to do with the comp selection being different pieces...
I think a workaround is to have Melodyne see it as one whole file by 'consolidating the file' (select region - shift+opt+3)... but I personally like seeing the rainbow of takes so I can differentiate haha.
Biggest workaround I have found now is that if you re-detect the algorithm (click on anything but selected, then reselect, in my case melodic...) then it will auto update. Does this have to do with Melodyne's bugs perhaps? Strangely, I didn't see this happen when it was committing the whole file, only this edit selection. Sometimes, the 'Add Selection to Existing' doesn't work either, up til re-detection.
Other than that, this sh*t is life changing!
Thanks again for all your help, the fact you're here and doing this for the community is so awesome. Soundflow all day baby!
Jordan
Necessary Noise
Andrew Scheps @Andrew_SchepsHey Jordan,
It's a Melodyne bug, and I can't even figure out what exactly triggers it. You've found the workaround though.
Thanks,
Andrew- Jordan Pascual @Jordan_Pascual
Hahaha good old Melodyne...
I don't know if this helps, but I've included a SHORT video this time, showing what I did as a workaround. IF there's any way to get kind of command that's in Keyboard Maestro into Soundflow, I'd love to hear it...
You're the best
Jordan
Necessary Noise- Andrew Scheps @Andrew_Scheps
SF doesn't have image recognition yet unfortunately.
- Jordan Pascual @Jordan_Pascual
Hey all good! How about going into the menus and such without image recognition.
i.e. having a script that selects the blobs, goes to menu 'Algorithm', goes to option 'Melodic', presses the blue 'redetect', and voila! Possible?
Jordan
Necessary Noise- Andrew Scheps @Andrew_Scheps
The problem with plugin windows at the moment is that unless the plugin manufacturer exposes the elements, as far as Pro Tools is concerned it's just a big blob, no individual elements. You could absolutely do it all with mouse clicks relative to things but it's not the most reliable way to do things. Hopefully that will change at some point.
- Jordan Pascual @Jordan_Pascual
cool cool! I'm good with the Keyboard Maestro extra step for now! If anyone else reads this in the future and wants to be lazy like me, DM me and I'll try to help! Thanks again Andrew! Kudos to the awesome script!
Jordan
Necessary Noise