JJ OS Feature Requests (ARCHIVE)

JJ says-

Since the function has many requests of a user, it is added by Ver1.19.
Please refer to the following site.

http://www7a.biglobe.ne.jp/~mpc1000/os2/trackmute_e.htm


wahoo!

Man I love JJ... Tap Button?

what is this tap button fetish Wu?

I've just recently learned how the old TR sequencers, as well as old analog sequencers, work. The loop edit mode that you access from the Grid mode by hitting the numeric button is very similar to this. You use the 16 pads to place 16th notes in a bar of music. With the TAP button, you can place these notes as the sequence is playing. Also another TR drum machine staple. Since I learned about this and discovered this loop editing mode, it just seems to me that that crucial element is missing. I really have grown to appricieate this way of sequencing. It really shows you why a lot of house and trance music was made from them... BUT, it seems to me that so much more could be done with it. It really allows you to create something that you would not have come up with from another setting. Check it out, if you haven't already, and I think that you'll see why a TAP button is really important for this type of sequencing.

ALSO: Load up some TR 808 samples and this could really be the closest thing to working with the real thing. (And you would be able to use this method with any sound.)

arebee wrote:JJ says-

Since the function has many requests of a user, it is added by Ver1.19.
Please refer to the following site.

http://www7a.biglobe.ne.jp/~mpc1000/os2/trackmute_e.htm

wahoo!

definitely cool. pretty quick response, too!

yo arebee:
for the record, when i got this same message from murai i asked if it was possible to implement the ACTIVE key idea we came up with (instead of the +/- tabs as in the link above). the reply i got back took a few reads for me to understand what he was trying to say, but the basic idea is:

1. the TRACK MUTE code is complex & this implementation is the least bug prone.

2. to implement the ACTIVE tab idea, whenever a pad is struck in the TRACK MUTE page the os would have to check if the ACTIVE key was pressed or not (so it knows if it should mute or make active the track). this constant checking & decision making in the code would possibly result in a delay or lag in performance which might cause the track to not mute (or become active) right away when you hit the pad.

or in JJ speak:
"Moreover, since the method performs the judgment of an active change or mute whenever Bud is struck, it may be overdue in whether a performance will stop for a while."

...so it sounds like he might have already tried the idea and saw it wouldn't work right.

either way, i'm glad to have this capability added.

wudsiba wrote:I've just recently learned how the old TR sequencers, as well as old analog sequencers, work. The loop edit mode that you access from the Grid mode by hitting the numeric button is very similar to this. You use the 16 pads to place 16th notes in a bar of music. With the TAP button, you can place these notes as the sequence is playing.

i don't get it. isn't that just the same as turning time correct to 1/16 and just hitting a pad in grid edit as the sequence loops around in overdub mode?

That's kind of like saying that you can record volocity in real time, so why add it to step recording. It works in the same way yes, but this would just add that feature to the loop editing. It can be done in other ways, but it seems like this would be something easy to add so that you could use the sequencer in a different way. I really think that this would be a big benefit that seems to have gotten lost in the newer way of doing things. I think it would still prove beneficial just like ping pong looping. (For example.) These old sequencers/drum machines are classics for more than just thier sounds... (Hope this doesn't seem like a smart ass response, as it's not meant to be.)

thanks for the report sooty-g...

i know i've already said it before but i've seen a lot request came back so here is this one again...

capacity to have more effects settings loaded in the ram...
it's been made for the programs and you can actually have only 20 effects settings.
pretty frustrating when you use those within effects automation...
i would at least need 30 of them

I would like to see a simple sample offset feature. Just something to delay a pad by, maybe, up to 20 ms.

It's a dream when you're layering samples--helps make them sound much bigger and thicker. Especially useful for snare/clap combos. If you're not sure what I'm talking about, download the demo of Poise:

http://www.anothersmallclue.com/poise.php

and check it out (Guru also has this feature, as well as FL Studio's native sampler channel). Slap a couple snares down, and mess with the offset knob on one of the while while they both play together. Just delaying one a couple ms can make a huge difference, and I can't imagine that it would be too difficult to implement. It would fit right in with all the other goodies in the GPE.

Until that day, I guess I'll just keep manually offsetting every single hit. Unless somebody knows of some way of doing this that I'm missing.

edit: I guess it could be fairly easily done in grid editing, but still, it would be nice to just be able to set an overall delay for the sample, so you wouldn't have to manually move every hit where you wanted it.

thehuman wrote:I would like to see a simple sample offset feature. Just something to delay a pad by, maybe, up to 20 ms.

It's a dream when you're layering samples--helps make them sound much bigger and thicker. Especially useful for snare/clap combos.

sounds like a good place for this potential feature would be in the SAMPLE LAYER screen.
(from the main screen, put the cursor over the sample name & hit the WINDOW button.)

somewhere in there would be a column named OFFSET where you could select a number of milliseconds to offset any one of the 3 layers. (say 1-500 milliseconds)

what would be especially powerful about this is if you could do it in realtime and especially if you could also offset layer 1 just by itself, even if you had no other samples layered with it. that way, if you sat there and played with the offset of the main sample while the sequence played back you could do real subtle timing shifts with the various sounds in your sequence.

mkl... wrote:i know i've already said it before but i've seen a lot request came back so here is this one again...

capacity to have more effects settings loaded in the ram...........pretty frustrating when you use those within effects automation...
i would at least need 30 of them

what effects automation are u referring too? just event list effect set changes

yeah - i'd like to see more, yet i only ever use about 10, even for a full liveset hour's worth....but i'm sure i'd use more in the future, esp. as i am using OS2 nearly all the time for new work.

first though i'd like to see real internal effects automation, like Qlink > recordable fx parameter changes. then mbe external MIDI>CC>effects autom.

peace

what effects automation are u referring too? just event list effect set changes

yes, that's it...and i don't use many effects because they need that kind of improvement to be useful to me...
i use my mpc for live purpose...and i already have something like 30 sequences ready to be played on stage.
i would simply love to have more fx settings avalaible...

i can admuit that q link to effects would be awesome (or aux sends) but there's much more to do before...

its a shame though, 'cos like u i also use an mpc for livesets, and when i use fx events in the seq, i sometimes get 'clicks' as the fx switch, and even when the sequence is looped and the SAME fx are 'reloaded' as its looping, but its probably quite inevitable given that there's an abrupt change in signal esp. if the input to the fx are differing through these loops....i've often wondered about a fix for this but nothing short of a tiny xfade in the fx bus would help.

some feature requests :

-fx automations in grid edit

-separate effects settings for master fx and "aux" fx

-q-link to fx parameters

-i still never use the real time pitch shift on audio in (it's useless because you can't use it while a sequence play (so you can't hardwire out 1-2-3-4 to audio and send the result via mains out...)

-lfo's to fx parameters

-lfo's in grid edit

-mute tracks via mixer (pad 4) (i prefer this one cause it allows to select the track and to work on fades...