JackAudio

jackaudio@lists.linuxaudio.org

601 discussions

by Matt Flax

Hi there, I am interested to know more about how jack threaded signalling works ... I know that jackd2 allows multithreading - what is the mechanism on Linux for synchronisation ? Is it using pthread conds, futex or something else ? thanks Matt

7 years, 8 months

[Jack-Devel] zinaddsubfx, jackd and Linux mint no sound

by Joe Frey

Sorry, due to posting with wrong email, I was told the post wouldn't stick. Sorry to double dip. Hello all, I have installed both versions of zinaddsubfx(jack and ALSA) on Mint 18.2 64. I am using qjackctl. I have gotten both amsynth and qsynth to work fine. When I start zinaddsubfx(jack) I can make midi connections in qjackctl ALSA tab and I see the meters move in zinaddsubfx. On the audio tab in qjackctl I do not see zinaddsubfx listed and cannot make the audio connections. If I start zinaddsubfx(ALSA) I see this program on the qjackctl audio tab but not on the ALSA tab in qjackctl and cannot make midi connections. Has anyone gotten it to work? Thanks. JoeF.

7 years, 9 months

[Jack-Devel] AES67 / SMPTE ST 2110-30

by Philippe Bekaert

Anyone working on AES67 / ST 2110-30 interfacing with jack audio? I’m considering to take up the glove, if it doesn’t already exist. Could also be a nice replacement for the net drivers. Best, Philippe. Philippe Bekaert full professor - project leader Expertise center for Digital Media - Hasselt University Wetenschapspark 2 - 3590 Diepenbeek - Belgium Tel: +32 11 268411 www.edm.uhasselt.be

7 years, 9 months

Re: [Jack-Devel] AES67 / SMPTE ST 2110-30

by happy musicmaker

That is such good news. What(low cost) hardware would this development be used on to support the developers with testing/debugging and maybe even development ? * MOTU LP32 (Preferred) * MiniDSP https://www.minidsp.com/products/network-audio/avb-dg (I think MOTU's switch uses midDSP switch hardware) I hope someday it will be possible to connect 4 or more 8 channel ADAT modules (32 channels) to a PC under Ubuntu via AVB with low latency. The only option to get this done under Windows is a Focursrite DANTE based Rednet 3 right now because Thunderbolt is not really available there as well. Plan to get Rednet3, but that does not solve the Linux environment which I prefer. Would love to be able to use the Rednet 3 under Linux but since DANTE is proprietary , so unlikely. My two wishes: [a] Multi (16+) channel low latency audio I/O using ADAT audio AD/DA [b[ Bitwig supporting LV2 plugins. With those two, the Linux Audio environment would be perfect and the world a better place. On Thu, Sep 28, 2017 at 11:20 AM, happy musicmaker < happy.musicmaker(a)gmail.com> wrote: > That is such good news. What(low cost) hardware would this development > be used on to support the developers with testing/debugging and maybe even > development ? > > * MOTU LP32 (Preferred) > * MiniDSP https://www.minidsp.com/products/network-audio/avb-dg (I think > MOTU's switch uses midDSP switch hardware) > > I hope someday it will be possible to connect 4 or more 8 channel ADAT > modules (32 channels) to a PC under Ubuntu via AVB with low latency. The > only option to get this done under Windows is a Focursrite DANTE based > Rednet 3 right now because Thunderbolt is not really available there as > well. Plan to get Rednet3, but that does not solve the Linux environment > which I prefer. Would love to be able to use the Rednet 3 under Linux but > since DANTE is proprietary , so unlikely. > > My two wishes: > [a] Multi (16+) channel low latency audio I/O using ADAT audio AD/DA > [b[ Bitwig supporting LV2 plugins. > > With those two, the Linux Audio environment would be perfect and the > world a better place. > > > > > On Thu, Sep 28, 2017 at 1:37 AM, Spencer Russell <sfr(a)media.mit.edu> > wrote: > >> That would be an amazing contribution. I'm seeing more AES67 gear show >> up in the studios I frequent and being able to route to/from those >> devices using JACK would be great. >> >> -s >> >> On Wed, Sep 27, 2017, at 10:20 AM, Philippe Bekaert wrote: >> > Anyone working on AES67 / ST 2110-30 interfacing with jack audio? >> > I’m considering to take up the glove, if it doesn’t already exist. >> > Could also be a nice replacement for the net drivers. >> > Best, >> > >> > Philippe. >> > >> > Philippe Bekaert >> > full professor - project leader >> > Expertise center for Digital Media - Hasselt University >> > Wetenschapspark 2 - 3590 Diepenbeek - Belgium >> > Tel: +32 11 268411 <+32%2011%2026%2084%2011> >> > www.edm.uhasselt.be >> > >> > _______________________________________________ >> > Jack-Devel mailing list >> > Jack-Devel(a)lists.jackaudio.org >> > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >> _______________________________________________ >> Jack-Devel mailing list >> Jack-Devel(a)lists.jackaudio.org >> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >> > >

