| Author |
Message |
|
Dizzi45Z
|
Post subject: Why Melodyne Editor Kills your workflow. Posted: Wed Feb 10, 2010 10:43 am |
|
Joined: Tue Apr 04, 2006 9:24 am Posts: 66
|
I want to start of by giving a brief background here. I have owned Melodyne since 2.0 days and I have absolutely loved the improvements in every version. I have pitch corrected 1000's of vocals at this point with the Melodyne Plug-in and I can absolutely fly with the Plug-in. I love Celemony. They have always responded to my emails and web posts and have done so for years. This is why I am so concerned with many of the changes with Melodyne Editor. It is a huge step back on workflow. HUGE! Vocals that use to take me 10 minutes to pitch correct now take me 40 or more minutes with many frustrating moments. Beyond crashes, and some broken features (which I am sure will be ironed out eventually), I want to share some points that I really hope are seriously considered to bring the speed of workflow back into Melodyne. 1. Correct Pitch. This is the big one. I next to NEVER pitch correct everything at once. My workflow is to edit as I go. The fact that the sliders are programmed differently so that every time you want to correct pitch drift on a note you have to slide the two sliders from left to right just kills me. This alone adds at least an additional 100 clicks of the mouse per track I correct. I completely understand why it is currently the way it is, but it needs to be changed back as it is a workflow killer. 2. Correct Detection. Why can't all the imported data have the same correct detection window? For example, if you import a section and then import another section later, when you go to correct detection, only one of those imports will show. This kills workflow because if you are working on the second imported section and go to fix a detection error, you must remember to click on one of the notes first. Otherwise it only displays your first imported section. I see very very few instances where you would ever want to have a track that you would be correcting monophonic and then polyphonic material. I wish that you only had to choose the detection once (such as with the plug-in) and that all detection appeared at the same time. 3. Note transitions are not as smooth. I rarely ever had the problem in Melodyne Plug-in with transitions between notes. It was often very smooth if you moved a note up a half or whole step. Now when I do this with Melodyne Editor, I often get nasty jumps between notes. This happens even when I adjust note transition to the smoothest setting. 4. No more note separation. http://img.skitch.com/20100210-pc47mptt ... qap81m.jpg This was a great time saver in lots of material where you needed overall more or less note separation. Now it doesn't exist. 5. Having to right click on the toolbar to "Set Replace Ranges to Notes." This is an extra step that is just annoying. I don't see where deleting a note and keeping it from playing would be the more common thing with monophonic material. I assume that this was put in so that we could delete notes and not have the old material play back. But I think the better option would be to allow us to mute notes instead. This could give us the same result without us having to keep clicking up in the toolbar every time we delete a section in Melodyne that we want to restore to the original playback. Collectively, these issues add hundreds of more clicks per track. Please focus back on workflow for us? I actually downloaded and installed Antares Autotune Evo today to see if that could hold me over until many of these issues are fixed. After an hour or two really digging in to Autotune, I came back to the realization of how much better Melodyne is. I reverted back to Melodyne Plug-in and I have to say that the Plug-in is just awesome. I just want to see Melodyne Editor's workflow just as good if not faster than what the Plug-in use to be. Thanks for listening.
_________________ Dave,
|
|
| Top |
|
 |
|
Claudio
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Wed Feb 10, 2010 1:21 pm |
|
Joined: Mon Jul 11, 2005 11:19 pm Posts: 6089
|
|
Hello Dave,
thanks a lot for your input. I have moved this thread to the features wish list. Also, I will pass it on to the team.
_________________ Claudio Dell'Aere
- - - - - - - - - - - - - -
Forum administrator
Celemony Software
|
|
| Top |
|
 |
