Keni

Thanks for chiming in. Lasso zooming 2 tracks with Lanes open yields one very large parent and it's two tiny lanes not even showing track 2 at all. ...and I editing clips between multiple tracks with lanes visible is much harder on the eye always confusing parent image with actual clips. A simple enable/disable button for that parent image process would help me a lot!

Yeah... Me again. I'm sure this gets old, but so is the issue and so am I. The issues being discussed: Zooming when trying to see Lanes on more than one track simultaneously! Right now requires constant fidgeting. Parent Track wav images! Please allow these to be disabled. They do little but cause visual confusion when performing tasks such as above. ...just my periodic prayer to the gods of DAWland. Please hear me! Thanks!

I never use ripple edit.

Ahhh! Well... That idea didn't work either, but I did finally stumble on the secret! This might get more refined as I use it more, but this is the scene... Select the note Select the tool split type Dbl-Click on the vertical line at note junction which has already changed to a different marker appearance Now using the note slip tool works independent of neigbor notes! At Last I can repeat this! I may have missed or done things not/necessary and I will clean it up with more use, but at least I'm finally on the path. I really needed this tool as the work arounds have been driving me batty! ?

Hmmm... Thanks! My first lightbulb just went on? I need to position the time marker as well as select the note! Of course! I just thought as well... We are talking about separating the note, not splitting. The split tool works fine. I have no problem there. I guess I didn't explain my dilemma well. In working note start/end times if you slip the end of one it also drags the beginning of the next. They can be disconnected, but the SEPARATE notes command seems to not heed note selection alone, so with this thought in mind I'm going to see if this affects my need in such... Thanks again...

So I guess either no one else has figured this out, or those who know wish to keep it a secret? This is unnerving! Thanks....

Hi Gang... I’ve been using Melodyne for a good 2 years or more now. My editing has been pretty good as I’ve been learning it’s use. One thing has been eluding me. Separating notes so that head/tail latch of consecutive notes can be disabled allowing editing say the tail if one note without affecting the beginning if the note that folliws. Most often I can’t get it to work and must seek other solutions. Every once in a while it works so I know I’m missing something. With time grid disabled, Melodyne Studio 4 I select the note (click on it and it turns red) R-click to select cut tool While context menu (tool selection pop up) is open and mouse over the cut tool, I move the pointer up to the Separate Note command and select it. Most of the time this seems to chop the note into two pieces on being a tiny portion of the note beginning. On rare occasions it separated the end of the note from the beginning of the note that follows which is what I was trying to achieve. So? What am I missing why is such a basic edit eluding me? I sure would appreciate a little guidance here if anyone can... Thanks

I don’t know your workflow, but maybe the use of freeze/archive/folders/hide in some combinations? Freeze frees up resources but leaves playable so some resources still used. Archive removes all but track is silent. Folders to group ideas and hide to get not-currently-being-used tracks out of sight?

Have you guys tried working with the Jet? I have not yet managed to understand the controls so to accomplish task. Is it me?

Yeah. V5 is great sounding but too resource heavy for much of my work. My workaround is to use v3 until the recording is done, then switch to v5 and freeze to get best sound.

Thanks, but highly unlikely. I have never used linked clips and as I just did so much work on the vocal tracks, I believe I’d have noticed?

I’m seeing it in this situation. I’ve never had this happen before so I’m thinking there is an underlying issue I should figure out. Vocal tracks are the tweeners. There are also hidden/archived tracks that are work tracks from comping the vocals (I save my melodyne tracks archived, then use copies which I render).

No. I am not dragging a Melodyne clip. It is an audio clip of guitar (di). Further exam shows that the 5 tracks between my audio source track and the MIDI track destination are somehow being included in the selection. PITA, but not a show stopper. Workaround? I moved the audio source track so it is adjacent to MIDI track and the conversion proceeded as expected after dragging. Then moved audio source back to where I want it. Thanks for the thought though...

Sorry to Sorry to hear it. The Roland gear usually works pretty well if you use their internal patches. Going external and it's worse. I was told that the system they use bypasses midi conversion (prior) hence less delay. But it’s not for everyone as you no longer play guitar when you use it so learning what it can do is essentially many new instruments including what it can do while playing real guitar parts. Sometimes it can do so but most often it's a controller, not a guitar?

Funny... I tend to do the same more often. I have some issues there which may be I need to learn more Melodyne. Dealng with bends, slides, and vibrato is still painful...

BTW, I also found realizing slow attack sounds don't typically work well with fast passages etc... Again requiring playing to the limits of the chosen sound/setup... ?

Ha! Love the idea, but these days I’ve learned I get on with others much easier when I act "polite"? ????

I’ve been playing with MIDI guitar fir many decades now. One of the central issues is the extreme width of guitar techniques (which can change every note at times) requires far more detail than current AI manages. Especially if you’re doing improv so pop on guitar. So it really needs a lot of attention and planning as to how well it works. In it’s most detailed mode, using 6 adjacent MIDI channels dedicated one/string is needed to bend one string and not affect others (for example). Might not be what is desired when playing some chords? Etc. I see it as needing a lot of extra work for most uses and these days it seems most people expect magic and we're not there... yet? In any case, I’m still using a Blue Chip Axon ax-100 (I have 2, one an SB) with Axon GK2 equivalent running any combination of hardware/VSTi synths I choose. I don’t use it often currently but that changes. It’s often too time consuming to setup especially when running MIDI mono mode. Big setup in a "synth" like Kontakt... I have (well had, until one was stolen last year) two hardware synths setup with whole banks of setups/sounds for MIDI guitar work. My precious Oberheim Xpander was stolen but I still have a basic live rig for my Roland U220 as guitar synth. Things work k pretty well when thought about and planned for. For quickie stuff I used to use the TT1 as it’s easy/fast to tweak for guitar though not my desired sounds too often. As to the triggering? It’s still at the mercy of physics. Measuring a waveform to determine it’s pitch demands an amount of time unlike an instant on from a switch (keyboard), so I find it needs me to learn using it within it's limits as any other instrument's limits. I usually avoid fast low note passages or scrubbed guitar chords and the likes (for example). Sorry for the long story. I guess I needed it having abandoned a guitar synth solo 2 songs back...

I'm not sure what's going on here. I've tried many alternative ways of approaching what used to work well... Dragging an audio clip to a midi track for conversion. Instead of converting the selected clip(s), it seems to be converting every audio clip in the song. I'm not sure of that extent because I keep giving up and re-booting before it finsihes, but even selecting a single 2 bar clip send Cake into non-stop conversions. Using the latest Cake release and Melodyne 4.x Any thoughts? Now seeing that it's converting the clips of all the tracks the originating audio was dragged across to reach the MIDI track...

Wow! Time flies. I hope it is as successful for Meng as it has been for us. Some of our lives depend on it! Congrats, Kudos, and best of luck in the future to Meng, Noel, and all the Bakers keeping this classic software in prime condition!

I think it’s 2.2.5 now. I see nothing obvious which I wouldn’t expect given the small increment of version number, but so far I notice no difference. I guess that’s good short of a full version 3 overhall.

I wonder what was fixed/changed. Is there a list of such?

Ahhh. Excellent! That’s what I suspected. Thanks Larry. I will run it now.

What is OLI? Thanks...

Thanks for the confirmation Noel. I was fairly certain of this as PC modules are special skinned VST devices to begin with.