7 years, 9 months

[Jack-Devel] Pd v. Jack2: can't connect named semaphore name

by dreamer

So, I'm trying to package Pure Data for the OpenPandora, however when trying to connect a running jack2 instance I get: Connect: can't connect named semaphore name = jack_sem.1000_default_system err = No such file or directory On the jack side I see: Jack: JackRequest::ClientCheck Jack: Check protocol client = 8 server = 8 Jack: JackRequest::ClientOpen Jack: JackEngine::ClientExternalOpen: uuid = 18, name = pure_data Jack: JackEngine::AllocateRefNum ref = 5 Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_pure_data val = 0 Jack: JackSocketNotifyChannel::Open name = pure_data Jack: JackClientSocket::Connect : addr.sun_path /dev/shm/jack_pure_data_1000_0 Jack: JackShmMem::new index = 5 attached = 40c47000 size = 432 Jack: JackExternalClient::Open name = pure_data index = 5 base = 40c47000 Jack: JackPosixProcessSync::TimedWait time out = 5000000 Jack: JackPosixProcessSync::TimedWait finished delta = 3112.0 Jack: JackEngine::NotifyAddClient: name = pure_data Jack: JackDriver::ClientNotify ref = 5 driver = system name = pure_data notify = 0 Jack: JackExternalClient::ClientNotify ref = 0 client = pure_data name = system notify = 0 ClientNotify fails name = system notification = 0 val1 = 0 val2 = 0 NotifyAddClient new_client fails name = pure_data Cannot notify add client Jack: JackExternalClient::Close Jack: JackSocketNotifyChannel::Close Jack: JackClientSocket::Close Jack: JackShmMem::delete size = 0 index = 5 Cannot create new client Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 14 Jack: JackSocketServerChannel::Execute : fPollTable i = 3 fd = 17 Jack: JackSocketServerChannel::Execute : fPollTable i = 4 fd = 20 Jack: JackSocketServerChannel::Execute : fPollTable i = 5 fd = 23 Jack: JackSocketServerChannel::Execute : poll client error err = Success Jack: JackSocketServerChannel::ClientKill ref = -1 fd = 23 Jack: Client was not opened : probably correspond to server_check Clearly the two are seeing each other, but I can't tell what is going wrong here. Any clues on how to proceed are welcome. cheers, d.

7 years, 9 months

[Jack-Devel] -d firewire -X alsaraw fails?

by David Kastrup

