Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7535 discussions

Re: [LAD] [Jack-Devel] Transport question

by Tim E. Real

On March 29, 2010 03:46:00 am Rui Nuno Capela wrote: > On Mon, 29 Mar 2010 02:42:12 +0200, salsaman(a)xs4all.nl wrote: > > On Sun, March 28, 2010 03:48, Tim E. Real wrote: > >> On March 27, 2010 07:54:21 pm Tim E. Real wrote: > >>> Hi list. Hi Salsaman. > >>> > >>> I built and installed Lives today. (Nice program!) > >>> > >>> I have now tested Lives, MusE, Rosegarden, and Ardour > >>> while running Jack-2. > >>> Each had blank default layouts, no tracks, except Lives > >>> which had one short video clip loaded. > >>> > >>> Guess what? They ALL stop unexpectedly at random times > >>> while rolling and hitting 'Rew' and 'FF' in QJackCtl. > >>> Even worse, they ALL fail to start sometimes when hitting 'Play' > >>> in QJackCtl, which is what Salsaman observed with Lives. > >>> > >>> However, I discovered that the problem depends on Jack > >>> buffer size (frames/period). > >>> With 1024 or 2048 for example, it happens very frequently. > >>> With 128, it happens very rarely. > >>> > >>> What's going on here? Clearly there's a problem. > >>> A setting? A bug? System issues? > >>> > >>> Thanks. Tim. > >> > >> Oh no! > >> I just tried some of the same tests *without* QJackctl > >> and the problem disappeared. > >> To see if the problem may just be more than one app running, > >> I tried with MusE and Rosegarden running. > >> Rock solid, no trouble so far. > >> Strange considering QJackCtl is 'lightweight' compared to the others. > >> > >> I was sure that I tried this before without QJackCtl and it happened. > >> > >> Looks like this topic should move back to LAD now. > >> Sorry for the noise. Will report back if anything changes, > >> with my luck, it just might. > >> > >> Rui and Salsaman what do you think about all of this? > >> > >> Thanks. Tim. > > > > As I reported, it was working fine for me using jack_transport, so I > > think > > > it is quite possible that something is going wrong in qjackctl. It would > > be interesting to trace the jack calls in qjacktl to confirm whether or > > not it is sending the transport stopped messages, and if so figure out > > what is causing it to do so. > > qjackctl issues jack_transport_stop() when you press its "pause" button. > similarly, jack_transport_start() when you press the "play" button. "rew" > and "ffwd" buttons just do de/incremental jack_transport_locate()'s -- this > has been like so and quite happily for way more than 5 years now :) > > it is funny that when you put lives in the picture and things behave > strangely you infer that the problem is something else. you already made > evidence that when *lives is not running* everything works as expected. > > imho, i'll reiterate that you should revise lives' jack_sync_callback, > probably it is misunderstanding the jack transport sync api protocol, > somehow. > > cheers Hi list, hi Salsaman, hi Rui. Disturbing result: I discovered that QJackCtl, running all by itself with no other apps running, exhibits the problem. Run QJackCtl. Set the Jack size to a relatively high value like 1024 or 2048. Now play the transport. In the majority of attempts it will not start - goes into stop immediately. If it does manage to start, try FF or REW. Again, in the majority of attempts it will stop. Rui can you please take a look and try that simple test to verify? I broke in with KDbg, and it is calling qjackctlMainForm::transportStop() Looking at the stack trace, as far as I can tell: It seems that in qjackctlMainForm::refreshStatus() in the line: bool bPlaying = (tstate == JackTransportRolling || tstate == JackTransportLooping); bPlaying is false because the tstate is either JackTransportStopped (in the case of hitting play), or JackTransportStarting (in the case of hitting FF or REW while playing). This eventually seems to cause the call to qjackctlMainForm::transportStop() via the line: m_ui.PlayToolButton->setChecked(bPlaying); But I'm not sure because the stack trace is a bit hard to follow. Maybe in the end it is a Jack or even a system problem, really I just want to solve this. It's driving me nuts for months now. So I need your help to identify where the problem lies. Is it Jack or what? Thank you for your consideration. Tim.

