Ok hi sevenscientist, I’m hoping to see a video soon.
I’ve got a few questions. I don’t know anything about how this is supposed to look, but just some observations.
- Clicking on Sample opens up the Sample-Recorder. However, when you click on the sample-button again, it doesn’t toggle the sample-recorder off. This can be done (the issue here is that once you’ve pressed Sample once, no amount of pressing any other buttons will toggle the sample-recorder display off.)
- What is Trim-button supposed to show? For me, it opens up this: .
This is my “Global View Preset #5”.
- What is Mixer-button supposed to show? For me, it opens up my “Global View Preset #3”.
- What is song-button supposed to show? For me, it opens up my “Global View Preset #4”
- What is “PROG”-button supposed to show? It opens up “Global View Preset #6”.
The rest (calling a specific Global View Preset when pressing Record, OverDub, etc) are suffering from the same thing.
I’m guessing that you are calling the default Global View settings shipped with a just-installed Renoise. That’s great! But a better way is to directly implement, in-mpe-script, the screensettings you wish to use. This way this script will function as-supposed-to, even if the user has already changed his global view presets. dBlue+vV+Conner_Bw were kind enough to break it down for me a while ago, so I’ll just paste a bit of code here.
-- Upper Frame: 1 Disk Browser, 2 Track Scopes, 3 Master Scopes, 4 Master Spectrum
-- Middle Frame: 1 Pattern Editor, 2 Mixer, 3 Sample Keyzones, 4 Sample Editor
-- Lower Frame: 1 Track DSPs, 2 Automation, 3 Instrument Settings, 4 Song Settings
renoise.app().window.active_upper_frame = 2
renoise.app().window.active_middle_frame = 1
renoise.app().window.active_lower_frame = 1
renoise.app().window.pattern_matrix_is_visible = false
renoise.app().window.sample_record_dialog_is_visible = false
renoise.app().window.upper_frame_is_visible = false
renoise.app().window.lower_frame_is_visible = false
Basically you can set your buttons to call these specific display functions, so you can have your MPE script show exactly what you want it to show. And you can toggle visibility of the sample record on and off, depending on what you want to do per button-functionality.
On a more positive side, I’m surprised and delighted to see that Save and New can be called from within a script
The step + / step - and <> are really cool, and the f.level ( Set Volume to maximum within selected sample ) was as surprising as the save + new.
I love that all the buttons have a tooltip on mouseover.
I’m slightly confused by “Step” calling a specific global view preset - if it’s just supposed to toggle follow-pattern off and record on. BTW, I’m fairly sure you can set these up to actually do the reverse, if follow pattern is off and record is already on - another click on the button would toggle follow-pattern on and record off. I’m also really impressed seeing that the samplename, pattern name and trackname can be called and shown directly in the script. That’s amazing!
It’d be nice if “Edit” button would also toggle the adv.edit parameter on and off - and for it to also be aware of which screendisplay it is on - for instance, Edit does nothing whatsoever if I’ve already been taken to GlobalViewPreset#8 by the “Step”-button.
I’m hoping you can add some text next to the “on/off/1/8/1/16/1/64” dropmenu, because it is extremely destructive on a currently functioning song- it’d be nice to know what this is doing without having know what the MPC2000XL does It also seems that it does a couple of things - resize the pattern - and switch quantize on and off.
Same with the metronome yes/no toggle - again, everyone else knows what this is, but I have to discover it by toggling it on and off and hoping nothing specifically goes wrong with my track
Same with the channel mute yes/no, again, feels a bit confusing to find these out by clicking blindly on the interface.
I realize you might want to keep the MPE so that it requires the original Global View Presets - but for anyone who has changed them, it’d be a godsend to simply call these directly from the MPE-script. If you call the screendisplay modes from the MPE-script directly, the user is left to muck around with GlobalViewPresets themselves, and then they basically get more functionality out of the MPE script while also retaining their self-made screensets, which might be called by other, non-mpe shortcuts/buttons.
Well, I hope reading this reply to your script wasn’t a total waste of time! Please carry on improving the script, either completely to how you want it tolook and function (who knows, maybe it already does exactly what you want it to do), or with these minor suggested modifications+improvements.
I’ll keep testing this tool on and off just to see how it progresses, and again: thanks for making it in the first place!