Jump to content

Mark Morgon-Shaw

Members
  • Posts

    1,284
  • Joined

  • Last visited

Everything posted by Mark Morgon-Shaw

  1. I think you'll find they would have slowed the tape down thus lowering the pitch of the song, recorded it and then returned the tape machine back up to normal speed. But a tape machine that has varispeed and is designed to operate that way, it's not going to make it break down. Yeah maybe the band should have lowered the key a couple of semitones but this was fairly common in the days of analogue tape , you still have to have good intonation though. What did he do when performing it live ? Most pro singers do have vocal coaches and a good one could probably add those extra few notes to a singers range over time. The insane logic would be chopping the tape into pieces and then splicing it all back together hap hazardly then wondering why it got stuck in the machine and won't play properly.
  2. It's a poor workflow. You are doing a post production during the actual recording. I'm not sure what you mean when you say " Melodyne corrupted line " ? I have no problem insulting anyone if it makes them get it right. It's a crutch if you're using it on every line just after you've recorded it. No legit singer would want to work like that, it's an art and a craft to coax the best performance from a vocalist. Maybe call up a local pro studio and ask them if you can sit in and observe a session so you can see what a proper workflow looks like when working with singers.
  3. No I was asking first just in case its my Buddy's fault somehow
  4. This is the way. The OP's issues spring from using Melodyne as a crutch.
  5. I don't think it is as you'll be hamstrung to a lowest common demoinator featureset in a world where DAW manufacturers are trying to one up each other for more users. On a commercial level what would be the point?
  6. I was trying to help out a guitarist freind of mine and it seems he has found a bug. When using Guitar Rig 7 , if you convert the track to a Melodyne FX Region and subsequently render it back to the track then Guitar Rig 7 no longer plays and no audio can be heard unless GR7 is deleted or Cakewalk is restarted. I've got him to test this with GR5 and TH3 and they work as expected , and we did figure out a workaround that if he puts GR7 into bypass before enabling the Melodyne FX region and also before rendering the region FX then the issue does not occur. I've not got the plugin myself as I'm not a guitarist and my buddy isnt' a forum user but thought I would post it up to see if anyone else can replicate.
  7. Mine is not very pretty but I find it super handy. I partly use it to address some shortcomings in CbB SuperZoom is a macro to close the browser and inspector and make CbB full screen Hide - Unhide is the shortcut to hide all tracks except the current selection Fit To Selection - Also shortut Tranpose Up & Down - This is a macro you can use on track view to quickly switch octaves so it uses : Process - Transpose and - + or - 12 semitones and saves multiple mouse clicks and typing the value in. I would say I use this one the most of all of them especially when arranging midi parts to find the right voicing but it works on audio too. Scale Vel - This is a shortcut to Process - Scale Velocity and opens the dialogue box Tempo Track - Shortcut to open / close tempo track CAL - This is a folder which reveals a bunch of my favourite CAL routines Normalize - Shortcut of Process - Apply Effect -Normalize, save going several menus deep Melodyne - Applies the Melodyne Region FX to selected clip Humanize - Shortcut to commonly used CAL Reset Midi & Audio - Shorcut to panic button Bounce to Clip - Brings up the bounce dialogue for selected clip Audient - Opens soundcard app for adjusting latency So that's mine - When I first had it I set it up as a glorified transport controller but I quickly found I never used it and decided to put all those tucked away commands that I used quite often or some macros of functions that I used a lot but took multiple clicks to achieve otherwise. And I've still got one spare button ! Might rig that to the coffee machine.
  8. I am ready for New Sonar...................your move Bandlab
  9. Ah. The dabblers and dilettantes . Gotcha. They are the prevailing demographic after all I guess.
  10. The answer is you can't and those are the tools you have available
  11. Doesn't seem like a bug to me, from my POV this is expected behaviour. In essence what the OP is requesting is for Cakewalk to instruct Melodyne to "mute" the previous take's blobs which I don't think it can. I could be wrong but it seems like all Cake does is pass audio over for Melodyne to process which it then sends back to the track. Cakewalk doesn't really have any other control over Melodyne such as mute states as far as I can tell. The previous audio is actually still in there inside Melodyne because the "take lane" is really just a sub-part of the same track. I don't think Melodyne is take lane aware, it just sees all lanes as one track. So as far as it's concerned you are recording over the top of yourself and it's displaying that as expected. Therefore expected behaviour rather than a bug, just not the behaviour the OP wants. This is partly a consequence of using Melodyne as a tracking tool in a DAW which now has multiple take lanes in unforseen ways. Cakewalk never had take lanes for many years after Melodyne came out and it doesn't seem as though this has been considered for a Melodyne based workflow. I'm not even sure it's within the Bakers gift to make it work the way the OP thinks it should. Whilst we wait to find out we have a few choices. 1. Do what every other vocal producer I know does and comp your vocal first and apply Melodyne to a consolidated vocal track. It's much easier that way - I don't even get why you would want to use Melodyne on the fly like that anyway ? It's a strange workflow as you're basically working the opposite way round to everyone else by pitch correcting things before deciding if you're keeping them or not. 2. Use separate tracks instead of take lanes ( like we used to back in the day ) for overdubs 3. Mute the blobs manually in the previous take from within Melodyne before recording the new take then they turn into a ghost note outline. This might alleviate some of the visual issues of overlaying notes. I've not tried it though as I don't work that way. 4. Delete the old blobs in Melodyne before transferring the new take. You can use the compare switch to go back and forth between track audio and Melodyne audio to check which one you like best. I may be wrong and maybe the Bakers can make Melodyne put the original take into mute mode automatically ( although you would still have the outline shown above I expect) but if not I suspect this may not be a quick fix. Lastly forget the tech and consider a good vocal coach, I'm no pro level singer either but I went from being pitchy AF to not needing to use Melodyne except for the odd word here and there by having a good teacher and working on my voice. Getting it right at source is far better than trying to fix it afterwards which should always be a last resort to be used sparingly.
  12. That's your issue right there. My wife needs her car fixing every few years because she rides the clutch and it wears it out to the point it needs replacing. I on the other hand have never needed a new clutch in any of my cars despite doing considerably more mileage. I understand how clutches work and what will cause them undue wear so I drive accordingly in order not to break it. Is the car manufacturer at fault or is it my wife's fault ?
  13. Not really Wrong tool for the job - If you use something like Izotope RX 10 it can transcribe your audio file so you can perform text searches.
  14. No the solution is to use the right tool for what you are trying to do. Probably one of the Auto-Tune-alike plugins. Take it into Melodyne when you're done recording and comping. Not during. Why not trial some different ARA host and see what happens ? Make a video about it. ( genuinely interested to see what happens )
  15. It's not comparable though - Melodyne has to take the audio file from the ARA host then run an analysis on it's pitch & tempo etc, and therefore it isn't designed for real time use. FX plugins affect the audio in realtime as they pass through the plugin - A realtime process..no handing off of the audio outside the DAW. If you want to constantly ping-pong your audio between CbB and Melodyne and drop in and out as though it were a native DAW audio track then I expect you'll get problems. Much better to use a plugin designed to do what you need ( i.e. realtime pitch correction ) than expect one to cope that isn't designed that way then complain when it breaks. Anything will break if you use it in unintended ways. Maybe so but probably not a high priority for an edge use case.
  16. I collab with lots of people on music for TV ( vocalists , more specialised instrumentalists etc. ) and I'm yet to meet anyone working in that part of the industry that exchanges DAW files with each other. We all just send audio stems, even the folks that use the same DAW because the likelihood of everyone having the same plugins and VSTi's is slim to none. A guitarist buddy of mine once sent me his project to mix and we made sure he didn't use any plugins I hadn't got so I just cake his Cakewalk Project....Ughhhh..garish colours everywhere, things laid out in the wrong order, no busses etc. It's just far easier to import audio into your own preferred template and on the rare occassion we ever decide we need to re-do a midi part we just ask for it. So I vote "No" and to spend the dev time on more fundamental issues like the big missing features people have been asking for at least the last 5yrs ( ie. Sampler - Chord track - Better Hardware integration etc ) rather than devising a complex solution to a problem that is better solved in other ways.
  17. It's not a fix , it seems you have a fundamental misunderstanding of the workflow Meldoyne was designed around. Lets go back in time to 2001 when Melodyne first came out. It was a standalone application that you had to upload or record your audio into so it could do it's thing. https://www.soundonsound.com/reviews/celemony-melodyne A couple of years later we got Melodyne Bridge & ReWire so we could transmit our DAW audio directly into Melodyne instead of importing / exporting between two separate Apps. In 2011 we got ARA ( audio random access ) which meant we no longer had to "transfer" our audio tracks into Melodyne manually- Melodyne could just "access " them with no other transfer necessary which gives a feel of it being more like part of the DAW than the seperate App it actually is. Over all those years the reccommended workflow has always been something like : 1. Record parts 2. Comp parts into complete performance or section 3. Transfer comped audio section into Melodyne 4. Perform non -destructive edits with Melodyne 5. Apply edits destructively and transfer corrected audio back into DAW Whilst the methodology has changed from separate programs, to bridge plugins, and then to ARA this workflow has remained unchanged. From what I have read you are trying to shoehorn an immediate/online workflow into what is essentially an offlne process by a separate App. Now I'm not saying it wouldn't be nice if it just "worked" as you think it should and we had rock solid glitch free instant swapping of audio freely between Meldodyne and Cakewalk regardless of where we punch in / out etc. But the truth is it's not really designed to do that and if you've been using it since 2001 like I have and been through all those various stages mentioned above plus all the changes to Cakewalk over those 20+ years you'd probably understand why it doesn't work that way and avoid the inevitable problems it causes. Maybe they can invent ARA 3 and make this a reality but for now you're either going to have to change your workflow and make a comp of your vocals and work with Melodyne once you've finished tracking ( i.e. how it works in professional studios ). Or alternatively use a pitch correction plugin like Autotune that operates in real time so you can make as many changes as you want on the fly becaause the audio is not being transferred to a different App to be processed. Either way the goal would be to deliver a more fully finished track to Melodyne for further enhancement, and not as part of the recording process.
  18. I never said they did. I just said learn one DAW really well because they can all do everything.
  19. I'm not talking about loading the samples for the project. Even if empty , when it loads for the first time it does a scan / update for any new libraries which takes time.
  20. Have you by any chance got Kontakt 7 in any of the slow loading projects as it does a re-scan of everything the first time you load it which slows down project load time considerably here. Once it's done it the first time it subsequently loads much faster.
  21. Or paste them into Chat GPT and ask it to summarize
  22. I agree but I think it's nuts that these types of settings are at project level, they should be global settings and not affected by updates overwriting templates etc
  23. We have trodden very similar paths.... Fostex X28H 4 track synced to Music - X 8 track Black Face ADAT synced to Cakewalk Cakewalk Pro Audio 9 - I still synced it to the ADAT for the main audio tracks and a few extra tracks recorded into the DAW A bedroom full of hardware synths, keyboards , reverbs , delays, compressors and other outboard - I even had a patchbay 😀 Then at some point I just sold it all and did everything in the box - so much easier and productive. Now I make 100 tracks a year.
×
×
  • Create New...