On Mon, Feb 24, 2014 at 07:53:58PM -0500, Paul Davis wrote:
On Mon, Feb 24, 2014 at 6:19 PM, Fons Adriaensen f...@linuxaudio.orgwrote:
The problem I guess is due to the way the HW related params
are set:
1. Allocate a hw_params struct
2. Fill in the params using set_*** functions
On Tue, Feb 25, 2014 at 6:48 AM, Fons Adriaensen f...@linuxaudio.orgwrote:
Wrong, at least for snd_hdspm (and I did my homework before posting this
message and the previous one).
Things appear to have changed (for the better) then, since back in the days
of legend.
Jörn Nettingsmeier wrote:
I'm trying to get my Gigaport HD+ to run at 48000kHz. The specs say it is
capable of 8ch @ 44k1/16, 6ch at 44k1/24 and 48k/24.
Please show the output of lsusb -v for this device.
When I try to start it at 48k, it comes up ok but ends up running at 44k1. It
shows 8
On 02/25/2014 12:54 PM, Paul Davis wrote:
On Tue, Feb 25, 2014 at 6:48 AM, Fons Adriaensen f...@linuxaudio.org
mailto:f...@linuxaudio.org wrote:
Wrong, at least for snd_hdspm (and I did my homework before posting this
message and the previous one).
Things appear to have changed
On Tue, Feb 25, 2014 at 8:25 AM, Jörn Nettingsmeier
netti...@stackingdwarves.net wrote:
If the maximum channel count is always fixed by the hardware, what is the
point of the corresponding jackd option? As I said, I don't remember if
ever doing something other than throwing the cannot set
On Tue, Feb 25, 2014 at 08:39:14AM -0500, Paul Davis wrote:
On Tue, Feb 25, 2014 at 8:25 AM, Jörn Nettingsmeier
netti...@stackingdwarves.net wrote:
If the maximum channel count is always fixed by the hardware, what is the
point of the corresponding jackd option? As I said, I don't
Fons Adriaensen wrote:
On Tue, Feb 25, 2014 at 08:39:14AM -0500, Paul Davis wrote:
imagine you have an N (where N 16) channel device but only channels 1-4
are connected. the channel count option stops you from having to look at
N-4 useless channels on the device all the time.
AFAIK, when
On Tue, Feb 25, 2014 at 02:25:25PM +0100, Jörn Nettingsmeier wrote:
If the maximum channel count is always fixed by the hardware, what
is the point of the corresponding jackd option? As I said, I don't
remember if ever doing something other than throwing the cannot set
channel count error...
On Tue, Feb 25, 2014 at 10:09:16AM -0500, Paul Davis wrote:
the option doesn't alter what the JACK backend sees from ALSA (or
wherever). it changes which channels get represented by JACK ports.
Wrong. If things were as you claim, this should just work:
(on a 64-ch card)
fons@hypatia:~ jackd
On Tue, Feb 25, 2014 at 10:52 AM, Fons Adriaensen f...@linuxaudio.orgwrote:
On Tue, Feb 25, 2014 at 10:09:16AM -0500, Paul Davis wrote:
the option doesn't alter what the JACK backend sees from ALSA (or
wherever). it changes which channels get represented by JACK ports.
Wrong. If things
hi clemens, thanks for your help.
On 02/25/2014 02:23 PM, Clemens Ladisch wrote:
Jörn Nettingsmeier wrote:
I'm trying to get my Gigaport HD+ to run at 48000kHz. The specs say it is
capable of 8ch @ 44k1/16, 6ch at 44k1/24 and 48k/24.
Please show the output of lsusb -v for this device.
see
On Tue, Feb 25, 2014 at 5:08 PM, Jörn Nettingsmeier
netti...@stackingdwarves.net wrote:
btw, the card claims 24bit support (whatever that is worth in this price
range), but i find i cannot specify 24bit int, only S16_*, float, and S32_*
- am i misunderstanding this option, or does it not
Hi *!
I'm trying to get my Gigaport HD+ to run at 48000kHz. The specs say it
is capable of 8ch @ 44k1/16, 6ch at 44k1/24 and 48k/24.
When I try to start it at 48k, it comes up ok but ends up running at
44k1. It shows 8 channels, so that's expected.
Now, how do I tell it to use only 6, so
On Mon, Feb 24, 2014 at 6:19 PM, Fons Adriaensen f...@linuxaudio.orgwrote:
The problem I guess is due to the way the HW related params
are set:
1. Allocate a hw_params struct
2. Fill in the params using set_*** functions
3. Submit the hw_params struct.
In step 2, the set_*** functions
14 matches
Mail list logo
