Midi effects greyed out when I select a range of hits in the piano roll

Bruamp

The model for applying MIDI FX has changed with X1. You have to add the FX to the track's FX bin, and configure it there. Then you can continue to use it as a real-time effect, or "apply" it to destructively render the changes. 

I believe you can also add a midi effect to a single clip, right? That's what thefyn is trying to accomplsh: only modify certain parts of the track..

Yes that's true, and now that you mention it, it appears that you can apply MIDI FX to a clip directly without first adding them to the clip FX bin by choosing Process Effect > MIDI FX in the clip's context menu. I could be wrong, but don't believe this option came up in the recent thread on this issue.


Good catch.

MGC59


We had a thread about this a few weeks ago. You can't use the Cakewalk FX anymore.
What you are trying to do will not work in the Midi FX bin either.
The CAL file workaround is not an improvement
I now have to go back to 8.5 to edit like I used to.
This is fail Cakewalk. This is a step back.

Did you see my last post? I tested the Clip FX option, and it works. No need to add the FX to the bin.


1. Select part or all of a clip.
2. Right-click it, and choose Process Effect > MIDI Effects > Cakewalk FX.
3. Choose the effect, set the parameters as desired, and OK. 

brundlefly

MGC59


We had a thread about this a few weeks ago. You can't use the Cakewalk FX anymore.
What you are trying to do will not work in the Midi FX bin either.
The CAL file workaround is not an improvement
I now have to go back to 8.5 to edit like I used to.
This is fail Cakewalk. This is a step back.

Did you see my last post? I tested the Clip FX option, and it works. No need to add the FX to the bin.


1. Select part or all of a clip.
2. Right-click it, and choose Process Effect > MIDI Effects > Cakewalk FX.
3. Choose the effect, set the parameters as desired, and OK. 

That was in the last thread also.

If you can't use it in the PRV (where I do all my midi editing) then what good is it? Seriously, a workaround for something that used to work flawlessly is not a viable solution.

It may "work" for you. It does not work to the capacity that it used to.

Brundlefly - Thank you for your reply in this matter.
As you can see from my 8 posts I don't spend a whole lot of time in writing in these forums. I do however gather a lot of info from here. 

I have been using Cakewalk since the Pre-Sonar days. With the exception of Sonar 7 (If I remember correctly) I have loved every version. That is until now. X1 has been a bittersweet struggle for me.

On one hand I am making some of the best recordings and on the other I am constantly fighting with the software.

I finally had a week off to really get into some long sessionswith X1 and I encountered new issues in every session. Quirky behavior, difficulty with workflow,  features I rely upon disabled, and glitches.

Some of these issues seem to resolve themselves by restarting the program and some occur randomly.  

My anger and frustration come from the fact that I am not someone's beta tester and  don't accept work-arounds for something that should function correctly. When I invest money in software (especially as much as I have in Cakewalk) I expect it to work at least as well as the last version.

Inspiration should not be ruined by a frustrating roadblock of poorly tested software.

The needless removal of a viable feature is mindboggling to me. CAL files have been around forever (and still are), yet I cannot access Cakewalk FX in PRV. That makes no sense to me.

That being said I seriously doubt there are too many people who have the same issue as I do. so I don't expect it to be fixed.

Sorry for getting on the soapbox but that's what unhappy consumers do.

I work in IT so change is a part of the landscape. Change/ommission for no good reason is just mind-boggling.

I get the feeling that Cakewalk is not quite in tune with the vast spectrum of their users.

Can anyone find any circumstances/selections where main menu Process/Apply Effects/MIDI Effects ISN'T greyed out?

Yes, when the FX is already in the FX bin of the MIDI track, the Process menu is available.

MGC59


....yet I cannot access Cakewalk FX in PRV. That makes no sense to me.

Yes You Can!!


You can access them in PRV WHEN you have the Select Tool selected. Then do what you use to do. Right click and all of them are available. Try it!!

And MGC59, I too am a long time user of this software. And I also find these little 'quirks" you speak of!! Like this one here. I use to right click/velocity all the time for drum parts. Little sections that just wasn't up to snuff could be varied by this method. Now it requires me to almost sit there with a finger on the "T" key all the time!! (when in PRV). I really need to set it up so that I can hot key each tool.

NP MGC59, good luck.

GremYou can access them in PRV WHEN you have the Select Tool selected.

Interesting. Good catch. And right-clicking a note also goes to Note properties like it used to in 8.5 - and as it still does with the Smart tool in the Staff View. I think they need to fix this inconsistency. I  think right-click should always give you a context menu by default, unless accompanied by a modifier or deliberately re-mapped by the user. I was never too keen on right-click being delete in the PRV.

Like many other users, I use the PRV all the time for midi editing - especially on drum tracks.

The way forward now seems to be:

1 - Hit 'T' (Or use the middle moluse button)
2 - Select the, er, select tool
3 - Select the data you want to apply a midi fx to
4 - Go back to the TRACK view
5 - Select Process Effect > MIDI Effects > Cakewalkf FX > Velocity (as an example)
6 - Make the changes you want and hit ok
7 - Go  back to the PRV to verify everything's ok, if not, Ctrl + Z and go back to step 4

If there's a quicker way to adjust select drum track velocities, then I'd like to know what it is!!!

brundlefly

Grem
You can access them in PRV WHEN you have the Select Tool selected.

Interesting. Good catch. And right-clicking a note also goes to Note properties like it used to in 8.5 - and as it still does with the Smart tool in the Staff View. I think they need to fix this inconsistency. I  think right-click should always give you a context menu by default, unless accompanied by a modifier or deliberately re-mapped by the user. I was never too keen on right-click being delete in the PRV.

Totally agree.
I KEEP right clicking and then having to Ctl Z to undo what I've just deleted.    This needs sorting out; it's a convoluted mess.

I've come to really like having erase on the right mouse button. Once you get the hang of that, and the other modifiers, editing in PRV using only the Smart Tool can get seriously fast.

I agree that it's unorthodox enough that it should be an option though.