Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7501 discussions

[OT] RME HDSP Multiface (1st gen), PCMCIA cardbus (1st gen), and PCI-to-PCMCIA cardbus (for desktop) for sale

by Ivica Ico Bukvic

Barely used. If interested, please email me your offer. Originally this thing cost ~$1,200 (with the PCI-to-PCMCIA cardbus for the desktop connectivity). Been used on Linux and Windows. Ivica Ico Bukvic, D.M.A. Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Assistant Co-Director, CCTAD CHCI, CS, and Art (by courtesy) Virginia Tech Dept. of Music - 0240 Blacksburg, VA 24061 (540) 231-6139 (540) 231-5034 (fax) ico(a)vt.edu http://www.music.vt.edu/faculty/bukvic/

16 years, 3 months

JACK and computer sleeping

by nescivi

Hiho, It seems that JACK (just tested with v0.116) does not survive when the computer is put to sleep, and woken up again. Is there any reason why this is so? sincerely, Marije

16 years, 3 months

Vamp Plugin Tester: a simple test utility for Vamp plugin development

by Chris Cannam

Announcing v0.1 of the Vamp plugin tester, a simple program that loads and tests Vamp audio feature extraction plugins for various common failure cases. It can't check whether you're getting the right results, but it can help you write more resilient and better-behaved plugins. Source code: http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1.tar.bz2 OS/X universal binary: http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1-osx-universal.… Windows binary: http://downloads.sourceforge.net/vamp/vamp-plugin-tester-0.1-win32.zip For more information about Vamp plugins, please see http://vamp-plugins.org/. The "home page" for this utility is the developer page at http://vamp-plugins.org/develop.html . There is some documentation for this program in the README file, but the short version is that you run it at a command prompt with the library name and plugin name, colon-separated, as an argument: $ ./vamp-plugin-tester vamp-example-plugins:spectralcentroid ... and see what it has to say about your plugins. It may also crash; if it crashes in the middle of one of its tests, that usually means that your plugin has crashed when faced with some unexpected input (run it in a debugger, or a memory checking utility if you have one, to find out where). This tester does report some genuine bugs when run against several of the existing Vamp plugins. I'll be aiming to make some fixes where I'm able. This is only the first release, so it's quite likely that the tester hasn't been tested enough itself yet. Please report any problems to me or the Vamp plugins develoment forum at http://vamp-plugins.org/forum/index.php/board,1.0.html . Chris

16 years, 3 months

problem with alsa/portaudio

by vincent meserette

Hi all, In one of my code, I use the snd_pcm_open() function of the ALSA lib to access to my sound device, but when I run it I have the following message : ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so After having searching on the web, it seems it comes from a conflict between alsa and pulse audio. As indicated on some forums, I have reinstalled pulse audio and libasound2-plugins but it doesn't work, even if the aplay function works well on my system. Does anybody know from where could come the problem ? Thanks in advance Best regards Vincent PS : my distribution of linux is ubuntu 8.10

16 years, 3 months

Re: [LAD] [LAU] Join the Debian Multimedia Team! (to improve the state of Linux audio)

by Grammostola Rosea

