Keni

All should be all. People can always use custom if there’s too much... My slant on this. I dislike the constant window hopping to find commands. I prefer to have everything available all the time.

Not in my experience or memory.. the most current was to insert/append the name Melodyne to the front of the current clip name. Not sure if it behaves differently, but not bounced. I use the render command in the Region fx Melodyne menu tree. Weird... I’ve always wanted to disable the renaming addition in this scenario, but losing the clip's original name is inconvenient for sure.

OK... I'm sure to be told this has nothing to do with this update, but I do this task constantly and yesterday it was "normal" not after the update. After a render of a Melodyne clip, the clip's name becomes empty instead of the original clip's name (with Melodyne affixed to the front.) Now mind you, I might actually prefer this as I'm constantly manually removing Melodyne form the clip's name afterwards, this is near the same but I have to remember the original name as it becomes empty after the render... I'm only running Melodyne 4 Studio (5 will not load on this OS which I'm trapped with)

Oops

Nothing yet...

You bet! But as I didn’t win, I’m hopeful for another chance! 😉 ...and uf that doesn’t win? I’m currently working on my next album which might make the following Grammy’s 🙏👽🎸🎶

Hi Gang... I just wanted to take a moment to thank everyone for their' support. As we all expected, I did not make the finals. It was fun dreaming though. So in my heart I wish to say that "anything's possible". Who knows. One of these years it might be You walking up to receive an award. I sure hope so! For me? Thrilling ride and... There's always next year. My NEW album (Hear Me Calling) is being released 11/23/22 and is in time to make the 2023 Grammy's! It ain’t over until... My humble gratitude 🙏

Absolutely! Nice way of saying it. I’ve been working at this issue for a while. Even the ability to lasso a group of controller values to slide left/right or compact/expand. A transform tool if must be but I was picturing it as simple as a dedicated command to allocate the lassoed data as selected and treat as group as would any selected notes currently?

I apologize if it seemed I was wasting ea time. It was not my intention. These are issues I did not have prior to this ea. (Controller editing? Special case as I found it hard to believe we would be given such a view in an edit window without being able to edit it). I understand that nothing was changed in this ea regarding these issues. But then what changed here? Thanks

Thanks Mark Ok. But something is different somehow. Though I admit to having continuous issues with controller editing since forever, it’s now doing some things in an unusual manner. Point in case. two successive notes. a mod wheel gets elevated to max for last note and returned to zero at note's end. with select envelopes with notes enabled, I select the last note which gets highlighted as well as the raise controlled markers, but not the return and moving the note a distance much later, only copies the selected portion. I then made sure to manually lasso the entire area containing both the note and controller values so all was highlighted but i end up with the same result. I haven’t had this situation happen before this. What was specific to this ea was my questions regarding controller editability in the main PRV view.

Behaving very strange trying to move notes with controllers. Now I see it need the controllers to be within the select range of the note and if events happen between notes, they are not moved (not tied to a note? A bit finiscky, but not working here anyway. I moved the note and the return value was moved with it but not the beginning set as they began slightly before the note. As the controller is happening during the note, shouldn't it be selected even if it began between notes? ...and then there's always the difficulties of moving controllers. If I have a controller range, why can't I simply slide it (or portion of) left right??? Very frustrating.

OK.. That would be great. First off, I don't use the inline editor. I tried that as another user suggested it might be working there. My request is simple and now has a bug attached as well (see edit to previous message). When I'm seeing the regular PRV view and see the controllers "behind" the notes (instead of in the controller view below in it's pane. I can not edit the controllers? I must switch to the controller view to do this. That's my "request". Editing them in the main PRV view. The bug is related to moving events while select controllers is enabled. I move the notes but the controller is not moving with them. In this case it's a mod wheel.

OK... Nice to have the finer resolution for the controllers... and being able to see them behind the notes? Currently useless for me. I can't see that view while editing them. Is there a plan to add this soon? On suggestion from the forum I tried the inline editor but no difference there. Am I missing something? Is there a way to edit the controller while seeing the "normal" notes view with controllers behind? Ouch! Just found another... In PRV. Select controllers with notes is enabled. I lasso a group of notes that has controller events. Moving the notes is leaving the controllers where the were...

I plan on checking out controller editing in inline editor, but if indeed we can’t edit such in PRV while displayed behind notes, it’s somewhat pointless. Opening the controller view removes it from the notes view leaving us the same as if we didn’t have this new view. Is this expected? Is it planned for an update? I like what I’m seeing as it appears a finer resolution but that may only be perceived. Most of controller editing is still a royal pain for me much of the time. I am (was?) hoping editing behind notes would somehow improve this?

Interesting. I’ll have to check it out tomorrow. I haven’t used that view in a long time as it always felt too small/confined for most of my needs. Handy for aligning midi notes/events to audio though... Thanks for the idea.

Is this new to the early release? Wait. Some of it. The orphaned automation has been around longer.

Love that I can see controllers behind notes, but can I edit them there too? So far I haven't stumbled on how to enable such (if available). My attempts to edit continue to deal with notes only unless I open the controller in a controller view below the note-screen

Yeah... I run into this a lot. Need/want to revert or change zoom is always a manual zoom in the PRV. I think it would be very handy to have the various zoom methods available in this view as well as the manual method.

Strange... I seem to be at 1.14 and not getting any updates shown available? Logging into my account online only shows a v2 that I can (will) install Ha! Downloading and installing gave me v 3.01! So only the info page is in need of updating?

I just filed a report at KV331 as well. I pointed to wrong forum though. Just realized. I will see about correcting that now Done!

You may be right. I already filed the Cakewalk report. I’m too burnt right now but I will attempt contacting KV331 tomorrow. Thanks again.

Wow! Amazing work. So we see there’s some common issues going around. Now for me to try remembering how to post a proper trouble report. I take it the Bakers are still doing things that way? Thanks 🙏 OK. I submitted a tech request. I guess that’s the path now? I also referred to this thread for them.

Could be. ...but could also be that two different routines are used in Cake. One saved with current settings (typically I change settings on synth and Cake remembers the changes without the need for me to save a preset. Doesn’t appear very necessary fir such a simple task. The other saving that data to a preset?

It might be a common programming technique used by some but not all... BTW, I did save the patch with fx disabled as a preset in the Cakewalk frame. When I use it, the fx status is correctly returned (fx disabled)

Thanks abacab... As it's happening with Starship too, it's not just my system. Some stuff does indeed get saved, but the simple task of muting the reverb and delay is where I discovered the issue. Closing and re-opening the project returns to the preset, not with these changes.