Linux-audio-user July 2005

linux-audio-user@lists.linuxaudio.org

191 participants
230 discussions

Re: [linux-audio-user] Even more music made with linux

by Kjetil Svalastog Matheussen <k.s.matheussen＠notam02.no>

James: >> http://www.notam02.no/~kjetism/mp3/preludium.ogg > >I always thought "bypass" meant "do bugger all to the signal". > >Maybe I'm wrong, but if I'm not, then you've been using Jamin as a >fancy noop in your graph. > Thats right. Everyone use Jamin and I wouldn't be any worse. However, no matter what I did, I couldn't get better sound out of it than what was already coming in, so "Bypass" was the setting that seemed to work best for preludium. >Anyway - interesting track. I was waiting for the preludium to move >onto a riffium or two, but maybe you're saving that part? Nice sound >though. > >Scared me half to death when it started to hiss and crunch at the end >- it was supposed to do that, yes? > It was intentional yes. :-) But you are kind of hurting my feelings now. That "hiss and crunch", as you call it, is actually the sound of when I'm trying to sing very seriously! ;-) >Good work - very atmospheric. Are you going to do something to >follow? Thank you very much. Perhaps there will be more parts.

19 years, 5 months

[linux-audio-user] [ANN] kluppe 0.5.1

by d13b

hi! this is the announcement of kluppe version 0.5.1 kluppe is a jackified loop-player for linux. new features since the last announcement include: *) a new homepage with documentation: http://kluppe.klingt.org *) a first step into midi support (granular mode supports pitch shift via midi) *) a number of bug fixes. download at http://kluppe.klingt.org/downloads/kluppe-0.5.1.tar.gz as always: please let me know if you run into troubles using/compiling kluppe or if you just want to suggest new features or give feedback. regards d13b -- +--------------------------------+ | kluppe audio looper v 0.5.1: | | http://kluppe.klingt.org | +--------------------------------+

19 years, 5 months

[linux-audio-user] FW: A few questions

by BJaY

Hi, I've posted this to CCRMA and LAU, hope this is OK. s/w FC3, 2.6.11-0.3.rdt.rhfc3 kernal, Ensoniq AudioPCI, acpi=off pci=noacpi no-hlt. 1) I recently upgraded from a Celeron 633 to a PIII 866 and now I can't get 48K to work properly. I set qjackctl 48000 but when I start it it reports 47010, Ardour reports 4.7K and QSynth/Fluidsynth is out of tune by about a tone. The clock also seems to be gaining time. This has happened to be before on my laptop (no upgrade, stuff was just out of tune). Suspect ACPI, any thoughts ? 2) Ardour segfaults when I try to resize (time stretch) a bit of audio (latest CCRMA reository) 3) I use the big free NS drum font and now and again, a sample sounds like it's coming from 'both' speakers rather than between them when using fluidsynth, I also happens with other fonts and non-percussive instruments, sonds like a phase shift of some sort, happends on both my machines, anyone else noticed this ? 4) I did some christmas carol arangements for guitar http://www.geocities.com/brooslea/, my first tinkerings with Lillypond, does this qualify for Made With Linux ? Has anyone got a server I can stick them on cos nobody can see them where they are. Also, any feedback on the lilyponding from lilypond guru's (in particular the placement of some of the rests) and the arrangements from guitar guru's gratefully recieved. 5) Anybody got latency figures for usb soundcards ? 6) Getting archives for ardour mailing lists - sourceforge generally. Where do I go to download a tarball of the mail archives on sourceforge ? 7) CCRMA low latency kernal : When it says experimental kernal 'may not work with your hardware' does this mean 'sound card' or are there many other issues ? 8) Issues with anacron and initial experience for music users shifting from Windows to linux : I've not seen alot of discussion about disabling various services (particualryly anacron) in install guides (CCRMA), any chance of adding this with a list of services to disable on the CCRMA install pages ? 9) Would it be a good idea to mention early on on the ccrma site that problems with sound cards should be directed at the alsa development team ? I posted some stuff to the linux-audio-dev mailing list about the trident sound driver (before I got my barings) and it took months to make its way to the alsa team. 10) Any chance of the most up-to-date version of alsa in the core repository (The one that fixes my problem (sis sound chip)) ? As I understand it, if you want to recompile alsa, you have to recompile ther kernal (somthing I have not yet had the guts to do) and I understand it can take all night. 11) Any chance you could add the business of alsa not starting properly on FC3 to CCRMA install documentation. Alot of pelple aquire their FC distributions from the back of a book or download it and then take a long time to become aware of the updates (that seem to fix the problem). This one took me ages. Thanks for all your help - IT WORKS ! Cheers, Bruce.