|
Christo
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Wed Feb 10, 2010 10:46 pm |
|
Joined: Tue May 29, 2007 7:14 am Posts: 192 Location: Sydney, Australia
Melodyne studio
3.2.2.2
Melodyne editor
2.1.0
WinXPpro SP3 Gigabyte GA-EP45-UD3R Intel Q9550 2.83GHz 4GBRAM Graphics:MatroxParheliaAPVe Soundcards: SSL/Soundscape MX4, Mixpander9 x2 DAW: SSL/Soundscape Editor
|
|
Dave, thanks for a clearly set out summation of the problems.
I fully concur with all points 1-4 and your summary (as MEplugin does not work in my DAWs yet, I have not experienced the frustration you mention in Point 5, but I sure understand the annoyance...).
I use MEstandalone extensively with Polyphonic material, where it is immensely powerful, but have noticed the problems you mention in Points 1-4, and still use the old MelodynePlugin in the DAWs with monophonic material where I prefer the sound and ease of operation.
I mentioned in another Topic that I think it was a major blunder that Celemony chose to replace the old MelodynePlugin with MEplugin at installation; the 2 plugins should have been separate entities, and I think most users would have been happy with that - thus we could still use old MelodynePlugin in legacy projects and in new situations where it's simplicity is all that is required.... or use MEplugin.... i.e. have a choice of what size hammer we use to solve a problem.
_________________ Regards
Christo
|
|
| Top |
|
 |
|
Dizzi45Z
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Thu Feb 11, 2010 8:49 am |
|
Joined: Tue Apr 04, 2006 9:24 am Posts: 66
|
Christo wrote: I mentioned in another Topic that I think it was a major blunder that Celemony chose to replace the old MelodynePlugin with MEplugin at installation; the 2 plugins should have been separate entities, and I think most users would have been happy with that - thus we could still use old MelodynePlugin in legacy projects and in new situations where it's simplicity is all that is required.... or use MEplugin.... i.e. have a choice of what size hammer we use to solve a problem. If I had written one more paragraph, it would say exactly what you had said above. When ME was in beta, it was nice having the two plug-ins. I have seen some tracks converted to ME not sound exactly the same as it did. This was frustrating when I had clients asking for a quick tweak with an older mix. I would have to spend the time going through and making sure it transferred correctly. However, I can also see where Celemony might not want to focus any more energy on an "older" plug-in and focus all their resources on the new one. Allowing conversion to the new plug-in would allow future compatibility for old projects if the old Melodyne Plug-in becomes incompatible on future systems.
_________________ Dave,
|
|
| Top |
|
 |
|
creater
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Thu Feb 18, 2010 9:25 pm |
|
Joined: Sun May 31, 2009 2:19 am Posts: 277
Melodyne studio
3.2.2.2
Melodyne editor
2.1.0
Mac OS X 10.8.2 Logic Pro 9.1.8 Ableton Live 8
|
|
..use the old MelodynePlugin in the DAWs "with monophonic material where I prefer the sound" and ease of operation.
Yes, and whoever thinks about exchanging Studio versions algorithm for monophonic material for a more "universal" one, I'll nuke his hometown for sure. It is so good as it is. Artifact-free monophonic pitch alteration is the bread and butter of things. Other effects can be added into a redesigned mixer as Melodyne Addition's and sold separately as try and buy plug-ins regarding more experimental effects.
I'll tripple the remark about extra clicking in ME, my 500 clicks suddenly becomes a 1000 clicks, doing the same job however more slowly. I also forget to deselect blobs all the time and the playhead will disappear out of sight. I would like to alter that feature, (use last selected object in menu for that function (in a normal use). But when I'm zoomed in really big, it needs to be as it is now because then the playhead passes so quickly cross the window so the work-blob has to remain in focus. A toggle on/off for that in the toolbar and another way to deselect.
Then suddenly the whole big working area would be free to use for other actions. I do think a one click in the work-area (close to the blob) should put the play-line there and if I move the play-line back-forth, it will scrub. When I so find my spot and let go of it, it should remain where I leave it. Take the bar-ruler away as a tool and use it for metering/loop only. In ME I now go up and get hold of that type of scrubbing and drag the cursor down close to the blob where it should be so I can see what I'm doing. Put the actions (from the bar-ruler) into the working area, inside and around the blobs. Start, stopp, scrub, the lot, so I can focus on that area only.
Put some colour to the side-bars in the ME plug-in, transparent sliders or buttons are hard to see. The eyes are much more sensitive to colours than to grey so light blue is fine. Finally when I am heavily zoomed in, the horizontal sidebar gets incredible small because it's proportional to the length of the file. It is also split in 3 parts (for zooming and moving) and transparent.. so the middle part for moving, is impossible to use. Especially in the plug-in without a transport function it's hard. I use the hand tool to move around, but the sidebars needs a redesign.
|
|
| Top |
|
 |
