how do you interpret the distinction of DRUM or MIDI tracks?

when making a track on the jjos2 sampler you record notes on tracks in sequences. when you create a track, you have a choice of making it a DRUM track or a MIDI track.

what is the difference? either can send midi: you can assign midi out 1A to a DRUM track, or by direct opposite, you can use MIDI tracks to sequence in-house programs (ie NOT sending midi).

you can even record QREAL and QLINK NOTE ON data in MIDI tracks: (though QLINK NOTE ON does not appear in STEP EDIT, and to view QREAL you must first change the track to DRUM and enter through 6grid).

why are there be 2 types of tracks? all data is recorded and evented regardless of track type

am i missing something?

I would hate editing midi in drum/pad mode. Can't see chords (not easily), can't see duration of notes, see note overlaps or gaps, etc.

On the other hand I would have no issues editing drums in midi mode though it's easier to program in a grid by hand.

I would hate editing midi in drum/pad mode.

but you ARE editing midi in drum/pad mode...

I never saw any difference. I would just change it to distinguish that it was a midi track. I'd like to know as well.

i agree wit da otha fella

i guess its easier to see da chords
where on drum edit its a big confusing ball when notes are on pad bank b and c
and da 6 pad screen

and also i like da fact dat i can distinguish which are midi like lithion said

From MPC2500 manual:

You can set the track type in the Type field in the MAIN page. There are two types of track: DRUM and MIDI. They are called DRUM track and MIDI track respectively. Below are the differences of each track type.

DRUM - Select this track type when you play the MPC2500’s internal sampler by hitting pads. The DRUM track data will be managed per pad.

MIDI - Select this track type when you use the MPC2500 as a MIDI sequencer with external MIDI devices (MIDI keyboard etc…). The MIDI track data is managed per MIDI note event. For more information, see the “MIDI sequencer feature” section on Page 24.

right, but doesn't that also work in complete reverse?

you can use MIDI tracks to sequence internal sounds. track data is still managed per pad in MIDI mode (qlink note on, qreal).

also, when in DRUM track, track data can be managed per midi note event as well...

Only difference is the access to the midi grid edit, bothers me too, why not just be able to view it on all tracks? 6pad grid edit could use some improvements, not being able to see which pads are recorded without turning overdub off and hitting the pads. Fold function or cursor down for scrolling would help much.

i agree. i feel that of all 5 editing screens, i work best in midi grid edit with TC off on doubletime res. i use a LOT of note ons, so being able to see note duration is so, so handy.

the downside of midi grid edit is that you MUST be in midi mode, which means the following:

- you can't see your qlink note on data. this is usually ok, cuz it's easy to do blind. but when you want to review or deep edit it, you can't see it in step edit. you have to change MIDI to DRUM just to view this information--which is THERE, it's just HIDDEN for some reason in MIDI step edit.

- you can't change your midi note assignments. try it: chop a sample, assign the notes to 35-96 in GPE, then reverse the assignements A01 and A02 (A01 will = 36, A02 will = 35). try recording these: NOTE: playback is reversed). in DRUM tracks, this works perfectly.

- you have to change to DRUM tracks to view your qreal data by entering 6grid.


-------

offhandedly, wouldn't it be nice to enter qreal edit or CC edit from mode/pad 1 (slider) rather than through grid edit?

Nym wrote:

I would hate editing midi in drum/pad mode.

but you ARE editing midi in drum/pad mode...

What I meant then were external midi devices.

As far as qlink/cc edit being accessible in an easier way, yes that would be nice. Anything where I don't have to go through several menus and hold shift down would be good.

What I meant then were external midi devices.

yeah i figured that one out eventually, tahnks for clarifying.

but of course, it remains - you CAN sequence external devices on DRUM tracks simply by setting the midi out to 1A (even if today, this is undesirable -- until MIDI GRID EDIT was introduced in early versions of os1 1.00, we had no alternative than to sequence external midi items in 16grid, 6grid or step edit)

knawmeen knawmeen

Anything where I don't have to go through several menus and hold shift down would be good.

yeah it's allll about the shortcuts!!!

until switching to os2 1.01 I actually rarely ever even bothered changing the tracks from drum to midi, even when using midi. it just never seemed very important

The grid edit and midi edit screens I kind of avoided for the most part in OS1, but now that OS2 has it right on the main screen staring me in the face I'm starting to pay much more attention to it and utilize it more and will change the tracks accordingly, as it sucks looking at the drum grid for a midi track

I think its useful to edit by knowing what pad numbers you want to edit, but sometimes you want to edit by midi note numbers, other than this i don't think there should be a distinction,as long as both are clearly visible. If you record qlink or mpc note on data in a sequence it should show up either way.

I think one bit of confusion comes from the MPC's stupid note order, e.g. isn't this why you cant transpose a range of notes from seq edit when your on a drum track? If you have notes in the correct ascending order you should be able to transpose notes of a drum program up 16 "semitones" to the next pad back for instance- and you can do this if you change it to a midi track first, but it'll get messed up if your notes aren't in the logical order.