I'm trying to get pulse and jack to be nice to each other. Running ubuntu
16.10 with cinnamon desktop.
I have a pretty simple system. The result of "aplay -l" shows that my main
card being used is:
card 1: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
Of course, since I'm running pulse, aplay -L changes this to:
pulse
PulseAudio Sound Server
So, now I *think* I know my default routing. It's just pulse sending stuff
to hw:1,0. Now, of course, pulse doesn't tell me this. It says I'm using
"Analog Stereo Output (unplugged)" from the PulseAudio Volume Control
configuration menu.
Starting up qjackctl I go to settings. There is no pulse driver, so I
select (I think incorrectly!) the alsa driver and HW:PCH,1 and start jack.
It appears that it's started and running.
Back to the terminal and try to play a file using aplay. Hmmm ... no output!
Back to pulse volume ctl. Input Devices shows a jack port. But, no output.
I really don't understand this at all. Help. Please.
--
**** Listen to my FREE CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
Hi,
I have always had this problem with a little ground loop hiss, which I
think I've traced down to the small current from the Power supply, used to
keep the motherboard turned on. If I plug my amplifiers in without their
ground plug (not a good idea, I know), I can get rid of almost all of it.
I may go to a 6 d/a channel USB audio interface to get rid of it, but I
wonder if anybody knows other things I can do; I wonder if it's just the
design of this motherboard, or perhaps of this power supply. If I knew for
sure that some other motherboard would not have this problem at all, I
might upgrade to it. After a lot of testing, I am sure that there's a
spurious signal included on the analog signals coming out of my computer's
built-in sound card or PCIE card, that is trying to get to ground and
causing the problem. Using a higher quality (2-channel) PCIE sound card
reduced it a good bit, but not entirely. I need 6 channels currently
(doing DSP in Linux), so I went back to using the on-board analog outputs,
and the noise is there, louder, again. Any ideas or education for me?
Thanks,
John
Hi all.
New release of OpenMusic 6.12 for Linux available, this time a 64-bit
version.
Main new features:
- 64 bit support for all platforms (no need for any 32-bit dependendencies)
- JUCE based audio i/o and device selection
Piles of enhancements and bug-fixes.
For more info about OpenMusic:
http://repmus.ircam.fr/openmusic/home
RPM, DEB and tar-ball available here:
https://forge.ircam.fr/p/OM/downloads/
The RPM is packaged on Fedora 24.
The DEB is packaged on Ubuntu 16.04.2 (running in a VM, minimally
tested).
The tar-ball doesn’t care. After extracting, OM can be run without
installation from inside the extracted folder. The only caveat is the
fonts (omfonts) need to be installed at the usual place. They may be
copied from the resources/ folder to wherever your system may look
(e.g. /usr/share/fonts on Fedora). Have a look at README.LINUX.
All sources are GPL and comes with the application. For access to the
current development versions look here:
git://git.forge.ircam.fr/OM.git
If you want to compile your own versions of the lisp sources there's a
guide at http://repmus.ircam.fr/openmusic/sources.
If you for some reason (old computer, weird architecture) need to build
a local version of OMAudioLib.so (JUCE based audio i/o) you'll find the
sources for this lib here:
git://git.forge.ircam.fr/omaudiolib.git
OM includes a full REPL and basic debugging aids, so if you just want to
load lisp-files or edit code there's no need to reach outside the
running application.
Thanks for all bug-reports!
-anders
Hi Francesco,
Am 18.03.2017 um 18:07 schrieb Francesco Ceruti:
> "JACK-Client" is used by one of the output-elements, [...] if you don't have JACK-Client and the element fail to load, it
> will not be visibile in the options.
thanks for the comprehensive answer. I figured out as much in the
meantime and added a new "python-jack-client" package to AUR and made it
an optional dependency of linux-show-player.
Overall I'm very impressed with the polishedness (is that a word?) of
the application.
Cheers, Chris
Hi,
what exactly does the fader of Ardour's mixer for MIDI tracks control?
I noticed that CC 7, CC 10 etc. could be selected by the editor, in
addition to the mixer's fader. CC 7 does control the volume, while the
mixer's fader seems to have impact to the note velocity.
I suspect it simply increases or decreases the recorded note velocity,
but by what values?
= 64 means velocity +- 0?
> 64 means velocity * 1.n to velocity * 2?
< 64 means velocity * 0.n to velocity = 0?
Or does it something completely different?
Regards,
Ralf
Being the OP (I think) I didn't mean to stir controversy with my questions.
As has been pointed out there are different ways to get to your preferred
configuration. Be that qjackctl, your own home brew, or some combination of
things.
Personally, most of the time, I just want it to work so I can get about MY
business and not the business of becoming a guru on some part of the chain
I need to get MY business done.
(My OP came from a desire to figure out why a particular configuration
seemed to be so finicky. A particular laptop, the alsa interface, and USB
in/out ports presented by a Behringer X32, plugging the same usb cable into
another laptop, just worked every time. In order to troubleshoot, I thought
maybe I'd gain more insight by mimicking what qjackctl does from the
command line. But, when I tried to duplicate a qjackctl start from the
command line, was stymied as to how.)
The entire linux audio (generic and pro) and the evolution thereof makes it
very difficult to get a clear picture of how it all works and how to get
what you want. (I've been a hardware/software engineer for 40 years,
messing with jack for the last 10 and still have questions...) To a new
comer or someone coming from a different audio platform, it would be hard
not to wonder if linux audiophiles aren't trying to make appear you need to
be some sort of linux mage to make it work. When in fact, you just need to
be a persistent investigator due to it's evolution (and lack of cohesive
end user documentation, again, because of it's evolution). Oh, and some
background in software, hardware, signal processing, and system
configuration doesn't hurt... For those who just want to make music or
record something quick...better stick to other platforms and cough up the
money that requires.
For me the corner case argument is moot. There a myriad of use cases and
work flows. In my case, I, mostly, do theater work where playing
prerecorded tracks, controlling various devices (mixers, projectors, sound
fx, players, etc.), and following a script is typical. For sound, that
typically, means using player apps that may or may not be jack aware
(though, when the choice is mine, I just use LinuxShowPlayer, since it
knows JACK), so having the pulse ports just appear when jack is started (by
whatever means) is nice. And, while I RARELY use Skype, being able to play
youtube without having to mess around is handy. Yes, I know I could get it
all to play nice with just jack...but, that's not what I prefer to use my
time doing.
And, for full disclosure, I use JACK to get to MIDI in ShowControl, the
open source theater production control software we are developing. But, I
don't have any desire to know more about the internals of jack than I need
to to use it as a tool. (but I need to figure out how to get that to start
with the preferred sound configuration...so I'll be looking in detail at
things like Christopher's jack-select, alas, deeper into the rabbit hole.)
;)
It's all good...just complicated. :)
Regards,
Mac
On Tue, Mar 14, 2017 at 1:28 AM, Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
wrote:
> On Tue, 14 Mar 2017 00:28:20 +0100, Christopher Arndt wrote:
> >Am 13.03.2017 um 20:04 schrieb Ralf Mardorf:
> >> DAW users very seldom need jackdbus and other users very seldom need
> >> the jack sound server at all.
> >
> >That's just your opinion, though. I find jackdbus very useful. I often
> >switch audio interfaces and JACK's dbus interface makes this a lot
> >easier.
>
> That's ridiculous, jackdbus might have advantages for some usage, but
> your examples don't cover them.
>
> >I wrote a little desktop systray app to switch JACK configrations via
> >dbus (I already announced this here a while ago):
> >
> >https://github.com/SpotlightKid/jack-select
>
> Selecting a sound card could be done with qjackctl, ardour, by command
> line and a lot of other ways, too, when using jackd.
>
> >For auto-connecting JACK audio and MIDI ports, I wrote a little helper
> >too:
> >
> >https://github.com/SpotlightKid/jack-matchmaker
>
> Connections for jackd audio and midi as well as alsa midi could be
> stored and restored by e.g. aj-snapshot, too.
>
> On Mon, 13 Mar 2017 14:27:09 -0700 (PDT), Len Ovens wrote:
> >This is a case where the combination of pulse and jackdbus work quite
> >well. Wanting to have a DAW on the screen and be able to, without
> >exiting from the DAW, play a u-toob vid...
>
> You don't need pulseaudio to do this, but even if it would require
> pulseaudio, it's a corner case.
>
> >There are a number of workflows where a pulse/jack combination is the
> >only way to make it work. (radio studio that uses skype for callin or
> >interviews comes to mind)
>
> Apart from skype interviews, what are those numerous workflows? How
> often do you hear skype interviews on radio? This is a corner case.
>
> Regards,
> Ralf
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
Hi,
I'm running multiple PC's with UbuntuStudio 16.04.
I'm trying to figure some differences in what happens between the PC's when
jack is started.
Questions:
- what is the process of determining what combination of jackd, jackdbus,
jack1, jack2 is actually being run from the command line or from qjackctl?
- since starting jack from the command line doesn't result with a pulse
source/sink, but starting it from qjackctl does end up with pulse
source/sink and system source/sink? (And, how do I duplicate what happens
when jack is started from qjackctl from the command line?)
Regards,
Mac