Linux-audio-user May 2004

linux-audio-user@lists.linuxaudio.org

154 participants
165 discussions

Re: [linux-audio-user] Ardour, Jack, and 2.6 kernels

by mark62756＠comcast.net

I actually get very very well latency in the 2.6.3-rc3 kernel... its the only 2.6 kernel i have used so far... and on the 2.4.23 kernel that is patched with low-latency has xrun saying 400+- ms which is crazy... and ll is turned on for sure... for 2.6 the highest i get is around 20 ms. but i am also running fluxbox which uses very little cpu.. my machine is a intel celron 533MHz with 256mb RAM with gentoo installed :) -- Marko Dimiskovski > Hi, > > torsdagen den 27 maj 2004 19.16 skrev cv223(a)comcast.net: > > So, based on Fernando's and Malcolm's advice, I decided to quit fussing > > with the 2.6 kernels and stick with the 2.4.23 that I have working to do > > some recording last night. The band came over - we were set and ready to > > go. I hit 'record' to get an idea of the drum mix (we're submixing to > > stereo) - 3 seconds in, Ardour stops with an 80ms xrun! Arrgh! I sweated > > through the rest of the evening, fearing another occurence at 3:30 into a > > 4:00 song. Fortunately, everything went ok. > > > > I guess I'm back to trying to figure out what's causing these long xruns, > > now under the 2.4.23 kernel. > > > > Do most people shut off non-essential daemons during recording sessions, or > > do any other tricks? This is kinda frustrating, as the CPU load seems > > rather low (< 15% when the xrun happened). I guess I'll test out reiserfs > > and even ext2 to see if the filesystem is the culprit. > > I actually run fullblown KDE most of the time, it works pretty well at 512x2, > I can run 256x2 but xruns get more frequent, but not unbearably so. I'm > mainly running MusE and I seldom get kicked out, but it does happen... > > There has been talk on the Jack list from time to time about adding a mode > where you won't get kicked out so easily even if Jack misses a beat. > For developing jack I think the current approach is good, the audio equivalent > of an assert, but for real usage it is a little hard on the user. Especially > if you are doing a performance, then it's devastating. > > To return to the subject, I hear others use lightweight window managers and do > stop all unnesesary services to get better stability, if you have problems it > will probably help. > > /Robert > > > > > Thanks for reading the ramble, > > > > Joel > > > > > > I guess my main motivation for trying out the 2.6 kernel is laziness. > > > > Just build the kernel and get the performance and ALSA without patches > > > > or compiling extra stuff. At least, that was _supposed_ to be the way > > > > it worked! I'll keep trying the new kernels, but keep the old faithful > > > > 2.4 kernel around for recording. > > > > > > > > I'm _still_ curious about what causes the long xruns, though. > > > > > > New versions of alsa can be compiled with the "--debug=full" option (I > > > don't think the current code in the kernel has that). That will enable > > > you to tweak a proc variable to dump the kernel stack on each xrun, it > > > is something like /proc/asound/card0/pcm0p/xrun_debug (for playback, > > > same for recording in pcm0c). "echo "2">/proc/.../xrun_debug" will turn > > > reporting on. You will get the stack traces in /var/log/messages. > > > > > > Not that you will immediately know exactly what has to be done to get it > > > fixed, of course :-) > > > > > > IMHO stick with 2.4.x, in my tests 2.6.x is not even close to being > > > ready for pro audio work. It will get better but it will take some time. > > > > > > -- Fernando > > -- > http://spamatica.se/music/

21 years, 1 month

[linux-audio-user] No MIDI output from Groove Agent under vsti

by Mark Knecht

Hi, I wonder if this is just my setup. So far I cannot get QJC to show my MIDI output from Groove Agent. Is this not supported? (That would be sad...) Are others able to get any MIDI output? MIDI input seems to be working fine. Also no audio from this one yet. The VSTi seems to run perfectly, but I don't get any sound yet. Thanks, Mark

21 years, 1 month

[linux-audio-user] vxpocket perfomance questions

by Chris Pickett

Hi, I have a VXpocket v2 running under a 2.6.5-gentoo-r1 kernel which is patched with rt caps. I find that with jackstart, I can get away with 2 periods of 512 samples if the communication is 1-way, but in duplex mode I need 2 periods of 4096 samples to avoid xruns. Surprisingly, my on-board soundcard has better performance! Is this much different under a low-latency 2.4 kernel? Would it be better if the card were hw:0 instead of hw:2? Also, is it normal for the card to distort if the PCM level is above 82? I wasn't having this distortion problem with W2K if IIRC. Cheers, Chris

