Does the world need another drum sampler vst?

[jamester]

doubleclick on the samples in the browserwindow and
it will preview the sound...
I dont have Reaper...

Well, I just tried it again and it was working as you said...for a while. Then it did the weird "make a new track" thing. Probably something with Reaper, I'll keep playing with it.

thx!

[very angry mobster]

Thanks for checking out Poise and the bug reports.

Is "Save Note Map" what it sounds like - I can name and save my own mapping?

It is. Pad trigger notes can either be changed individually or via "Menu->Learn All Trigger Notes".
:!:But Poise expects to a "NoteMaps" directory to be in the same place as the dll and may crash if it's not there. (This has just been added to my bug list).
If there is a "Default.map" file in the NoteMaps folder, Poise will attempt to load it on startup.

Simple and to the point, but with the features that really count.

That's what I'm aiming for.

Step sequencer. Skinning or at least themes.

I'm not going to include a step sequencer. I want to focus on getting the other features right.
I would like to make Poise skinable but I haven't looked into that yet, so I'm not sure when/if it will happen. I would also like to make the GUI resizable.

a REVERSE button please!

It will be added at some point.

The samples should be previewed when dbl clicked. The knob is a volume knob. I've added the reaper problems to my bug list as well.

[jamester]

Good stuff VAM, I look forward to following its progress!

[aciddose]

the world needs "a" sampler vst which works correctly. due to the limitations of vst you'd really need to make each "voice/channel" a seperate generator module in a modularly patched "minihost" within the plugin. otherwise you could i suppose make this a modular vst host with components designed specifically for replay of samples. patching could then be used to create a wide variety of configurations suitable for many purposes - for example emulations of "xox" drum machines could be accomplished with accurate accents and mixing groups.

if you're doing a drum sample replay plugin, you might as well go all the way - otherwise the world doesnt need another of the usual trash.

[very angry mobster]

That's an interesting idea aciddose. I think the trick would be to create a gui that made using all the modules simultaneously easy/quick. I've tried doing something like that using energyXT+Tobybear's sampler but it got frustrating very quickly. Perhaps something more like the KarmaFX synth would work better, with all the module gui's being displayed on the main screen with the module routing.

What limitations are you thinking of though? And how would a modular host bypass them?

[aciddose]

vst's limitations include the fact that you can not reliably adjust the number of inputs/outputs or parameters of a plugin. so adjusting the number of 'drum' channels would require that you have an internal mixer, effects and routing. if that were done, you could save the whole configurations including patches and allow for basic customization of the gui meaning whole basic emulations of drum machines (or whole new configurations) could be set up and traded via single files.

it wouldnt need to be too easy to use if you could save the whole configurations/patches and reload them.

[very angry mobster]

Like a Karma FX or Vaz Modular for drums? Might as well just use Reaktor though.

I often find multi in/outs vst's a annoying to use. For me an internal mixer + ability to load vst fx + mixing down to a limited number of outputs (maybe 2 or 4 stereo pairs) would be perfect.

[MRT]

Gave it a try and am impressed, quick and easy to setup sounds good and has a lot of variations for adjusting the playback. Built in browser and preview is very nice.

Does this load multiple samples per pad? Multiple samples per pad, possible round robin sample switching, adjustable crossfade, basicly any setup that articulates between hits to give a more natural real drum sound.
That would be my wish

As it is it's a really nice sample player.

[aciddose]

"Might as well just use Reaktor though."

maybe, but this is over-kill and it lacks the drum-specific features you could implement in a plugin designed specifically for the purpose. like i said, might as well go all the way, otherwise the world doesnt need another of the same.

i've thought of doing this plugin multiple times in the past, but i've always wanted to finish xhip (or, get the first official release out) first.

vaz modular has the same sort of interface configuration ability i'm referring to, but again you'd want to be more specific to drums rather than just offering generic knob controls.

if somebody else doesnt make it, i will, just a question of "when" really.

[triple p]

I have guru, and personally i don't need another drum plug, as for the world....

[very angry mobster]

Guru looks really good, although I haven't tried the demo, but $249 is out of my price range. And more moderately priced stuff doesn't quite fit the bill for me.

@aciddose: It does sound like a good idea. I look forward to seeing your take on it if nobody else gets there first!

"Does this load multiple samples per pad?"
No. Mainly because I haven't created the interface components and haven't figured out how it would all work smoothly & quickly. It would be good though.

[computercontrolled]

Id like somethin like the FL studio one, FPC is called, dont remember, or th eupocoming BEAT INC. Id liek to get a pad controller and id love a drum sampler in the AKAI sampeler type

[aciddose]

"haven't figured out how it would all work smoothly & quickly"

it depends entirely upon what you're using to do it, but if possible you could go part way on what i suggested. you could make each individual drum sound a seperate "generator" with all the features. each would have it's own gui-in-a-gui to set it up, but externally would appear very simple with maybe mixer controls, so on.

you could use "set" generators which contain even more generators inside then, making it possible to load multiple samples into a single drum channel.

but, considering the effort it might be better to design it from the start with those features in mind. i'm not sure how else you could layer the samples, maybe just layer them directly - you could allow loading samples and have a 'clear' button separately. when loading another sample you could mix that into the existing sample data automatically.

[stale bread]

i know that you decided not to add an stepsequencer, but it's those tiny omissions that have alot of developers even the big ones missing the mark from the drumsampling enthusiast, as a matter of fact it's why so far another drumsampler is always needed. take battery, at least commercialy its the king right, but with no slicer its' like some track star with no legs which is to say not going to get very far with the diehard drumsamplist/samplist out there. so basicly I beg you to reconsider adding the stepsequencer.
Fxpansion are pretty much heroes at this point for not saying 'no' and giving it their best shot, for some reason there are alot of biases when it comes to drumsamplers, developers seem to be trying to figure out what they can keep out of them as opposed to synths where they're trying to figure out what they can get into them. It should be the same way for drumsamplers/slicers and nobody knows why the bias exist.
when you combine a sample slicer with a stepsequencer it just automaticly equals sampler goodness.

anyway regards and yes we need more.

[aciddose]

"trying to figure out what they can keep out of them"

object oriented / modular design still hasnt caught on even though it's been well developed for twenty years now. using the usual c-style or flat design methodologies as you add features, code complexity increases non-linearly. (exponentially, or quadratically.) due to that the difficulty associated with adding or removing features increases the same way. the only way to keep a "flat" program maintainable is to minimize the number of included features.