No, but I have a new item in my todo 🙂

Yes, we have a big problem with ID’s and automatic attribution of ID. It is fixed in 0.8.21 version, but there are still display bugs (in lists — it’s not really bugs, it’s just messy information) when opening multiple scores.

Thanks for the reply. Already downloaded the new beta and it works great.

Im finsihing up my M4L device and soon I’ll provide the examples to you which I think you will find VERY interesting mainly because I have found ways to sync Iannix to Live (evwen though Iannix doesnt feature a BPM based timeline).

To be sincere, what Im trying to achieve goes away from the purpose of this software I suppose as it is targeted to more « defined » created music and not ayto-generated triggers.

The examples will showcase what Im saying but in the meantime my problem is this: my script creates 8 circles and 8 cursors and sets them into groups. I was hoping to provide to the end user a « Cyclic Sequencer » where the end user will add the triggers (by clicking his mouse) where he pleases without getting in the hassle of using scripts. This gives me the problem that the triggers do not belong to any group so I cannot target them from M4L.
I even thought of creating an M4L « add created triggers to groups » button but still I cannot target « current » objects via osc (only via script – or am I wrong?)
The only solution would be to provide ready-made scripts-scores (with ready made triggers grouped) which is not what I want.

Also, as a feature request, it would be perfect if we could define (via script) default messages for triggers, cursors and curves, in other words everytime the end user adds a trigger (via mouse-click not script), it will have a script-designed default message for example
« registerMessage triggers 1, trigger_value cursor_id »

Anyway, all the above sound pointless unless you actually get to see what Im trying to achieve, and that will possibly be during the weekend! So, talk to you soon.

I would like to see this feature, but IMHO, this is a potential can of worms and I recommend deferring this feature to a later point in the development of Iannix.

I believe doing process performance-profiling portably within a multi-platform program like Iannix is one of those esoteric design issues that carries subtle gotchas. Native Instruments seem to have gotten it right in their dual-platform (Mac/Win) Reaktor. But because Max/MSP in their CPU utilization display only counts DSP loading and no control-rate functions, it is often in profound disagreement with the OS’es own profile tool (I’ve seen 200%-500% differences).

I think all of these variables are design factors in performance monitoring by a single process:

• number of CPU cores
• 32bit / 64bit
• whether high res counters are available, or whether you must depend on the default software tick-counter (some flavors of a given O/S only implement a subset of the API’s counters — think Win32 and the so-called « multimedia counter »).
• the risk of your own measurements influencing the results (i.e., one’s own process loading the CPU)
• access rights to performance counters on behalf of the process (e.g., as much as possible, I work under a low-privilege user logon, so programmatic privilege-elevation could be needed)
• platform portability (Qt implements timers, but I don’t think Qt addresses process-profiling in their API — wouldn’t it be fabulous if I’m wrong!)

Despite all the buzzwords, I’m not a sysinternals guru and in this case I might be more like Chicken Little. So please take all of this with a pinch of salt.

Cheers,
–Bob

Here’s a screenshot: