CLICK from main screen (F2) in os2 - do you use it?

please read this in its entirety and only post acutely on topic relating exclusively to the items discussed below:

this is an attempt to gather some information regarding the current os2 access to CLICK from the MAIN SCREEN. currently, the ability to edit/turn on/off the metronome can be accessed by hitting F2 on the main screen.

i have heard several users puzzled as to why CLICK is so prominently displayed, implying that they do not access CLICK very often. CLICK is accessed just w/ F2--no holding shift, no holding TC (though there is space there).

are there users who benefit MIGHTILY by single button access to CLICK from MAIN who would tantrum if it was accessed in a different way? say, SHIFT+F(x)?

the reason i ask is because there has been a request for some sort of MAIN screen TRACK LEVEL control. unfortunately, MAIN screen is jam packed with display right now. there's a great deal of stuff you can do from the main screen, which is great, but admittedly we are definitely missing TRACK LEVEL.

as you know, there are a couple types of track specifications in the track mixer. there's TRACK tracks, whose level is global, and PGM tracks, whose level is independent per pad.

an ON MAIN SCREEN TRACK track volume control is easy to fathom--it's the exact same thing as what you find in the non-graphic track mixer (dont sleep). however, PGM tracks aren't global, so this hopeful TRACK LEVEL control wouldn't work...or would it?

my solution to that issue is to make the hopeful TRACK LEVEL param in MAIN screen function as if you were in GPE hitting WHOLE. in theory, it's still editing single pad levels--just all of them at the same time, by contrast to TRACK tracks, in which there is only 1 param to edit per ALL PADS.

so, a brief recap:

-move CLICK to SHIFT+f(x) button
-put a TRACK LEVEL param accessed by hitting f2 (f2+datawheel + and - changes level is my idea)
-for TRACK tracks, TRACK LEVEL directly corresponds to the TRACK MIXER
-for PGM tracks, TRACK LEVEL directly corresponds to ALL PADS (WHOLE A01-D16) in the PGM MIXER

your thoughts?

For Me, [CLICK] is an option that you set just use once to set it up. And once you found your setup, you never use it again. I would have absolutely no problem with moving it to the [OTHER] options/settings menu.

I'd like to see a track level button on [F2], because I miss it, since the Velocity field is gone in OS2. Even cooler would be, to be able to customize the F-Button setup. But I guess that wont happen

stan steez wrote:For Me, [CLICK] is an option that you set just use once to set it up. And once you found your setup, you never use it again. I would have absolutely no problem with moving it to the [OTHER] options/settings menu.

I'd like to see a track level button on [F2], because I miss it, since the Velocity field is gone in OS2. Even cooler would be, to be able to customize the F-Button setup. But I guess that wont happen

I would back STAN's words....

stan steez wrote:For Me, [CLICK] is an option that you set just use once to set it up. And once you found your setup, you never use it again. I would have absolutely no problem with moving it to the [OTHER] options/settings menu.

I'd like to see a track level button on [F2], because I miss it, since the Velocity field is gone in OS2. Even cooler would be, to be able to customize the F-Button setup. But I guess that wont happen

Co-Sine.

good idea....more please.

i use "click" more than other Fkeys in the main screen. I'm afraid I will be defeated by the majority. No problem for me if there would be kind of 2 different main screen Fkeys. For instance you have your normal way and when pressing shift+main screen you have a secondary Fkeys main screen. In my idea, the worst thing is always to press shift endlessly.
Anyway one could say "unconclusive workarounds" i guess.

i agree with stan, i need click once a month.

I agree with Stan as well.

I like quick access to click for live playing and drumming practice.
I guess i could live without it though... as long as its appears under the shift key, and is replaced by something that I find useful.
Track volume falls into this category you lucky,lucky people.

big up bro ! you gotta be the most mpc saint

it seems a great idea , as long as the level adjusts only the volumes of the events of the pad-performances on that particular track.
personally i would just like the good-old midi velocity control, rather than a global level control, which it seems we already have. i mean, if it edits all the pads levels, wouldnt it be exactly the same function as we currently have in the track mixer?

