Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Official wish list
I opened a new page in the wiki, because there were same discussions in the forum about new features for the firmware.
You can find the page here:
http://wiki.sonic-potions.com/index.php/Official_Wishlist
I hope this is ok.
Please feel free to add new entries or correct it.
You can find the page here:
http://wiki.sonic-potions.com/index.php/Official_Wishlist
I hope this is ok.
Please feel free to add new entries or correct it.
Comments
Thnx!!
do you need a different subscription or password?
Thnx!!!
And i wich that the "note" option for each voice becomes a global setting and not individual for each kit.
Other drum sound as Modulation Source.
global note setting: I scratched my head over this for a while. Does this mean something like "move track note assignments from kit data to global data"? This is sensible and much easier to put into my custom FW now that kits are versioned. I'll get around to it at some point.
solo voice: This is sensible. in the custom FW, for PERF mode, shift-voice is select (useful for quickly rotating multiple tracks). I am planning shift double-tap voice for solo/unsolo. I've got it working *kinda*, it will get there
the rest in this section (PERF/PATGEN) are sensible and I'd like to add eventually. There are varying levels of trickery involved with each.
step copy: is in the custom FW now
letter inputs: this is er... 'different' in the custom FW. my concern was mainly that in stock, there were too many letters stacked on one knob and I always ended up needing the encoder to select the right one. I'm taking comments on advantages/disadvantages of what I have in place.
voice stuff: I don't really mess with voice stuff much except...
envelopes: I'm not too keen on implementing a standard ADSR envelope on either the amp or mod, but I would like a way of sustaining a voice indefinitely. What I would like to try is putting 'direction' and 'position' parameters for envelopes. You could then use sequencer automation to reverse the envelopes or hop to different positions.
I'd also split 'slope' into 'attack slope' and 'decay slope', which ought to cover the 'slope type' request, and is easier to extrapolate from current kits, since one is always the inverse of the other (ie, the current slope control varies att/dec from log/exp -> lin/lin -> exp/log).
click:
rather than messing with the parameters that get displayed, i'd like to split offset and 'snappy' out of the transient menu completely. The new menu would look something like:
page 1: OFS(offset, 0-127); SNP(snap envelope amount); SDK(snap envelope decay); SCA(track scale)
page 2: WAV; VOL; FRQ (old transient parameters)
And my personal requests:
- looping samples
- when a sample is loaded to OSC, 'offset' controls sample start position.
The channel note setting is shown as semitones from c-0? and step mode note setting is shown as a note. Thus, when having a pattern and the channel note setting is not an octave, the notes are wrong in step mode.
So what about having only a global note, which can also be used to transpose a pattern?
The different notes are then selected in the step mode for each channel, which are updated depending on which global note was selected.
What do you think? Make this sense?
I erased this entries:
OSC:
DRUM 1-3:
* Change frequency range to 0-127 HZ, zero mutes the oscillator
Because I think these ponits are more a restriction than a progress.
And you can mute the oscillator by using the volume option in the Mix section or am I wrong?
What do you think?
This setting is saved as a kit parameter for some reason, which could be a huge pain in the ass for some users because if you wanted to change something in your MIDI setup, you'd have to go re-save all your kits to have them work properly.
This parameter also exists as a modulation destination for steps - I don't mean the 'note' setting that sits next to the velocity parameter in the step data, but if you go into the assignable modulation destinations, there is a 'note' setting there as well. In my opinion,there isn't much point in modulating what MIDI note the voice responds to, unless I'm missing some incredibly esoteric sequencing method.
As far as I know, the only things that do affect the pitch of the voiceare the OSC settings and the step 'note' (the one next to velocity),where the step note may or may not correspond to the actual pitch produced - it should really be labelled something like 'semitone offset' and defaults to D#5 only because that's the centre value of the 0-127 range.
Anyway, my motivation isn't to mess with what pitches are produced when, I'm just talking about changing how MIDI settings are applied.
Transpose would be a good option to add eventually, but I won't be trying it any time soon. I think the best way to get that working would be some kind of macro that operates on the pattern data for a voice to +/- all the step 'note' (semitone offset) settings (again, the one next to velocity (volume) ).
I think the transpose tool is already there, because you can transpose a pattern by changing the semitones in the OSC section, but it is not really obvious which note the LXR is playing (you have to add the semitones to the step 'note', right?). Wouldn't it make more sense to change the parameters here? What I mean is that the note setting in the OSC menu is shown as a note (not semitones) and the note for each step in the step mode is shown as semitones (not notes).
In a sceond step the semitones in the step mode could be replaced by notes again showing the resulting note calculated by the OSC note setting and the number of semitones choosen for each step. I see! But you could also just change the global midi note? Why it is sensible to copy the track midi note to the global midi note?
This wouldn't change the sound of any kits, it would just solve some headaches for people who trigger the LXR from an external sequencer.
This would be great!
Try it out & let me know what you think!
I will check it out at the weekend.
Is the transpose amount saved with the kits or only when record is used?
Pretty easy to implement, and wouldn't change the sound of existing kits.