From: Renato B. <re...@gm...> - 2010-02-24 11:17:27
|
I know I have a tendancy to sort of talk too much, it's just I'm enthusiastic to have found an open source guitar processing project which imho is better than commercial software (I've long used guitar rig 2 and 3). I know you are working much on this program and in no way I want to put stress on you - rakarrack for me is allready perfectly usable as is. I just like to help how I can (I'm not good enough at coding - maybe someday). Ok, just wanted to say this because recently I talked a lot on this list and I don't want you to think I dislike what you are doing or how you are doing it. Actually, I quite like it :) Having said this, I have some little remarks/observations/feature requests: 1) The list of midi-assignable parameters in the MIDI learn window it's sort sort of a mess, especially as more effects are added. Would it be possible to have it alphabetically ordered? Or even better, it would be nice to have it organized as a tree: one would see only the effect's names (Derelict, EQ etc) and then clicking on one of these would make appear under it the list of it's parameters. Clicking on it again would make the list of it's parameters disappear. This way the whole thing would be quite tidy. Also, regarding midi learn, it would be awesome if one could assign a midi cc to a parameter also by middle clicking (or similar) on the parameter (in the main window) and moving/triggering his midi controller 2) It would be nice if rakarrack were able to switch to the next or the previous effect in the bank by MIDI program changes. 3) I noticed that sometimes turning on or off an effect causes quite loud pops. Also with some effects, with some parameters, sliding them back and forth produces many clicks and pops instead of a smooth transition. I can provide more precise examples (i.e., which effect, which parameter) if needed (I'm not at home now). I realize this can be very complicated to sort out and that it can vary from case to case, depending on the type of processing that is being applied to the signal... just pointing it out. cheers, keep up the good work Renato |
From: Josep A. <ho...@te...> - 2010-02-24 13:26:15
|
Hi I really like constructive criticism .. dont worry :-) and I hope you continue in this way, any idea is welcome, another thing is if we can reach to satisfy, but we try :-) 1.- Yes .. you true ... is really hard to find parameters ... alphabetically order is easy to do :-) and I will do it as soon is possible. The tree view list, is more hard because the actual stable release FLTK 1.1.x dont has a tree widget, the next stable release of FLTK that will be called 1.3 will add this widget, I can adapt the 1.3 tree widget to the program, but will be a little bit more complex to compile rakarrack, I think is better wait to the stable FLTK 1.3 to do this changes. Open a window with the middle click for example is also easy and I will add .. :-) 2.- Rakarrack accepts program change ... add the next/previous will be easy .. I will add too :-) > 3) Yes you true .... some On/Off functions or moving some parameters cause pops ... that is more hard to fix .. need a complete revision of all the parameters ... They are some cases that will be hard to fix ... because the design of some ZynAddSubEfx effects are not RT Kernel safe, and we use some tricks to avoid the SegFault, some of this tricks cause the pops, we have already modified the design of some Zyn effects to avoid to use this tricks, but ... we need more work to do .... also they are other causes in not Zyn effects that need revision. We have in mind ... dont worry :-) Thanks ... Josep |
From: Renato <re...@gm...> - 2010-03-02 21:35:19
|
> 2.- > > Rakarrack accepts program change ... add the next/previous will be > easy .. I will add too :-) > > great :) also, regarding turning on/off effects with midi, wouldn't it be wiser to have one midi signal trigger on/off an effect, instead of having two separate values needed, one for off and one for on? It would be more intuitive I think Also, instead of mapping the position of the effect in the preset, wouldn't it be better if it mapped to the particular effect? That way I could change order of the effects in my preset, but my midi button would allways trigger phaser's on/off (for example). Also, if I like to have phaser's on/off allways on the same button, I don't have to remap my midi button for every preset, depending on where the phaser is in that particular preset. OTOH I don't see how one would prefer having the same button allways mapped to the 3rd (for example) effect in the preset - I think it's more convenient the other way Ahh also (last one i promise :) ) all this on/off thing could be added to the MIDI learn dialog - couldn't find it currently cheers Renato |
From: Josep A. <ho...@te...> - 2010-03-03 12:34:47
|
Hi > great :) also, regarding turning on/off effects with midi, wouldn't it > be wiser to have one midi signal trigger on/off an effect, > instead of having two separate values needed, one for off and one for > on? It would be more intuitive I think That's and old request :-)... and you right .. now you can change :-) see the MIDI implementation chart. I dont check it ... please .. if something fails tell me. > Ahh also (last one i promise :) ) all this on/off thing could be added > to the MIDI learn dialog - couldn't find it currently It is already ... is called Multi On/Off. Josep -- Josep Andreu <ho...@te...> |