15 years, 10 months

Re: [LAD] [LAA] [ANN] guitarix-0.07.0 release 'reloaded'

by Andreas Degert

2010/3/29 torbenh <torbenh(a)gmx.de>: > On Sun, Mar 28, 2010 at 11:33:12PM +0200, Andreas Degert wrote: >> >> - --quit doesn't work (unknown dbus command) > > yes. its not implemented yet. > >> - --quitas saves but doesn't quit the application > > the patch doesnt obey quit. i mailed it a bit too fast. > sorry. > >> - --quitas and --saveas only seem to save when called the first time with >> a session name > > do you mean a specifying the same session name twice ? > the SM refuses to overwrite existing sessions. > it doesnt print the error code, i think. > > i really need to give pyjacksm some love. i was focussing on getting > a couple of apps patched, and mainly tested using > > jack_session_notify save /full/path/to/session_dir > > it should be working correctly in jack1 svn r3976 > > >> >> - --load gives an exception, but works after killing the daemon > > i will go over jacksm now. > in dbus mode there are some problems. > >> >> - the saved command line contains -f ${SESSION_DIR}guitarix.state, but >> SESSION_DIR doesn't end with a /. Is just the slash missing in the >> command line or is the value of SESSION_DIR wrong (for now i have >> added a "/") ? > > yes. the slash was missing from the replaced value. > fixed in jacksm git now. > > the separators are os dependent. and i wanted to leave them out of the > API as much as possible. The current git version of jacksm works now for me. Guitarix also seems to work fine in a session, but i'm puzzled about weak linking. The function address (of jack_set_session_callback) is null depending on if its in libjack.so or not when ld is run, but independent of the version of libjack.so.0 at runtime. It seems as if the address is always bound lazily at function call time, not when the function pointer is checked for 0 (means it crashes when session support is compiled in but the libjack used at runtime doesn't support it). ciao Andreas

15 years, 10 months

[LAD] digiface vs. multiface vs. jack vs. other cards

by Fernando Lopez-Lezcano

At CCRMA we have several studios with linux computers in them (in addition to computers sprinkled throughout the building). Some of the studios have digiface interfaces, some multiface. All of them are connected to the sound system or mixer digitally through adat lightpipes. Workstations have Delta 66 or Gina3G soundcards. It would be nice for a user to be able to play, say, a stereo Ardour session in any of them without any changes to the session or routing. The digifaces send channels 1-24 out the adat ports. The multifaces on the other hand send 9-16 on the adat port. Deltas and Ginas send out stuff on channels 1-4 or 1-6. You can see the multiface interfaces are a problem. To get sound out of them you have to send on channels 9-16 which is different from _all_ others! I tried several workarounds without much success: a) fix this at the alsa level. Should be the way to go, right? Create an /etc/asound.conf that uses ttable to translate channels for the multifaces so that the digital out is actually sent through channels 1-8 (and create the same name plug interface in all other computers that does nothing so that the user can set that name as the default in qjackctl and will get the same behavior in all computers). Works, but not quite. When I try to use that "fake" plug interface with jack2 I get a warning that I'm using a plug interface (sort of fair) and jack only opens it with _2_ i/o channels (even though the ttable is 18 channels wide!). If I _force_ input and output channels in jack to 18 it does work fine. But now it will _not_ work on other computers that have less (or more) than 18 channels. Argh. b) fix it in hdspmixer. Well, it turns out that hdspmixer does not read the default matrix gains from a file so I can't really override the default. AFAICT the gains are calculated algorithmically in the code and there is no command line option to load presets from a file. Or I could write a small script that will set the right gains for 1-8 to go out through 9-16 but if a user starts hdspmixer that gets undone with no warning. And, of course: c) give up and connect an 8 channel analog snake to the analog outputs of the multifaces and do away with a digital connection to the mixer... Anyone has any other suggestions?? This should be easy to fix, right? :-) -- Fernando

