I'm the (un?)lucky owner of an M-Audio Fast Track Pro USB audio
interface and I'm having some serious problems getting this device to
record audio reliably under Linux.
I've been using arecord and occasionally Audacity for all of my
testing. My problem is this: Recording a take works about 80% of the
time. In the remaining ~20% of cases, the captured audio is extremely
loud with severe digital distortion. Once this problem shows up, it
persists for any subsequent takes. The only way I've found to make
the problem go away, at least temporarily, is to power-cycle the Fast
Track Pro.
I considered the possibility that this particular device might be
defective, but it seems to work wonderfully under Windows.
I'm calling out to other Fast Track Pro users in the hope that someone
out there has encountered the same problem and better still, found a
solution.
Any suggestions at all would be greatly appreciated!
.lewis
Hello everyone,
I've posted a question about using the Zoom H5 as an audio interface
to sound.stackexchange.com, see
https://sound.stackexchange.com/q/44364/24842
I've found scattered references to H5 working on Linux. One is on this
mailing list -
http://linux-audio.4202.n7.nabble.com/checking-passive-input-frequencies-on…
But I can't get it to work.
I've posted the contents of that question below. Any help would be
appreciated. Please copy me on any reply. Thank you.
Regards, Faheem Mitha
###################################################################
I just purchased the Zoom H5 sound recorder, with the intention of
using it both as a sound recorder, and also as a audio interface under
Linux. My OS is Debian stable. Currently 9/stretch.
Unfortunately, there is hardly any documentation on how to use it
under Linux. I managed, by looking at the manual, to get my OS (Debian
stable/stretch) to at least recognize the device.
However, right now I'm not sure how to go with either Stereo or 4
Track. In both cases I end up with a screen that shows `USB AUDIO I/F
XY5`, along with L, R, 1, and 2. But I see no motion in any of these.
However, right now I'm not sure how to go with either `Stereo` or
`Multitrack`. In both cases, it is clear that I need to go with the
`Bus Powered` option. As mentioned in various places, if I choose
`Stereo`, Debian thinks it is the H4, but with `Multitrack` correctly
identifies it as the H5.
In both cases I end up with a screen that shows `USB AUDIO I/F`, along
with L, R, 1, and 2. But I see no motion in any of these.
`lsusb` is showing the following:
Bus 006 Device 006: ID 1686:01c5 ZOOM Corporation
The syslog is printing a bunch of complaints:
May 28 21:38:01 orwell kernel: [1505026.660071] usb 11-1: Warning! Unlikely big volume range (=4294967295), cval->res is probably wrong.
May 28 21:38:01 orwell kernel: [1505026.660076] usb 11-1: [2] FU [Mic Capture Volume] ch = 2, val = 1/0/1
May 28 21:38:01 orwell mtp-probe: checking bus 11, device 3: "/sys/devices/pci0000:00/0000:00:13.0/usb11/11-1"
May 28 21:38:01 orwell mtp-probe: bus: 11, device: 3 was not an MTP device
May 28 21:38:01 orwell systemd-udevd[28202]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.
May 28 21:38:02 orwell pulseaudio[6363]: [pulseaudio] alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 0 to -1 which makes no sense.
The H5 is also showing up in `pavucontrol`. The configuration section
offers various options. I'm not sure which one to choose - the options
are:
Analog Stereo Output + Multichannel Input
Analog Stereo Output
Digital Stereo (IEC958) Output + Multichannel Input
Digital Stereo (IEC958) Output
Multichannel Input
Off
If I choose `Multichannel Input`, then it shows up in `pavucontrol`
under `Input Devices`, but the volume level (or whatever it is called)
for that device stays at zero. As it happens, I have another, regular
mic plugged into my main (PCI Express) sound card (Xonar DX) right
now, and that is responding fine. Also, I assume a working mic makes
some noise, and the mics on the H5 are completely silemt.
I'm sure I'm missing something obvious, so help would be much
appreciated, bearing in mind my knowledge of things sound-related is
very limited.
And finally, can someone exactly what an "audio interface" means,
exactly?
V 1.5.8 - Kingfisher
Bright flash of colour.
The most significant changes in this release are all usability ones.
At the request of one user (and agreement of several others) some of the
microtonal settings are now MIDI-learnable, and appropriately highlighted.
The CLI can now open and close instances, and switch between them.
There is a new 'Solo' type 'TwoWay' this works in a similar way to 'Loop', but
(apart from zero) values less than 64 step from right to left, instead of the
other way round. The highlighting is also a bit better. Both 'Loop' and
'TwoWay' also have debounce protection of approximately 60mS.
The CLI can now clear a part's instrument. A fairly obvious option that somehow
got missed.
In the Banks windows Instruments can now be swapped between banks and bank
roots. Banks can also be swapped between roots. This is an extension using
exactly the same controls as those already available for in-bank swaps.
The latest feature is autoloading instances. With this enabled, any instance
that was open when the main one is closed will be re-opened on the next run. If
these instances were set for starting with their default state, then all those
settings will be performed. Therefore, a very comprehensive and detailed
session can be started with a single command!
A lot of the documentation supplied with Yoshimi has been updated, including
the Advanced User Manual.
Yoshimi source code is available from either:
https://sourceforge.net/projects/yoshimi Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi(a)freelists.org
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hello, All--
I have been unsuccessful getting Yoshimi to work in Ubuntu Studio 18.04.
This has been the case for the Yoshimi included in the distro, 1.5.7, and
1.5.8. When starting, the GUI and splash screen appear. The splash screen
does not disappear, and the GUI is completely frozen. the command,
"killall yoshimi," fails to eliminate the GUI.
i'm sorry i can't be of more help, as no error messages have been
generated. If anybody else has had this experience, i'd be happy to hear
any solutions you've learned.
Thank you!
tom
Hi, Will!
>Did you compile youself?
>If so, did you check the dependency list?
Yes, i did compile from source, and yes, all dependencies were in place. i
just rechecked them to be sure. All dependencies are in place.
>Are you running with jack or alsa?
>What window manager are you using?
i've been running with jack. i'm going to reboot and try with alsa. Since
it's ubuntu studio, i'm pretty sure the window manager is xfce.
i recompiled, with better success. Yoshimi did connect to jack. However,
the GUI is still frozen. i'll reboot and try alsa.
Dear Linux Audio Conference friends!
We need your support for this year's conference [1].
Currently we are still looking for volunteers to help us with the
following:
* Session Chairs - https://dudle.inf.tu-dresden.de/LAC18_Session/
* Stage Hands - https://dudle.inf.tu-dresden.de/LAC18_Stage/
* Camera/ Videomixer operators -
https://dudle.inf.tu-dresden.de/LAC18_Video/
If you would like to support us, please provide your mail address and
availability
to the corresponding dudle instance.
A short introduction/workshop for the different kinds of tasks will be
held on Thursday,
20180607 16:00 (CEST) (two hours before the Welcome Speech).
Your e-mail address will only be used by us to communicate with you
through a dedicated
mailing list, that will be disposed of after the conference.
The organizing team would like to thank you in advance, if you can spent
some time
to help us with running the conference.
See you in Berlin!
[1] https://lac.linuxaudio.org/2018
--
Linux Audio Conference team