would a jjos pgm compatible VST be appealing to you?

would you have use for a modestly priced VST that reads jjos DRUM pgms with the following possible features/limitations?

probably imports the following:

samples assigned to 1 pad bank only (A)
layers: velocity splits, levels, tuning, etc.
pad mono/poly settings

------------

maybe imports:

amp envelopes
velocity settings
mute groups
program mono/poly settings (sets all to same choke group)
pgm-level sample start/end

---------------

probably does not import:

pitch envelopes

----------

definitely does not import:

filter envelopes
LFO
velocity => filter/attack/pitch
HOLD param (os128xl)
INST pgms
multiple banks
DIRECTION
layer crossfade
NDC

What will it export?

If looped samples are recognised I'd be up for it. All pad banks or at least a choice of which bank to load out of pgm would be nice too, but understand we can't have everything!

looping would be a big plus for me, too. i currently rev/crossfade are not implemented natively, so i don't know if it's even possible.

regardless i think a quick 16 chop pgm export to vsti would be nice for polyphony savings. i'll explore this.

mokomo wrote:What will it export?

you mean what format will it export? i can't say, but it'd be cool if it could export pgm. personally, i think there's not much sense making pgms on a computer since jjos makes it so easy

Probably not.

Probably not too.

what my initial reaction would be "no" also, but i'm really allured by the polyphony saving potential. i'm just gathering info here - what would make this appealing, or do you guys just have no need for something like this?

Nym wrote:what would make this appealing

first of all, only 16 pads/one bank really is a deal breaker imo.

also, i think program mono/poly, amp envelopes and mute groups are necessary.


honestly, if i could throw a NDC program in (even if it destructively extracted each slice) i'd pay $100+ easy....

btw, has there ever been a feature request to have a button to extract all slices from a NDC sample? that would be dope

I use the mpc as the sampler. But reaper as the sequencer.. (button mash the phrase/drums in live to reaper as a audio loops)
When i want to layer drums some more i use audio to drumtrigger midi notes and reasampler to layer..(copy and paste reasampler to add another layer)

REally not usefull for me as i have an alternative already that is pretty damn quick and for the polyphony benifit my way is faster especially having track templates in reaper(for layering on whats there already) I guess if you want to preserve your pgm drum sounds for the particular beat it would be good but i track in as i sequence so not really any point for me...

The only import of hardware jjos into software that would be incredibly usefull would be full import...
With the vsti having the routing abilities in pgm or track mode mixer having atleast 16(32 mono outs) stereo outs to the daw. kind of a jj os vsti plugin...

And must be both available for mac and pc...

The only pain for me atm is making a full piece inside the mpc and getting it out into a multitrack daw...
I know it's stepping really close to the ren, but for me that's the only real deal i'd buy it.. I'd buy it for every computer i use it on... And if every function in the vsti is midi learnable imagine the possibilties(and a hardware mod that makes all function buttons on the mpc1k 2k midi)...... The plus for me is not starting in the studio... It's starting on the mpc and ending in the multitrack daw studio...

The plus for me is not starting in the studio... It's starting on the mpc and ending in the multitrack daw studio...

yup. i'm convinced. there's no need a vst

nope.. what would be useful is a cross-platform (and I mean Linux compatible as well) beat slicer in the vein of recycle that can export to jjos pgms and creates the MIDI sequence as well .

I'd settle for windows compatible.. but cross platform would be best.

I think that a VST that has the midi mapped out for the midi button mode thingy would be a good idea in some ways. Well more a skin for the midi functions with named buttons. Really its a macro, but if it was packaged as a VST that just dropped into your DAW and gave you button mode control control (or what ever it is called).

Get me?

So its just mapped out to the default MPC map and then gives you DAW control in that mode. You probably got most of that done anyways.

did anything happen with this?