|
ilterocktive
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Thu Feb 25, 2010 5:39 pm |
|
Joined: Wed Oct 14, 2009 10:44 am Posts: 15
Melodyne editor
1.0.11VST3
WinXP SP3, Konnekt Live, Nuendo 4.3
|
|
| Top |
|
 |
|
CelemonyCustomer
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Thu Mar 04, 2010 5:04 pm |
|
Joined: Thu Mar 04, 2010 12:23 am Posts: 2
Melodyne editor
|
It would also save a huge amount of time if I were able to define the algorithm to use BEFORE the transfer, instead of after the huge polyphonic analysis on a melodic track.... My work has been slowed so much I really am considering "downgrading" (BTW, anyone else hit by outrageous file save/backup times now too? [posted in the ISSUES])
|
|
| Top |
|
 |
|
Freddie H
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Fri Mar 05, 2010 12:58 pm |
|
Joined: Sat Sep 30, 2006 6:07 pm Posts: 140
Melodyne editor
Latest
Melodyne studio
Latest
Windows 7 Ultimate x64 & SONAR X2 x64bit.
|
The "analyst" aren't always perform in the BEST! Also the GUI of Melodyne Editor in PLUGIN-MODE hangs and crash randomly. You never know when it will happen? You need to re-open the Melodyne-Editor to get the graphic OPEN! After a while it crash randomly so you can't open it anymore at all! Then you need to re-load the SONG/Project file when it totaly hangs! Its BAD and its killing the workflow and all the inspiration.  Happens on PC or MAC and I have no idea WHY you at CELEMONY can't re-produce this yourself when you do BETA TEST?? I don't know but I can probably find like 20-30 professional Producers like me, that can concur that WE all SAYING! Please address this bad GUI issues thank you. =)
|
|
| Top |
|
 |
|
Dizzi45Z
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Mon Apr 12, 2010 10:30 pm |
|
Joined: Tue Apr 04, 2006 9:24 am Posts: 66
|
Wow! I'm sooo disappointed. Not a single one of these issues was addressed on the new update.  I would at least like an explanation from Celemony as to why they are deciding that 400 clicks versus 200 clicks is a good idea. Or how I should be changing my workflow. I guess for everyone who wants to pitch correct their whole project all at once to create CRAP can continue to enjoy the new workflow of Melodyne. ...... Another 4-5 months of Melodyne Plug-in for me (or whatever it takes for the next update - if there is an improved workflow). I could tolerate a 10 minute per track increase in workflow. But this 2-3 times the time to correct tracks is absolutely ridiculous. Obviously the new designers don't run a commercial recording business where you don't have all day to correct vocals on a clients dime.
_________________ Dave,
|
|
| Top |
|
 |
|
Dizzi45Z
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Wed Apr 14, 2010 9:18 pm |
|
Joined: Tue Apr 04, 2006 9:24 am Posts: 66
|
|
Quick apology for being so upset on my last post. The Celemony company is awesome. I just hate seeing such a great product make a poor turn. Congrats on creating a miracle product though.
_________________ Dave,
|
|
| Top |
|
 |
|
mrtomcat
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Tue May 25, 2010 7:20 am |
|
Joined: Fri Jan 26, 2007 6:34 am Posts: 31 Location: Studio City,CA
Melodyne editor
|
|
I could not agree more with this post...
I actually went back to the Melodyne Plugin as of yesterday and all is well again...however having spent money on the update and liking some of the new features and of of course needing to know that there will be support I am truly hoping that Celemony gets this message and will address this in the next update...hopfully not too far in the near future.
|
|
| Top |
|
 |
|
Claudio
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Tue May 25, 2010 1:06 pm |
|
Joined: Mon Jul 11, 2005 11:19 pm Posts: 6089
|
mrtomcat, I have already suggested some solutions for your issues in this thread. And yes, we do read these posts and are grateful for any feedback and suggestions.
_________________ Claudio Dell'Aere
- - - - - - - - - - - - - -
Forum administrator
Celemony Software
|
|
| Top |
|
 |
