your opinions: what are undesirable defaults in jjos?

hey, i'm gathering info on some default settings that i find undesirable in jjos in hopes of small changes to make the overall platform more convenient.

first: create a new program. this program's midi layout is in GENERAL MIDI specification, that goofy non-chromatic order where pad a04 is in the 80s, and the rest are scrambled all around. i find this silly and intolerable and would prefer a default of CHROMATIC PAD layout.

second: SLICE, RELEASE is automatically set to 10. this is the SLICE release, NOT the amp ADSR release. this is a destructive release that sometimes i forget to reduce to zero, so i have to rechop everything. i think by default this should be zero.

third: new program, amp ATTACK is automatically 3. i think this should be default 0, but i'm kind of conflicted because i don't trust inexperienced users to know about zero crosspoint transients and how to avoid clicks in their sliced samples.

what are some others?

Matter of preference but I'd like when you create a NDC auto program that it would be set at MONO by default.

I agree that the midi layout has to be changed.

I think amp attack needs to be 0, especially for the n00bs. Because if they are anything like me, they forget everytime then can't work out why all their drum sounds sound weak!
It seroiusly pisses me off. And since when do we have to design a machine to hold the hands of inexpirienced users? It just doesn't make sense to me.

Second.

Amp attack at 3 is non-sensical and obnoxious. I've banged my head against the wall so many times trying to find out why certain hits sound off only to realize i forgot to twirl that down to 0.

Exactly where do you turn that to 0?

in GPE's AMP ENVELOPE screen.

in case you don't already know, this is a very important concept in sound shaping:
http://en.wikipedia.org/wiki/ADSR_envelope

so important that i have a tattoo of adsr on my stomach.
the more i think about this, the more i agree that it really should be a default of zero

as many new users who would complain of the click when slicing samples = as many users who simply load drum oneshots and would unwittingly leave an unnecessary attack of 3 on their oneshots.

i despise amp attack @ 3!
and has akai ever given an explanation for the reasoning behind the odd pad # layout?

the

Scarecrow wrote:i despise amp attack @ 3!
and has akai ever given an explanation for the reasoning behind the odd pad # layout?

the pad layout is supposed to make sense when using a general midi drum-map. sometimes I'll use the mpc to trigger some percussion in my alesis qsr (which is mapped according to general midi standards) and the layout actually makes some sense that way (certain types of drum sounds are grouped together generally)... but when using the mpc strictly as a sampler it doesn't serve any real purpose.

Nym wrote:in GPE's AMP ENVELOPE screen.



so important that i have a tattoo of adsr on my stomach.

And here I was thinking I was so original. I always wanted that tatooed "love"/"hate" style on my knuckles. Add that to the list of things law school is depriving me of.

legs - a general midi program saved into your autoload would allow you to continue to use that alesis very easily. i'm stoked about the removal of the general midi program layout because it doesn't prevent folks from continuing to work exactly as you do with the alesis - it'll save the rest of us sooo many clicks...

haha the knuckles would have been dope. don't feel like you can't do it. i'd love to get something on the knucks but i'm working in an elementary school right now and i can't yet...

my next two tats are gonna be "etre et durer" on my left collarbone and the double helix on the underside of my forarm.

so i just figured something awesome out in jjos2 im not sure if it applies to jjos1 or not. It is regarding the wacky pad assignment. if you would like the program to go 35-98, you hit mode+ program
go to amp (f2) highlight any note under the note section, hit open window there is an option to assign them automaticly to 35-98 ! Im very excited about this find.

most definitely. that's what many of us have done every time we create a new program.

legs mechanical wrote:Second.

Amp attack at 3 is non-sensical and obnoxious. I've banged my head against the wall so many times trying to find out why certain hits sound off only to realize i forgot to twirl that down to 0.

i wasn't aware of this setting, so took a look at a few progs last night. with some, dropping the attack to 0 made the sounds sharper, but with others it was a no-go, creating pops in the sound. so wouldn't defaulting to 0 be just as unwelcome as 3?

rarara wrote:i wasn't aware of this setting, so took a look at a few progs last night. with some, dropping the attack to 0 made the sounds sharper, but with others it was a no-go, creating pops in the sound. so wouldn't defaulting to 0 be just as unwelcome as 3?

I think 0 would be better b/c i think most people try to trim their samples (i do at least..) so that they sound as good as possible with an instant attack. Later I'll roll back a little if I need to. 3 just seems a little arbitrary. And we are talking about a DRUM machine... and losing some of the attack of a drum hit (from a live drumming pov) doesn't make much sense.

Nym wrote:legs - a general midi program saved into your autoload would allow you to continue to use that alesis very easily

Yeah. I've got one I use all the time. An also programs that set the pads like bass guitar strings in rows (dope since i'm a better bassist than keyboardist) and one to make the qsr drum mappings match my standard self-made drum programs. There's a lot of great stuff you can do as far as pad templates for strange musicality. (there's actually a mapping system who's name eludes me now that was supposed to be an alternative to the chromatic mapping of keyboards based on a 4*4 board that creates harmony and melody in a pretty ingenious way. I gotta google that shit.)

[deleted] [irrelevant] [requesting existing features] [nader '08!]