Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7513 discussions

by Lee Revell

Disk IO priorities have been discussed on the list before, and they are now in the mainline kernel (search LKML for "IO priorities" for details). I think they're only supported by the CFQ scheduler. This might be fun for someone to experiment with, I'm sure any HDR application would like this feature. Lee

20 years, 1 month

[linux-audio-dev] [ANN] E-Radium V0.61d

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

http://www.notam02.no/radium/ INTRODUCTION ------------ E-radium is Radium and a special version of E-UAE. Radium is a midi music editor for the amiga and E-Uae is an amiga emulator. CHANGES ------- 0.61c -> 0.6d: -Increased amount of Z3-memory from 32 to 64. Also increased the amount of chip-mem from 2 to 8 to let there be more time to quit/save after getting a warning about too little memory. For now, this seems to work... -Lowered the keyboard repeat rate a bit. -Fixed make install -Use standard mouse pointer. -Upgraded Radium from 0.61c to 0.61d: -Added scroll-mouse support. Scrolling up is exactly the same as pressing arrow up, and scrolling down is exactly the same as pressing arrow down.

20 years, 1 month

[linux-audio-dev] [OT] 2-D slider widget?

by James McDermott

Has anyone written code for, or even just seen, a 2-D slider widget? What toolkit was it in? Do people around here prefer QT to GTK+, or vice versa, and does anyone use FLTK, or something else? I think the ideal widget would allow the user to click or click-and-drag a cursor around the 2-D area, returning x and y coordinates of course; and would allow a bitmap to be displayed underneath the cursor; and would allow some way to constrain the cursor movements (eg within a circular area inside the widget). Such a thing would be great for lots of audio applications, like controlling filter cutoff and resonance at the same time. That's what I'll be doing, only a bit more complicated..!

20 years, 1 month

[linux-audio-dev] [a bit OT] scroll and zoom conventions

by Alfons Adriaensen

Hello all, I'm trying to clear up my mind as to what conventions to follow in a GUI for the actions of zooming in and out e.g. a spectrum or an impulse response window. It's not the intention to launch a debate about this, just to collect other people's ideas. The accepted model for scrolling is that the user 'moves' a *clipbox* that determines what part of the *content* is visible. For example, when you drag a scrollbar to the right, the clipbox moves to the right. What actually happens of course is just the opposite: the clipbox remains static on the screen, and the content moves to the left. The other model is used as well, for example Acrobat Reader lets you drag the content directly. Now my question: what about zooming ? For keyboard shortcuts, Ardour uses '+' to zoom out and '-' to zoom in. This is consistent with the idea that the user modifies the clipbox. But I still have to think before using it, each time, and I could easily imagine using '+' to zoom in. In fact I have no clear preference. Then there's the questions of icons. If in addition to the arrows in a scrollbar you would also have small buttons to zoom in and out, what should they look like ? Zoom in Zoom out - + -><- <-> or the inverse ??? -- FA

20 years, 1 month

[linux-audio-dev] Gamepad as midi controller?

by Jens M Andreasen

Hi! Today I went downtown to the big store, to buy a few things I need for other purposes. They sell computer related stuff as well, and I picked up a gamepad which had an analogue mini joystick buildin. I've always thoght that gamepads are glorified arrow keys, but that mini analogue joystick left me wondering ... Anybody here have had any luck using something like that under Linux? For the price of only slightly more than a scrollwheel mouse I think it's a bargain. Could find good use for balancing out parameters in a 2d space. It has quite a few buttons also that could be useful for selecting modes. It is a USB device (great), but the box says only that it works with all versions of Windows known to mankind ... It looks like this: http://www.clasohlson.se/images/products/S/hi/B/326344_X_2004-08-09_121320.… So, could this be an answer to the budget synthesists need for hands on control of his linux based softsynths? mvh // Jens M Andreasen

20 years, 1 month

[linux-audio-dev] gcc4 patch for swh plugins

by Doug McLain

Here is a patch that got swh plugins built for me on FC4 gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) the original fails on gcc4 for both use of a removed optimize option -fmove-all-movables and for declaring an already defined non-static variable as static. More on the removed optimization flag here: http://gcc.gnu.org/gcc-4.0/changes.html The options |-freduce-all-givs| and |-fmove-all-movables| have been discontinued. They were used to circumvent a shortcoming in the heuristics of the old loop optimization code with respect to common Fortran constructs. The new (tree) loop optimizer works differently and doesn't need those work-arounds. -- http://nostar.net/

20 years, 1 month

[linux-audio-dev] AI Composer Competition

by Leonard "paniq" Ritter

http://www.paniq.org/index.php/AI_Composer_Competition -- -- leonard "paniq" ritter -- http://www.paniq.org -- http://www.mjoo.org

20 years, 1 month

[linux-audio-dev] HOw to create an ALSA out port

by Christoph Eckert

Hi, I just wote a program to configure a m-audio Midisport 8x8. Currently the program can only write a sysex file. It would be convenient to send the data to the Midisport control port instead. UNfortunately, I have no clue how to do so easily. I only need to write sysex data which are kept in a character array. Is there a possibility to easily * connect to a certain port of a device (the Midisport control port) * send the contents of the array to this port * close the port I have already seen some documentation (especially the examples of M- Nagorny), but as I just started to write code it's still too complicated for me. Furthermore I was told that I do not need a fully featured port and that a rawmidi port would be enough for my needs. So, any pointer to some docs or example code I can understand would be really cool. Thanks & best regards ce

20 years, 1 month

[linux-audio-dev] I need help to maintain TerminatorX

by Dubphil

Hello, I use TerminatorX extensively, but it has been noticed that the turntables has mono output. I believe it was a plugin in AMS, in my routing scheme, that was the guilty, but finally not, it is in fact TerminatorX. I've contacted the maintainer, but it seems that this project is dead. I would like to keep it alive but I'm certainly not enough skilled in c++ programming :( To give an example of what I'm able to do : with jackd, terminatorX is connecting automaticaly the L/R output to the Alsa_pcm playback 1 and 2. This was not very good for me, because I don't need this particular connection. So I must each time disconnect them. I've succeeded in disabling this feature quite easily. Now, the goal is to let TerminatorX playing the turntables in Stereo. Does this task seems difficult ? Anyone during the holidays could point me on the good direction ? TerminatorX source code is not huge, quite well organised but not very well commented :( Regards. Philippe

20 years, 1 month

[linux-audio-dev] ANN: libgdither 0.6

by Steve Harris

http://plugin.org.uk/libgdither/ Bugfix release. Added patch for 64bit architecture support, thanks to Andreas Steinmetz, and a bugfix to the shaped dither that increases its signal to noise ratio. All projects that use this code should update. The intention is that applications that require this function should include hte code, rather than adding it as a depenency. About libgdither: Libgdither is a library for applying dithering to PCM audio sources. Dithering is a process to remove the intermodulation distortion from signals that are to be been reduced in bitdepth. This code is (c) Steve Harris 2001-2005 and released under the GNU Public Licence. Details may be found in the file COPYING. It can do conversions between any combination of: in out (optionally interleaved) ------------------------------------------------------------- normalised mono float 8bit unsigned ints normalised mono double 16bit signed ints 32bit signed ints normalised float normalised double At any bitdepth supported by the input and output formats

20 years, 1 month

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