2 Aug
2014
2 Aug
'14
2:02 a.m.
Well, I have the s/pdif output of my
USBDualTubePre microphone preamp plugged
into the s/pdif input of my M-Audio 2496,
though I have yet to be able to record
any sound.
I am using Audacity.
I have used Audacity successfully in the past
to record though the analog inputs of the
M-Audio 2496 (to digitize sound from cassettes
and vinyl) but Audacity's VU meters just
don't register anything from the microphone
going to the USBDualTubePre preamp to the
M-Audio 2496's s/pdif input.
Does anyone have any suggestions?
I imagine I need to configure something
with one of the mixers, I have available?:
alsamixer
alsamixergui
envy24control (Envy24 Control Utility)
xfce4-mixer
Thank you for your help.
P.S. I am trying to only do a mono recording and so
I have my microphone plugged into the right channel
of the preamp.
2 Aug
2 Aug
3:38 a.m.
On Fri, 1 Aug 2014, Ivan K wrote:
Well, I have the s/pdif output of my
USBDualTubePre microphone preamp plugged
into the s/pdif input of my M-Audio 2496,
though I have yet to be able to record
any sound.
I am using Audacity.
ok.
I have used Audacity successfully in the past
to record though the analog inputs of the
M-Audio 2496 (to digitize sound from cassettes
and vinyl) but Audacity's VU meters just
don't register anything from the microphone
going to the USBDualTubePre preamp to the
M-Audio 2496's s/pdif input.
:)
The s/pdif inputs are 9 and 10 normally (on the ice1712). Audacity will
only record those if you record 10 tracks at a time. You can then split
them into single tracks and then delete unused tracks... The mixer will
not let you change this. If you are using pavucontrol, you can try
setting the device to s/pdif only in the configuration tab... I have the
devices turned off in pluse on my system so I can't check, I run pulse
into jack all the time. Anyway look in the configuation tab for your
device.
Or you can start Jackd first and then set audacity to talk to jack instead
of alsa or pulse. You can use qjackctl to connect audacity to channel 9
for recording. To see levels hit pause and record... infact you will have
to do this before you connect ports with qjackctl.
This is why I would use pulse bridged to jackd so I can connect pulse to
the right ports ahead of time. Then if audacity is using pulse it will
"just work" (for me anyway).
--
Len Ovens
www.ovenwerks.net
4:27 a.m.
Len Ovens <len(a)ovenwerks.net> writes:
The s/pdif inputs are 9 and 10 normally (on the ice1712).
Damn good information to have. Where is that sort
of information documented?
Audacity will
only record those if you record 10 tracks at a time. [...]
Or you can start Jackd first and then set audacity to
talk to
jack instead of alsa or pulse. You can use qjackctl to connect
audacity to channel 9 for recording. To see levels hit pause
and record... infact you will have to do this before you
connect ports with qjackctl.
This seems most promising to me.
I have audacity started up and in "pause/record mode".
I have qjackctl started up.
But I don't really know where to go from here. I have
hit the qjackctl "Connect" button, and see both the
"Audio" and "Alsa" tab. Perhaps you direct me where to
go next or direct me to some documentation?
Thank you for your pointers!
This is why I would use pulse bridged to jackd so I
can
connect pulse to the right ports ahead of time. Then if
audacity is using pulse it will "just work" (for me anyway).
7:02 a.m.
On Fri, 1 Aug 2014, Ivan K wrote:
Audacity uses the portaudio library to connect to Jackd.. so in the
qjackctl connections window and the audio tab you should see PortAudio on
the right side. Connect system/capture_9 to PortAudio/in_* (the * is a
number that changes every time you hit record) and you should see the left
meter showing audio. You may wish to disconnect whatever audacity auto
connects first. The only documentation to look for portaudio is in the
audacity setup screen where you set up jack it says:
Using: PortAudio V19 bla bla bla
If all you want to do is record, mhWaveEdit does play nicer with jack.
You can set up which ports it connects to by default. The ports stay put
from application start to finish. I don't know how the editing features
are compared to Audacity though.
--
Len Ovens
www.ovenwerks.net
Len Ovens <len(a)ovenwerks.net> writes:
Not really. But the ice1712 is the same chip used for the delta1010 which
has 8 analog and one s/pdif pair. I just guessed... and kept trying inputs
till I found it. I also have the USBDualTubePre and had to find out with
my Delta66... I use inputs 1,2,3,4,9,10 ...
The s/pdif inputs are 9 and 10 normally (on the ice1712).
Damn good information to have. Where is that sort
of information documented? Or you can
start Jackd first and then set audacity to talk to
jack instead of alsa or pulse. You can use qjackctl to connect
audacity to channel 9 for recording. To see levels hit pause
and record... infact you will have to do this before you
connect ports with qjackctl.
This seems most promising to me.
I have audacity started up and in "pause/record mode".
I have qjackctl started up.
But I don't really know where to go from here. I have
hit the qjackctl "Connect" button, and see both the
"Audio" and "Alsa" tab. Perhaps you direct me where to
go next or direct me to some documentation? 
9:01 a.m.
On 08/01/2014 06:58 PM, Len Ovens wrote:
On Fri, 1 Aug 2014, Ivan K wrote:
Audacity uses the portaudio library to connect to Jackd.. so in the
qjackctl connections window and the audio tab you should see PortAudio
on the right side. Connect system/capture_9 to PortAudio/in_* (the * is
a number that changes every time you hit record) and you should see the
left meter showing audio. You may wish to disconnect whatever audacity
auto connects first. The only documentation to look for portaudio is in
the audacity setup screen where you set up jack it says:
Using: PortAudio V19 bla bla bla
My experience with recording via Audacity using JACK is that the
PortAudio connection only appears in JACK while Audacity is actually
using it (playing or recording). So I guess you start recording in
Audacity, pause it, tweak the connections in JACK, then continue recording.
I record using a USB card that has only 2 inputs, so I've never had to
tweak the connections JACK provides.
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
Len Ovens <len(a)ovenwerks.net> writes:
Not really. But the ice1712 is the same chip used for the delta1010
which has 8 analog and one s/pdif pair. I just guessed... and kept
trying inputs till I found it. I also have the USBDualTubePre and had to
find out with my Delta66... I use inputs 1,2,3,4,9,10 ...
The s/pdif inputs are 9 and 10 normally (on the ice1712).
Damn good information to have. Where is that sort
of information documented? Or you
can start Jackd first and then set audacity to talk to
jack instead of alsa or pulse. You can use qjackctl to connect
audacity to channel 9 for recording. To see levels hit pause
and record... infact you will have to do this before you
connect ports with qjackctl.
This seems most promising to me.
I have audacity started up and in "pause/record mode".
I have qjackctl started up.
But I don't really know where to go from here. I have
hit the qjackctl "Connect" button, and see both the
"Audio" and "Alsa" tab. Perhaps you direct me where to
go next or direct me to some documentation?
10:55 p.m.
Thanks to everyone whom responded.
Len Ovens <len(a)ovenwerks.net> writes:
Audacity uses the portaudio library to connect to Jackd.. so in the
qjackctl connections window and the audio tab you should see PortAudio on
the right side.
and
"David Jones" <gnome(a)hawaii.rr.com> writes:
My experience with recording via Audacity using JACK is that the
PortAudio connection only appears in JACK while Audacity is actually
using it (playing or recording). So I guess you start recording in
Audacity, pause it, tweak the connections in JACK, then continue recording.
Well, no matter if Audacity is recording or playing,
all I see in qjackctl, [Connect], "Audio" tab is:
== == Readable Clients/
== == Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/
== == Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
I see don't see a mention of audacity or portaudio.
Also, does "system" refer to my M-Audio card or
the integrated audio on the motherboard?
If system does refer to my M-Audio card, I don't
see anything in the under Readable Clients/Output Ports
that distinguishes between the s/pdif input and the
ADC input.
On the other hand, when I run mhWaveEdit, as suggested by
Mr. Ovens, I do see the word "mhwe" listed both in
the Readable Clients/Output Ports and Writable Clients/Input Ports.
At this point, I can continue to work with mhWaveEdit
as audacity appears to be problematic.
----
So running mhWaveEdit, I still cannot create any audio
files with actual sound, or see mhWaveEdit's VU meters
show any volume.
So, does "system" in the connect window of qjackctl
refer to my M-Audio card?
Thank you for your suggestions!
3 Aug
3 Aug
12:13 a.m.
On 08/02/2014 10:55 AM, Ivan K wrote:
Thanks to everyone whom responded.
Len Ovens <len(a)ovenwerks.net> writes:
Hmmm, just on off-chance ... you do have Audacity set to use JACK?
Sorry, maybe not being very helpful here.
Audacity uses the portaudio library to connect to Jackd.. so in the
qjackctl connections window and the audio tab you should see PortAudio on
the right side.
and
"David Jones" <gnome(a)hawaii.rr.com> writes:
My experience with recording via Audacity using JACK is that the
PortAudio connection only appears in JACK while Audacity is actually
using it (playing or recording). So I guess you start recording in
Audacity, pause it, tweak the connections in JACK, then continue recording.
Well, no matter if Audacity is recording or playing,
all I see in qjackctl, [Connect], "Audio" tab is:
== == Readable Clients/
== == Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/
== == Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
I see don't see a mention of audacity or portaudio. Also, does "system" refer to my M-Audio card
or
the integrated audio on the motherboard?
I believe that JACK's "system" refers to the audio card you've set JACK
to use.
If system does refer to my M-Audio card, I don't
see anything in the under Readable Clients/Output Ports
that distinguishes between the s/pdif input and the
ADC input.
Didn't someone else in this thread already post about that? That SPDIF
was 7 & 8?
On the other hand, when I run mhWaveEdit, as suggested
by
Mr. Ovens, I do see the word "mhwe" listed both in
the Readable Clients/Output Ports and Writable Clients/Input Ports.
A lot of audio programs are smarter about working with JACK than Audacity.
At this point, I can continue to work with mhWaveEdit
as audacity appears to be problematic.
----
So running mhWaveEdit, I still cannot create any audio
files with actual sound, or see mhWaveEdit's VU meters
show any volume.
So, does "system" in the connect window of qjackctl
refer to my M-Audio card?
Thank you for your suggestions!
Sorry, I've run out of clues. On my simple setup here, I started JACK,
started Audacity, set Audacity to use JACK (it defaults to ALSA on my
laptop); hit pause, then record, then unpaused. A PortAudio connection
appeared in JACK's writable ports window. It was already connected to my
in ports. I paused recording in Audacity and checked JACK; connection
still there. When I hit Stop button in Audacity, the PortAudio
connection disappeared from JACK.
I have jackdmp (JACK2) 1.9.10, Audacity 2.0.5.
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
12:49 a.m.
New subject: [Bulk] Re: Record from M-Audio 2496 S/PDIF input
On Sat, 2014-08-02 at 12:13 -1000, david wrote:
Sorry, I've run out of clues.
The order to start the applications is very important.
First the OP needs to start jackd, e.g. by QjackCtl.
When jackd is running, the OP needs to start Audacity.
By Audacity's select box "Jack Audio Connector", not "ALSA" has to
be
selected.
After pushing Pause and Record,the PortAudio input ports are visible.
alsamixer, envy24control or mudita24 is needed to rout the S/PDIF
signal. I remember that once a blind user had issues to get it working
for his Envy24 card, when using alsamixer, but using a GUI there
shouldn't be an issue.
I searched old mails to find the answer how the alsamixer issue was
solved ...
[rocketmouse@archlinux ~]$ top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
23101 rocketm+ 20 0 3165168 363776 74424 S 120.7 9.6 15:36.66 evolution
... opening a mail in Evolution's search folder might take a few hours. I'm not
kidding.
1:10 a.m.
New subject: [Bulk] Re: Record from M-Audio 2496 S/PDIF input
On Sun, 2014-08-03 at 00:49 +0200, Ralf Mardorf wrote:
... opening a mail in Evolution's search folder
might take a few
hours. I'm not kidding.
Here are the results:
http://lists.linuxaudio.org/pipermail/linux-audio-user/2012-December/088655…
http://lists.linuxaudio.org/pipermail/linux-audio-user/2012-December/088656…
http://lists.linuxaudio.org/pipermail/linux-audio-user/2012-December/088657…
http://lists.linuxaudio.org/pipermail/linux-audio-user/2012-December/088658…
Hth,
Ralf
8:44 a.m.
On Sat, 2 Aug 2014, Ivan K wrote:
Thanks to everyone whom responded.
We try....
== == Readable Clients/
== == Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/
== == Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
This does not look 2496 ish, it looks audiophile 192 ish... from my
understanding and concidering I have not used either one of them. This to
say that there are two m-audio audiophile models... that use two different
kernel modules for two different chips inside.
The difference is that the 2496 uses the ice1712 which should show as 12
inputs and 10 outputs... same as the delta44 delta66 (I have this) and
delta1010. The 192 has an ice1724 which is 4 in and 8 out... but the
analog in and the digital in are different devices. The analog in would be
hw:0,0 and the s/pdif would be hw:0,1.
This page:
http://linuxmusicians.com/viewtopic.php?f=27&t=8898
seems to verify that much.
So, after you have jack running try running:
zita-a2j -d hw:0,1 -r 48000 -p 256 -n2 -c 2
This assumes your USBDualTubePre is set to 48000... and you have set Jack
that way too :) Change the 48000 to 44100 otherwise. This would show up in
qjackctl as zita-a2j capture_1 and 2 (does here)
if you don't have zita-a2j (you should download it) you can test with
alsa_in instead.
alsa_in -j spdif -d hw:0,1 -r 48000 -p 256 -n 2 -c 2
This would show up in qjackctl as spdif capture_1 and 2
The -r value should be the same as your analog i/o and your pre s/pdiff
rate (rear panel switch)
The -p value (with zita-a2j) can be one step less than you have jack set
(I may get corrected :)
and -n should be the same.
--
Len Ovens
www.ovenwerks.net
11:22 a.m.
New subject: [Bulk] Re: Record from M-Audio 2496 S/PDIF input
On Sat, 2014-08-02 at 23:40 -0700, Len Ovens wrote:
This assumes your USBDualTubePre is set to 48000...
and you have set
Jack that way too
and don't forget to chose 'S/PDIF in', _not_ 48000 for the sound card's
clock.
11:55 a.m.
On Sat, Aug 02, 2014 at 11:40:48PM -0700, Len Ovens wrote:
So, after you have jack running try running:
zita-a2j -d hw:0,1 -r 48000 -p 256 -n2 -c 2
This assumes your USBDualTubePre is set to 48000...
and you have set
Jack that way too :) Change the 48000 to 44100 otherwise. This would
show up in qjackctl as zita-a2j capture_1 and 2 (does here)
Just use
zita-a2j -j spdif -d hw:0,1 -r 48000 -p 256 -n2 -c 2
to get correct port names.
if you don't have zita-a2j (you should download
it) you can test
with alsa_in instead.
Wouldn't recommend that, and zita-a2j is included as an internal
client with recent Jack1 releases anyway. It can even be started
in one command together with Jack.
The -p value (with zita-a2j) can be one step less than
you have jack
set (I may get corrected :) and -n should be the same.
There are no such restrictions.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
5:28 p.m.
On Sun, 3 Aug 2014, Fons Adriaensen wrote:
On Sat, Aug 02, 2014 at 11:40:48PM -0700, Len Ovens
wrote:
zita-a2j -j spdif -d hw:0,1 -r 48000 -p 256 -n2 -c 2
to get correct port names.
I must have an older version, my man page doesn't show -j, good to know it
is there, thank you.
Wouldn't recommend that, and zita-a2j is included
as an internal
client with recent Jack1 releases anyway. It can even be started
in one command together with Jack.
Hmm, I use 1.9.10. In the past I have used the features of jackdbus for a
lot of things, but I am now probably to the point I don't have to. Jack is
started at session start with jack_control but could be just command line.
I don't use zita-a2j that much (testing only) as the old ensoniq card
while quite quiet is "only" 16 bit and uses 1/8 plugs. I normally use no
more than 2 inputs anyway. However, the debian/ubuntu repos seem to make
it as hard as possible to install jack1... or rather hard to remove jack2
or run jack1 along side. However, starting zita-a2j on the side is not a
problem.
--
Len Ovens
www.ovenwerks.net
6:07 p.m.
On Sun, Aug 03, 2014 at 08:24:57AM -0700, Len Ovens wrote:
On Sun, 3 Aug 2014, Fons Adriaensen wrote:
It's shown by the command line help, but indeed not in the manpages.
Will be fixed.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
On Sat, Aug 02, 2014 at 11:40:48PM -0700, Len
Ovens wrote:
zita-a2j -j spdif -d hw:0,1 -r 48000 -p 256 -n2 -c 2
to get correct port names.
I must have an older version, my man page doesn't show -j, good to
know it is there, thank you.
4 Aug
4 Aug
8:57 p.m.
Thanks again to everyone who is helping me out.
I try to work with and digest everything that
people suggest which is why I do not respond
right away.
Let me fill you in on a few problems I have
had over the last day or more.
First: when I was trying to start Jack up
with qjackctl, I would get a window which read:
# [Window]
# Error - JACK Audio Connection Kit:
#
# Could not connect to JACK server as client.
# - Overall operation failed.
# - Unable to connect to server.
# Please check the messages window for more info.
The message window had a lot of text, some of
which was:
# Messages:
# 20:19:52.805 Patchbay deactivated.
# 20:19:52.817 Statistics reset.
# 20:19:52.870 ALSA connection change.
# Cannot connect to server socket err = No such file or directory
After using GOOGLE to try to locate an answer to this
question, I came across this solutions:
delete {$HOME}/.jackdrc
delete {$HOME}/.config/rncbc.org/QjackCtl.conf
make the user that you are trying to run Jack under
a member of the "audio" group. (I am running Fedora 20
if that matters, maybe other distributions do not have
an "audio" group.
With that, Jack was able to start again.
HOWEVER ... I have lost some of my M-Audio cards
functionality.
qjackctl's [Connect] window under the Audio tab
USE TO DISPLAY THIS:
On Sat, 2 Aug 2014, Ivan K wrote:
== == Readable Clients/Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
BUT NOW, since my problem with starting JACK up,
the "Writable Clients/Input Ports" box is blank.
I lost my eight "writeable ports" and I am presently
working to get them back. Any tips would be
appreciated.
Incidentally, what do these eight playback connections
represent. The "M-Audio Audiophile 2496" only has
three outputs, left and right analog and S/PDIF.
And so do these playbacks 1 through 8 refer to some
sort of mixing channels in the firmware of the
Audiophile 2497?
To repeat, though, I have lost these playbacks 1 through
eight in the Writable Clients/Input Ports box. How can
I get them back?
Responding directly to others,
Len Ovens <len(a)ovenwerks.net> writes:
This does not look 2496 ish, it looks audiophile 192
ish...
This to say that there are two m-audio audiophile models... that use
two different kernel modules for two different chips inside.
Oh my card is definitely the "M-Audio Audiophile 2496". It says
so on the box. And the commands aplay and arecord list the device as:
card 0: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi [ICE1712 multi]
Subdevices: 1/1
Subdevice #0: subdevice #0
[...]
zita-a2j -d hw:0,1 -r 48000 -p 256 -n2 -c 2
alsa_in -j spdif -d hw:0,1 -r 48000 -p 256 -n 2 -c 2
I will report on my success and failure with the
zita-a2j/alsa_in commands soon.
Ralf Mardorf <ralf.mardorf(a)rocketmail.com> writes:
and don't forget to chose 'S/PDIF in', _not_ 48000 for the sound card's
clock.
I will not loose that bit of information.
Thank you all for your continued help.
10:03 p.m.
On Mon, 4 Aug 2014, Ivan K wrote:
make the user that you are trying to run Jack under
a member of the "audio" group. (I am running Fedora 20
if that matters, maybe other distributions do not have
an "audio" group.
Ubuntu does not add users to audio by default as some other distros do, so
it has to be done manually :P Hopefully this will change.
HOWEVER ... I have lost some of my M-Audio cards
functionality.
qjackctl's [Connect] window under the Audio tab
USE TO DISPLAY THIS:
On Sat, 2 Aug 2014, Ivan K wrote:
Have you tried to see if your s/pdif in works now? That looks like it
"may" be hw:0,1 jack has been started with.
In qjackctl, setup screen, there is an "Interface:" box in the top(ish)
right corner, beside that there is a ">". If you click on that, there
should be a list of devices. Maybe give us a list of those. (full text)
== == Readable Clients/Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
BUT NOW, since my problem with starting JACK up,
the "Writable Clients/Input Ports" box is blank.
I lost my eight "writeable ports" and I am presently
working to get them back. Any tips would be
appreciated. Incidentally, what do these eight playback
connections
represent. The "M-Audio Audiophile 2496" only has
three outputs, left and right analog and S/PDIF.
And so do these playbacks 1 through 8 refer to some
sort of mixing channels in the firmware of the
Audiophile 2497?
The ice1712 has 8 analog outputs and 8 analog inputs as well as s/pdif in
and out (and some other stuff) It does not monitor the outputs to see if a
DAC is connected to them and so they all show up. The card manufacture
chooses how much of this they will use. It seems there is enough
communication from the ADCs that the chip can tell what is connected or
not... or maybe the kernel module is more picky with the 2496 than with
the d66. M-Audio may have added some glue logic that keeps this card from
working just like the other delta series cards. It may be interesting to
see if forcing the kernel module to see this as a delta1010 will give you
full access. (including things that are not there.)
Normally with the ice1712 there should be 12 inputs (8 analog, s/pdif pair
9 and 10 plus the multi-mixer outputs 11 and 12) and 10 outputs (8 analog
and one s/pdif pair) In the case of the 2496, inputs 1,2,9,10 and outputs
1,2,9,10 should be valid. However, it looks like the kernel driver is not
set up that way. Channels 11 and 12 (inputs) should also be available as
the output of the internal mixer and all outputs (10 of them) can be used
as inputs to this intenal monitor mixer. (this sounds nice, but the
reality is I have never used it :) as I have an external mixer already)
try adding a line to /etc/modprob.d/alsa-base.conf (this assumes a debian
based distro... Ubuntu for example)
options snd_ice1712 delta1010
(or delta1010lt)
(from:
https://www.kernel.org/doc/Documentation/sound/alsa/ALSA-Configuration.txt
)
See if jack then shows 12/10 i/o and your s/pdif audio shows up on input 9
or 10.
Oh my card is definitely the "M-Audio Audiophile 2496". It says
so on the box. And the commands aplay and arecord list the device as:
card 0: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi [ICE1712 multi]
Subdevices: 1/1
Subdevice #0: subdevice #0
Then the below should not work:
> [...]
> zita-a2j -d hw:0,1 -r 48000 -p 256 -n2 -c 2
> alsa_in -j spdif -d hw:0,1 -r 48000 -p 256 -n 2 -c 2
--
Len Ovens
www.ovenwerks.net
5 Aug
5 Aug
12:34 a.m.
I wrote:
HOWEVER ... I have lost some of my M-Audio cards
functionality.
qjackctl's [Connect] window under the Audio tab
USE TO DISPLAY THIS:
On Sat, 2 Aug 2014, Ivan K wrote:
I think I figured out why this is so. Jack is currently configured
to look for "card 0" as displayed in /proc/asound/cards
Yesterday, "card 0" was my M-Audio 2496, and eight
"Writable Clients/Input Ports" were visible in qjackctl.
Today, "card 0" is my webcam and my M-Audio 2496
is "card 1". My webcam has no playback capability
(just a microphone) and so qjackctl now displays no
"Writable Clients/Input Ports".
I imagine I changed the numbers on my audio devices
with all of the fiddling I have been doing.
Questions:
How do I change the audio devices back, so my
M-Audio card is "card 0".
Or
How to I get jack/qjackctl to look for "card 1"
rather than "card 0"?
Thank you all again for your help and patience.
P.S. I still am interested in the answer to this as well:
== == Readable Clients/Output Ports
== == - system
== == capture_1
== == capture_2
on the right, and then on the left, I see:
== == Writable Clients/Input Ports
== == - system
== == playback_1
== == playback_2
== == playback_3
== == playback_4
== == playback_5
== == playback_6
== == playback_7
== == playback_8
BUT NOW, since my problem with starting JACK up,
the "Writable Clients/Input Ports" box is blank.
I lost my eight "writeable ports" and I am presently
working to get them back. Any tips would be
appreciated. Incidentally, what do these eight playback
connections
represent. The "M-Audio Audiophile 2496" only has
three outputs, left and right analog and S/PDIF.
And so do these playbacks 1 through 8 refer to some
sort of mixing channels in the firmware of the
Audiophile 2497?
Thanks.
1:33 a.m.
On 05/08/14 08:34, Ivan K wrote:
I think I figured out why this is so. Jack is
currently configured
to look for "card 0" as displayed in /proc/asound/cards
Yesterday, "card 0" was my M-Audio 2496, and eight
"Writable Clients/Input Ports" were visible in qjackctl.
Today, "card 0" is my webcam and my M-Audio 2496
is "card 1". My webcam has no playback capability
(just a microphone) and so qjackctl now displays no
"Writable Clients/Input Ports".
I imagine I changed the numbers on my audio devices
with all of the fiddling I have been doing.
Questions:
How do I change the audio devices back, so my
M-Audio card is "card 0".
Put this in your alsa conf file in /etc/modprobe.d/ :
options snd slots=snd_ice1712,snd_hda_intel
options snd_ice1712 index=0
options snd_hda_intel index=1
This is from my system, obviously replace snd_hda_intel with the driver
name of your webcam. You could also blacklist the webcam snd driver.
Check with aplay -l
Cheers
Roger
9:12 a.m.
New subject: [Bulk] Re: Record from M-Audio 2496 S/PDIF input
On Tue, 2014-08-05 at 09:33 +1000, Roger wrote:
options snd slots=snd_ice1712,snd_hda_intel
options snd_ice1712 index=0
options snd_hda_intel index=1
Hi Roger,
you're using the slot method, so the index lines aren't needed.
[rocketmouse@archlinux ~]$ cat /etc/modprobe.d/alsa-base.conf
# ALSA module ordering
options snd slots=snd_hdspm,snd_ice1712,snd_ice1712
[rocketmouse@archlinux ~]$
I'm aware that some distros provide a default alsa-base.conf with many
lines that are unneeded. For a DAW it can't harm to tidy up audio
setting.
Regards,
Ralf
12:38 p.m.
New subject: [Bulk] Re: Record from M-Audio 2496 S/PDIF input
On 05/08/14 17:10, Ralf Mardorf wrote:
On Tue, 2014-08-05 at 09:33 +1000, Roger wrote:
Thanks. It
works anyway. :) I will edit.
options snd slots=snd_ice1712,snd_hda_intel
options snd_ice1712 index=0
options snd_hda_intel index=1
Hi Roger,
you're using the slot method, so the index lines aren't needed.
3:52 a.m.
I have successfully recorded from my
USBDualTubePre microphone preamp using the S/PDIF
into my M-Audio 2496. I used mhWaveEdit.
The issue was that qjackctl was displaying the
Readable Clients/Output Ports and
Writable Clients/Input Ports of my _motherboard_
audio, not my M-Audio 2496.
A recent off list reply coached me to set the
correct device in Qjackctl with "Setup | Interface | >".
Early on, Len Ovens informed me that the S/PDIF
inputs of the ice1712 are 9 and 10.
And of course, using envy24control to set "Master clock"
to s/pdif rather than a sample rate was required as well.
And so, thank you to all who responded!
6 Aug
6 Aug
1:44 a.m.
On 4 August 2014 at 18:52, Ivan K <ivan_521521(a)yahoo.com> wrote:
I have successfully recorded from my
USBDualTubePre microphone preamp using the S/PDIF
into my M-Audio 2496. I used mhWaveEdit.
The issue was that qjackctl was displaying the
Readable Clients/Output Ports and
Writable Clients/Input Ports of my _motherboard_
audio, not my M-Audio 2496.
A recent off list reply coached me to set the
correct device in Qjackctl with "Setup | Interface | >".
Early on, Len Ovens informed me that the S/PDIF
inputs of the ice1712 are 9 and 10.
And of course, using envy24control to set "Master clock"
to s/pdif rather than a sample rate was required as well.
And so, thank you to all who responded!
Thanks for the discussion and your conclusions. I'm about to try
to transfer the content of an audio DAT tape using a Panasonic
DAT deck via the S/PDIF i/o on my Delta 1010 audio interface.
You all may have just saved me some headaches. FWIW, I'll be
attempting this using Ardour, which plays quite nicely with
JACK[12], and plays quite nicely on my system in general. But,
S/PDIF is new to me.
Cheerio....
--
Kevin
3 Aug
3 Aug
5:37 p.m.
On Sun, 3 Aug 2014, Fons Adriaensen wrote:
Wouldn't recommend that, and zita-a2j is included
as an internal
client with recent Jack1 releases anyway. It can even be started
I had heard that a2jmidid was going to get rolled in as well. It seems
these things are not noted on:
http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
--
Len Ovens
www.ovenwerks.net
3561
days inactive
3564
days old
linux-audio-user@lists.linuxaudio.org
22 comments
7 participants
participants (7)
-
david -
Fons Adriaensen -
Ivan K -
Kevin Cosgrove -
Len Ovens -
Ralf Mardorf -
Roger