Melodyne 4- Amazing New Tool for Mix Engineers

[Rich WestphalParticipant]

Well, here's another little odd thing, lol,,
I was talking with Celemony about them dropping their forum from their site.
So I suggested they use a Facebook group for a forum user base,,.
Long story short, they asked if I would create one...
I agreed so it is new, not been posted anywhere yet, but here it is,,,

https://www.facebook.com/groups/1682563571957436/?ref=bookmarks

[Lee HawkinsParticipant]

I updated to Studio from Editor. Huge improvement from V3 Editor. I need to get deep with the new features but my first impressions are all good.

[thedoveParticipant]

Witch craft !!

(I have essentials)

C

[Johnny SommererParticipant]

that's wicked!!

[Alex WilsonModerator]

So I am just trying the new Melodyne 4 to capture the MIDI for Bullet (have been meaning to try this method since I saw Warrens video on Youtube: https://www.youtube.com/watch?v=O8Hsm0Gx140). Have to say, I kind of like the results so far, although I am not sure if I would convert to this method yet (as I have been using Trigger to do this longer, so it is my comfort zone).

One big question I have (and I am hopeful that some one here can help me) is how do you make the new version stop trying to figure the timing out for the track? When I am doing it for Bullet, it is giving different times for the Kick and the Snare, and neither of those match back to the originals.

Since I couldn't figure that out, I just used Melodyne as a plug in within Pro Tools so it honored the timing of the host. The only down side to this is you have to play the entire track to Transfer to Melodyne (although, I have to do that with Trigger too).

The one thing that I like a lot better than Trigger, is it actually makes the notes longer (like a full 8th note or so) vs. Triggers tiny little Transient MIDI note (will try to attach a screen capture of what I am talking about). On the other hand, I actually think Trigger is a bit more sensitive to the velocity of the drum hits (as well as those little ghost notes and such if you set it to capture those).

Overall, I really enjoyed trying this out, think I will make this my main method for a little while just to see if I end up liking it better, or if it offers some benefits that I haven't noticed yet. As of now, it is much slower for me this way, but I don't blame the process, as the issue here is just my learning curve...

~Alex

*Image notes: MDynKick, MDynSN_Top are Melodyne and TrigKick, TrigSN are Slate Trigger. The waves are the track that I used (Kick on top, snare on bottom). Also, Both of the Midi tracks are mapped out to the instrument where I have the virtual instrument (I mostly use SSD4, but will also use some NI stuff, Toontracks or others from time to time)...

[Loren KnightParticipant]

I have Studio One 3 and am just starting to learn this new DAW. My previous experience with pitch correction is with IL Newtone and it's not bad at all. But I was excited to know that I'd have access to Melodyne in S1 v3.

THEN I ATTENDED IMSTA FESTA LA yesterday. I won the four o-clock raffle. The lady started listing software I'd never heard of before and then she said "...Molodyne Editor, or..." I didn't let her finish. "Melodyne, yeah. I take that." I didn't even think for a second.

So yeah, I won a full license to Melodyne Editor 4. Now I'm just deciding if I should just do the standard license or if I should now finally give in and go with an iLok license. With an iLok I can also go ahead and check out Slate's free Virtual Rack software. I don't know. The thought of an iLok makes me grit my teeth.

[Author]

Posts