imo, what we really need is a solution in the track mixer where its possible to mix different tracks off a single pgm individually,without having them forced to share the same track-based effects routing, but i'm guessing this would need some major programming work.

anyways nym to directly respond to your question, my suggestion:

why not go back to controlling track velocity (a midi thing like the old MPC os), rather than level , in the main window using the F2-DATA WHEEL +/- as you proposed , you could remain with the same 'inst' and 'pgm' mixer configuration that jj has currently, as this parameter is just midi, right?

mixing in this fashion, even if the levels are all linked as 'pgm' in the mixer window, there is still a way (using the midi vel parameter in MAIN window) to quickly get seperate volume levels on that drum program's associated tracks and still have effects all separated by pad.

whew!

CommanderRobot wrote:i agree with stan, i need ***** once a month.

Sorry!!! LOL

I agree with Stan also.

Stan's the man, co-sign!

personally i would just like the good-old midi velocity control, rather than a global level control, which it seems we already have.

actually, we already have both, in multiple places. global level we have in GPE: per-pad layer sample level, pad program level, track mixer graphic view, and track mixer text view.

for global velocity, enter SEQ EDIT to add, subtract, etc velocity to either the whole track or specific pads.

but to address your question:

why not go back to controlling track velocity (a midi thing like the old MPC os), rather than level

well, because it's the same problem as the ones i listed in the other thread: i'll sum them briefly:

1- TRACK VELOCITY is post-record only, does not influence realtime pad performance
2- VELOCITY does not = LEVEL, in all samplers/synths worth their salt, velocity is set to many different parameters, and sometimes not LEVEL at all. this isn't to say that using VELOCITY to set a recorded pad's VOLUME is somehow "wrong," because it's not, depending on how you have set the PAD's params...but bringing up/down global VELOCITY as a means of level setting/mixing is problematic because:
---> many pgms have many different pads which are set to many different velocity->level curves, which means that if you try to bring their velocity all down at one time, it does NOT mean that they will all decrease in volume at the same rate. pads w/ velo settings of 0-100 will get quieter faster than pads w/ velo settings of 50-100. pads w/ velo settings of 100-100 will never get quieter when you drop velo.

as a result, if you have a drum track in which your kick velo is 50, hat velo is 0, and snare is 100 and you turn down the TRACK VELOCITY of all, the SNARE will never decrease in level, the kick will turn down some, and the hat will turn down a lot. see? difficult to explain but look at the VELO setting in amp adsr in os2. set up the kick/hat/snare example i just described, and then after recording a quick pattern bring down their velocities via SEQ EDIT to see the issue.

whew is right. i could have showed you that in less than 1 minute in real life dammit hahah

you also mention that you'd like...

a way...to quickly get seperate volume levels on that drum program's associated tracks and still have effects all separated by pad.

truly, for that, i truly believe that you will be a happier man if you perform this task via entering GPE and selectively change the levels of your assigned samples under the first GPE page, F1 sample.

if it's just a single pad you're editing, just hit MODE over the PAD/SAMPLE display (directly below PGM) in MAIN screen to pull up GPE's single-pad view for extra quick access to individual pad levels. and, of course, tapping another pad while in this popup PROGRAM editor allows you to see other pads.

the reason i think you'd come to prefer this is that it's directly reflected in your PRE-recorded pad sounds, ie you don't have to wait until after you've recorded your pads to hear the effect of your volume increase/decrease. in this case, it pays to set your params "earlier" in the chain of events than post-recorded midi FX.

what a seriously dense post, i realize how difficult this can be to conceptualize in a text box. also, i don't have a real firm grasp of your familiarity simply because i dont know enough about your workflow etc. if you want to discuss this more conventionally you could give me a call. i live in the states though, dunno where you're from

whew but cool! thanks for it all,and i'll click about dem windows per dem suggestions man.

yo i downloaded yer album off yer site. nice beats.