[PlanetCCRMA] running jack on fedora

[matthew shanley]

fernando's suggestion to change the frame peroid to 512 fixed the main 
problem. setting force 16bit does help it not try the other settings 
first and makes it start up faster. thanks to both of you for your help.

matt



Karsten Wiese wrote:
> Am Freitag, 23. Januar 2004 21:37 schrieb Fernando Pablo Lopez-Lezcano:
> 
>>>i have been running the plannet on a redhat 9 computer for awhile now,
>>>and i just installed it on a new fedora installation on an ibm t22
>>>laptop. when i run qjackctl and try to start jack, i get messages in the
>>>window saying: "starting" then "started" but then just afted that
>>>"stopped" and a box pops up saying "could not connect to JACK server as
>>>client". opening the messages box i see:
>>>loading driver ..
>>>apparent rate = 44100
>>>creating alsa driver ...
>>>hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|rt|32bit control device hw:0
>>>configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
>>>Couldn't open hw:0 for 32bit samples trying 24bit instead
>>>Couldn't open hw:0 for 24bit samples trying 16bit instead
>>>ALSA: cannot set period size to 1024 frames for capture
>>>ALSA: cannot configure capture channel
>>
>>This sound card does not like periods of 1024 frames...
>>Try changing that to a different number, for example 512
>>
>>
>>>cannot load driver module alsa
>>>15:20:26.235 JACK was stopped successfully.
>>>15:20:27.910 Could not connect to JACK server as client.
>>>
>>>alsaplayer and xmms both play fine and my qjackctl settings are
>>>identical to the ones that work fine on my rh9 machine.
>>
>>But probably the soundcard is different and can't work with the same
>>jack parameters as the old one.
> 
> 
> does "Force 16bit" in qjackctl's setup make any difference?
> 
> Karsten
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>