JackAudio

jackaudio@lists.linuxaudio.org

601 discussions

[Jack-Devel] application to application latency?

by Thor Angutang

Hi list. I am sure this has been answered before: On windows: I am running audio from ableton to a spatialisation software and from the spatialisation software to the soundcard. The latency added for each step seems to be equal to the vector size setting (for instance 512)? Meaning that the output latency for such a setup would be 1024? Is this correct? Thank you list! All the best Thor

8 years, 6 months

[Jack-Devel] jack midi event reserve vs. write

by ROBERT WOLF

Dear All, What exactly is the difference between *jack_midi_event_reserve* and *jack_midi_event_write* ? In particular, if I call *jack_midi_event_write*, does it actually copy the data from the buffer, which I provide? Or does it use that same buffer. Another question is how can I send midi events generated from GUI, (which does not run in the audio callback)? My guess is to cache them somewhere and transmit them inside the callback? Am I guessing correctly? Cheers, Robert

8 years, 6 months

[Jack-Devel] jackd2 problem with netjack2 disconnect

by Jan Reusch

hi there i already opened up an issue on github [1] but it seems there is more activity. so i decided to send my problem also to this list, i hope that's ok? we have a setup here with one jackd2 instance running with netmanager as audio-master and one jackd2 instance connecting to it via netjack2 as audio-slave. when i restart the jack daemon on the slave i occasionally end up with an unusable jackd2 instance on the master. this seems to come from the way the netmanager component destroys handles for netjack2 masters (JackNetMasterInterface instances) if a netjack2 master handle encounters a network error or the connection gets closed, it sends its own jackd process a KILL_MASTER signal via a local socket. if this packets gets lost the jackd2 process gets rendered unusable (other local jack-clients and netjack clients can process audio anymore...) the quick(!) choice to evaluation if i'm on the right track was to remove sending of this multicast packet and setting a newly introduced flag fExit in the JackNetMasterInterface::Exit method. in JackNetMasterManager::Run i hooked up to check all netjack2 slaves periodically for this fExit flag and if it is set, it gets removed&the the associated objects deleted. i also removed the call to pthread_exit and instead switched to throwing an exception as it gets catched (by the netjack1 code anyway) by JackNetMaster::SetProcess. my testsetup was two machines, one running with netmanager and one connecting to it via netjack2. i restart the jackd process periodically. one cycle consists of - starting jackd - wait for 10 seconds - stop jackd - wait for 5 seconds after about ~10 minutes the jackd on the master (which doesn't get restarted) runs into the problem and is unusable from this moment on. with the patch attached to the issue the jackd process gets unusable after ~12 hours (this time with the logoutput i attached to the issue) i don't know if this is still a problem with my patch (besides it needs much nicer integration anyway) or i hit another problem here. i would be glad if someone could have a look on it and point me in the right direction! thanks! Jan [1] https://github.com/jackaudio/jack2/issues/239 -- Barco Control Rooms GmbH Greschbachstrasse 5a D - 76229 Karlsruhe http://www.barco.com mailto:jan.reusch@barco.com __________________________________________________________________________________________ Registered at 76229 Karlsruhe, Amtsgericht Mannheim, HRB 102241, Management: Piet Candeel, Lutz Nehrhoff von Holderberg This message is subject to the following terms and conditions: MAIL DISCLAIMER<http://www.barco.com/en/maildisclaimer>

8 years, 6 months

[Jack-Devel] jackdbus process eats two CPU cores for hours on end

by Thomas Howe

Hi all, I'm having a problem with the jackdbus process; after some hours it starts maxing out two of my four CPU cores, which in turn causes xruns when running apps. It looks like other people have found the same problem, but no solutions. Here's a video of this happening: https://drive.google.com/open?id=0B2eROo5JatB4eHZweUtROTduSWc I cut the important bits out and sped it up. It shows me starting jack via QJackCtl with a monitor of the log file and QJackCtl's messages in the first section, the processor spike in the second, an xrun in the third, and the processors returning to normal in the fourth. There's a clock at the bottom left corner of the screen. I'm running Arch with the Linux 4-8-4.1-ARCH (x86_64) kernel. Let me know what other information would be useful! I can't figure out how to even start debugging this. Thanks for watching, Tom

8 years, 6 months

Re: [Jack-Devel] jack_get_sample_rate

by Kjetil Matheussen

(putting back jack-devel again) It just says that it configures for 22050Hz, it doesn't say whether it succeeded. So things seems to work as it should. On Tue, Dec 13, 2016 at 10:38 AM, ROBERT WOLF < robert.wolf(a)hercsmusicsystems.com.au> wrote: > Two programs show this information: > > 1. QJackCtl. > 2. When I run my own program *AND* jack server is not running, *THEN* for > some reason the jack server gets started (apparently using the command > stored in .jackdrc file) and I see the following printout: > > 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 = 22050 > creating alsa driver ... hw:PCH,0|hw:PCH,0|1024|2| > 22050|0|0|nomon|swmeter|-|32bit > ALSA lib conf.c:4578:(parse_args) Unknown parameter 1 > ALSA lib conf.c:4711:(snd_config_expand) Parse arguments error: No such > file or directory > ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL hw:PCH,0 > control open "hw:PCH,0" (No such file or directory) > configuring for 22050Hz, period = 1024 frames (46.4 ms), buffer = 2 periods > ALSA: final selected sample format for capture: 32bit integer little-endian > ALSA: use 2 periods for capture > ALSA: final selected sample format for playback: 32bit integer > little-endian > ALSA: use 2 periods for playback > > > > *HOWEVER!!!! **jack_get_sample_rate(...);* still reports *44100*. > > How intriguing?! > > > > On 13/12/16 19:53, Kjetil Matheussen wrote: > > Which program shows this window? > > (added jack-devel mailing list back to the conversation) > > On Tue, Dec 13, 2016 at 8:35 AM, ROBERT WOLF <robert.wolf@ > hercsmusicsystems.com.au> wrote: > >> There is a window with messages and it says this: >> >> configuring for 22050Hz, period = 1024 frames (46.4 ms), buffer = 2 >> periods >> >> >> On 13/12/16 11:09, Kjetil Matheussen wrote: >> >> >> >> On Mon, Dec 12, 2016 at 7:33 AM, ROBERT WOLF < >> robert.wolf(a)hercsmusicsystems.com.au> wrote: >> >>> Dear All, >>> >>> According to the documentation *jack_get_sample_rate* reports the >>> sample rate as was used by *jackd*. >>> This does not happen in my case. >>> I start *jackd* using different sampling rates (i.e. 22050, ect.). >>> JACK reports that it does indeed uses the selected sampling rate. >>> >>> But *jack_get_sample_rate* always returns 44100. >>> >>> Why? >>> >>> >> How did Jack report that it used the selected sampling rate? >> I.e. where did you read that? >> >> >> >> > >

8 years, 6 months

Re: [Jack-Devel] jack_get_sample_rate

by Kjetil Matheussen

Which program shows this window? (added jack-devel mailing list back to the conversation) On Tue, Dec 13, 2016 at 8:35 AM, ROBERT WOLF < robert.wolf(a)hercsmusicsystems.com.au> wrote: > There is a window with messages and it says this: > > configuring for 22050Hz, period = 1024 frames (46.4 ms), buffer = 2 periods > > > On 13/12/16 11:09, Kjetil Matheussen wrote: > > > > On Mon, Dec 12, 2016 at 7:33 AM, ROBERT WOLF <robert.wolf@ > hercsmusicsystems.com.au> wrote: > >> Dear All, >> >> According to the documentation *jack_get_sample_rate* reports the sample >> rate as was used by *jackd*. >> This does not happen in my case. >> I start *jackd* using different sampling rates (i.e. 22050, ect.). >> JACK reports that it does indeed uses the selected sampling rate. >> >> But *jack_get_sample_rate* always returns 44100. >> >> Why? >> >> > How did Jack report that it used the selected sampling rate? > I.e. where did you read that? > > > >

8 years, 6 months

[Jack-Devel] [jackaudio/tools] e7cb11: transport.c: save the first tick as double

by falkTX

Branch: refs/heads/master Home: https://github.com/jackaudio/tools Commit: e7cb1162a433cffb3a50eecad10f75aaee3ab434 https://github.com/jackaudio/tools/commit/e7cb1162a433cffb3a50eecad10f75aae… Author: falkTX <falktx(a)gmail.com> Date: 2016-12-13 (Tue, 13 Dec 2016) Changed paths: M transport.c Log Message: ----------- transport.c: save the first tick as double

8 years, 6 months

[Jack-Devel] [jackaudio/tools] eb19b1: transport.c: fix drift due to rounding errors

by falkTX

Branch: refs/heads/master Home: https://github.com/jackaudio/tools Commit: eb19b1a582192ff5603a6c1e579ec71a1aa5e88d https://github.com/jackaudio/tools/commit/eb19b1a582192ff5603a6c1e579ec71a1… Author: falkTX <falktx(a)gmail.com> Date: 2016-12-13 (Tue, 13 Dec 2016) Changed paths: M transport.c Log Message: ----------- transport.c: fix drift due to rounding errors store real tick value internally as double. use it when calculating changes, then finally set the real tick.

8 years, 6 months

Re: [Jack-Devel] jack_get_sample_rate

by Kjetil Matheussen

(Added jack-devel mailing list again) Yes, I would think that jack_get_sample_rate is the only way to know the sample rate. If qjackctl shows different information it must be a bug in qjackctl. However, I noticed that your jack version is 7 years old. If qjackctl displayed the wrong information in 2009, it's probably been fixed now. On Tue, Dec 13, 2016 at 11:00 AM, ROBERT WOLF < robert.wolf(a)hercsmusicsystems.com.au> wrote: > In this case I would understand as follows: > 1. Starting JACK server with 22050 Hz sampling rate is more-or-less a > recommendation only. > 2. The way to know the sampling rate for sure is to call > *jack_get_sample_rate*. > 3. I can testify that the actual sampling rate is the same as reported by > *jack_get_sampling_rate*, because if it was not then my program would > sound differently. > > If my understanding is correct then I consider the case closed! > > Cheers, > > Robert > > > On 13/12/16 20:13, Kjetil Matheussen wrote: > > (putting back jack-devel again) > > It just says that it configures for 22050Hz, it doesn't say whether it > succeeded. > So things seems to work as it should. > > > > On Tue, Dec 13, 2016 at 10:38 AM, ROBERT WOLF <robert.wolf@ > hercsmusicsystems.com.au> wrote: > >> Two programs show this information: >> >> 1. QJackCtl. >> 2. When I run my own program *AND* jack server is not running, *THEN* >> for some reason the jack server gets started (apparently using the command >> stored in .jackdrc file) and I see the following printout: >> >> 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 = 22050 >> creating alsa driver ... hw:PCH,0|hw:PCH,0|1024|2|22050 >> |0|0|nomon|swmeter|-|32bit >> ALSA lib conf.c:4578:(parse_args) Unknown parameter 1 >> ALSA lib conf.c:4711:(snd_config_expand) Parse arguments error: No such >> file or directory >> ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL hw:PCH,0 >> control open "hw:PCH,0" (No such file or directory) >> configuring for 22050Hz, period = 1024 frames (46.4 ms), buffer = 2 >> periods >> ALSA: final selected sample format for capture: 32bit integer >> little-endian >> ALSA: use 2 periods for capture >> ALSA: final selected sample format for playback: 32bit integer >> little-endian >> ALSA: use 2 periods for playback >> >> >> >> *HOWEVER!!!! **jack_get_sample_rate(...);* still reports *44100*. >> >> How intriguing?! >> >> >> >> On 13/12/16 19:53, Kjetil Matheussen wrote: >> >> Which program shows this window? >> >> (added jack-devel mailing list back to the conversation) >> >> On Tue, Dec 13, 2016 at 8:35 AM, ROBERT WOLF < >> robert.wolf(a)hercsmusicsystems.com.au> wrote: >> >>> There is a window with messages and it says this: >>> >>> configuring for 22050Hz, period = 1024 frames (46.4 ms), buffer = 2 >>> periods >>> >>> >>> On 13/12/16 11:09, Kjetil Matheussen wrote: >>> >>> >>> >>> On Mon, Dec 12, 2016 at 7:33 AM, ROBERT WOLF < >>> robert.wolf(a)hercsmusicsystems.com.au> wrote: >>> >>>> Dear All, >>>> >>>> According to the documentation *jack_get_sample_rate* reports the >>>> sample rate as was used by *jackd*. >>>> This does not happen in my case. >>>> I start *jackd* using different sampling rates (i.e. 22050, ect.). >>>> JACK reports that it does indeed uses the selected sampling rate. >>>> >>>> But *jack_get_sample_rate* always returns 44100. >>>> >>>> Why? >>>> >>>> >>> How did Jack report that it used the selected sampling rate? >>> I.e. where did you read that? >>> >>> >>> >>> >> >> > >

8 years, 6 months

[Jack-Devel] jack_get_sample_rate

by ROBERT WOLF

Dear All, According to the documentation *jack_get_sample_rate* reports the sample rate as was used by *jackd*. This does not happen in my case. I start *jackd* using different sampling rates (i.e. 22050, ect.). JACK reports that it does indeed uses the selected sampling rate. But *jack_get_sample_rate* always returns 44100. Why? Cheers, Robert

8 years, 6 months

← Newer
1
...
38
39
40
41
42
43
44
...
61
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

JackAudio