15 years, 10 months

[LAD] [OT] Turing machine

by fons＠kokkinizita.net

If you know Turing's 'Computable Numbers' you may enjoy this: <http://aturingmachine.com> Ciao, -- FA O tu, che porte, correndo si ? E guerra e morte !

15 years, 10 months

[LAD] [LAA] [ANN] guitarix-0.07.0 release 'reloaded'

by hermann

guitarix is a simple Linux Rock Guitar amplifier and is designed to achieve nice thrash/metal/rock/blues guitar sounds. Guitarix uses the Jack Audio Connection Kit as its audio backend and brings in one input and two output ports to the jack graph. Release 0.07.0 comes with a bunch of major changes : * nearly complete reworked source by Andreas Degert * amp and effect units based direct on faust expressions * all faust sources included * new accumulated tuner unit with new interface (analogue Style needle meter) * Midi controller connections could saved with in presets and/or general * a editable Midi controller map is available * new human readable preset style * knobs could be used like sliders (press ctrl + mouse-button and move the mouse horizontal, leave the ctrl and hold mouse-button for fine tune), or like real knobs (turn them around) * convolution unit based on zita-convolver is now integrated in the engine * presets could change with Midi Program Messages * I'm sure I have some things forgotten to mention here. Check out the new great sound of the faust optimized sources. To the midi learn function: a middle mouse button click on a controller pop's up a little widget, move the midi controller you will use, the controller number is shown in the widget. Press OK when you've done. That's it. By the way, a right click on a controller pop up a spinbox for direct enter the value with your keyboard. have fun ________________________________________________________________________ guitarix is licensed under the GPL. Project page with screenshots: http://guitarix.sourceforge.net/ download: http://sourceforge.net/projects/guitarix/ please report bugs or suggestions here: http://sourceforge.net/apps/phpbb/guitarix/ For capture, guitarix uses the great 'jack_capture' (version >= 0.9.30) written by Kjetil S. Matheussen. If you don't have it installed, you can look here: http://old.notam02.no/arkiv/src/?M=D For extra Impulse Responses, guitarix uses the zita-convolver library by Fons Adriaensen. If you don't have it installed, you can look here: http://www.kokkinizita.net/linuxaudio/index.html We use faust to build the amp and effects and will say thanks to : Julius Smith http://ccrma.stanford.edu/realsimple/faust/ : Albert Graef http://q-lang.sourceforge.net/examples.html#Faust : Yann Orlary http://faust.grame.fr/ For faust users : You could find the tools we use to convert (and plot) the resulting faust cpp files to the needed include format in the /guitarix/tools directory. Faust dsp files are in /guitarix/src/faust and the resulting cc files are in /guitarix/src/faust-cc As default we have disable faust for build, if you wane play with the faust expressions, simply add --faust to the ./waf configure step, then faust will be used to rebuild the included faust-cc files. regards Hermann Meyer, James Warden, Andreas Degert

15 years, 10 months

[LAD] [LAA][ANN] first release of aj-snapshot

by lieven moors

I would like to announce that I've written a small command line utility to store/restore all current JACK and/or ALSA (midi) connection to/from an XML file. I've released it under GPLv3, and you can download the tarball at: http://sourceforge.net/projects/aj-snapshot/ You can also clone the git repository with: git clone git://gitorious.org/aj-snapshot/aj-snapshot.git Bugs can be reported at sourceforge, and I'll be around for any questions on this list. Since I'm not an experienced developer, I would appreciate feedback on the actual code, if anyone cares to have a quick look... Greetings, Lieven Moors

15 years, 10 months

Re: [LAD] automation on Linux (modular approach)