Hi, when I try (on Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-======================================-========================-========================-================================================================================== ii jackd2 1.9.10+20150825git1ed50c amd64 JACK Audio Connection Kit (server and example clients) ) the command jackd -d firewire -X alsaraw -r 96000 -p 512 I get the following output (the start is not all that interesting): jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp 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 no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" 1505250482905708: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.3.0- built Aug 12 2016 08:47:17 00245641440: Warning (dice_eap.cpp)[ 115] init: no EAP mixer (device does not support EAP) 00245641530: (dice_avdevice.cpp)[ 713] showDevice: DICE Parameter Space info: 00245641627: (dice_avdevice.cpp)[ 714] showDevice: Global : offset=0x0028 size=0360 00245641650: (dice_avdevice.cpp)[ 715] showDevice: TX : offset=0x0190 size=0568 00245641658: (dice_avdevice.cpp)[ 716] showDevice: nb= 2 size=0280 00245641671: (dice_avdevice.cpp)[ 717] showDevice: RX : offset=0x03C8 size=1128 00245641678: (dice_avdevice.cpp)[ 718] showDevice: nb= 1 size=0280 00245641689: (dice_avdevice.cpp)[ 719] showDevice: UNUSED1 : offset=0x0000 size=0000 00245641696: (dice_avdevice.cpp)[ 720] showDevice: UNUSED2 : offset=0x0000 size=0000 00245641706: (dice_avdevice.cpp)[ 722] showDevice: Global param space: 00245648092: (dice_avdevice.cpp)[ 725] showDevice: Owner : 0x00000000FFFF0000 00245653331: (dice_avdevice.cpp)[ 728] showDevice: Notification : 0x00000020 00245663787: (dice_avdevice.cpp)[ 731] showDevice: Nick name : iO 14 00245669859: (dice_avdevice.cpp)[ 735] showDevice: Clock Select : 0x04 0x0C 00245675606: (dice_avdevice.cpp)[ 739] showDevice: Enable : false 00245681508: (dice_avdevice.cpp)[ 743] showDevice: Clock Status : locked 0x04 00245688523: (dice_avdevice.cpp)[ 746] showDevice: Extended Status : 0x00000000 00245695403: (dice_avdevice.cpp)[ 749] showDevice: Samplerate : 0x00017700 (96000) 00245700433: (dice_avdevice.cpp)[ 752] showDevice: Version : 0x01000400 00245705069: (dice_avdevice.cpp)[ 761] showDevice: Version : 0x01000400 (1.0.4.0) 00245710923: (dice_avdevice.cpp)[ 764] showDevice: Clock caps : 0x1121007E 00245719370: (dice_avdevice.cpp)[ 767] showDevice: Clock sources : 00245719394: (dice_avdevice.cpp)[ 773] showDevice: SPDIF 00245719432: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719448: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719469: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719484: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719504: (dice_avdevice.cpp)[ 773] showDevice: ADAT 00245719520: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719539: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719554: (dice_avdevice.cpp)[ 773] showDevice: Firewire 00245719574: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719589: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719607: (dice_avdevice.cpp)[ 773] showDevice: unused 00245719623: (dice_avdevice.cpp)[ 773] showDevice: INTERNAL 00245719643: (dice_avdevice.cpp)[ 776] showDevice: TX param space: 00245719658: (dice_avdevice.cpp)[ 777] showDevice: Nb of xmit : 2 00245719680: (dice_avdevice.cpp)[ 779] showDevice: Transmitter 0: 00245725359: (dice_avdevice.cpp)[ 782] showDevice: ISO channel : -1 00245732416: (dice_avdevice.cpp)[ 784] showDevice: ISO speed : 2 00245738802: (dice_avdevice.cpp)[ 787] showDevice: Nb audio channels : 6 00245743550: (dice_avdevice.cpp)[ 789] showDevice: Nb midi channels : 1 00245749373: (dice_avdevice.cpp)[ 792] showDevice: AC3 caps : 0x00000000 00245753967: (dice_avdevice.cpp)[ 794] showDevice: AC3 enable : 0x00000000 00245761348: (dice_avdevice.cpp)[ 797] showDevice: Channel names : 00245761403: (dice_avdevice.cpp)[ 802] showDevice: Line 1 00245761423: (dice_avdevice.cpp)[ 802] showDevice: Line 2 00245761448: (dice_avdevice.cpp)[ 802] showDevice: Line 3 00245761466: (dice_avdevice.cpp)[ 802] showDevice: Line 4 00245761489: (dice_avdevice.cpp)[ 802] showDevice: SPDIF L 00245761506: (dice_avdevice.cpp)[ 802] showDevice: SPDIF R 00245761530: (dice_avdevice.cpp)[ 779] showDevice: Transmitter 1: 00245768428: (dice_avdevice.cpp)[ 782] showDevice: ISO channel : -1 00245774396: (dice_avdevice.cpp)[ 784] showDevice: ISO speed : 2 00245780427: (dice_avdevice.cpp)[ 787] showDevice: Nb audio channels : 4 00245787338: (dice_avdevice.cpp)[ 789] showDevice: Nb midi channels : 0 00245792771: (dice_avdevice.cpp)[ 792] showDevice: AC3 caps : 0x00000000 00245797845: (dice_avdevice.cpp)[ 794] showDevice: AC3 enable : 0x00000000 00245804113: (dice_avdevice.cpp)[ 797] showDevice: Channel names : 00245804140: (dice_avdevice.cpp)[ 802] showDevice: ADAT1 00245804155: (dice_avdevice.cpp)[ 802] showDevice: ADAT2 00245804176: (dice_avdevice.cpp)[ 802] showDevice: ADAT3 00245804192: (dice_avdevice.cpp)[ 802] showDevice: ADAT4 00245804216: (dice_avdevice.cpp)[ 806] showDevice: RX param space: 00245804233: (dice_avdevice.cpp)[ 807] showDevice: Nb of recv : 1 00245804252: (dice_avdevice.cpp)[ 809] showDevice: Receiver 0: 00245810261: (dice_avdevice.cpp)[ 812] showDevice: ISO channel : 2 00245816310: (dice_avdevice.cpp)[ 814] showDevice: Sequence start : 0 00245822033: (dice_avdevice.cpp)[ 817] showDevice: Nb audio channels : 8 00245829099: (dice_avdevice.cpp)[ 819] showDevice: Nb midi channels : 1 00245836232: (dice_avdevice.cpp)[ 822] showDevice: AC3 caps : 0x00000000 00245841167: (dice_avdevice.cpp)[ 824] showDevice: AC3 enable : 0x00000000 00245847606: (dice_avdevice.cpp)[ 827] showDevice: Channel names : 00245847621: (dice_avdevice.cpp)[ 832] showDevice: Bus1 L 00245847626: (dice_avdevice.cpp)[ 832] showDevice: Bus1 R 00245847636: (dice_avdevice.cpp)[ 832] showDevice: Bus2 L 00245847642: (dice_avdevice.cpp)[ 832] showDevice: Bus2 R 00245847649: (dice_avdevice.cpp)[ 832] showDevice: Bus3 L 00245847655: (dice_avdevice.cpp)[ 832] showDevice: Bus3 R 00245847663: (dice_avdevice.cpp)[ 832] showDevice: Bus4 L 00245847667: (dice_avdevice.cpp)[ 832] showDevice: Bus4 R 00245875561: (dice_avdevice.cpp)[ 323] setSamplingFrequency: Setting sample rate: 96000 port_name "firewire_pcm:0005950400400fc2_midi 0_in" already exists driver: cannot register port for firewire_pcm:0005950400400fc2_midi 0_in Cannot attach audio driver JackServer::Open failed with -1 no message buffer overruns Failed to open server Uh, port already exists? The Firewire ports are not visible from Alsa (I have blacklisted snd_dice since it does not play well with the Alesis io|14) and there just is (seq and raw, respectively): dak@lola:/usr/local/tmp/lilypond$ aplaymidi -l Port Client name Port name 14:0 Midi Through Midi Through Port-0 20:0 UM-4 UM-4 MIDI 1 20:1 UM-4 UM-4 MIDI 2 20:2 UM-4 UM-4 MIDI 3 20:3 UM-4 UM-4 MIDI 4 dak@lola:/usr/local/tmp/lilypond$ amidi -l Dir Device Name IO hw:1,0,0 UM-4 MIDI 1 IO hw:1,0,1 UM-4 MIDI 2 IO hw:1,0,2 UM-4 MIDI 3 IO hw:1,0,3 UM-4 MIDI 4 but those have nothing to do with the jackd error (right?). So jackd somehow gets in a loop or something? -- David Kastrup

