Sir, I spent 8 dollars on that soundcard, and you called it "garbage".
How dare you? It even has 3D stereo. Yes, you read that right. 3. D.
In reality though, the 3d stereo claims are just for marketing. The
stereo image sounds normal.
On 12/14/20 4:42 PM, David Kastrup wrote:
> Brandon Hale <bthaleproductions(a)gmail.com> writes:
>
>> One last thing you can try, if the headphone jack still doesn't work
>> after a fresh install, is getting a cheap usb audio soundcard. It will
>> have less noise and give you a reliable dac in the future on
>> Linux. Here
>> <https://www.amazon.com/gp/product/B00IRVQ0F8/ref=ppx_yo_dt_b_search_asin_ti…>
>> is one that I have personally used that has saved my life a number of
>> times.
> I'd be wary about the "3D stereo" thing. My own "garbage for the win"
> sound card looks like this:
>
>
> Yes, those are 3.5mm connectors. I think the line input is dead by now
> (but mic inputs can be misused well enough) and the soundcard mixer is
> such a mess that I haven't gotten the headphone output to work under
> Windows (but abusing the front 2.1 output by using a headphone in it
> works reasonably). The latency is suboptimal and I think it cuts off
> around 15kHz. Backside has an optical S/PDIF input and an output.
>
> Another option worth considering are handheld recorders: those tend to
> have a "soundcard mode" as well. Unfortunately, with my Zoom H2
> recorder I haven't found a way to use recording (built-in mics or
> external) and playback (headphone or line output) at the same time
> without the input unconditionally also appearing at the output.
> Undesirable for the application I was considering it for (Jamulus).
>
> Possibly newer models fare better in that regard.
>
On Fri, 11 Dec 2020 17:43:42 +0100 Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
>
> Hello David,
>
> > After much experimentation with settings, I have now got the sound
> > from Qtractor back to the headphones. The distortion is still
> > there. I would be tempted to think it might be a fault with my
> > Raspberry Pi, but the sound is fine when using 'aplay', so clearly
> > the sound system on the Pi is fundamentally OK.
> >
> > Comparing the settings in QJackCtl in the Parameters and Advanced
> > tabs, they are the essentially the same both on the Pi and on my HP
> > laptop running Ubuntu 18.04.
> >
> > I'm stumped.
>
> You might want to check out
> https://wiki.linuxaudio.org/wiki/raspberrypi#on-board_audio
>
> The onboard audio is still PWM and < 16-bit as far as I know so maybe
> that's the cause of the distortion.
It seems possible - although since the sound is at least superficially
OK when played through HDMI but is completely unusable through the
headphone jack, I would have thought I needed to be looking somewhere
else.
I had a look at the wiki page you linked to. Unfortunately there
doesn't seem to be a date on it, and I am wondering whether it is
perhaps partly out of date. It mentions Raspberry Pi 1 and 2, but has
no mention of 3 or 4. Also it has a section on building a real-time
kernel, but I understood that all up-to-date Linux kernels have real
time capability, and certainly my QJackCtl reports that jack is running
in real time.
I haven't so far listened to any actual music played from Qtractor
through the HDMI: perhaps I should try this, to see whether the sound
is sufficiently good to use for editing etc. But even if it is, it
still doesn't solve the basic problem, which is that I can't use the
sound coming through the headphone socket.
I have a feeling I'm going to have to go back to plan A - which is
using my laptop computer, as I have in the past. Qtractor and jack run
fine on this. I was just hoping to use the Pi which would have been
more convenient in some ways.
Before I give up, I might just try a completely fresh install of the OS
on the Pi. It's just possible something has got messed up along the
way.
Thanks for your suggestions.
David
I am running Qtractor and QJackCtl on a Raspberry Pi 3B+, with sound
output through the headphone jack.
When I play a wav file using 'aplay' it sounds fine, but if I load it
into a track in Qtractor, it is very distorted. A female voice sounds
like basso profundo (although the speed is correct) and is very
distorted. It looks to me as if this is probably because the output of
Qtractor is not being directed through jackd.
QJackCtl seems to show that jack is running OK and speaking nicely to
Alsa, but there is one oddity. The Qtractor Connections window shows,
in the Audio tab, the expected Qtractor output connected to System.
Normally I would expect the QJackCtl Connect window to show the same in
its Audio tab, but in fact it shows nothing at all - neither Qtractor
nor System. (Yet it is showing the expected Midi Through and Qtractor
on both sides of the Midi tab, cross connected as expected.)
The Messages tab of QJackCtl shows that jackd is running, but it
doesn't report anything extra when Qtractor is started. Yet on my
Ubuntu machines, QJackCtl knows automatically when I start Qtractor.
Any ideas why QJackCtl doesn't seem to know what's trying to connect
through it?
David
Hello Everyone,
PianoBooster is back! It has been a very long time since there has been an
announcement about PianoBooster posted to this list and there have been
lots of changes. First there is a brand new website see
https://www.pianobooster.org/ and the official source code has just moved
to a new GitHub repo. See https://github.com/pianobooster/PianoBooster so
please update your URLs to point to this new website and repo.
Piano Booster is an Open Source program that helps with playing the piano
and learning to sight read music. It's key feature is that it listens and
follows what you are playing on the piano and waits for you to find and
play the right notes. It helps you with this by giving you audio feedback.
So if you play a wrong note then that note will have the Harpsichord sound
but the right notes
will have the Piano sound.
The new features in this release is a built-in FluidSynth sound generator
which makes it much easier to use. Also included are two music courses,
Please see https://www.pianobooster.org/music-info.html
For a video demonstration see:
http://www.youtube.com/watch?v=UGbfm8Tv-20
PianoBooster is licensed under GPL and runs on Linux, Windows and the Mac.
PianoBooster is available from: https://www.pianobooster.org .
Thanks
Louis
Hi!
We juste realized a new song, recorded in video, as usual, in
#AlmostLiveConditions, but this time we didn't had the director's cut,
neither the platform on which it's been dropped:
https://www.youtube.com/watch?v=K8Mdiubg98I&feature=youtu.be
or in audio only:
https://plagiatbros.bandcamp.com/album/monnaie-chiffre-oseille-bif-jack-shi…
Everything is CC4.0-BY-SA
It's a live recording, we do use a FLOSS setup online including:
- Ladish / Gladish,
- zynaddsubFX,
- SooperLooper,
- Non-mixer,
- seq24 (our self patched-version),
- x42-fat1 microtonalized version,
- many plugins: calf, swh, tap, caps, invada...
- ecasound,
- mididings (as our main control piece),
- tapeutape (a sampler which is not developped anymore),
- calfjackhost,
- Open Stage Control,
- Pedalboards (teensy code to get an osc pedalboard)
You can find the setup here:
https://github.com/PlagiatBros/PlagiatSetup/
And for the recording, mixing and mastering:
- Ardour,
- LSP plugins.
Thanks for your attention.
On Wed, 09 Dec 2020 16:25:33 +0000 David Sumbler <david(a)aeolia.co.uk> wrote:
> I am running Qtractor and QJackCtl on a Raspberry Pi 3B+, with sound
> output through the headphone jack.
>
> When I play a wav file using 'aplay' it sounds fine, but if I load it
> into a track in Qtractor, it is very distorted. A female voice
> sounds like basso profundo (although the speed is correct) and is
> very distorted. It looks to me as if this is probably because the
> output of Qtractor is not being directed through jackd.
Thank you for the various responses to my query. To answer Rui's
question first: the binary I am using is from the Raspian repository,
and is version 0.9.5.
The discrepancy between what QJackCtl and QTractor are showing in their
respective connections windows fortunately seems to have largely
disappeared for some reason unknown to me, and clearly the signal is
being directed from Qtractor through Jack.
As regards the distorted sound, I thought it might be useful to direct
the sound through HDMI (although this is not what I want to do
ultimately) to see if the same thing happens. It has taken me hours of
fiddling around with settings to achieve this, but finally I succeeded.
The same .wav file that I played in Qtractor and which was badly
distorted through headphones, sounds absolutely fine through an HDMI
setup.
After much experimentation with settings, I have now got the sound from
Qtractor back to the headphones. The distortion is still there. I
would be tempted to think it might be a fault with my Raspberry Pi, but
the sound is fine when using 'aplay', so clearly the sound system on
the Pi is fundamentally OK.
Comparing the settings in QJackCtl in the Parameters and Advanced tabs,
they are the essentially the same both on the Pi and on my HP laptop
running Ubuntu 18.04.
I'm stumped.
David
Hello,
I am using ubuntu studio 19.04 and I have a 16 port powered usb hub and 16 usb sound cards.
This much works fine - they are all listed when i type 'aplay -l' and i can get sound out of each of them.
The issue is that the usb devices don't always load in the same order so following instructions from this site (https://alsa.opensrc.org/Udev) I am attempting to write a UDEV rule to give them a unique / static ID based on which port (DEVPATH) they are plugged into. My udev rule looks like this:
SUBSYSTEM!="sound", GOTO="my_usb_audio_end"
ACTION!="add", GOTO="my_usb_audio_end"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.4/1-1.2.3.4:1.0/sound/card?", ATTR{id}="USB_1"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.3/1-1.2.3.3:1.0/sound/card?", ATTR{id}="USB_2"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.2/1-1.2.3.2:1.0/sound/card?", ATTR{id}="USB_3"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3.1/1-1.2.3.1:1.0/sound/card?", ATTR{id}="USB_4"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/1-1.2.4.1:1.0/sound/card?", ATTR{id}="USB_5"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.2/1-1.2.4.2:1.0/sound/card?", ATTR{id}="USB_6"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.3/1-1.2.4.3:1.0/sound/card?", ATTR{id}="USB_7"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.4/1-1.2.4.4:1.0/sound/card?", ATTR{id}="USB_8"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2/1-1.2.1.2:1.0/sound/card?", ATTR{id}="USB_9"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.1/1-1.2.1.1:1.0/sound/card?", ATTR{id}="USB_10"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.3/1-1.2.1.3:1.0/sound/card?", ATTR{id}="USB_11"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.3/1-1.2.4.3:1.0/sound/card?", ATTR{id}="USB_12"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.4/1-1.2.4.4:1.0/sound/card?", ATTR{id}="USB_13"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.2/1-1.2.1.2:1.0/sound/card?", ATTR{id}="USB_14"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.1/1-1.2.1.1:1.0/sound/card?", ATTR{id}="USB_15"
DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.3/1-1.2.1.3:1.0/sound/card?", ATTR{id}="USB_16"
LABEL="my_usb_audio_end"
and this sort of works, but only for the first 9 usb devices I plug in.
The strange thing is that it doesn't matter which 9 - I can plug any of the 16 cards into any of the 16 ports and the first 9 will always follow the udev naming rule, but after that it reverts to the default naming scheme.
Can anyone help me understand why this might be happening?
Many thanks
Hi!
Installed a new kernel on my Debian Testing machine with
kxstudio-"extension"
:~$ uname -a
Linux mmmaschine 5.9.0-4-rt-amd64 #1 SMP PREEMPT_RT Debian 5.9.11-1
(2020-11-27) x86_64 GNU/Linux
and had a new problem that jack couldn't launched - which bever had been
a problem, so far. Dived into journalctl -f and stumbled upon
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio]
module-alsa-card.c: Failed to find a working profile.
Dez 04 11:18:17 machine pulseaudio[1852]: E: [pulseaudio] module.c:
Failed to load module "module-alsa-card" (argument: "device_id="3"
name="usb-KORG_INC._KONTROL49-00"
card_name="alsa_card.usb-KORG_INC._KONTROL49-00" namereg_fail=false
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes
use_ucm=yes avoid_resampling=no
card_properties="module-udev-detect.discovered=1""): initialization failed.
Knowing, that the Korg has no audio-abilities, I checked
:~$ cat /proc/asound/cards
 0 [PCH           ]: HDA-Intel - HDA Intel PCH
                     HDA Intel PCH at 0x4001110000 irq 134
 1 [Loopback      ]: Loopback - Loopback
                     Loopback 1
 2 [DSP           ]: H-DSP - Hammerfall DSP
                     RME Hammerfall HDSP 9652 at 0xa0100000, irq 17
 3 [KONTROL49     ]: USB-Audio - KONTROL49
                     KORG INC. KONTROL49 at usb-0000:00:14.0-2, full speed
Unplugging the Korg Kontrol49 made it possible to launch jackd, again.
My questions:
How can I force my system not to handle the Korg as an audio but a MIDI
device?
Is this something happening on kernel level, so *someone*â„¢ has to fix
stuff here?
Greets!
Mitsch
