Hi!
I know you're interested in stuff like that, so I think that information is gonna be helpful to you, read it here please <http://nophustupu.nicholasyost.com/e4sxf>
Faithfully, Daniele Torelli
Hello friend,
I wanted to thank you a lot for all you've done, it was a real help. Please read my whole message here <http://jisethyzo.juliaburnessjewellery.com/e4taq>
Yours faithfully, Daniele Torelli
Branch: refs/heads/master
Home: https://github.com/jackaudio/jack1
Commit: 04a18e8914a1f1c2d5e43bcaeb2fd44b37b9cfe6
https://github.com/jackaudio/jack1/commit/04a18e8914a1f1c2d5e43bcaeb2fd44b3…
Author: Uladox <uladoxiental(a)gmail.com>
Date: 2016-08-14 (Sun, 14 Aug 2016)
Changed paths:
M include/internal.h
M jackd/engine.c
M jackd/jackd.c
M libjack/client.c
Log Message:
-----------
Removes use of gloabl jack_tmpdir.
Uses static local variable like how jack_user_dir does. jack_get_tmpdir()
replaces jack_tmpdir for the most part except in jackd -l where it would
cause an infinite loop, and instead DEFAULT_TMP_DIR is used, which is
what it would happen anyway. Also in jack_user_dir the default value is
used if jack_user_dir returns NULL from some error, but an error message
is printed with jack_error(), this is the same as the old behavior, but
I am not sure this is quite what should happen. Still, the exact same
behavior as before is acheived except without the use of the jack_tmpdir
global and the memory issues caused by calling jack_get_tmpdir().
Commit: 0880dfaaf0509f4508c7ec47497793bf7f675f99
https://github.com/jackaudio/jack1/commit/0880dfaaf0509f4508c7ec47497793bf7…
Author: Paul Davis <paul(a)linuxaudiosystems.com>
Date: 2016-08-29 (Mon, 29 Aug 2016)
Changed paths:
M include/internal.h
M jackd/engine.c
M jackd/jackd.c
M libjack/client.c
Log Message:
-----------
Merge pull request #47 from Uladox/master
Fixed leaked memory with jack_tmpdir.
Compare: https://github.com/jackaudio/jack1/compare/8a7253575c58...0880dfaaf050
Hi!
A while ago I initiated work on a Linux driver for Line6 devices (now under sound/usb/line6 in the Linux kernel tree). Some of these devices have weird sample rates (39062.5Hz, derived from the 10MHz USB clock divided by 256). The alsa_in and alsa_out jack clients are convenient tools to use such Line6 devices together with more standardized hardware operating at, e.g., 48kHz. However, alsa_in only supports integer sample rates, and even after a couple of minutes, alsa_in doesn't detect the correct resampling factor 1.2288 (48000/39062.5), but still reports the initial approximated value 1.228816 (48000/39062). Admittedly, the error isn't too big, but is larger than the error of high-quality crystal oscillators. And, after all, why use an approximation if we know better?
I modified alsa_in and alsa_out such that they accept a sample rate in floating point format (command line option "-r") and query the fractional sample rate from the ALSA driver to compute the initial estimation of the resampling factor (see attached patch).
What do you think about this patch?
Kind regards,
Markus
Hello JACK community,
I’m planning my new audio editing setup (both hard- and software) and before investing in hardware, I’d like to ask for advice.
Here’s what I want to do:
– Both computers run Linux.
– On Computer A, I can browse the web and see Youtube videos, I can listen to MP3 files with Totem and I can do DAW stuff with Ardour.
– Computer B does nothing more than getting all the sound output from A and feed it to the speaker through it’s soundcard.
Here’s my theoretical approach:
– Both computers run JACK.
– A runs PulseAudio in top of JACK.
– A runs with the net backend using netJACK2.
– B has the Net Manager loaded which gets the audio from A and pipes it to the soundcard.
– Every time I boot the two computers, they are ready to work. No daemons I have to launch manually, etc. I want the configuration to be done one time for all.
I got my understanding of JACK through the network from here: https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_Net… And this site would also be my guide for setting up the thing.
But I’m not a JACK expert at all. It’s the first time I’m doing something like this. So I want to make shure I got the basics right. And, maybe you now even a better step-by-step tutorial which does exactly what I want.
So, I appreciate any comments on this.
Bye,
xan
The FFADO developers are pleased to announce FFADO version 2.3.0, a package
of userspace drivers for firewire audio interfaces. While there are no
significant new features in this version compared to the last, FFADO 2.3.0
contains a large number of incremental improvements. Users of FFADO are
encouraged to upgrade.
This source-only release can be downloaded from the ffado.org website at
http://ffado.org
or via the direct link:
http://ffado.org/files/libffado-2.3.0.tgz
Notable changes include:
* Configuration entries added for additional devices which work with the
generic support layer (PreSonus Studiolive 32.4.2, Presonus StudioLive
16.0.2, ICON FireXon, Onyx Blackbird and the new Onyx 1640i, among
others).
* Support added for the newer Focusrite Saffire Pro 26.
* Improved build support for various downstream consumers.
* Better routing for selected Saffire devices and the Firestudio Mobile.
* Significant cleanup and refinement of the M-Audio and Yamaha driver.
* Compilation fixes for recent versions of gcc.
* Recover from dead streams without causing jackd to shut down.
Thanks go out to the developers and users who contributed code and
information which went into this release: Kristian Amlie, Melanie Bernkopf,
David Binderman, Philippe Carriere, Yves Grenier, Florian Hofmann, Hector
Martin, Mathieu Picot, Philippe Ploquin, Stefan Richter, Takashi Sakamoto,
Jano Svitok, Karl Swisher, Steven Tonge and Jonathan Woithe.
I just installed Ubuntu trusty (on crouton on an Acer Chromebook), and am
trying to get sound going (so I can run Super-Collider.)
Upon the advice of various webpages I've come across that discuss
installation of Super-Collider, I've tried:
- removing pulseaudio
- adding myself to the "hwaudio" group
- adding '@audio' entries to /etc/security/limits.conf
But I always get "Could not connect to JACK server as client" when I run
qjackctl.
This is the output I get when I run qjackctl. I've tried changing the
interface to both 'cras' and 'hw:DAISY12S', but neither work.
23:54:23.518 Patchbay deactivated.
23:54:23.585 Statistics reset.
23:54:23.598 ALSA connection change.
23:54:23.643 D-BUS: Service not available (org.jackaudio.service aka
jackdbus).
23:54:23.667 JACK is starting...
23:54:23.668 /usr/bin/jackd -dalsa -dcras -r44100 -p1024 -n2
23:54:23.686 ALSA connection graph change.
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... cras|cras|1024|2|44100|0|0|nomon|swmeter|-|32bit
Couldn't connect to cras.
control open "cras" (Operation not permitted)
configuring for 44100Hz, period = 1024 frames (23.2 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
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
23:54:23.980 JACK was started with PID=13310.
23:54:24.042 JACK was stopped successfully.
My apologies if I'm asking this in the wrong place, or if I'm not giving
enough info. I'll ask elsewhere if that's more appropriate. But any
advice or suggestions would be much appreciated!
Hi,
I'm trying to get receive audio data from a USB software defined radio and
pipe it through jack to alsa out and also to another app dl-fldigi.
It's working (off a fashion) using this hacky script
https://gist.github.com/jrobinson-uk/123daebd8ff58d636ba02da9dfd7f3e1 which
basically
starts the jack server
starts the 3 apps to link (mplayer --> alsa_out --> dl-fldigi)
links mplayer to alsa then also to dl-fldigi
I have 2 questions:
Some of the apps either crash occasionally (dl-fldigi) or their is a case
for restarting them (mplayer), at the moment I have to recreate the
connections each time an app closes. Is it possible to create the
connections first and have them persist, then connect the apps when they are
(re)started?
Secondly I have some audio issues, there are fractional pauses every so
often which make the audio had to decode, is there anything about piping
through jack that could cause this, on something which might mitigate it?
James
--
View this message in context: http://jack-audio.10948.n7.nabble.com/Linking-apps-together-from-script-tp1…
Sent from the Jackit mailing list archive at Nabble.com.