19 years, 5 months

[linux-audio-user] FOMUS

by David Psenicka

I'd like to announce a new project, "Fomus." Fomus is a music notation tool in Lisp for computer music composers that converts "raw" musical data into an output file or files suitable for loading into several different notation programs. The purpose is to provide a better alternative to current options for importing data and formatting it into a score. The program tries to automate a variety of tasks including note spellings, distribution of notes across voices and staves, clef signatures, ottava brackets, combining notes and rests in multiple-voice parts, and (maybe one of the more useful functions) quantizing note offsets and durations by finding combinations of tuplets/beat divisions that minimize the amount of error. Support also exists for articulation markings including slurs, other markings like text and dynamics, and some special types of notation like tremolos, harmonics (some of these aren't implemented yet). It can also be used as a Common Music backend, and will use some of CM's functionality if present. Fomus is still in its initial testing/development stage so many bugs exist, some minor things aren't implemented yet (including backends--it only outputs LilyPond files at the moment), the documentation needs to be finished, the interface needs to be simplified, etc.. This project grew out of a smaller collection of Lisp functions I've been using over the past few years to notate my own pieces. The main website is at http://common-lisp.net/project/fomus/doc/ and contains instructions for CVS download. At the moment the program should compile in the latest versions of CMUCL and SBCL on Linux and CMUCL and OpenMCL in Darwin (it won't compile in Darwin SBCL at the moment). Any comments, feature requests and bug reports are welcome from anyone interested in using it and seeing it develop--there is a mailing list link on the website. (I apologize for the cross-posting.) -David Psenicka

19 years, 5 months

Re: [linux-audio-user] Usability vs Intuitability in Ardour

by Renick Bell

> > nothing other than its an impediment to getting started..most apps > > including mac/win DAWs and word processors let you create an untitled > > proj without first prompting for a save location..but agree copying > > 80gb would be bad.. > > yes, and we've wondered how they manage to do that and discussed it > several times over on #ardour. we have never come up with a solution > that felt "right" for a potentially multi-user system. For what it's worth, I've just switched (about a month ago) to Ardour from Cubase SX. In Cubase, I am required to choose or create a project folder as soon as I start a new project. Ardour's requirement for the same was completely natural for me. Making people think a bit before they jump seems like a good idea to me. I really don't understand most of the complaints about Ardour's usability, at least for experienced DAW users. I've been using Cubase for eight years, and I've mixed a handful of sessions in ProTools. For me, getting used to Ardour just required an afternoon reading the wiki and a couple of ignorant questions in #ardour that had been answered in the documentation. The lack of tools (scissor, eraser, etc) threw me off at first, but I've found that the reduction in mousing by using the keyboard more really improved my speed (and reduced the pain in my wrist). How to do these operations was explained in the documentation. Wishing that one could operate a tool of this complexity without reading the manual is absurd. Just aping what other apps have done for familiarity's sake also doesn't make sense. Had Ardour had a scissor tool in the toolbar, I might not have ever realized there was a better way of working. My biggest gripe (which is still a trivial one) was about the lack of anti-aliased text in the interface, and that seems to be coming soon. -- Renick Bell http://www.the3rd2nd.com

