Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7440 discussions

by Kjetil Svalastog Matheussen

Vstserver is a program that must be running when using programs using vstlib. Vstlib is a library that can be used by programs to run windows vst audio plugins under i386linux/i386freebsd/i386solaris/i386etc. (May require som modifications for other os-es than i386linux). A tutorial for vst plugins in linux can be found here: http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/ A list of some of the plugins working and not working: http://80.61.20.184/vst/ 0.3.0 -> 0.3.1: -Added a watchdog for the processthread if its running SCHED_FIFO. If the processthread use more than 10 seconds to process a chunk, it should be killed. Tested with an endless loop, and it seems to work. -Added "make install" and "make uninstall". -Updated the INSTALL file. The installation should now be a bit easier. Download source from: http://www.notam02.no/arkiv/src/ Mandrake users can find rpm packages here: http://rpm.nyvalls.se/ --

20 years, 7 months

[linux-audio-dev] [ANN] Digital Room Correction (DRC) 2.3.2

by Denis Sbragion

Hello, Digital Room Correction 2.3.2 has been released and is available at: http://freshmeat.net/projects/drc/ Changes: This version adds a sharpness factor parameter to the sliding low pass prefiltering procedure, adds an option to read and write double precision floating point files, and adds some checks to warn when the input signal is too short to provide accurate results. Bye, -- Denis Sbragion InfoTecna Tel: +39 0362 805396, Fax: +39 0362 805404 URL: http://www.infotecna.it

20 years, 7 months

[linux-audio-dev] libsndfile-1.0.6 released

by Erik de Castro Lopo

Hi all, The above new version has just been release and is available here: http://www.zip.com.au/~erikd/libsndfile/#Download The big fix in the above is a fix that allows reading and writing of files larger than 2Gig on 32bit Linux and Solaris. The problem was that config.h was not being included before stdio.h so that a couple of #defines were not be set to enable large file support. As before, writing AIFF and WAv files larger than 2Gig does not really make sense. Anomg the supported file formats which allow large files are W64, AU and PAF. Cheers, Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid) +-----------------------------------------------------------+ Windows 95/98 - 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -- +-----------------------------------------------------------+ Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid) +-----------------------------------------------------------+ Hiesenbugs - The bugs that go away when you turn on debugging.

20 years, 7 months

[linux-audio-dev] Re: Modular Jack patch bay

by Juhana Sadeharju

>From: Dave Robillard <drobilla(a)connect.carleton.ca> > >This is what LADCCA is for really.. session management is well out of >the domain of a patch bay, IMO So what is the purpose of Patchbay? Users launch applications from a shell and then uses Patchbay for connecting the applications? That would mean a lot of manual connection work each time. A few weeks ago I tested a midi keyboard with Fluidsynth. Each time I changed the sample file in the shell, I had to reconnect the thing. Very annoying. I could not see a screenshot of the LADCCA? Does it provide what I suggested? Is the case that either we should add the requested features to Patchbay or add GUI to LADCCA? If both are out of question, we need yet another application. >This doesn't have anything to do with the patch bay, but anyone who >implements a reverb like this should be taken out back and shot >regardless. ;) This is definately LADSPA-domain. I tried LADSPA already. :-( >> Inserted Patchbay files may need null nodes. If multiple modules >> needs the same input, then with the null node the inputs can be >> combined. > >Jack allows multiple connections. Yes, but how user would know what connections to make? The reverb was just one example figured out in frustation, but maybe people would like to provide such connections for other applications? A synth application followed by effect applications. LADSPA requires a host. If one places multiple effects to the path, then the host must support multiple effects and their easy control. Too complicated. Jack + multiple simple LADSPA hosts would work better -- if there would be some way to easily control the Jack system. Now I would like to have a completely graphical control application, such as Patchbay. Regards, Juhana

20 years, 7 months

[linux-audio-dev] [ANN] liblrdf v0.3.5

by Steve Harris

http://plugin.org.uk/lrdf/ Changes: * Better compatibility with LADSPA (thanks to Mike Rawes) * Speed improvements * Better preset reading example * Removed external dependence on ladspa.h * Fixed syntax error that upset some compilers - Steve

20 years, 7 months

[linux-audio-dev] Re: Modular Jack patch bay

by vanDongen/Gilcher

My preference : The line doesn't need to be thick. Clicking it selects it (and shows it by changing the color, maybe making it thicker as well ), pressing delete removes it. Handles of some sort to create segmented patch cords would be nice. As would the ability to rotate a client box over 90 degrees, so you have the connection at the top and bottom. Another feature could be symbolic link objects. Sometimes you have a signal detour to some part of an app that is somewhere else on the graph and allready heavilly connected to all kinds of other stuff. A symbolic-link to foo:input12 foo:output12 could be nice then. Gerard On Friday 06 February 2004 13:50, Dave Robillard wrote: > What's the best way to disconnect ports? I've thought of: > > - putting a handle in the middle of connection lines, so you can > right-click them to get a menu > > - making the lines really thick, same deal as above > > - just being able to right click a port and disconnect all connections > (with the obvious disadvantage of forcing you to maybe disconnect > something you don't want to) > > - clicking on the source port then the dest port (just like connecting), > except if they're already connected, disconnect them > > > Ideas? Opinions? > > -Dave -- electronic & acoustic musics-- http://www.xs4all.nl/~gml

