15 Aug
2009
15 Aug
'09
10:10 p.m.
Having obtained a solid 2ms latency at 48kHz with my Multiface II, I
decided to shoot for 96. Partially I wondered if it might help with the
loss of high end I was trying to troubleshoot in the earlier post about
impedance matching -- I'm definitely losing treble somewhere. I've
verified that I can compensate for it coming back into the mixer with
EQ, but the point is, I shouldn't have to. CD's are only 44.1kHz, and
they have no lack of treble at all. (Though it does often sound grainy
or metallic to me...still, it's treble.) I can't imagine a reason that
48kHz should be dulling the top end.
Anyway, the RME should be able to do 96kHz, so whether it solves the EQ
issue or not, I wanted to try it. This is what I'm getting at just
about any setting in the Jack messages:
apparent rate = 96000
creating alsa driver ...
hw:1,0|hw:1,0|2048|2|96000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 96000Hz, period = 2048 frames (21.3 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 32bit integer
little-endian
ALSA: use 2 periods for capture
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
If I set it to 3 periods per buffer, it just changes to:
ALSA: got smaller periods 2 than 3 for capture
All of this sounds like I'm just using parameters that the driver/card
doesn't like. I'd be grateful for the information if someone who has a
Multiface that works at 96kHz could post their Jack settings. I'm sure
this must be possible, but I'm apparently just not asking for the right
settings from the interface. The machine is a 3.2GHz AMD quad, so I've
got plenty of system bandwidth, and the card is the PCI-E version.
Addendum: This is what I get for not being satisfied. You'd think I'd
quit when I got solid 48kHz, but nooooo...
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
15 Aug
15 Aug
11:19 p.m.
Nevermind... I just found in the separate program HDSPconf where you
can set the master sample clock. It was set to 48kHz. That made
settings higher than that impossible card-wide...
I didn't expect such a setting there because 99% of the parameters in
HDPSconf are for the digital i/o's and don't affect the analog ins.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
16 Aug
16 Aug
4:37 p.m.
Brent Busby <brent(a)keycorner.org> writes:
I just found in the separate program HDSPconf where
you can set the
master sample clock.
Or a command:
amixer -c $1 cset numid=11,iface=PCM,name='Sample Clock Source' 6
--
Esben Stien is b0ef@e s a
http://www. s t n m
irc://irc. b - i . e/%23contact
sip:b0ef@ e e
jid:b0ef@ n n
5:22 p.m.
On Sun, 16 Aug 2009, Esben Stien wrote:
Brent Busby <brent(a)keycorner.org> writes:
That is handy... So far about the only thing I've been doing from the
shell with recording/midi is sysex dumps. I find being able to do sysex
dumps that way to be so useful, if you wanted to be really despicable
you could even market a product based on it...
Brent's Shell Librarian, v1.0... :)
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
I just found in the separate program HDSPconf
where you can set the
master sample clock.
Or a command:
amixer -c $1 cset numid=11,iface=PCM,name='Sample Clock Source' 6 
2:07 a.m.
Brent Busby wrote:
Having obtained a solid 2ms latency at 48kHz with my
Multiface II, [..]
How did you measure the 2ms?
Flo
--
Machines can do the work, so people have time to think.
public key DA43FEF4 x-hkp://wwwkeys.eu.pgp.net
2:27 a.m.
On Sun, 16 Aug 2009, Florian Faber wrote:
Brent Busby wrote:
Well, that's what it says in QJackCtl. I remember some posts on here
awhile back about there being many ways of measuring it, but I don't
remember the jist of it. I do know that I've never gotten that low in
QJackCtl without xruns before though -- I used to get them just trying
to do 10ms at 44.1kHz.
I did find the problem with 96 by the way, and now I'm getting 2ms (as
shown by QJackCtl at that speed and no xruns.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
Having obtained a solid 2ms latency at 48kHz with
my Multiface II, [..]
How did you measure the 2ms? 
6:08 p.m.
On Sat, Aug 15, 2009 at 07:10:46PM -0500, Brent Busby wrote:
Having obtained a solid 2ms latency at 48kHz with my
Multiface II, I
decided to shoot for 96. Partially I wondered if it might help with the
loss of high end I was trying to troubleshoot in the earlier post about
impedance matching -- I'm definitely losing treble somewhere. I've
verified that I can compensate for it coming back into the mixer with
EQ, but the point is, I shouldn't have to. CD's are only 44.1kHz, and
they have no lack of treble at all. (Though it does often sound grainy
or metallic to me...still, it's treble.) I can't imagine a reason that
48kHz should be dulling the top end.
It shouldn't, certainly not if you are using RME gear.
Try to find out where this happens. Next step is to
measure it, that could provide a hint as to how & why.
Ciao,
--
FA
Io lo dico sempre: l'Italia รจ troppo stretta e lunga.
7:19 p.m.
On Sun, 16 Aug 2009, Fons Adriaensen wrote:
On Sat, Aug 15, 2009 at 07:10:46PM -0500, Brent Busby
wrote:
It stopped happening when I figured out how to record at 96kHz, but it
still disturbs me that I don't know why. I don't mind recording at 96
though.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
Having obtained a solid 2ms latency at 48kHz with
my Multiface II, I
decided to shoot for 96. Partially I wondered if it might help with the
loss of high end I was trying to troubleshoot in the earlier post about
impedance matching -- I'm definitely losing treble somewhere. I've
verified that I can compensate for it coming back into the mixer with
EQ, but the point is, I shouldn't have to. CD's are only 44.1kHz, and
they have no lack of treble at all. (Though it does often sound grainy
or metallic to me...still, it's treble.) I can't imagine a reason that
48kHz should be dulling the top end.
It shouldn't, certainly not if you are using RME gear.
Try to find out where this happens. Next step is to
measure it, that could provide a hint as to how & why.
5624
days inactive
5625
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Brent Busby -
Esben Stien -
Florian Faber -
Fons Adriaensen