priority, etc.
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
priority, etc.
by Elliott Chapin
::
Rate this Message:
Dear Fernando et al. -
Until recent updates I was having a fine time with CCRMA rt/Jack under FC11. There seem to be various problems now, and I am not sure whether they come from the rt kernel, CCRMA Jack or alsa; or that they are just out of sync. As a starter, the other day F. questioned priority of 89 but did not give a good lower number. The most interesting Qjackctl error message was "cannot connect to server socket". Comments, troubleshooting tips, please. Perhaps I'm looking at known issues which are being worked on ... Thx, E.C. -- http://clients.teksavvy.com/~echapin _______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
|
|
|
Re: priority, etc.
by S C Rigler
::
Rate this Message:
I'm still on FC10, but I noticed that at some point a "pulse-rt" group had been added to my system that was allowed to run at a priority "20". You might want to make sure you aren't a part of any groups that might conflict with your ability to run with a priority 89.
On Sun, 2009-10-04 at 12:46 -0400, Elliott Chapin wrote: Dear Fernando et al. - Until recent updates I was having a fine time with CCRMA rt/Jack under FC11. There seem to be various problems now, and I am not sure whether they come from the rt kernel, CCRMA Jack or alsa; or that they are just out of sync. As a starter, the other day F. questioned priority of 89 but did not give a good lower number. The most interesting Qjackctl error message was "cannot connect to server socket". Comments, troubleshooting tips, please. Perhaps I'm looking at known issues which are being worked on ... Thx, E.C.
_______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
|
|
|
Re: priority, etc.
by Fernando Lopez-Lezcano
::
Rate this Message:
On Sun, 2009-10-04 at 12:46 -0400, Elliott Chapin wrote:
> Dear Fernando et al. - > > Until recent updates I was having a fine time with CCRMA rt/Jack under > FC11. Do you know/remember which version were you running when all was fine? > There seem to be various problems now, and I am not sure whether > they come from the rt kernel, CCRMA Jack or alsa; or that they are just > out of sync. It'd be good to have a list of problems. This is too generic a description to try to answer. > As a starter, the other day F. questioned priority of 89 but did not > give a good lower number. I think a good number would be 72. For some reason I found that the default priority of the latest Planet CCRMA jack builds is incorrect (too low at 10), I have to look at that - something is not being patched correctly. If you are running the rt kernel, check the output of: /etc/rc.d/init.d/rtirq status That will give you the priorities of all rt tasks at the kernel level. You want Jack to run just below the priority of the interrupt threads for the soundcard or soundcards, and above the rest of the interrupts. That's the ideal situation (sometimes impossible when the soundcard shares the interrupt with something else). > The most interesting Qjackctl error message was "cannot connect to > server socket". It'd be nice to take a look at the complete error messages. > Comments, troubleshooting tips, please. Perhaps I'm looking at known > issues which are being worked on ... -- Fernando _______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
|
|
|
|
|
|
|
Re: priority, etc.
by Elliott Chapin
::
Rate this Message:
> > Well, qjackctl does not do anything but call jackd. Most likely the > options in qjackctl are not set correctly and/or differ from what you > were doing in the command line. > > What are the options you are currently using in qjackctl? For starters > make sure "Interface" is pointing to "hw:0" and not just "default". I knew about that one. > > "Frames/Period", I'd start with 1024 (and if it works try with lower > values if you need lower latency), and "Periods/Buffer" possibly 2 or 3. > Do _not_ set "Input Channels" or "Output Channels". ^^^^^^^^^^^^^^ Thanks! For "Priority" use > 72 as outlined before. "Realtime" should already be set. Recent qjacktl offers jackd-realtime (server); that doesn't work - jackd does with "realtime" checked. "Start jack server on application startup" (misc) seems to be essential. There's an (ignorable) error warning - just go ahead and load plugins. In the middle of clearing things up I tried (failed) to find and destroy all qjackctl data. Can't help wondering where they are hidden. -- http://clients.teksavvy.com/~echapin _______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
|
|
|
Re: priority, etc.
by Fernando Lopez-Lezcano
::
Rate this Message:
On Tue, 2009-10-06 at 22:26 -0400, Elliott Chapin wrote:
> > > > Well, qjackctl does not do anything but call jackd. Most likely the > > options in qjackctl are not set correctly and/or differ from what you > > were doing in the command line. > > > > What are the options you are currently using in qjackctl? For starters > > make sure "Interface" is pointing to "hw:0" and not just "default". > > I knew about that one. > > > > > "Frames/Period", I'd start with 1024 (and if it works try with lower > > values if you need lower latency), and "Periods/Buffer" possibly 2 or 3. > > Do _not_ set "Input Channels" or "Output Channels". > ^^^^^^^^^^^^^^ > Thanks! > > > For "Priority" use > > 72 as outlined before. "Realtime" should already be set. > > Recent qjacktl offers jackd-realtime (server); that doesn't work - jackd > does with "realtime" checked. "Start jack server on application startup" > (misc) seems to be essential. There's an (ignorable) error warning - > just go ahead and load plugins. > > In the middle of clearing things up I tried (failed) to find and destroy > all qjackctl data. Can't help wondering where they are hidden. I think it is: ~/.qt/qjackctlrc (or has that changed in the latest versions?) -- Fernando _______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
|
|
|
Re: priority, etc.
by Rui Nuno Capela
::
Rate this Message:
On Wed, October 7, 2009 05:06, Fernando Lopez-Lezcano wrote: > On Tue, 2009-10-06 at 22:26 -0400, Elliott Chapin wrote: >> >> In the middle of clearing things up I tried (failed) to find and >> destroy all qjackctl data. Can't help wondering where they are hidden. > > I think it is: > ~/.qt/qjackctlrc > (or has that changed in the latest versions?) > since qjackctl >= 0.3.0 that the configuration file is located on ~/.config/rncbc.org/QjackCtl.conf cheers -- rncbc aka Rui Nuno Capela rncbc@... _______________________________________________ PlanetCCRMA mailing list PlanetCCRMA@... http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma |
| Free embeddable forum powered by Nabble | Forum Help |