19 years, 5 months

[linux-audio-user] audacity and jack

by Brad Fuller

I've seen several messages describe audacity usage with jack. I searched for a package like this and also looked at the source doc to see if I could build it in. I don't see anything. Do I need to build audacity with the portaudio=v19 switch to obtain it? Or, is audacity even jack aware? -- Brad Fuller (408) 799-6124 ** Sonaural Audio Studios ** (408) 799-6123 West San Jose (408) 799-6124 Cambrian ________________________________ Hear us online: www.Sonaural.com

19 years, 5 months

[linux-audio-user] Mastered in Ardour and JAMin

by Bob

Hi All Take a listen! Ardour and JAmin really doing their thing! http://www.hearmymusic.co.uk Also just Mastered four Long speeches, over an hour long each, with no dropouts or Glitches., and they really needed some work!! Cheers Bob

19 years, 5 months

[linux-audio-user] El-Cheapo success with alsa lib 1.0.8 but not with 1.0.9

by Salvatore Di Pietro

HI all, I managed to combine 2 Sb Live (a 5.1 Digital and a 5.1 Player one) in a single 4 in 4 out device following the El-Cheapo HOWTO. The thing used to work flawlessly on my system: Slackware 10.1 kernel 2.6.12.2 vanilla (but older versions worked equally well) ALSA 1.0.8 JACK 0.99.0 all compiled from sources AMD Athlon XP 3000+ AsRock K7S8X SB Live! Digital 5.1 SB Live! Player 5.1 ForteMedia FM801 RTL8139 Matrox G450 DualHead AGP every card runs on its own IRQ: root@slack101-sal:/home/salvuz# cat /proc/interrupts CPU0 0: 3067468 IO-APIC-edge timer 1: 4252 IO-APIC-edge i8042 8: 0 IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 12: 68805 IO-APIC-edge i8042 14: 130386 IO-APIC-edge ide0 15: 107823 IO-APIC-edge ide1 16: 0 IO-APIC-level FM801 17: 2080 IO-APIC-level eth0 18: 1138 IO-APIC-level EMU10K1 19: 0 IO-APIC-level EMU10K1 20: 0 IO-APIC-level ohci_hcd:usb2 21: 0 IO-APIC-level ohci_hcd:usb3 23: 0 IO-APIC-level ehci_hcd:usb1 NMI: 0 LOC: 3067418 ERR: 0 MIS: 0 With this setup I was used to little or no xruns even at 128 frames per buffer. But upon upgrading to ALSA 1.0.9 (and later releases) I get (no matter if via command line or qjackctl): root@slack101-sal:/home/salvuz# jackd -R -v -dalsa -d multi4 getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_oss.so getting driver descriptor from /usr/lib/jack/jack_alsa.so jackd 0.99.0 Copyright 2001-2003 Paul Davis 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 registered builtin port type 32 bit float mono audio running with uid=0 and euid=0, will not try to use capabilites loading driver .. new client: alsa_pcm, id = 1 type 1 @ 0x805bad0 fd = -1 creating alsa driver ... multi4|multi4|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames, buffer = 2 periods Couldn't open multi4 for 32bit samples trying 24bit instead Couldn't open multi4 for 24bit samples trying 16bit instead Couldn't open multi4 for 32bit samples trying 24bit instead Couldn't open multi4 for 24bit samples trying 16bit instead new buffer size 1024 registered port alsa_pcm:capture_1, offset = 4096 registered port alsa_pcm:capture_2, offset = 8192 registered port alsa_pcm:capture_3, offset = 12288 registered port alsa_pcm:capture_4, offset = 16384 registered port alsa_pcm:playback_1, offset = 0 registered port alsa_pcm:playback_2, offset = 0 registered port alsa_pcm:playback_3, offset = 0 registered port alsa_pcm:playback_4, offset = 0 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. -- jack_rechain_graph() 4576 waiting for signals [sits there for about seven seconds...] jackd watchdog: timeout - killing jackd Killed root@slack101-sal:/home/salvuz# zlorfik! :) If I reinstall _only_ alsa-lib-1.0.8 (having removed alsa-lib-1.0.9) keeping the reast of ALSA to 1.0.9, everything returned to work, so I think something changed in alsa lib 1.0.9 that causes trouble to this setup... Anyone else tried building an El-Cheapo multi I/O and noticed the same thing with alsa-lib 1.0.8->1.0.9 ? ciao -- salvuz POST FATA RESVRGO Linux registered user #291700 | machine #174619 get counted on ---> http://counter.li.org/ <---

