music July 2010

music@lists.fedoraproject.org

18 participants
32 discussions

Audio testers wanted
by Development discussions related to Fedora 17 Jul '10

17 Jul '10

Hi, there are some audio applications that need a bit of wider testing. Please add a comment in bodhi for the packages and thumbs up/down as appropriate: rakarrack-0.5.8: rawhide https://admin.fedoraproject.org/updates/rakarrack-0.5.8-2.fc13 https://admin.fedoraproject.org/updates/rakarrack-0.5.8-2.fc12 EL-6 audacity-1.3.12-0.4.beta: rawhide https://admin.fedoraproject.org/updates/audacity-1.3.12-0.4.beta.fc13 https://admin.fedoraproject.org/updates/audacity-1.3.12-0.4.beta.fc12 EL-6 (freshly built) Thanks for your assistance, David.

4 5

Re: [Fedora-music-list] [PlanetCCRMA] [LAD] FIxed alsa-tools' envy24control missing peak level meters and "Reset Peaks"
by Niels Mayer 16 Jul '10

16 Jul '10

On Fri, Jul 16, 2010 at 5:27 AM, Geoff King <gsking1(a)gmail.com> wrote: > Niels, Thank you for taking the time to work on improving Envy24Ctl. > I tried your patch for the peaks and it seemed to work fine for me. I > can't comment on the code (as I'm much more musician than programmer), > but had no problem patching and installing. Looking forward to trying > this new patch and whatever else you come up with. Geoff Geoff -- thank you for trying out the patch! (And, OT, thanks for working w/ Rui to help fix http://sourceforge.net/tracker/?func=detail&atid=733076&aid=3021645&group_i… :: "help fix qtractor crash on bus changing/configuration (3021645)" -- Envy24 and multichannel qtractor users, yes, it's time for a "svn up" ). FYI, to try out the new levelmeters "easy", if you're running Fedora x86_64, use the "envy24control" binary directly, or drop the levelmeters.c file into your build: http://nielsmayer.com/npm/Efficient-Meters-Envy24Control.tgz ( for details http://nielsmayer.com/npm/Efficient-Meters-Envy24Control.README ) ........ On a completely different "note" the envy 24 manual ( http://alsa.cybermirror.org/manuals/icensemble/envy24.pdf ) has interesting info on the envy24 digital mixer that I've snapshotted: Diagram: http://nielsmayer.com/npm/envy24mixer-architecture.png Note the way it truncates in the mixer: the more inputs you "mix" at once, the fewer bits each input source gets, and it's not clear what kind of dither, or it's a straight truncate of 24... ultimately the envy24 seems oriented towards producing a 16 bit, and not 24 bit master (which makes sense given that the chip is well over a decade old and HD audio production for "prosumer" was rare): .......... 4.5.5 Multi-Track Digital Monitoring The Envy24 integrates a 36-bit resolution digital hardware mixer. The width of the data path is strictly to ensure that during processing of all the channels, under any condition, no resolution is lost. The dynamic range of the end user system will be limited by the range of the physical output devices used. In order to maintain identical gain to the input stream (i.e. 0dB), the resulting 24-bit is not msb-aligned to the 36-bit. The overflow bits correspond to the analog distortion due to saturation. The user would need to reduce the overall attenuation of the inputs to avoid clipping. Insertion of the digital mixer adds only a single sample cycle delay with respect to the original data. This extremely low latency all digital mixer provides monitoring functionality and can replace a traditional external analog input mixer. There are 20 independent audio data streams to mix and control the volume. ... .............. --Niels http://nielsmayer.com

1 0

Re: [Fedora-music-list] [LAD] FIxed alsa-tools' envy24control missing peak level meters and "Reset Peaks"
by Niels Mayer 15 Jul '10

15 Jul '10

On Tue, Jul 13, 2010 at 9:54 PM, Niels Mayer <nielsmayer(a)gmail.com> wrote: > As a second patch (coming soon), I've rewritten the meters in a more > sensible fashion, drawing a single rectangle to represent the > instantaneous level (2-3 X-primitive draws per meter total and one > blit, versus hundreds of draws and a blit per value change per meter > in the original code). Patch for https://bugzilla.redhat.com/show_bug.cgi?id=602903 (see also http://old.nabble.com/FIxed-alsa-tools'-envy24control-missing-peak-level-meters-and-"Reset-Peaks"-ts29144830.html ) (1) http://nielsmayer.com/npm/Screenshot-Efficient-Meters-Envy24Control.png * To see what the new meters look like. (2) http://nielsmayer.com/npm/Efficient-Meters-Envy24Control.tgz * Contains levelmeters.c and x86_64 binary 'envy24control' that should at least work on Fedora 12 and OpenSuse and other 2.6.32-based distros. (3) http://nielsmayer.com/npm/Efficient-Meters-Envy24Control.patch * To apply the patch, grab the most recent stable release ( ftp://ftp.alsa-project.org/pub/tools/alsa-tools-1.0.23.tar.bz2 ) or git pull from trunk of the "alsa-tools" project. * After unpacking and assuming you've got the patch in ~/Efficient-Meters-Envy24Control.patch.patch do: >> cd alsa-tools-1.0.23 >> cat ~/Efficient-Meters-Envy24Control.patch | patch -p1 * It should give message "patching file envy24control/levelmeters.c" * Follow the directions to compile alsa-tools. FYI here's what my "top" processes look like when running a test to output individual streams to all 10 PCM output channels -- note X consumes between "1.7%" to "2.0 %" and "envy24control" "0.7%" to "1.0%": 15210 npm 20 0 643m 14m 8964 S 6.6 0.4 0:05.85 gst123 15184 npm 20 0 643m 14m 8984 S 6.3 0.4 0:13.11 gst123 15190 npm 20 0 643m 14m 8980 S 6.0 0.4 0:12.48 gst123 15172 npm 20 0 643m 14m 8968 S 5.6 0.4 0:15.42 gst123 15178 npm 20 0 643m 14m 8984 S 5.6 0.4 0:14.17 gst123 13684 root 20 0 527m 112m 31m S 2.0 2.8 3:26.11 X 13923 npm 20 0 863m 60m 37m S 1.0 1.5 2:49.08 plasma-desktop 14163 npm 20 0 597m 27m 15m S 1.0 0.7 1:08.29 chrome 14155 npm 20 0 1038m 170m 14m S 0.7 4.3 1:00.87 chrome 15226 npm 20 0 192m 9316 6908 S 0.7 0.2 0:00.51 envy24control Here's the envy24control from my first patch, using the original meters that cause many separate XDrawRectangles for each LED-looking segment. The performance difference is quite noticeable as the fans start running louder and the system load climbs upwards as soon as the original envy24control starts running: X consumes 5.7-10% CPU, and envy24control between 2.0% and 2.7%. 15172 npm 20 0 643m 14m 8968 S 6.1 0.4 0:53.83 gst123 15178 npm 20 0 643m 14m 8984 S 6.1 0.4 0:51.48 gst123 15190 npm 20 0 643m 14m 8980 S 6.1 0.4 0:49.60 gst123 15210 npm 20 0 643m 14m 8964 S 6.1 0.4 0:44.01 gst123 13684 root 20 0 527m 112m 31m S 5.7 2.8 3:42.78 X 15184 npm 20 0 643m 14m 8984 S 5.7 0.4 0:51.07 gst123 15398 npm 20 0 192m 9332 6908 S 2.4 0.2 0:02.32 envy24control.f 14163 npm 20 0 597m 27m 15m S 1.0 0.7 1:15.54 chrome 13923 npm 20 0 863m 60m 37m S 0.6 1.5 2:55.04 plasma-desktop Just to show that it's the same performance as the original envy24control from alsa-tools-1.0.22-1.1.fc12.ccrma.x86_64: 15178 npm 20 0 643m 14m 8984 S 6.3 0.4 1:28.72 gst123 15190 npm 20 0 643m 14m 8980 S 6.3 0.4 1:26.65 gst123 15210 npm 20 0 643m 14m 8964 S 6.3 0.4 1:20.59 gst123 15184 npm 20 0 643m 14m 8984 S 6.0 0.4 1:28.21 gst123 13684 root 20 0 527m 112m 31m R 5.6 2.8 4:21.30 X 15172 npm 20 0 643m 14m 8968 S 5.6 0.4 1:31.51 gst123 15455 npm 20 0 192m 8700 6316 S 2.3 0.2 0:01.74 envy24control 14163 npm 20 0 597m 27m 15m S 1.3 0.7 1:23.02 chrome 13923 npm 20 0 863m 60m 37m S 0.7 1.5 3:00.72 plasma-desktop -- Niels http://nielsmayer.com