21 years, 1 month

[linux-audio-user] Linux swapping / multiple swap drives

by Sampo Savolainen

Hello, Can someone tell me how Linux selects which swap to use. I know there is a swap priority, but my problem is a bit more complex. I have to hard drives, both containing swap partitions. The first hard drive also contains the OS and ardour sessions. The second hard drive is 'extra space'. I would like to use both drives for recording (not at the same time), but I'm concerned about how Linux selects which swap drive to use. Ideally, when recording to drive 1 the OS would use the swap partition on drive 2 and vice versa. I don't know enough about Linux internals, so if someone does, please could you inform me? Sampo

21 years, 1 month

[linux-audio-user] Re: Any instructions about for running a Win VSTi under vstserver (Mark Knecht)

by Kjetil Svalastog Matheussen

Mark Knecht: > Dave, > Thanks for the encouragement. Just back from lunch and trying out > Chris's suggestions about vsti as it looked simple, but so far no luck. > That's for another thread later today if I cannot get it working myself. > > One question about all of this. It appears that if I run vstserver > it attempts to start EVERY VST (or even every file!) in my vst > directory?! Is this correct? Yes, but only once. It caches the information about the plugins parameters and such. Just let it run. If it seems to hang, Ctrl-C it, and start vstserver once more. > > My version of Snd does appear to have the LADSPA 1.1 stuff built in > so possibly your example will work for me when I find a VSTi I can trust... > Thats not much point. You can't send midisignals to vst-plugins from SND. James Stone: > > > > How does that work? The "accessibility from seq24" bit, I mean. > > Preferably in terms that make sense to someone who's only passingly > > familiar with either seq24 or pd. > > seq24 will not start if vsti is running! > What? I don't have my linux-machine here so I can't test that. But it sounds very strange that you can't start seq24 if a vsti is running. What happens? Is there any messages to the console? Can you start seq24 if jack-rack is running? (the midi code in vsti is stolen from jack-rack) I'm sure either/both Rob C. Buse (author of seq24) and/or myself are interested in some bug-reports here. --

21 years, 1 month

[linux-audio-user] ANN: Linux sound theme "Borealis" v.0.5 now available...

by Ivica Ico Bukvic

Hi all, This is yet another release of what started out as an experiment and has become a pet project of mine -- desktop sounds for Linux. Changelog: *New sounds for Kmail, Kopete, Kdevelop, Ksysguard, exit session & minimize window. *Finalized 3 versions of the startup sound. *New automated install script included *Changed soundfile names to better reflect their function. *Rearranged sounds for some events *Remastered sounds for better balance *Removed addon packages. *PLEASE NOTE that Kopete sounds (and some others) are still work-in-progress... For those interested, you can find the package at its usual place: http://www.kde-look.org/content/show.php?content=12584 Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/

21 years, 1 month

Re: [linux-audio-user] Steinberg The Grand

by Kjetil Svalastog Matheussen

Carl Hetherington: > > > > I guess this should be an option. In the mean time, in the > > jackclient.c file, remove the following lines: > > > > effect->dispatcher (effect, > > effEditOpen, > > 0, 0, NULL, 0); > > > > And recompile. > > > Thanks Kjetil, that works great. The problem I'm having now (;-) is that > the audio thread gets killed by the watchdog. > If the audio thread gets killed by the watchdog, there is something serious wrong. Which watchdog, vstserver's or jack's watchdog? Does your machine freeze in ten seconds before the audio thread gets killed? > > Am I right in assuming that wine doesn't have much to do with the audio > thread? Sometimes, but it might be necesarry for the plugin developer to sometimes at least send some kind of message, with the help of wine, to the non-audio part of the plugin. I guess... > If so, what could be different about the audio code's environment > on Linux compared to windows? Any suggestions on how I can investigate > the problem? If the non-audio part of your plugin behaves strange, everything can happen (write wrong bits to memory used by the audio-part for example), so... --

21 years, 1 month

[linux-audio-user] Linux Audio on the IBM ThinkPad R50

by Dan Harper

Hi all, I just purchased an IBM ThinkPad R50 and an RME Hammerfall DSP Multiface w/ Cardbus interface. I've placed a document online about the success or failure of setting all this up with Linux. So far a success, but it's still in progress. I'll post again as it's updated. URL: http://www.danharper.org/Linux_on_the_IBM_ThinkPad_R50.html Regards, Dan -- Dan Harper http://danharper.org

21 years, 1 month

[linux-audio-user] Newbie checks in

by Jos Laake

