i suspect it's more a "drawing the ui" thing
oh that could be it, I remember some performance issues with macOS's GUI colorspace conversion at some point, maybe it's more costly with the gradient for some reason
at worst if you don't need the ui during playback maybe you can run in command-line mode
e.g. once you have your score:
./score yourfile.score --autoplay --no-guihere with an OSC gradient running at a 5ms interval it does not even register, it shows me 0.0% of CPU lol
(versus ~8-10% when the UI is shown but it's linux, not macos, graphics stack is different, yada yada)
(but before that... Sleep 😅 good night !)
the version I am using is the official 3.0.10 on a mbp 16.1 i9 with 32gb ram on macos 12.3.1 - maybe I can make a debug build and monitor it with xcode, that can maybe tell where the cpu cycles go.
have a good sleep and thanks for all your help :)
I think that you can just do it with the official release, normally there should be at least the function names which is good enough to have a good idea of what goes wrong in this case, especially in the headless case
Oh, I did not know this tool before, super handy! I made a report for about 10s while running, so w/o the setup and headless, only a color automation, its 50mb big. How should I get this to you? Would prefer to not have this public in the internet
6.48 Mc 75.4% 6.40 Mc void std::1::thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ossia::executor::executor()::'lambda'()> >(void)
Seems to be where the CPU cycles go
Seems to be where the CPU cycles go
Ok, if I disable parallel execution the cpu usage goes down to 2%
parallel basically busy-waits on threads to make sure they stay scheduled
but I could maybe implement the exponential algorithm there: https://timur.audio/using-locks-in-real-time-audio-processing-safely
if you don't have 15 long VST chains running in different tracks parallel executionis likely not worth it
Wow, just made a test run and now barely hit 200% cpu with OF, SC and score running :) runs really smooth now :)
Hej there, highest praise for the project! Great piece of software! :D
Got a little problem starting to use Javascript. I'm doing the following in 3.0.11: Create OSC Device default settings, create a child of float OSC:/test, dragging a Javascript process onto the first Node or Interval. Now dragging over the OSC:/test onto the ValueInlet in the GUI, the Inputs-Address Textfield gets populated correctly with OSC:/test. In the default JS code I move the line console.log(in1.value); above the if clause. In Message Log getting Debug: undefined (:8). - in1 show as JS:ValueInlet(ox1d...) (:8).
Got a little problem starting to use Javascript. I'm doing the following in 3.0.11: Create OSC Device default settings, create a child of float OSC:/test, dragging a Javascript process onto the first Node or Interval. Now dragging over the OSC:/test onto the ValueInlet in the GUI, the Inputs-Address Textfield gets populated correctly with OSC:/test. In the default JS code I move the line console.log(in1.value); above the if clause. In Message Log getting Debug: undefined (:8). - in1 show as JS:ValueInlet(ox1d...) (:8).
Hej @jcelerier and @thibaudk thanks for the swift help! Here the most basic reproduction
the if statement id here to filter out undefined values
that is why you get a lot of these when you move the console log out of it
So just keep everything inside the if statement and you should be good to go ?
Maybe I am missing something in your question ?
the second score I posted it simply the basic umodified JS with OSC:/test as input and OSC:/test2 as output, but the output is never generated, so OSC:/test must be unidentified or nor handled correctly as an input
just tested, I can confirm
now let me test with a ControlInlet instead
Yes Maybe you want to Change ValueInlet for ControlInlet
changing to ControlInlet (and re-setting it's port to listen to OSC:/test) you will see a continuous output
I gess ControlInlet is not referenced in the documentation https://ossia.io/score-docs/processes/javascript.html
And it may be a little confusing to see it appear as a slider