by alex stone

Incidentally, there is an excellent app called jm2cv that does a good job of "converting" cv data to jackmidi (and vice versa) written by Peter Nelson. (See the non-mixer webpage for details) So if your particular app of choice has midi out for automation, you can direct it to a CV in port for, as an example, fader control in non-mixer. Just start jm2cv, and ports in and out of it in your favourite patchbay. Simple stuff. Alex. -- www.openoctave.org midi-subscribe(a)openoctave.org development-subscribe(a)openoctave.org

15 years, 10 months

[LAD] Again MIDI jitter - tested with Fons test applications

by Ralf Mardorf

Regular it shifted between 2395 and 2404, but with a few exceptions, one time 2302, three times 2304, two times 2305 and two time 2494. See attachment. What might cause this exceptions? Could it be access to the RAM by the graphics? Is there something bad because of the IRQs? Regular shift 2404 - 2395 = 9 frames of jitter, exceptional maximal shift 2494 - 2302 = 192 frames of jitter. I guess this does mean ... 5.3 ms / 512 frames = 0.010351562 ms/frame Maximal difference for regular jitter 0.093164062 ms. Maximal difference for exceptional jitter 1.9875 ms. ... am I wrong? When I once tested it by recording I got this result for ALSA MIDI on Linux, Cubase runs on Windows on the same machine: ||Cubase|HR tmr|System|PCM pl|PCM ca ------++------+------+------+------+------ 500.0 || 493.0| 504.9| 505.6| 503.4| 503.2 1000.0|| 993.4|1005.4|1005.8|1005.3|1006.4 1500.0||1494.5|1503.6|1506.4|1507.4|1507.3 2000.0||1994.8|2003.8|2007.2|2007.9|2009.5 2500.0||2492.4|2504.1|2504.3|2503.6|2503.2 3000.0||2992.9|3006.0|3006.2|3005.9|3007.6 3500.0||3493.7|3502.7|3505.4|3506.5|3509.5 4000.0||3994.6|4003.1|4003.2|4008.8|4009.9 msec +/- 0.1 msec maxDif|| 4.8| 6.0| 7.2| 8.8| 9.9 minDif|| -2.4| -2.7| -3.2| -3.4| -3.2 --------------+------+------+------+------ Jitter|| 2.4| 3.3| 4.0| 5.4| 6.7 msec +/- 0.2 msec It's impossible to make music using external MIDI equipment and ALSA MIDI on my machine and for Windows it isn't really much better. While the test using Fons apps resulted with 1.9875 ms (if I understand it correctly) for JACK MIDI, my tests resulted with 4.0 ms for the system timer using ALSA MIDI. If you play one drum sound after the other using hardware MIDI and you record one sound after the other to audio tracks, than jitter needs to be less 2 ms. I don't know how much under 2 ms, but more than 2 ms is audible and sounds horrible. spinymouse-sudo@64studio:~$ hwinfo | grep irq [snip] irq:1 0 ( 133) "timer" irq:0 1 ( 7480) "i8042" irq:1 4 ( 3) "serial" irq:1 7 ( 0) "parport0" irq:0 8 ( 1) "rtc0" irq:0 9 ( 0) "acpi" irq:0 12 ( 300250) "i8042" irq:1 14 ( 28748) "ide0" irq:0 16 ( 1) "ohci_hcd:usb1" irq:0 17 ( 12747) "ohci_hcd:usb2" "ohci_hcd:usb5" irq:0 18 ( 2) "ohci_hcd:usb4" "ohci_hcd:usb6" "radeon@pci:0000:01:05.0" irq:0 19 ( 2) "ehci_hcd:usb3" irq:0 21 ( 246087) "ICE1712" irq:0 22 ( 23094) "ahci" "firewire_ohci" irq:0 25 ( 1925) "eth0" used irqs: 0,1,4,7,8,9,12,14,16,17,18,19,21,22,24,25 spinymouse-sudo@64studio:~$ uname -a Linux 64studio 2.6.31.12-rt20 #1 SMP PREEMPT RT Sun Feb 7 13:55:55 CET 2010 x86_64 GNU/Linux spinymouse-sudo@64studio:~$ cpufreq-selector -g performance spinymouse-sudo@64studio:~$ jackd -Rdalsa -dhw:0 -r96000 -p512 -n2 -Xseq jackdmp 1.9.3 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 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 JACK server starting in realtime mode with priority 10 creating alsa driver ... hw:0|hw:0|512|2|96000|0|0|nomon|swmeter|-|32bit Using ALSA driver ICE1712 running on card 0 - TerraTec EWX24/96 at 0xcf00, irq 21 configuring for 96000Hz, period = 512 frames (5.3 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 port created: Midi-Through:midi/playback_1 port created: Midi-Through:midi/capture_1 port created: TerraTec-EWX24/96:midi/playback_1 port created: TerraTec-EWX24/96:midi/capture_1 port created: USB-Device-0x170b:0x11:midi/playback_1 port created: USB-Device-0x170b:0x11:midi/capture_1 ###################################################################### spinymouse-sudo@64studio:~$ cat /usr/src/jack_midi_test/jack_send.cc [snip] // This list of note on/off events is sent // in an endless loop, one item every DELTA // audio frames, on channel CHANNEL. // Note Notes [NNOTES] = { { 0x90, 48, 100 }, { 0x80, 48, 0 }, { 0x90, 50, 100 }, { 0x80, 50, 0 }, { 0x90, 52, 100 }, { 0x80, 52, 0 }, { 0x90, 53, 100 }, { 0x80, 53, 0 }, { 0x90, 55, 100 }, { 0x80, 55, 0 }, { 0x90, 57, 100 }, { 0x80, 57, 0 }, { 0x90, 59, 100 }, { 0x80, 59, 0 }, { 0x90, 60, 100 }, { 0x80, 60, 0 } }; [snip] spinymouse-sudo@64studio:~$ qjackctl ###################################################################### spinymouse-sudo@64studio:~$ /usr/src/jack_midi_test/jack_recv ###################################################################### spinymouse-sudo@64studio:~$ /usr/src/jack_midi_test/jack_send ###################################################################### Connected: jack_send out --> system midi_playback_3 system midi_capture_3 --> jack_recv in Results: 2400 2400 2401 2401 2400 2401 2399 2399 2400 2400 2399 2402 2400 2400 2400 2400 2400 2401 2398 2401 2400 2401 2400 2402 2399 2400 2399 2401 2400 2402 2400 2402 2396 2402 2399 2400 2401 2399 2402 2399 2400 2400 2399 2400 2401 2401 2399 2401 2399 2401 2400 2399 2401 2400 2400 2400 2401 2399 2400 2400 2400 2401 2400 2399 2402 2400 2400 2401 2401 2400 2399 2400 2400 2400 2402 2304 2494 2401 2400 2400 2398 2404 2398 2402 2399 2400 2400 2403 2398 2398 2402 2400 2401 2401 2400 2401 2399 2400 2400 2401 2401 2399 2399 2400 2401 2400 2401 2401 2401 2398 2400 2400 2400 2402 2400 2400 2398 2400 2401 2402 2401 2397 2400 2400 2400 2401 2402 2400 2399 2399 2401 2399 2402 2399 2400 2399 2401 2401 2398 2401 2401 2399 2400 2400 2400 2401 2401 2398 2401 2400 2401 2401 2401 2400 2399 2399 2400 2401 2400 2398 2401 2401 2399 2400 2401 2400 2402 2398 2400 2400 2400 2400 2402 2398 2401 2400 2402 2399 2399 2402 2399 2400 2400 2399 2403 2400 2399 2401 2401 2400 2401 2400 2398 2401 2400 2400 2402 2399 2400 2399 2401 2400 2401 2402 2398 2400 2400 2401 2400 2400 2401 2399 2400 2400 2400 2402 2399 2399 2400 2400 2400 2402 2400 2400 2400 2399 2400 2400 2402 2399 2399 2400 2401 2400 2400 2402 2399 2400 2400 2400 2402 2399 2401 2400 2399 2399 2400 2399 2403 2400 2399 2400 2400 2400 2401 2398 2403 2398 2401 2399 2402 2400 2401 2399 2399 2401 2400 2399 2402 2399 2399 2401 2401 2399 2402 2400 2399 2400 2400 2399 2401 2403 2398 2400 2400 2398 2404 2398 2401 2400 2400 2401 2400 2400 2401 2398 2399 2401 2400 2402 2402 2397 2401 2400 2400 2401 2400 2401 2398 2401 2400 2399 2402 2402 2400 2397 2402 2399 2402 2399 2400 2399 2401 2402 2399 2399 2399 2399 2402 2400 2402 2398 2402 2399 2401 2399 2400 2400 2403 2399 2399 2403 2302 2492 2309 2498 2399 2398 2304 2498 2401 2399 2399 2400 2401 2400 2401 2402 2397 2399 2305 2400 2402 2495 2399 2400 2304 2401 2400 2402 2494 2305 2400 2399 2401 2497 2302 2401 2400 2400 2400 2402 2401 2398 2401 2399 2400 2401 2402 2396 2403 2400 2400 2400 2401 2401 2398 2401 2400 2400 2402 2399 2402 2397 2401 2400 2401 2401 2399 2400 2400 2399 2401 2401 2401 2398 2401 2400 2400 2401 2402 2402 2396 2400 2400 2400 2403 2398 2400 2399 2402 2399 2402 2400 2399 2400 2399 2401 2401 2402 2398 2399 2400 2400 2401 2401 2400 2400 2399 2400 2400 2402 2401 2403 2395 2400 2400 2400 2400 2400 2400 2399 2401 2400 2400 2400 2402 2399 2399 2400 2401 2400 2399 2403 2399 2399 2400 2399 2403 2401 2397 2402 2399 2401 2400 2399 2404 2397 2401 2399 2402 2400 2402 2396 2402 2399 2400 2401 ^C spinymouse-sudo@64studio:~$