1 0

Linux Group on Soundcloud--something to listen too
by Sean Beeson 14 Jul '10

14 Jul '10

Hi all, If you would like to hear what others are doing with Linux and audio there is a SoundCloud group for Linux audio there that I moderate. Feel free to let the rest of the world know about what you do. Go Linux :D http://soundcloud.com/groups/linux you'll know me as 0x1--my creative name. --Sean

1 0

FIxed alsa-tools' envy24control missing peak level meters and "Reset Peaks"
by Niels Mayer 12 Jul '10

12 Jul '10

I've been long annoyed by alsa-tools' envy24control (*) lack of peak-level indication in it's metering, and the non-implementation of its "Reset Peaks" button: https://bugzilla.redhat.com/show_bug.cgi?id=602903 I've fixed that annoyance. Now, a small white line appears above the highest level on each meter, and can be reset via "Reset Peaks" button. Original source: http://git.alsa-project.org/?p=alsa-tools.git;a=blob_plain;f=envy24control/… Patch: http://nielsmayer.com/npm/602903.patch To run this version of envy24control grab the most recent stable release ( ftp://ftp.alsa-project.org/pub/tools/alsa-tools-1.0.23.tar.bz2 ) or git pull from trunk of the "alsa-tools" project ( http://alsa-project.org/main/index.php/GIT_Server ). After unpacking and assuming you've got the patch in ~/602903.patch do: >> cd alsa-tools-1.0.23 >> cat ~/602903.patch | patch -p1 it should give message "patching file envy24control/levelmeters.c" ... follow the directions to compile alsa-tools.... Can whoever's in charge of these things commit this change "upstream" and get it to propagate to the distros? Alternately, give me commit access and I'll do it myself, if people agree this patch is worth having. Next steps: (1) Think about building-in meter ballistics from Fons Adriaensen's jkmeter ( http://www.kokkinizita.net/linuxaudio/downloads/jkmeter-0.4.0.tar.bz2 ). Which helps implent Bob Katz' "K System" ( http://www.digido.com/level-practices-part-2-includes-the-k-system.html ). Although it probably most makes sense to implement such metering on the main "digital mixer" meter of envy24control, if it's not too inefficient, I'd want it available on all meters, despite the warning from Fons ( http://old.nabble.com/First-release-of-jkmeter-td18798950.html ). > This is the type of meter you want for live recording, > mixing and mastering. It probably makes no sense to > use it on all tracks of a DAW, where keeping digital > level within limits is the main purpose of metering. (2) Fix https://bugzilla.redhat.com/show_bug.cgi?id=602900 which causes 'envy24control' to crash when given "-D" argument. and behave incorrectly when given a correct non-numeric name for an audio device: e.g. >> envy24control --card M66 >> invalid card type (driver is USB-Audio) >> envy24control --card M66 --device M66 >> Segmentation fault (core dumped) (3) Apply more reasonable defaults and automatically size to correct dimensions. I use, for example: >> envy24control --card 2 --outputs 4 --input 4 --pcm_output 8 --view_spdif_playback --midichannel 1 --midienhanced --window_width 1275 --tall_eq_mixer_heights 1 & (4) Add midi output, in addition to midi input, which would monitor the hardware peak metering from the ice1712 ("amixer -c M66 cget iface=PCM,name='Multi Track Peak',numid=45") and output a MIDI note-on on the corresponding MIDI channel whenever a specified threshold value was exceeded. This could be used to implement "automatic gain control" in association with the midi-controllable ADC gain provided by envy24control. Niels http://nielsmayer.com PS: (*) http://alsa.opensrc.org/index.php/Envy24control Cards supported by this fix: * M Audio Delta 1010 * M Audio Delta 1010LT * M Audio Delta DiO 2496 * M Audio Delta 66 * M Audio Delta 44 * M Audio Delta 410 * M Audio Audiophile 2496 * TerraTec EWS 88MT * TerraTec EWS 88D * TerraTec EWX 24/96 * TerraTec DMX 6Fire * TerraTec Phase 88 * Hoontech SoundTrack DSP 24 * Hoontech SoundTrack DSP 24 Value * Hoontech SoundTrack DSP 24 Media 7.1 * Event Electronics, EZ8 * Digigram VX442 * Lionstracs, Mediastaton * Terrasoniq TS 88

1 0

Planet SuperCollider 3.4 for Fedora 13 ?
by Bernardo Barros 12 Jul '10

12 Jul '10

Hey all, Since Plannet CCRMA is moving step by step to the new Fedora 13, it will be nice to take in mind that by chance SuperCollider is also making a major update with the 3.4 version about these days. I think that version should be the right version for PlanetCCRMA for Fedora 13, shouldn't it? I think PD-extended also have a more recent version, 0.42 I think. (and Fedora 13 rocks btw!) Best! Berrnardo

2 2

Musicians' Guide in Development; Testing Needed!
by Christopher Antila 12 Jul '10

12 Jul '10

Hello: The Docs SIG is working on a guide for some of Fedora's music and audio software, to be released with Fedora 14. The Musicians' Guide is being written primarily by me, as part of the Fedora Summer Coding program. Some of the first drafts are complete, with others being added regularly. I would greatly appreciate the help of all willing parties, to read the documents, establish and ensure consistency, and check for grammar. You are even invited to use the documents to learn the software, if you wish - all programs contain a tutorial where concepts are explained in the context of producing a useful sound file (although I assume that most subscribers to this list will already know). The following web page will be updated regularly, as new material for testing is written. https://fedoraproject.org/wiki/User:Crantila/FSC/Testing All comments and any assistance are appreciated. In particular, if you would prefer alternate programs for certain tasks, you can submit requests with reasons - I know there has been some preference shown for Denemo and MuseScore over Frescobaldi, for instance, and there are tons of helpful little programs for synthesis and DSP. Changes and additions will not make it into the Fedora 14 Guide. Regards, Christopher.

