Could someone confirm it's absolutely hopeless to write a real timeline 

interface driven by a Java external ? A clocker sending an int in my 

Java inlet, with a simple calculation inside, to redraw my cursor, takes 

30% (!!) cpu, even in outletHigh (worse without, ~ 50-60%), even if the 

drawing message is put outside (in max), so without any String 

operation... The same thing in max without Java doesn't move the cpu 

cursor *at all* (0-2%). What the hell ? Writing a timeline in *max only* ?

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

Could someone confirm it's absolutely hopeless to write a real timeline 
interface driven by a Java external ? A clocker sending an int in my 
Java inlet, with a simple calculation inside, to redraw my cursor, takes 
30% (!!) cpu, even in outletHigh (worse without, ~ 50-60%), even if the 
drawing message is put outside (in max), so without any String 
operation... The same thing in max without Java doesn't move the cpu 
cursor *at all* (0-2%). What the hell ? Writing a timeline in *max only* ?

f.e
-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


java, lcd & cpu usage