15 years, 10 months

[LAD] automation on Linux (modular approach)

by fons＠kokkinizita.net

(forgot to copy this to LAD) On Wed, Mar 24, 2010 at 06:45:00PM -0400, Paul Davis wrote: > On Wed, Mar 24, 2010 at 5:59 PM, <fons(a)kokkinizita.net> wrote: > > > When connected via a loopback on a HW interface > > I expected the worst case to be events quantised > > to Jack period (256 frames). Actually it's 10 times > > what bridge were you usng between JACK and ALSA? It was -X raw. I just repeated the test with -X seq and that provides a completely different picture. Jitter is +/- 2 frames, with occasional outliers at around 160 frames, nothing in between. That is with a 30-track Ardour session running in the background, DSP load 15%, CPU load 27%. Unpatched 2.6.32 kernel (which may explain the occasional larger error). Not bad at all. Ciao, -- FA O tu, che porte, correndo si ? E guerra e morte !

15 years, 10 months

Re: [LAD] Linux-audio-dev Digest, Vol 37, Issue 24

by Jeff McClintock

> From: David Olofson <david(a)olofson.net> > a simple synth for a small prototyping testbed I hacked the other day: What I like about this concept is that very concise code provides for full control of a note's pitch. You can play it in any scale. You synth supports microtuning. You can 'bend' a specific note while it's playing. You can play two voices in unison. These features takes pages of code in my MIDI synths. Microtuning is seldom supported by soft-synths. With your model it's difficult NOT supporting it. Jeff McClintock

15 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev