I suggest the cursor/curve inspector to allow user to change OSC message period. The « setMessage » API is great and I just now made use of it, but I would find it very useful under many conditions to do it directly from the inspector.

I may want to (or need to) do thinning of OSC packets and then, if necessary, perform smoothing in my downstream app. Sometimes a high level of cursor tracking-precision is not needed, and one can do smoothing in the server (in Max, for example, where I would use the [line] or [line~] object to generate a smooth ramp).

Cheers,
–Bob

I appreciate the mouse wheel zoom in/zoom out of the entire score.

I would love also to have mouse wheel resize of individual objects (or any number of objects selected at the moment). Thanks for listening :–)

Cheers,
–Bob

I wish to preface this by saying the 0.8 release is a giant step beyond the previous 0.6 versions and Iannix now achieves much of its original promise.

However, there is one aspect of the current infrastructure that just seems to me architecturally misguided: the project management / file navigation, update, and-save mechanism. Integrating project management functions into an Inspector is a worthy goal, but this implementation is incomplete and fragmented. One of the deficiencies that must be overcome is the forced and awkward interaction between the File Inspector and the File Menu. The mechanism invites disaster in several ways. Just one example: Invoke « New script », and whatever Current Project score is selected in the Inspector (and one is always selected) will go dirty and a subsequent save will wipe out previous work. One must always ensure a new score or duplicate score has been created and selected before loading anything else or invoking a script. Simply loading an example can make a previous score go dirty.

There is much precedent out there and I suggest that this part of the Iannix infrastructure be modeled after a more conventional and intuitive design.

Thanks for hearing my blather,
–Bob

I’ll put this under BUGS, but you may wish to consider it a current feature :–)

Objects appear in the Object List Inspector multiple times. If objects in different scores have the same ID, they can appear simultaneously and appear to be duplicated. If your Current Project lists more than one score and you are not working on the first one that comes up when you load Iannix, you may have objects from multiple scores in the list. Furthermore, for every additional score that you choose to work with during a particular Iannix session, those scores’ objects will be added to the list and they will remain there. This can result in three, four, or more objects in the list with the same ID (if, for example, you’ve cloned several scores from a common prototype). If you’ve worked on more, those will be added to the list as well. This will also result in not seeing an object light up when you click it in the list because it is actually located in a score you’re not currently viewing.

I strongly feel objects only for the current active score should appear in the list (same for groups, of course). Simply browsing through your scores will add objects to the list for any of the other scores and they will stay there until closing the current session of IanniX.

Cheers,
–Bob

In the Object-selection Inspector, clicking group name should select all of that group’s member-objects (similar to clicking on an Object Name from the list).

Cheers,
–Bob

Clever. I’ve noticed that a new posting wakes up the spam-bots. It’s not from message-on-reply because they jump in on a new thread with their auto spam.

No cheer,
–Bob