|
From: Pascal B. <pa...@ba...> - 2015-04-13 08:58:52
|
Thanks Roald for this feedback. > > i-score appears to me as a nice tool but currently it's still a bit "crude ». You’re right, as we mention on the download page, it’s a prototype. We expect v. 0.3 for which the development team is hard at work to be more functional. Most of the features you are requesting are on the backlog (some are even already implemented) > > Some suggestions to improve it: > > 1. Add a zoom setting for the timeline axis. have you tried cmd + or - ? > 2. Besides the creation of automation boxes by clic+drag, add the > possibility to create boxes using a menu (with right-clic for instance) > which would allow one to set start and end times or start time and > duration. > 3. Display start/end/duration times (and not noly duration) in each > automation box. As all events are relative to the previous constraints/relations (this is more obvious in 0.3 than in 0.2), I’m not certain of the validity of handling dates (which makes almost no sense once a trigger point has been introduced…) but we can give it a thought… I understand you’re using i-score in a static way (no interactive triggers), don’t you N > Also, it would help to have the current position of the mouse > pointer on the time axis displayed. good idea ! > 4. Add a "quantize" setting when positioning/creating boxes, with a free > setting expressed in seconds or milliseconds. good idea ! > 5. Edition of the curves as lists of numbers could be helpful too (with > a paste function to import data from other programs). this is a planned feature of 0.3 Thanks again for your feedback, please feel free to give us more. Best, Pascal |