Removing selected parameters from MIDI track

[Gades]

Sometimes could be handy to remove from existing MIDI track selected MIDI parameters, eg. panorama, strange CC58, CC10 and so on. For now we need to select parameter's tab, click on lane area for grab the focus, select all values by Ctrl+A, delete them and right click on the tab to remove parameter completely. For 10 parameters per track it's time consuming and boring
"Remove parameters" command should display a window with all parameters defined for the track, with checkboxes. User select parameters to remove and click OK, the command iterates through parameters, removes all points/values and removes parameter's tab. After all I would like to have MIDI track without selected parameters
For macro purposes, "Remove parameters" could get name or code of the parameter to remove.

 

[lokeyfly]

As far as I know, you'll have to remove those parameters from the instrument tracks as they apply. Still, your checkbox idea is a good one. Likely where the three horizontal dots tab is, open that which is the Automation window. It would be nice to have not just what is entered as available automation, but a selection box against each parameter. Or at the very least, select all tabs (control + A), or control select at the instrument tabs themselves. It would be nice to easily defeat a parameter, even momentarily, just to hear the results it has for that instrument. I'll have to look into that more.

If you make a formal feature request with Presonus, place the link in this thread and I think you'll get some up vote support.

 

[Gades]

I meant parameters for MIDI track - lanes visible in MIDI editor, not regular automation parameters for any track in arrangement window. You know, modulation, expression, after touch, velocity. These parameters are not visible in the track inspector. Besides, I want to remove some of them completely, because moving MIDI eventwith these parameters between tracks may affect instrument on other track (change panorama e.g.) and it's hard to notice at the first moment.




Those parameters may be add/remove in the dialog window from three dots:

but this editor removes parameter from all parts and if any of parts has no this parametr, Studio One crashes (7.02 and 7.1).

Additional command in Scoring Tools with names or other ids of parameters to remove would be very handy to create "special actions", eg. remove one parameter from drum events and other from orchestral. I use macros a lot because of Stream Deck - it's very easy and quick, but Studio One has very limited set of commands (compared to Reaper). PreSonus should provide a scripting engine...

 

[lokeyfly]

I meant parameters for MIDI track - lanes visible in MIDI editor, not regular automation parameters for any track in arrangement window. You know, modulation, expression, after touch, velocity. These parameters are not visible in the track inspector.

yes, I had deleted that part of my resoonse. Anyway, good you provided screenshots.
Yes, unfortunately, once a parameter is assigned and the Control Link sees it (hand turns white) and it is either dragged to its own lane (between or added to tracks), or even over a track, while the oarameter(s) can by made visible or hidden by virtue of the on/off (dot) in the Tracks Editor, the only other thing that can be done there is right click to hide or remove that parameter.
MMV, but that is pretty fast as I see it.

 

[Gades]

yes, I had deleted that part of my resoonse. Anyway, good you provided screenshots.
Yes, unfortunately, once a parameter is assigned and the Control Link sees it (hand turns white) and it is either dragged to its own lane (between or added to tracks), or even over a track, while the oarameter(s) can by made visible or hidden by virtue of the on/off (dot) in the Tracks Editor, the only other thing that can be done there is right click to hide or remove that parameter.
MMV, but that is pretty fast as I see it.

If you have many parameters to remove, it's not so fast. You have to click on every tab, select remove action from menu and confirm in dialog. Or you can use "tree dots" button to remove many parameters, but - for me, on Windows 10/64bit, SO 7.02 and 7.1 - this method ends with SO crash if one of event has no one of removing parameters.
And, what is also important, there is no internal command for do it in macro, without opening MIDI editor. The fastest way would be create a macro with Scoring Tools command to remove specific parameters (I often get 5-6 of them), select track/event and call macro to clean track/event even if there is no specified parameter (to avoid crash of SO).

I've already created macro for remove selected parameter:

so for now I open MIDI editor, select parameter's tab, press a shortcut for this macro and tab is gone, but still I have to open MIDI editor, navigate through tabs, select specific (in general always the same) parameters, run macro, select another etc. I wish to have possibility to create macro with commands: Remove parameter("CC58"), Remove parameter("Pan"), Remove parameter("Init")... and run it with shortcut for every MIDI track, without testing if all of these parameters exist

In the fact, command with parameter to specify tab/MIDI parameter would be a great solution

 

[lokeyfly]

Ok. Wow, that's a lot of parameters you're often removing. I get the need for the macro. It's a bit thwarted by still having to go in and remove those other parameters, and deal with a potential crash....
As a roundabout suggetion, ince you have the track the way you want it, you could create a few varied presets of the most "types" of instruments you use for the instruments you do this routinely with and use that as a workaround? That would be a drag & drop affair. I mean routinely deleting "10 parameters per track it's time consuming and boring " sounds pretty ...well... time consuming and boring.

 

[Gades]

Ok. Wow, that's a lot of parameters you're often removing. I get the need for the macro. It's a bit thwarted by still having to go in and remove those other parameters, and deal with a potential crash....
As a roundabout suggetion, ince you have the track the way you want it, you could create a few varied presets of the most "types" of instruments you use for the instruments you do this routinely with and use that as a workaround? That would be a drag & drop affair. I mean routinely deleting "10 parameters per track it's time consuming and boring " sounds pretty ...well... time consuming and boring.

