Re: [Bluemusic-users] assigning widgets values to i-rate variables
Brought to you by:
kunstmusik
From: Atte A. J. <att...@gm...> - 2008-10-29 08:06:52
|
Steven Yi wrote: > Glad that works! I'm going to update documentation will issue a > release tonight. Great! This means that we can start working on new versions of stuff in blueShare. Should I start making notes about which things work, and which doesn't? I'm not sure that all authors of the affected stuff in blueShare are active, should we (I) hotfix their code and submit API versions of the instruments/fx in question? > As for running with the API, I don't think you can up the priority as > it is in the same process as blue. I may be able to try increasing the > priority in Java, but I am not sure how much of a difference that will > make. I just tried setting the render thread to max priority, but I > don't know if it makes a difference. It still won't be like upping > the priority of the process using sched. (The code is now in CVS and > will be in the release build I do tonight.) I tried cvs, and it doesn't make any difference. > I'm not sure of any other thing I can do to increase the priority. On > Linux, you might be able to increase the priority of the java process > that runs blue as a whole, though I don't know how the system will > react to that. I was able to make blue run glitch free with the API with -B256 -b45 () by doing "sudo chrt -f -p 80 17783", where 17783 is the pid of the java process. This is good news, as it means there must be a way to get things running smoothly. However in itself it is not a viable solution since the process that needs this seems to be spawn when rendering. This means I have to start the render, look at the output of htop, and issue the command with the correct pid. I attached a screenshot of htop after the changed priority. So I think we need to make changes to the way blue spawns the thread, doing something like this automatically. BTW: I see two java processes taking up cpu when rendering with blue, one seems to be the main blue thread, since it keeps it's pid throughout a blue session, the other one I suspect is the one spawned when rendering. I also tried changing the pid of the main thread, but that doesn't seem to be inherited by the render thread. There are also quite alot of other threads looking similar (in the screenshot I count 9 in all), but taking up much less cpu. Could you elaborate a bit on why all these threads are there? Where in the code is the spawning of the render thread happening? I'd like to take a look at the code and fool around with it a bit, maybe I can come up with something... -- Atte http://atte.dk http://modlys.dk |