Hi all, I'm a lifelong musician turned geek who is now returning to the music arena. I'm not new to technical issues. My day job until recently was working on real-time Linux for Sony, so I know my way around a Linux system fairly well. The music part I've got down. But music technology, well, the last time I recorded anything was on a Tascam 4-track reel-to-reel and, whoa! Things have changed! And I'm gonna need some help getting up to speed with all this cutting edge digital audio stuff available today. As an avid open source supporter, I intend to use a Linux box as a multitrack digital studio to help me bring 20 years of sidetracked musical talent back to life. But so far I've had nothing but trouble so I went looking for help and ended up here. So here's what I've got... On my main machine, I'm using RedHat 9 (kernel version = 2.4.20-6) on a little cube Pentium4 machine (Ice Cube). The audio module that RedHat came up with at configuration is: 'i810-audio' I'm also working with an old Gateway dual Pentium II runing RedHat 9 with SMP (kernel version = 2.4.20-6SMP) and this one is using a Creative Labs SoundBlaster MP3+ USB Audio unit. It comes up with an audio module called 'audio'. (I'd like to set this up for my son who is a budding guitarist). I was thinking about using the latest ALSA drivers (1.0.4) and Audacity, but, first thing first. I'm having trouble getting the ALSA drivers working. First question: Is this the best way to go? I mean, I want to do pro or near-pro quality audio, but I don't want to spend boatloads on sound cards without knowing there's good open source software to use. Thanks in advance for any and all help. ~Jos~ Jos Laake Santa Cruz, CA

21 years, 1 month

[linux-audio-user] Rosegarden mysteries

by Artem Baguinski

hello i'm trying various audio softwares and i got stuck with rosegarden. i can't figure what am i doing wrong and especially - what i am doing right when i suddenly hear it playing my music ;) here is what i'm doing: 1. start timidity $ timidity -iA Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 32768, period size 8192 bytes TiMidity starting in ALSA server mode Opening sequencer port: 128:0 128:1 128:2 128:3 i know timidity is setup correctly because i can play midifiles with it 2. start rosegarden $ rosegarden ... loads of messages, really scary ... on the console where i started timidity the following appears: --------------------------------------------------------------------------- Requested buffer size 32768, fragment size 8192 ALSA pcm 'default' set buffer size 32768, period size 8192 bytes --------------------------------------------------------------------------- 3. trying it out: i enter some notes in a notation editor, set the tracks instrument to Midi software device #1 and click the play button. i hear nothing, the blue cursor doesn't move, on the console the following apears: --------------------------------------------------------------------------- rosegarden (sequence manager): ControlBlockMmapper::updateMetronomeForPlayback: muted=true rosegarden (sequence manager): SequenceManager::play() - starting to play AlsaDriver::stopClocks AlsaDriver::stopClocks: ALSA time now is 0.000000000R rosegarden (sequencer): mmapping /tmp/kde-artm//segment_87d60e0 rosegarden (sequencer): MmappedSegment::map() : 0x4223c000,212 rosegarden (sequencer): mmapping /tmp/kde-artm//rosegarden_metronome rosegarden (sequencer): MmappedSegment::map() : 0x4223d000,25172 rosegarden (sequencer): mmapping /tmp/kde-artm//rosegarden_tempo rosegarden (sequencer): MmappedSegment::map() : 0x42244000,4 rosegarden (sequencer): mmapping /tmp/kde-artm//rosegarden_timesig rosegarden (sequencer): MmappedSegment::map() : 0x42245000,4 rosegarden (sequencer): RosegardenSequencerApp::play() - starting to play AlsaDriver - initialisePlayback rosegarden (sequencer): [calling jumpToTime on start] rosegarden (sequencer): jumpToTime( 0.000000000R) processMidiOut[0]: event is at 0.000000000R ( 0.000000000R ahead of queue time) processMidiOut[0]: instrument 2016 -> output device 128:0 pitch: 64, velocity 100, duration 0.500000000R AlsaDriver::startClocks AlsaDriver::startClocks: started clocks RosegardenSequencerApp::incrementTransportToken: incrementing to 14 rosegarden (sequencer): Sequencer status changed from 0 to 1 --------------------------------------------------------------------------- where should i look for the reasons it doesn't wanna roll? the mystery is that sometimes it works. and i have no idea how to recreate that state. versions $ rosegarden -v Qt: 3.2.3 KDE: 3.2.2 Rosegarden: 4-0.9.7 $ timidity -v TiMidity++ version 2.13.0 -- gr{oe|ee}t{en|ings} artm

21 years, 1 month

← Newer
1
2
3
4
5
6
7
...
17
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 May 2004