9 22

Re: [Fedora-music-list] Musicians' Guide in Development; Testing Needed!
by Philip Rhoades 12 Jul '10

12 Jul '10

People, On 2010-07-10 15:39, Orcan Ogetbil wrote: >> Christopher, >> >> I wouldn't classify myself as an "absolute beginner" but I just did: >> >> yum install qtractor >> >> which installed: >> >> qtractor x86_64 0.4.6-1.fc14 >> rubberband x86_64 1.5.0-1.fc12 >> >> I then typed: >> >> qtractor >> >> and got: >> >> qtractor: symbol lookup error: qtractor: undefined symbol: >> _ZN9QListData11detach_growEPii >> > > I see that you are using rawhide (Fedora 14 pre-alpha). I need to > remind you that this is not recommended for production machines, and > you should expect such breakages when you are using rawhide. > > With that in mind, could you post me your output of > ldd -r /usr/bin/qtractor > (Probably, the package just needs a rebuild due to a soname bump of a > library, but just to make sure) I am not desperate to get qtractor going - I was just responding to the Subject line - I thought the results might be useful for somebody. When I get time I would like to learn some more music stuff - at the moment I am just a wannabe . . Orcan, Do you still want the output of "ldd -r /usr/bin/qtractor" ? - I can send it if you like (I don't have your email address) - I lost all the recent fedora-music mails and had to recreate these ones from the web pages. Regards, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil(a)pricom.com.au

2 2

help fix qtractor crash on bus changing/configuration (3021645)
by Niels Mayer 11 Jul '10

11 Jul '10

