chuck uses sampling rate of 44100 with jack instead of 48000

Bug #114161 reported by taw
2
Affects Status Importance Assigned to Milestone
chuck (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: chuck

The manual says ChucK should use 48000 sampling rate with jack,
or autodetect the correct sampling rate.
       --srateN Set sampling rate (default to 48000 for jack, auto detected otherwise).

But it seems to be using 44100 by default with jack.

$ jackd -d alsa
jackd 0.102.20
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
[Switch to another terminal]
$ chuck /usr/share/doc/chuck/examples/stk/clarinet2.ck
[chuck]: (via rtaudio): no devices found for given stream parameters:
... RtApiJack: the requested sample rate (44100) is different than the JACK server rate (48000).

[chuck]: cannot initialize audio device (try using --silent/-s)
$ chuck --srate48000 /usr/share/doc/chuck/examples/stk/clarinet2.ck
---
reed stiffness: 96.822256
noise gain: 58.311473
vibrato freq: 54.560872
vibrato gain: 30.220581
breath pressure: 91.044858
^C
[chuck]: cleaning up...
$

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta?

Changed in chuck:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in chuck:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.