what happened to 'broken drum machine'? More MP3s

[blortblort]

I dig the "pure generator" but as a beatbox with sequencer, there IS much more to break

[Juanjo]

...if BDM should be a pure generator or a beat box with patterns

mmm... ideally both, no?

[liqih]

ok I see you want it all!, <grin>

my mummy told me: "never ask to users"

you will have a pattern sequencer, but don't complain if it's broken,

(I wonder how we could do betatesting on BDM, LOL)

[Az're-ul]

good, so I big question is:

should BDM have a sequencer or not??

making a nice sequencer is already some work, but making a "cleverly broken" one it's surely an hard task, <grin>

of course I have some ideas to run thru, but I'd love to hear your opinion
if BDM should be a pure generator or a beat box with patterns

thanks

Sorry Liqih, its fence sitting time for me. I'd probably vote for a sequencer to keep everything self contained but as always there are pro's and con's

I like built-in sequencers for the immediacy they offer, but I also like the greater control available from the host's piano roll.

A module will I presume from your side of things be easier to program but a sequencer may add a broader spectrum of erroneous behaviour.

If you go the generator route could you add a MIDI handler which would 'randomly' corrupt the incoming data?

If there isn't a built sequencer it then becomes a drum module, at least it will have the same initials

Just my 2 cents

Steve

[liqih]

A module will I presume from your side of things be easier to program but a sequencer may add a broader spectrum of erroneous behaviour.

yep, looks like we all agree on that

If you go the generator route could you add a MIDI handler which would 'randomly' corrupt the incoming data?

yes it could work

[Az're-ul]

More:

- UI errors i.e. gui controls (buttons, sliders) not always responding to mouse clicks and movements (as if they were loose), random midi/automation misfirings, etc.
This would add a layer of unpredictability to the actual handling of the instrument (of course it could be optional).

Genius! I didn't even think of the UI. You could take this a stage further by having the controls crackle as you move them and only working for half their throws, having all the LEDs go off or even having BDM stop responding completely for a time.

[ouroboros]

(I wonder how we could do betatesting on BDM, LOL)

"Hi liqih, I just got done testing the latest BDM beta. It seems to be working fine, but in FL, when I hit record, this beautiful drumline comes out, full of groove and feel with perfect transients and tunings. It's like a real drummer is here in my house with me. Also, I should let you know that all the volume levels are perfectly matched and it keeps incredible time with my host and the project I'm working on. Can you please fix it?

other than that, I like it.
sincerely,
BDM betatester"

[liqih]

More:

- UI errors i.e. gui controls (buttons, sliders) not always responding to mouse clicks and movements (as if they were loose), random midi/automation misfirings, etc.
This would add a layer of unpredictability to the actual handling of the instrument (of course it could be optional).

Genius! I didn't even think of the UI. You could take this a stage further by having the controls crackle as you move them and only working for half their throws, having all the LEDs go off or even having BDM stop responding completely for a time.

crackle maybe, but I think that an unpredictable interface could be frustrating, no?

[Juanjo]

More:

- UI errors i.e. gui controls (buttons, sliders) not always responding to mouse clicks and movements (as if they were loose), random midi/automation misfirings, etc.
This would add a layer of unpredictability to the actual handling of the instrument (of course it could be optional).

Genius! I didn't even think of the UI. You could take this a stage further by having the controls crackle as you move them and only working for half their throws, having all the LEDs go off or even having BDM stop responding completely for a time.

crackle maybe, but I think that an unpredictable interface could be frustrating, no?

Yeah, I think that a global "ui errors on/off" switch would be necessary if you end up implementing any of this (nice ideas btw azrael)... this way it would be "frustrating" only if/when the user wanted it to be i.e. for experimental real-time performances, or to look for weird inspiration...


And more:

- A "tilt" button equivalent to physically dropping or hitting the "hardware" i.e. unexpected consequences

(again, just throwing ideas around)

[ouroboros]

A dc offset parameter, maybe a crossfading thing, where you could enable a pop or click and position it from beginning to end of the hit(sample?) triggered. If you could automate it in a random way, too that would be cool.

and "tilt" is a lot better than a screwy UI!

My extra special wish list:
1. often when you program a glitch, especially a stutter, the fast repetition/ delay retrigger creates an almost "lead" like sound. If there were a way to manipulate this stutter-sound to then "play it" that would be awesome. Right now, I sequence a beat, then sequence the fx stutter, then sample it, then re-sequence the sound and crossfade between the loop I have sliced/delayed and the sampler which I can then play.
as here (mp3)
http://www.box.net/shared/33r14ggbbm
loop-dblue glitch,. the slice increasingly smaller, then played in a sampler up high.

2. If there is an internal note sequencer, not just pattern, how about a ring mod that one can sequence as well.

more smoke blowing

[runagate]

More:

- UI errors i.e. gui controls (buttons, sliders) not always responding to mouse clicks and movements (as if they were loose), random midi/automation misfirings, etc.
This would add a layer of unpredictability to the actual handling of the instrument (of course it could be optional).

Genius! I didn't even think of the UI. You could take this a stage further by having the controls crackle as you move them and only working for half their throws, having all the LEDs go off or even having BDM stop responding completely for a time.

crackle maybe, but I think that an unpredictable interface could be frustrating, no?

People might just think that they'd incurred the copy protection like on Acidome, which I still, regretably, have yet to experience. I can't believe I want to crack something that was given to me for free just to watch it die.

If you make BDM faulty like this, then people will stop stealing your software just to see the awesome copy protection cause it to die!

/off irony

[liqih]

thanks guys for all the input, keep it coming, ouroboros thanks also for the audio example,

for the time wasters <grin>, here is the first alpha:
four analogue style generators BD SD HH CP and output mangler,
no automation or chaos beaviour yet,
also no skin and no PCM (the VCOs will be mixable with PCM sounds)
the RAR includes a MIDI file to help you to find the playing notes.

http://www.dashsignature.com/upload/BDM ... ws_VST.rar

don't expect great sounds from this alpha, just smooth beeps,

(before someone would asks it in these controversial days, this plugin is coded in C++ from scratch)

...

[Jazzyspoon]

nice. Can't wait for further development on this one. very interesting concept.
Maybe you could build a broken "circuit bent" reverb or something as a companion?
Thanks for letting us in on it.

[liqih]

thanks Jazzyspoon,


for all here showing how I would map the sounds to keys, note that these are not presets on the keys, they are relative variations of the sound settings

good?

[liqih]

and here is the update alpha 2 with an energyXT project which gives me much fun, <grin>

if you have energyXT 1.4 load it (you'd need also RubyTube or another compressor enhancer for a better sound, not absolutely neccessary)

http://dashsignature.com/upload/BDM_0.0 ... ws_VST.rar

just play the loop and try the controls,

of course you may try the DLL in another host but you have to make your presets.