19 years, 5 months

Re: [linux-audio-user] Usability vs Intuitability in Ardour

by eviltwin69＠cableone.net

On Tue, 26 Jul 2005 10:57 , Eric Dantan Rzewnicki <rzewnickie(a)rfa.org> sent: >On Tue, Jul 26, 2005 at 11:03:49AM +0100, Steve Harris wrote: >> On Tue, Jul 26, 2005 at 10:36:10 +0100, tim hall wrote: >> > Last Monday 25 July 2005 22:15, Kevin Cosgrove was like: >> > > On 25 July 2005 at 15:46, Ben Loftis ben(a)glw.com> wrote: >> > > > Most professional audio gear is like a bicycle. A bike is >> > > > certainly not intuitive to a first time user, but once you >> > > > learn how to balance, steer, etc, you can get around faster >> > > > than someone on foot. This has sometimes been described as >> > > > "intuitable" rather than intuitive. >> > > Or, "discoverable" versus "usable". >> > > Word is easy to discover for easy things to do. 'vi' is >> > > *much* faster, if my 'vi' speed versus the 'Word' speed of my >> > > compatriots is any gauge. Pull-down menus are "intuitive", where >> > > as hot-keys are not. But, hot-keys get the work done quickly >> > > once they're known. Pull-down menus which list their hot-key >> > > shortcuts in the menu are quite nice for me. The Opera web >> > > browser is one example of this. >> > Thanks Kevin. All keybindings have to be learned. I can't use vi without >> > constant reference to the manual. I dare say the same would be true of emacs. >> > I dislike them both and use nedit for everything, simply because it works >> > much more like a Windows based editor, so I had to relearn less in order to >> > get typing when I first migrated. It's nothing to do with intuitabilty either >> > - old habits die hard. >> True, you have to decide wether its worth the effort. When I started >> developing on UNIX machines I watched the old hands and relaised that 1) >> they were all much faster than me, and 2) they (almost) all used vi. So I >> took the effort to learn, in the knowledge that I would spend a lot of my >> life typing. It took makes months to be able to fly vi, but now you can >> prise it from my cold dead fingers. >> I experience extreme discomfort when forced to use a non-modal editor, >> and when I have to go through afterwards and remove all the ^[hhhhhhcw >> afterwards :) >> For anyone whos thinking of learning, dont start by trying to digest it >> all, just start with i A yy dd, and go from there, its all pretty >> logical when you get into it. > >Yes. I find vi to be very intuitive. > iiiiime too:wq!

19 years, 5 months

Re: [linux-audio-user] Usability vs Intuitability in Ardour

by eviltwin69＠cableone.net

On Tue, 26 Jul 2005 11:37 , luis jure <ljc(a)internet.com.uy> sent: >el Tue, 26 Jul 2005 09:17:53 -0400 >Brett McCoy idragosani(a)chapelperilous.net> escribió: > > >> Real Programmers use cat... > >maybe, yes. but REAL-REAL Programmers punch ones and zeros directly on the >surface of the hard disk with the tip of a magnetized needle. or something. > >but i still don't know what REAL-REAL-REAL-REAL Programmers use. anyone? Punch paper tape and the damn switches on the front panel of course.

19 years, 5 months

← Newer
1
...
4
5
6
7
8
9
10
...
23
Older →

Jump to page:

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-user July 2005