Main menu
You are here
Feature requests and possible bugs
Hi Rui,
I've been having a fantastic time composing with Qsynth. It is such an effective and practical tool. I have made a list of feature requests and potential bugs, can I ask you to take a look at them and tell me what you think?
- Possible bug: When a session file is saved under a different name, the individual clip names aren't renamed accordingly. Is this expected behavior?
- Feature request: A tool directed to fine tune the velocity of a group of notes at once, by applying some kind of weight over these values. It could either affect the note velocity or allow insertion of multiple events (such as volume changes) within an interval and under a given value curve. It could be a new tool or an extension to the normalization tool that is parameterized by two percentage delimiters instead of a fixed percentage value.
- Possible bug: What is the normalization percentage value based upon? Sometimes normalizing the note velocity by 75% results in a small change, sometimes in a big change, either towards a higher or a smaller value.
- Feature request: A "panic!" button that resets MIDI tracks/events, allowing to fix missed note off events, clean the MIDI event bus, and reset channel volumes so they won't be affected by a previously reproduced volume change event.
Thanks again for such a wonderful application!
Re: Feature requests and possible bugs
fantastic time composing with Qsynth
i assume you mean Qtractor :)
Possible bug: When a session file is saved under a different name, the individual clip names aren't renamed accordingly. Is this expected behavior?
yes. clip names stay as they were first time saved (eg. recorded).
Feature request: A tool directed to fine tune the velocity of a group of notes at once...
can you elaborate in more detail? does changing the velocity of a selection group (shift+drag top-edge vertically) help in any way?
Possible bug: What is the normalization percentage value based upon?
aha, even i found myself lost in that one :) well, the midi normalize tool varies event values (eg. note velocities) in direct proportion to the maximum event value--if, for instance, the highest event value do change in -10% to settle at the given parameter percentage (0-100%=0-127), than all other events will get changed same amount (-10%)--i know this parameter percentage is misleading and i guess the other option (absolute value, 0-127) is a better one to try :)
Feature request: A "panic!" button that resets MIDI tracks/events
whenever you stop playback a ALL_SOUNDS_OFF and ALL_NOTES_OFF is sent out and this is what a "panic" button would do. it just happens that not all synths respond to these with the desired behavior (shutting up all the pending voices). however, this shouldn't be an issue with synth plugins: is that your case?
cheers
does changing the velocity of
i assume you mean Qtractor :)
That's right, Qtractor, how dumb of me :P
does changing the velocity of a selection group (shift+drag top-edge vertically) help in any way?
i know this parameter percentage is misleading and i guess the other option (absolute value, 0-127) is a better one to try :)
Indeed, shift + drag top-edge works great! And now that I know about the shortcut, it is great friends with absolute value normalization :) Both of them solve almost all of my problems!
Feature request: A tool directed to fine tune the velocity of a group of notes at once...
can you elaborate in more detail?
There is still one that I wold find useful: Is there any way to select a group of notes and force their velocities to interpolate between two given values? Or to accomplish a similar result (specially in a group of constant velocity notes) by inserting a group of volume controllers (sorry, this is the right terminology and I didn't use it), also ranging between two values?
whenever you stop playback a ALL_SOUNDS_OFF and ALL_NOTES_OFF is sent out and this is what a "panic" button would do. it just happens that not all synths respond to these with the desired behavior (shutting up all the pending voices). however, this shouldn't be an issue with synth plugins: is that your case?
Yes I have this issue with my fluidsynth plugin dealing with previously triggered volume controllers, and with the MIDI input (specially with the MIDI input). I'm considering rising Jack's latency (currently at 21.3 ms), but it is not always due to xruns, so I'm a bit clueless about this one.
Thanks!
Qsynth 3.5
Hello Rui.
I would be very grateful if you would add a 'save settings' option for the interface
geometry. The default size is horrendously large!! Resizing at start up is *very* tedious
in what is otherwise an excellent piece of software.
If I am overlooking something, please feel free to correct me. :-)
Kind regards,
Rob Bridge.
Re: Qsynth 3.5
do you mean that you'll have to resize the main window each time you run qsynth? it is supposed to remember its last size and position. weird :)
maybe it's all a matter of window manager, widget style, desktop theme?
cheers
Qsynth 3.5
Yes, exactly that I'm afraid... :-S
A Qsynth.conf is created in ~/.conf/rncbc.org
From the file:-
[Geometry]
qsynthChannelsForm\x=2
qsynthChannelsForm\y=23
qsynthChannelsForm\width=401
qsynthChannelsForm\height=246
qsynthChannelsForm\visible=true
qsynthMessagesForm\x=0
qsynthMessagesForm\y=0
qsynthMessagesForm\width=328
qsynthMessagesForm\height=200
qsynthMessagesForm\visible=false
qsynthMainForm\x=155
qsynthMainForm\y=749
qsynthMainForm\width=1268
qsynthMainForm\height=249
qsynthMainForm\visible=true
I'm using GNOME2/Metacity environment.
Thanks again,
Rob
Add new comment