7 years, 9 months

[Jack-Devel] Fwd: Jack Connection Audio + Live 9 + win10 64bit

by Mica Cat

---------- Forwarded message ---------- From: Mica Cat <micacatt(a)gmail.com> Date: 2017-09-06 11:27 GMT+02:00 Subject: Jack Connection Audio + Live 9 + win10 64bit To: Mica Cat <micacatt(a)gmail.com> hello all sorry my english i m french. I have try this soft ( jack audio) but Live 9 refuse connecting at JackAudio Cannot open client > Cannot connect to named pipe = \\.\pipe\client_jack_Ableton Live 9 Suite_0 > err = 5 > Cannot connect client pipe > Cannot connect to client name = Ableton Live 9 Suite tank you

7 years, 10 months

Re: [Jack-Devel] Jack server keeps playing sound after client disconnetcs

by Ralf Mardorf

On Thu, 24 Aug 2017 11:50:23 -0700, Yuri wrote: >On 08/24/17 10:31, Ralf Mardorf wrote: >> seemingly jackaudio.org was down, so consider to resend your concerns >> to the mailing list, since it's up again. I'm not a jackd developer, >> just a user and simply try to point out, that Ctrl+C isn't a shortcut >> that ensures a specific action of an application. You seem to assume >> that Ctrl+C does kill an app or something similar, but actually an >> app is free to continue running or to do anything else. > > >No, I am not assuming this. Ctrl+C, of course, doesn't guarantee a >particular action. I am just pointing out that in case of a >client-server architecture, which is the case here, server can't rely >on the client to always take a particular action before disconnecting. >It is a much more sound strategy to always clean up after >disconnecting client regardless of what the client did. > > >So, you are saying that all OSes suffer from this problem, not only >FreeBSD? One client I observed this recently with is 'sclang' from >SuperCollider. Hi, I don't know, I'm on Linux, but don't use Ctrl+C to exit an app launched by command line, that is a jackd client. Either I'm using the apps regular options to exit or if something should go wrong, I'm using a script to send all apps that are part of a jackd session, including jackd, a SIGKILL, before the same script restores the jackd session. IMO a sound server aimed for real-time usage should assume that clients do the right thing. Much likely the sound architecture of FreeBSD isn't that reliable for a real-time audio sound server as ALSA in combination with the Linux kernel's real-time capabilities is. Actually I don't understand the problem. Why do you sent a SIGINT to an app? What is done by the app, after receiving the SIGINT? I don't know what jackd does or should do. The strategy you mentions might be right or wrong, however, using Ctrl+C IMO is asking for trouble, since we seldom know what action does follow. Regards, Ralf