I prepare a lot of orchestral mock-ups of classical pieces of music based on public MIDI files and files from my co-workers. At the beginning I have to "init" each file before I start a real work. I need to clean it out, check octaves, remove "unneccesary" parameters, clean modulation/expression data, prepare tempo, metrum, scale. After that I grab my track presets with attached orchestral instruments and put them into the project, move MIDI events there and now is the main part of work (choose articulation, record modulation/expression, correct velocity and so on).
First round, with cleaning and other "technical" things to do it's really boring and I look for every opportunity to simplify my life

 

[lokeyfly]

I still think selection of parameters on/off/delete/add would be useful.
We work very different as I always work from a blank slate. : )
But that's the beauty of independent, workflows.

I'm still not clear why you'd even have to delete parameters that you don't actually use, but in an effort to fix what you'd need, I'd prepare an FR for it. Then link the FR here. You might find others have the same issue, and vote it up. I will.
Good luck, going forward.

 

[Gades]

I have to remove these parameters because they send an information to orchestral libraries and change their configurations. E.g. many of public MIDI file has CC02 (breath control) or CC07 (volume) parameters. If I run MIDI event with these CCs, my library get CC02 (mainly vibrato) or CC07 data and changes those parameters - instrument will lost vibrato or will be very quiet. The same with panorama or program change, and many other CCs. After that the library may sound strange in many ways or its behavior may be "magical" (something changes without reason), but the changes may not be immediately noticeable. If I don't notice this and start arranging, I may misjudge the dynamics or tone of what I'm hearing and may do stupid things, like bump the volume in the mixer or "fight" with panorama - believe me, this request has serious practical source I would like to avoid the waste of time

You mentioned about the link, but I'm not able to see it Thanks anyway!

 

[lokeyfly]

I think the link is still here my friend.

Presonus forums - Questions & Answers | PreSonus

Hi all Just a comment, really. I just looked at the 'community' tab on the main ... the different pages? Thanks for listening. PreSonus Forums

answers.presonus.com

You'll have to start a feature request for what you want to request as a feature. Keep it short, clear and to the point.Your subject you used in this post is perfect! Maybe also address the cross conflict you're experiencing just to bolster the point made. A short paragraph will do. Then post the link here for further visability.

If there is a better FR link that I'm currently not aware of, someone here will provide further help.
All the best and I hope you have an easier time with those conflicting parameters that you have to delete across different tracks at times. For me, I start out clean, but details get considerably archaic toward the middle and end.
Peace, out.

P.s. For future reference, be sure to add your equipments specs to your forum signature. This seriously helps with providing the best information towards your related equipment and issue. You'll only need to add it once.

 

[Gades]

I think the link is still here my friend.

Presonus forums - Questions & Answers | PreSonus

Hi all Just a comment, really. I just looked at the 'community' tab on the main ... the different pages? Thanks for listening. PreSonus Forums

answers.presonus.com

Oh, you meant PreSonus Feature Request... Sorry, I don't believe in FR, so many requests still are hanging (abandoned? ignored? forget?). That's why I wrote my ideas on Studio One Toolbox forum... I've tried, many times, create new, vote for existing, without any results
I hope Lukas will be faster and much more kindly

 

[Lukas]

but this editor removes parameter from all parts and if any of parts has no this parametr, Studio One crashes (7.02 and 7.1).

Could you post the steps to reproduce this here? I cannot get Studio One to crash by removing automation parameters.

Regarding your request: Unfortunately, this isn't something I can solve with a script. It's a feature that Studio One doesn't currently offer, and scripting doesn't yet have access to part automation.

So I'm afraid in this case it would really be a feature request for PreSonus. And actually it's something I've already discussed with product management and I hope we can work together to implement some long awaited features (automation lane presets, automation lane removal, default automation parameters per instrument and more...).

 

[Gades]

In my case, the reproduction steps are very simple, but it doesn't always work - unfortunately it takes 4-5 minutes to restart Studio One and re-load whole orchestral session, so I'm not that keen on testing this multiple times, I'd rather just avoid that scenario
- I have 15-25 tracks with orchestral libraries (BBC SO, Berlin, Cinematic Studio, Audio Imperia), song length - 2-15 minutes
- tracks become from GeneralMIDI file, with "unneccesary" CC parameters (121, 10, 7, 2)
- I open one of MIDI event and enter "three dots" parameter editor, select parameters to remove and click right arrow button to get dialog:

- after confirmation Studio One freezes for long time and suddenly disappears
- Studio One restarts and asks for run in "safe mode"

In dmp files I found last logs before restart, look like this one:
11:15:40 exec Remove Automation: RemoveEnvelopeRegionAction
In dmp.txt file you can find logs read by WinDbg - unfortunately, I'm Java developer, so I'm not able to get better information from this dump

This problem doesn't occur when I remove tabs manually, so I prepared macro, defined shortcut and run it from Stream Deck. It's slow, because I need to enter every MIDI event and click many times (on every tab) to run the macro... But, also in this case I need to be careful, because after removing tab usually focus has Velocity tab (that's the reason I need so many clicks on every tab), but sometimes focus is lost (!) and running macro in this situation also freezes and crashes SO...

BTW. "three dots" editor needs an immediate improvement to search/filter parameters or add CC parameter manually:

 

[Gades]

By the way, is there any chance to add to export window option to disable showing Explorer window with finished file? Now are two options: leave export dialog on the screen and do not open file dialog or close export dialog and open file dialog. There should be the third option: just close export dialog:

I ask for this feature since 4th version and still nothing...