20 years, 7 months

[linux-audio-dev] Re: Modular Jack patch bay

by Juhana Sadeharju

>From: Dave Robillard <drobilla(a)connect.carleton.ca> > >What's the best way to disconnect ports? I've thought of: > >- putting a handle in the middle of connection lines, so you can >right-click them to get a menu No no. >- making the lines really thick, same deal as above Make the lines thick only if it is visually justified. If you only want grab the cable, then make the grabbing distance long enough. The same for the grabbing distances of the ports. When working fast, any tiny things are no no -- there are plenty of examples on tiny things already. Change the cable and the port colors when they are in focus, to indicate that something can be done to them. Probably three distances are needed: -Port picking distance -Cable-end picking distance -Cable picking distance If one may start a new cable by picking the port, then cable-end picking distance must be slighly larger -- and the area between the port picking distance and the cable-end picking distance are used to pick the ends of the cables. - Grab and drag the end of the cable; the cable-end picking distance should be long enough so that grabbing a cable is possible even if the port has multiple connections (Note: this does not delete the cable) - Grabbing both ends deletes the cable Change color only of the end of the cable to indicate that it can be picked up. - Ctrl + mouse button 1 on a cable: deletes cable; the menu is ok too, but I prefer faster ctrl+mb1 - Sweeping a rectangle area on canvas, followed by a deletion operation Make enough alternatives because usability is a matter of choise. Regards, Juhana

20 years, 7 months

[linux-audio-dev] alsa-playback (in plain c)

by Julien Claassen

Hi all! I wanted to do a simple task. I just want to playback a raw file (16BIT, stereo, 44100Hz). So I used the alsa_pcm_seq-howto and compied a bit of code from it. But it doesn't work. I get the device read for playing and I get sound... But it's just noise. I'm frustrated. I tried to copy the relevant part out of the aplay-sources, but they have so many config stuff... Can anyone help me with a bit of code or a place where I should just get some code for only: 1. opening a raw-file 2. setting up the alsa-driver for playbakc 3. Read data from the file and write it to the soundcard. I want nothing fancy. Just a stupid little part of c-code, which performs just that task. Kindest regards and thanks for any help Julien http://ltsb.sourceforge.net - the Linux TextBased Studio guide --------------------------------------------------------- SBS C-LAB Fuerstenallee 11 33102 Paderborn Phone: (+49) 5251 60 6060 Fax: (+49) 5251 60 6065 www.c-lab.de/~wegge

20 years, 7 months

[linux-audio-dev] Support for MAudio Revo under Alsa ?

by Robert Rozman

Hi, I wonder if Revo can be used as 4xstereo channel output (Delta410 at twice the price can do it) under Alsa ? Will anyone try it ? Delta 410 can do this: http://www.avsforum.com/avs-vb/showthread.php?s=&threadid=342158 I wonder if Revo can also do it ... Regards, Robert.

20 years, 7 months

[linux-audio-dev] [ANN] lakai-0.1

by Frank NEUMANN

"At last", Roboff says, "I have it." - from "Mask Of The Sun" Hi LAD'ers, I'm happy to announce the first release (0.1) of lakai, a small tool package that allows to exchange data (samples, programs) between a Linux PC and an Akai sampler (S2000 tested; other 2xxx/3xxx models might work or not) over SCSI. This permits "complete backup" and "complete restore" of the sampler RAM contents. Availability: http://sourceforge.net/projects/lakai (the web page was not updated yet) Right now, everything is just shell-based, no GUI yet, and the tools are rather rudimentary, the source is ugly and sprinkled with TODOs and printf's etc. pp., but at least it WorksForMe(tm). I welcome comments, success stories and bug reports, but my answers might take a while :-). All further info is in the archive in the README - read it, it took me a while to put it together. This stuff comes rather late - in fact, I created this sourceforge project more than 4 years ago, and I have only been working on it very rarely for a long time (and it's even quite small). The S2xxx model samplers are only available second-hand today, and software-based samplers (like http://www.linuxsampler.org) are already on the way. I am still very proud that I finally got this baby out of the door. Ha! :-). Enjoy, Frank -- Frank Neumann (Frank.Neumann(a)st.com), VIONA Development Center STMicroelectronics, Karlstraße 27, 76133 Karlsruhe

20 years, 7 months

Jump to page:

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