Maybe it's a Cubase thing, or terminology thing. By 'initilized' do you mean that the bank of 32 is set and that there is no way to load any other bank at present? In Cubase, anyway, when the drop down preset list appears, the current names of the presets in the bank don't seem to be changeable and using normal 'save' from inside GUI, I can't seem to save anything to anyplace I can find it later. I'll give it a shot with Chainer to see what happens. I'm just not sure whether when you say you'll do presets later if you mean that the functionality is all there, but you are waiting to the end to create some presets, or that both the full functionality and presets will be created later?
With presets, you just save as fxp to save a single instrument or to fxb to save all presets as a bank.
By initialized I just mean they don't have any good presets, they are all just the same. The preset system is fully functional though. I just don't want to do the presets until I'm sure that nothing major is going to change. In the beta stage, big things can change, but once v1 is out all changes have to be backward compatible so that older projects sound and behave identically and so it gets trickier to add stuff as that has to be the priority. So leaving the presets and manual til last means I only have to do those jobs once
Having said that I'm very close now, I'm doing the synth presets right now.
Sure, but a real piano continues to have the specific notes set, no matter which key or register you are playing in. I only asked for naming the C keys (not any others) as an octave referant with the transpose at zero. That way, I could quickly, for an example, set the transpose at '3' and easily compose something in D#. Of course a fantastically elegant solution ... which I'm just throwing out there as an idea, although probably unrealistically complicated to implement ... would be to have the two octave range anchors, bottom, middle and top, change the name on the 'C' key to reflect the transpose value, i.e., if the original transposed value at 'off' or zero reflects C2, C3 and C4, setting transpose to '- 3' would reset those values to A1, A2 and A3 in the 'label' on the octave marker keys of the vertical keyboard. And what the hell, while I'm fantasizing, make the range marker lines, bottom, middle and top, a little wider and impose across the grids the same shading scheme as in the 'squash to scale' keyboard. I obviously have no clue as to what is possible or how much work this would require ... but to specifically designate a note by placement would be better than the system of having a rule for which note the out of scale grid note goes to ... as I add this last phrase to avoid ending with a preposition.
I have added black note markings to the background so it is easier to see. At some point I might add intelligent naming etc... But it's not a priority right now.
Great. Anyway, I thought yesterday when I was mucking about I noticed that the CC1 and CC2 weren't copying. I'll check again.
Well wait until the next version and report back if it isn't working as I've done some work on that area.
Are you a 'lefty?'
Seriously, it is just a small point, but thanks for listening. I do appreciate your openness to feedback.
haha, no I'm not actually but I think it's that thing like in 3d shooter games where some people have to reverse the mouse up down.
GUI size is always a compromise, but right now it seems pretty 'in the ball park.' I was actually thinking of just a small bar immediately above the upper tabs with the 12 key names, two little squares or circles for each, one for mute and one for solo.
Not sure I understand, as the 12 keys are in the same sequence? I was thinking a mixer strip possibly to the right of the lists. That would expand the plugin a bit, but would also create some more space for future stuff, which I'm sure there will be plenty!
Andy, keep up the great work!
I can't wait to get v1 done now, I'm trying to get the remaining big jobs out of the way now.