Crypto wrote: > On Monday 09 March 2009 16:29:53 Ivica Ico Bukvic wrote: > >>> My point was : if Debian Multimedia is just an effort to make things >>> better >>> looking on the audio/multimedia side, then it has more to do with the >>> "Debian packages and process" group of people than with the linuxaudio >>> people. >>> >> I guess this part is for Debian folks to answer. Even if multimedia part >> cannot be treated as a separate entity, perhaps having Debian as a whole a >> member of Linuxaudio.org would not be a bad idea. After all, we do have >> Canonical/Ubuntu and Mandriva on board already. >> >> +1 > > I think one of the most important things to have would be a debian RT kernel > that can be installed like any other deb package already can. This would mean > to patch/finetune a standard kernel to make it RT capable everytime a new > standard kernel is released. Maybe it could be sufficient not to do that for > EVERY single kernel version that is released but stick to some "milestone" > versions instead that nevertheless reliably do the RT and of course MIDI > stuff. > > This RT kernel could then be offered as a standard debian package in any of > the existing standard debian repositories, so that anyone needing RT could > install it on their machine in parallel to their previously installed > ordinary kernel without having to change a lot on their machines. > > As for the LAU-related stuff: > It seems to me that there are some great LAU applications out there for which > there are no deb packages available (neither are Ubuntu packages). I think we > need some place where LAU programmers can announce their software (which has > been here so far) and make other folks aware of it and we also need some kind > of deb repository where programmers can release their software so we can all > apt-get it. Maybe this place could be on an official debian software site > with only one limitation: as this software tends to be updated frequently it > is kind of experimental and debian people would rather not declare this > as "rocksolid stuff" that can be mixed with the standard release of debian. > So people of debian could release LAU related software on their sites without > having to give any "warrantee" for it. > > BTW: when having a LAU related repository I look forward to seeing DSSI-VST > and fst released as true apt-get installable packages ;-) > > I think such a repository you're talking about could be indeed a good idea. But it could have some disadvantages to, like also all those custom PPA Ubuntu repo's has. The packages maintained by the Debian Multimedia Team are safe, stable and have good quality. The Debian packages do pass some quality rules, which is a very good thing imho, better then having a repository without any 'warrantee'... Also your idea could have the effect that people only upload their packages to this repo and not to Debian itself, so there will be a quality loss... But for packages which are valuable and do not pass the (license) criteria of Debian it could be good to have such a repository. For example for a realtime kernel and stuff like dssi-vst, (FST is a candidate for Debian imho), linuxsampler (?), Jost... Also, some developers make packages of there apps themselves. I think it's the best for Debian (based) distro's that they build it against Debian unstable, so the community can use it and the package maintainers can use it to build it against their distro easily. So maybe some kind of an - Debian Multimedia 'experimental' repo > for packages build against unstable, which are not in Debian yet. Devs can upload their packages to this repo and package maintainers can use it for uploading it to Debian. (I think if you setup such a thing, it should happen in corporation and communication with the Debian Multimedia Team!) - Debian Multimedia non-free repo > for dssi-vst, jost, etc. Btw. There was a guy who was aiming to have such a Debian repo with a realtime kernel: https://www.scimmia.net/code/wiki/DebianRepository Above all, the most needed are people who want to maintain packages for the Debian Multimedia Team! Regards, \R

16 years, 3 months

libzita-convolver

by Jaromír Mikeš

Hello, I am trying build debian package library of zita-convolver I need to fill some description there. There is not this kind of information in orig. tarball. Can any advise me what write there? Thank you mira

16 years, 3 months

[ot] Vim substitution question...

by Julien Claassen

Hello all! I'm sorry to bother you with that, but I don't find a feasable solution for this. It's all about patterns. Imagine the following text examples: <A HREF="url" TITLE="MY_TITLE"> <a NAME="x" id="x"> <P align="center"> What I need to do is make sure, that every TAG (a and p in these cases) and every attribute (href, title, name, id and center in these examples) is lower case. I've tried a lot, but I'm not the crack at patterns and so I got no completely satisfying result, if I got any at all. :-( Could someone please help me here? Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

16 years, 3 months

testing jack client, errors, shutdown..

by Alex Norman

I'm wondering if it is possible to force a jack client into an error condition without actually changing the client. I'm wanting to see what actually happens when my client's error + shutdown handlers are called. It seems as though my 'shutdown handler' isn't being called when jack shuts down. Thanks, -Alex

16 years, 3 months

Strange network problem ?

by Fons Adriaensen

Hello all, Today I had a strange problem when using the WFS system here. The 'master' PC sends a multicast message every 1024 samples (21.333 ms) to all 'render' PCs. This has to arrive on time, and when it's late the renderers will mute their output and report the error in their status messages. Today I used some ssh -X logins from my laptop in the WFS room to the WFS master to run Ardour and some other apps for a demo. All this worked well all the time, as it has done before. I left everything running when going for lunch with our visitors, and when I returned restarted Ardour to listen again. I got a lots 'of 'message too late' errors from the rendering machines, and interrupted sound. Strange enough this seemed to be related to the _volume_ of the sounds... In other words to Ardour's level meters. Restarting Ardour in a new ssh login did not help, but running it directly on the WFS master solved the problem. So apparently the network traffic required to update Ardour's meters was causing the delays. And clearly the whole remote X session was slower than normal. CPU loads looked normal. Now all this should be peanuts for a Gbit network that has no other traffic at all, and it worked perfectly before. I just never left it running for such a long time. Anyone an idea as to what is happening here, and how it could be cured ? TIA, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Be quiet, Master Land; and you, Professor, will you be so good as to listen to me ?

16 years, 3 months

[ANN] Qtractor 0.4.0 (foxy dryad) released!

by Rui Nuno Capela

Howdy! It's been quite a while since last time (Fluffy Doll on Xmas:). However, Qtractor is back again on track and this time with great news. And the big news are that this pet is leaving its rusty four-on-the-floor cage and spreading it's musical genre targets. Still a bedroom/home-studio sequencer though, but not for the techno-boy/girl only anymore--if one may trump about it, it's getting a general-purpose sticker now. And what makes it like just that? One long due feature, now stroked by implementation lightning: Tempo/Time-signature Map. Or in other words: project sessions may now have multiple parts with different tempo (BPM) and/or time-signatures. Tempo/time-signature map is/was a very pervasive feature change. Although deeply internal, as it's only evidently visible from the new View/Tempo Map... interactive yet primitive dialog, it is also accessible by double-clicking on the time rulers (main track-view and MIDI clip editors) and by left-clicking over the main tempo spin-box, which also introduces the time-signature figures as seen from the current play-head position. One should probably say that this is the major change in Qtractor internals since its primordial inception. No doubt, we're still in /alpha/ status. It surely will take a (another) while, a year or so, for a similar payload take a lift, ever again. No sweat. Watch for next favorite feature requests, like MIDI controller map/learn/feedback and automation. Coming next, soon, hopefully :) A few words of caution must be said now. It is of paramount interest for all of you who already use Qtractor for any (small) project or prototype, to be prepared for less amenable surprises. Being optimistically wise, there's a very good chance that all new workings will bring a better experience overall. But given the whole nature and depth of what got through, it is wise enough to have your backups at hand and up to date. Don't hesitate asking for help, in any case. Caveat emptor! So, with no further ado, there it is: Qtractor 0.4.0 (foxy dryad) is now released! Good old intro/description: Qtractor is an audio/MIDI multi-track sequencer application, written in C++ on top of Qt Software's Qt4 framework, having JACK and ALSA as its main infrastructures and Linux as native and exclusive platform. Specially suited to the lone-wolf composer, arranger and (re)creative music-maker personal home-studio, it still hopes to evolve as a fairly featured desktop audio/MIDI workstation or at least, a prototypical part of it ;) Release highlights: * Tempo-map/Time-signature support. (NEW) * MIDI Song Position cueueing support. (NEW) * MIDI Clip Quantize command. (NEW) * Zoom direction mode option (NEW) * MP3 audio format support (FIXED) * and many other assorted fixes and brand new bugs ;) Website: http://qtractor.sourceforge.net Project page: http://sourceforge.net/projects/qtractor Downloads: - source tarball http://downloads.sourceforge.net/qtractor/qtractor-0.4.0.tar.gz - user manual http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf (nb. yes, it's the same old, dusty and outdated manual, sorry) Weblog (upstream support): http://www.rncbc.org License: Qtractor is free, open-source software, distributed under the terms of the GNU General Public License (GPL) version 2 or later. Features: - Multi-track audio and MIDI sequencing and recording. - Developed on pure Qt4 C++ application framework (no Qt3 nor KDE dependencies). - Uses JACK for audio and ALSA sequencer for MIDI as multimedia infrastructures. - Traditional multi-track tape recorder control paradigm. - Audio file formats support: OGG (via libvorbis), MP3 (via libmad, playback only), WAV, FLAC, AIFF and many, many more (via linsndfile). - Standard MIDI files support (SMF format 0 and 1). - Non-destructive, non-linear editing. - Unlimited number of tracks per session/project. - Unlimited number of overlapping clips per track. - XML encoded session/project description file. - Point-and-click, multi-select, drag-and-drop interaction (drag, move, drop, cut, copy, paste, delete, split) - Unlimited undo/redo. - Built-in mixer and monitor controls. - Built-in connection patchbay control and persistence (a-la QjackCtl). - LADSPA, DSSI and native VST plug-ins support. - Unlimited number of plug-ins per track or bus. - Plug-in presets, programs and chunk/configurations support. - Audio/MIDI clip fade-in/out (linear, quadratic, cubic). - Audio/MIDI clip gain/volume, normalize and export. - Audio clip time-stretching (WSOLA-like or via librubberband), pitch-shifting (also via librubberband) and seamless sample-rate conversion (via libsamplerate). - Audio/MIDI track export (mix-down, merge). - Audio/MIDI metronome bar/beat clicks. - Unlimited tempo/time-signature map. - MIDI clip editor (matrix/piano roll). - MIDI instrument definitions (a-la Cakewalk(tm)) - JACK transport sync master. - MMC control surface enabled. - MIDI Song Position cueuing support. - Configurable keyboard shortcuts. Change-log: - MIDI (re)connections fix; now caring for the ALSA client and port textual names only, avoiding as much as possible, any reliance on those volatile client and port numbers. - Transport/Backward and Forward commands may now reset to immediate full start or end of session locations, by just pressing the Shift or Ctrl keyboard modifiers and clicking their respective toolbar buttons. - Default session/MIDI resolution has been set to 960 ticks per beat (960 TPQN, where a beat equals a quarter-note); it is worth of note that the previous default resolution was set to one order of maginute lower, ie. 96 TPQN ;). - Making (dis)connections now also flags session as dirty. - Internal Audio/MIDI engines queue/time drift correction takes a brand new approach, specially adapted to rolling tempo/time-siganture changes. - MIDI monitor refresh-cycle slight internal optimization. - Converted obsolete QMessageBox forms to standard buttons. - Transport/Rewind and Fast-forward commands may now be set to double-speed, by pressing the Shift or Ctrl modifiers while clicking their respective tool buttons. - MIDI clip editor zoom ratios are now saved and preserved across sessions. - Time-signature is now directly accessible from the main tempo spin-box which also reflects current tempo status. - Time/frame spin-boxes now allow to step change each field individually, depending on the cursor beam position. - Make sure that Transport/Follow playhead option is only effective when playback is actually rolling. - Primordial attempt to include MIDI Song Position Pointer (SPP), Song Start, Stop and Continue sequencing support. - A completely new time-scale infrastructure is now in place, with full support for session tempo and time-signature map; this long due feature is primarily accessible through the main menu, View/Tempo Map...; also by double-clicking on the the main window and MIDI clip editor time rulers and left-clicking on the main toolbar tempo/signature spin-box. - Moving and resizing individual clips now cares for track proper ordering and overlapping changes, avoiding nasty out of sequence clips and other unpredictable effects. - An expedite MIDI clip quantize command is now available from the main track view menu (Edit/Clip/Quantize), which simply applies the current snap-to-beat setting to a MIDI clip range selection. - Fixed that hideous bug affecting overlapped audio clips when playhead gets moved backward, causing the playback of those audio clips in particular, go out of sync. - Tracks are now limited to their minimum height, specially effective in face of vertical zooming. - Zoom mode option introduced (on menu View/Zoom/Horizontal, Vertical, All). - Tempo beat type is a new session property; however it is not yet user modifiable and currently disabled to default MIDI quarter note (1/4). - All open MIDI clip editor time-scales are now updated and corrected when the main session time base changes (tempo, time-signature, resolution, etc.) - MIDI metronome fixed, preventing duplicate click events. - MP3 audio file decoding was broken for way too long and falling short for every file with custom frames, ID3 tags and comments. Got shamefully fixed. - Time signature denominator (ie. beat divisor) is now an accessible and effective session property. - Attempt to retain original size (clip length) of all audio clips when changing the global session tempo and automatic time-stretching is not an option. Cheers && Enjoy! -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

16 years, 3 months

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-dev