In another thread I mentioned: > You can get it to change the number of channels, but it may crash > jackd in the process. Requiring a qtractor restart after you save the > file/template with the multichannel audio bus. This is a known bug: > http://sourceforge.net/tracker/?func=detail&atid=733076&aid=3021645&group_i… > that is still present in subversion. > Rui needs help reproducing this bug: "Crash after changing audio bus - ID: 3021645)" http://sourceforge.net/tracker/?func=detail&atid=733076&aid=3021645&group_i… If interested, please enable gdb coredumps and send backtraces in reply-all to this thread. To do this you need (1) Build from subversion a debug build: http://qtractor.sourceforge.net/qtractor-downloads.html#SVN and compile using http://qtractor.sourceforge.net/qtractor-index.html#Installation but with "/configure --enable-debug" (2) do command ' bash -c "ulimit -c" ' If it returns 0, do ' bash -c "ulimit -c unlimited" ' (3) Run Qtractor and attempt to reproduce the problem: In my case, the crash, however, isn't happeing in qtractor, it's happeing in jack2 -- which in this case for simplicitly, I'm letting qtractor startup w/o qjackctl. ( jack-audio-connection-kit-1.9.4-1.fc12.ccrma.x86_64 ) Below is the qtractor log output that happens after I go to "VIew -> Buses..." , select "Audio Master" -> "Audio" -> "Channels" --> "12" -> "Update" If I were to save the template containing these settings, I could startup qtractor in 12 channel mode. It's the updating of master bus from 2-> 12 that causes jackd to die, takes everything else down with it, and forces you to save and restart qtractor. ............. 13:05:35.220 Open session: "Untitled1". 13:05:36.689 Session started. Cannot connect to server socket err = Connection refused Cannot connect to server socket Cannot connect to server socket err = Connection refused Cannot connect to server socket no message buffer overruns no message buffer overruns jackdmp 1.9.4 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 60 audio_reservation_init Acquire audio card Audio2 creating alsa driver ... hw:M66|hw:M66|256|2|44100|0|0|hwmon|hwmeter|-|32bit Using ALSA driver ICE1712 running on card 2 - M Audio Delta 66 at 0xec00, irq 21 configuring for 44100Hz, period = 256 frames (5.8 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: MT4:midi/playback_1 port created: MT4:midi/capture_1 port created: MT4:midi/playback_2 port created: MT4:midi/capture_2 port created: MT4:midi/playback_3 port created: MT4:midi/capture_3 port created: MT4:midi/capture_4 port created: MT4:midi/capture_5 port created: BCD3000:midi/playback_1 port created: BCD3000:midi/capture_1 port created: UM-2:midi/playback_1 port created: UM-2:midi/capture_1 port created: UM-2:midi/playback_2 port created: UM-2:midi/capture_2 port created: QmidiNet:midi/playback_1 port created: QmidiNet:midi/capture_1 port created: QmidiNet:midi/playback_2 port created: QmidiNet:midi/capture_2 port created: QMidiRoute:midi/capture_1 port created: QMidiRoute:midi/playback_2 port created: QMidiRoute:midi/playback_3 port created: Qtractor:midi/playback_1 port created: Qtractor:midi/playback_2 port created: Qtractor:midi/capture_2 port created: Qtractor:midi/playback_3 port created: Qtractor:midi/playback_4 port created: Qtractor:midi/capture_4 port created: Qtractor:midi/playback_5 port created: Qtractor:midi/capture_5 13:05:37.169 Audio connections change. 13:05:37.176 MIDI connections change. 13:05:51.799 The audio engine has been shutdown. Make sure the JACK audio server (jackd) is up and running and then restart session. JackClientSocket::Read time out JackClientSocket::Read time out Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 1 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 1 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 1 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 1 JackSocketClientChannel read fail Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 7 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Cannot write socket fd = 12 err = Broken pipe Could not read result type = 2 13:05:51.971 Audio connections change. ..................... Above happening off current subversion trunk: "At revision 1597." Niels http://nielsmayer.com

1 0

Musicians' Guide Version Questions.
by Christopher Antila 11 Jul '10

11 Jul '10

Hello again: Over the past few days, I've been trying to work out details that require knowing which version of certain software will be available from Fedora's standard repository in Fedora 14. The packages are: jack-audio-connection-kit : will this be based on jack1 or jack2? qtractor : will this definitely be available? It seems to be in rawhide. supercollider-* : to confirm, these will *not* be available in F14? Also, here is a list of the other included software. If you happen to know that a program will be changed dramatically in F14, please let me know, so that it can be documented correctly. -ardour -qjackctl -frescobaldi -lilypond -solfege -rosegarden4 Thank you for your assistance! Christopher.

4 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

music July 2010