[mod-users] A review of a kind for the current state of the mod
spamatica at gmail.com
Thu Mar 3 16:10:17 UTC 2016
2016-03-02 16:19 GMT+01:00 Robert Jonsson <spamatica at gmail.com>:
> 2016-03-02 12:37 GMT+01:00 Filipe Coelho <falktx at gmail.com>:
>> On 01.03.2016 21:11, Robert Jonsson wrote:
>>> Hi all,
>> Hi there!
>> Soundwise I can't complain about the hardware, seems very good.
>>> I see however there are quite a few xruns, which of course needs to be
>>> addressed. I only ran it with the GUI open, possibly that increases the
>>> load. I managed to login via ssh and I can see jackd taking a lot of CPU.
>>> I'm sure I'm threading in already trampled territory but I'll just voice my
>>> thoughts anyway. ;)
>> Having the GUI open doesn't affect the load much.
>> All the GUI objects are rendered on the web-browser, and their loading is
>> usually only done once.
>> I didn't check what connections were done through jack but since all
>>> plugins probably are instantiated in the mod host, maybe it would be better
>>> to connect the hardware directly to the mod host rather than using jack as
>>> an intermediate? For the future maybe.
>> In our current setup we're using JACK2 for its multi-core graph
>> processing and async mode.
>> Note that mod-host is running as an internal jack client, so there's no
>> expensive context switching between processes going on.
>> Using JACK allows us to simplify a lot of things.
>> Why reinvent the wheel? ;)
> Indeed, it makes sense to have it as an internal client. That explains the
> high cpu-load for jackd too.
> Just left to find the corner cases that break RT :) ... a few clicks ;)
Just remembered that I was gonna mention this, not sure it's applicable but
better safe than sorry.
For me the biggest culprit to achieving good RT is definitely frequency
scaling. Don't know how this platform is configured but if it allows
scaling try to turn it off.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users