|
mrtomcat
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Tue May 25, 2010 8:09 pm |
|
Joined: Fri Jan 26, 2007 6:34 am Posts: 31 Location: Studio City,CA
Melodyne editor
|
|
Claudio,
these are the exact same issues I mentioned in my other thread. With several people listing these how can you even still question this?
I was using 1.1.5 and the old plugin by far sounds better, more consistent, workflow is 100 times faster and it crashes less. I took the same vocal track that sounded like crap after hours using ME and got it to sound great and natural in minutes on the old plugin...Workflow is better, note seperation is better and the overall sound is better in the old plug in... I am NOT the only one having these issues.
I also want to stress that I am not holding a grudge against Celemony I was a HUGE fan until ME which I believe could have been amazing if you would have first focused on making the actual monophonic pitch correction solid vs introducing DNA.
You keep asking for sound file examples but we can't run the two products on the same machine...that alone would solve many headaches btw.
also I just noticed that the buttons on the lower right corners that allow to increase the blob sizes that you now removed are another big part of making the workflow easier since the Zoom makes you move away from your workflow as well...vs pushing a button and voila you can see your blobs...
|
|
| Top |
|
 |
|
Christo
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Wed May 26, 2010 12:29 am |
|
Joined: Tue May 29, 2007 7:14 am Posts: 192 Location: Sydney, Australia
Melodyne studio
3.2.2.2
Melodyne editor
2.1.0
WinXPpro SP3 Gigabyte GA-EP45-UD3R Intel Q9550 2.83GHz 4GBRAM Graphics:MatroxParheliaAPVe Soundcards: SSL/Soundscape MX4, Mixpander9 x2 DAW: SSL/Soundscape Editor
|
|
I echo mrtomcat's comments to a large extent:
But I cannot compare workflow between ME Plugin and Old Plugin because ME Plugin does not work in my DAW (but Old Plugin does work very nicely, despite the DAW being on your 'blacklist'), hence my comments are a comparison between ME Standalone and Old Plugin.
Workflow in ME is awkward and slow compared with old Plugin. When working with simple vocals, the Old Plugin wins everytime for ease of use.
> we can't run the two products on the same machine.
a huge blunder.
_________________ Regards
Christo
|
|
| Top |
|
 |
|
Dizzi45Z
|
Post subject: Re: Why Melodyne Editor Kills your workflow. Posted: Wed Nov 03, 2010 3:26 am |
|
Joined: Tue Apr 04, 2006 9:24 am Posts: 66
|
|
Claudio,
I just finished reviewing the latest update Melodyne Editor 1.2. Again. No improvements on workflow at all! Here you have a bunch of us talking about how horribly slow Melodyne Editor (in comparison to Melodyne Plug-in) is and there have been no workflow improvements through the last two updates. NONE.
Regarding my Hugest Biggest Pet Peeve of Editor is #1 that I posted as the original post. The ideal scenario to solve this would be to create a button that we could have predefined "correct pitch" parameters that every time we wanted to correct pitch drift/pitch center, we would simply highlight the note and then click the button which would conform to those settings. That would improve some of the workflow over even the Melodyne Plug-in which still requires the two clicks to open up Correct Pitch and press Okay.
Claudio, if you only hear one thing from me, please make this the one thing. The other slow workflow improvements can be painfully dealt with, but this one is the big deal breaker that will keep me on Melodyne Plug-in (old version) until it is no longer compatible in Pro Tools.
Is the Pitch Drift tool the same algorhythm as the pitch drift we choose with the slider in Correct Pitch? The biggest problem here is that you can go beyond 100% to the point where the pitch is actually reversed. I would love it to zero out at 100%, or to show the percentage next to the note when you are dragging so that we know where the limit is and don't try to go too far.
_________________ Dave,
|
|
| Top |
|
 |
Who is online |
Users browsing this forum: No registered users and 1 guest |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Style based on a design by phpBBegypt
|
|