7 years, 10 months

Re: [Jack-Devel] ?==?utf-8?q? Jack server keeps playing sound after client disconnetcs

by Ralf Mattes

Sorry, used the wrong sender: Am Freitag, 25. August 2017 10:42 CEST, "Ralf Mattes" <r.mattes(a)mh-freiburg.de> schrieb: > > Am Freitag, 25. August 2017 04:15 CEST, Yuri <yuri(a)rawbw.com> schrieb: > > > Sorry, but you are completely wrong. It's Jack that doesn't clean up> after the failed clients that is a problem. > > > > So far this is only your diagnosis and it's backed up by very little evidence. > You haven't provided us with information about the real symptoms - > "old audio" is a pretty broad description. Are we talking about the amount > of audio data that gets processed in one jack process callback (as Chris Claude > wrote, that would be sample-rate / (n-periods * buffer-size) ). I doubt you can > even hear this. For anything longer, I think your diagnosis is off. Where should > those sample came from? Who would be filling the shared memory buffers? > I think for any serious debugging you need to provide us with better symptom > descriptions. For example, as Ralf already did notice, sending an interrupt signal > to a process doesn't mean that that process dies an instant death. The process could > have installed a signal handler that performs, a graceful fade-out. Also, you wrote: > > > This particluar application, sclang, doesn't quit by itself without > > Ctrl-C, if this isn't encoded in the script. > > I hope you now that sclang is not a jack (audio) client, it's only an interpreter that > controls the supercollider server process (scsynth or supernova) by means of OSC > messages. You either need to send the server a stop message or kill it. > > Sorry, but you are completely wrong. It's Jack that doesn't clean up> after the failed clients that is a problem. > > Can you describe what you would expect as a "clean up? AFAIK jackd plays the > last filled buffer, then detects that the client fails to fill the buffers and "zombifies" > (read: kills) the client - unless you told the server not to! Did you? Or did you crank up > the client timeout? > > Cheers, Ralf Mattes > > > > Yuri > > > > > > _______________________________________________> Jack-Devel mailing list > > Jack-Devel(a)lists.jackaudio.org > > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >

7 years, 10 months

Re: [Jack-Devel] Jack server keeps playing sound after client disconnetcs

by Ralf Mardorf

On Thu, 24 Aug 2017 08:56:40 -0700, Yuri wrote: >On 08/24/17 08:51, Ralf Mardorf wrote: >> FWIW SIGINT could be handled by the client, IOW Ctrl+C not >> necessarily does what you expect it to do, Ctrl+C doesn't result in >> e.g. SIGKILL. > > >If Jack relies on clients to clean up, this will require fixing a lot >of clients for this to work. It is better if this is handled in the >server. Hi Yuri, seemingly jackaudio.org was down, so consider to resend your concerns to the mailing list, since it's up again. I'm not a jackd developer, just a user and simply try to point out, that Ctrl+C isn't a shortcut that ensures a specific action of an application. You seem to assume that Ctrl+C does kill an app or something similar, but actually an app is free to continue running or to do anything else. Regards, Ralf

7 years, 10 months

← Newer
1
...
30
31
32
33
34
35
36
...
61
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

JackAudio