Free sliders software for linux

KLcdDimmer is a KDE applet to adjust LCD brightness.
To adjust the brightness simply click with the mouse left button and use the slider
KLcdDimmer relies on an external program to get/set the brightness, such as smartdimmer or nvclock.
For instance, Ive used
- SmartDimmer
- NVclock
but it is supposed to work also with others, since you can configure the applet.
Installation:
When you run configure, you should pass the KDE root directory as --prefix (in my system it is /usr).
The steps to perform for the installation are standard for packages in source form: once you have unpacked the sources in a directory, `cd to the directory containing the packages source code and execute the following steps:
./configure --prefix=
make
make install (as root)
Then youll be able to add the applet to the panel, by using your KDE panel.
Enhancements:
- Fixed tooltips and added whats this helps
- Fixed geometry (now should fit the panel better)

TCMixer is a compact X11 audio mixer.

Can be controlled from keyboard. Supports mixer callbacks. Very fast Xlib based UI routines, optimized mixer code.

Version 2.0 adds complete keyboard control over the mixer. Read the ASCII diagram below:

.-----..---.
| TAB || Q | .---.
`-----`--- | ^ |
`---
.---..---..---..---..---..---..---. .---..---..---.
| Z || X || C || || || || M | | < || v || > |
`---`---`---`---`---`---`--- `---`---`---

Tab, Right arrow: next channel
Mod-Tab, Left arrow: previous channel
Up Arrow volume up
Down Arrow volume down
Q quit
M mute
Z,X,C Line, Mic, CD record source

The keys are grabbed as scancodes, so I think this should work on all international/whatnot keyboards. zxc are in the lower left corner and the m key is 3 keys after, so its like "zxc...m" on the bottom row. "Q" should be right next to the Tab key. Scancodes returned by the keys located there should be the same regardless of keyboard layout. If not, let me know.

Current channel is marked with a green LED on the slider bar. Slider slide, changing volume. There is a row of buttons on the top. If a button is yellow, it means the channel is on and not muted. If its off, the channel is muted. Push it again to go back to the last known volume setting (remembered before pushing the button). If a channel was muted and you moved the slider, without pushing the button, it will become unmuted... If the button is red, you will not see a mixer slider for that channel, and it means your soundcard doesnt support that particular channel (most likely going to be true for Bass / Treble channels on elcheapo cards and also on some PCI cards (AudioPCI for example)).

Most modern sound card controls are here, and this should be enough for basic volume adjustment when you play your cd or mp3s or whatever. Missing controls will be deleted from the face of the mixer, but it will not be resized, so if your card is so lame that half the controls are "red" on the mixer, then you should find a new card.

Choose recording source by using radio buttons under the sliders by clicking on them or pressing z, x or c keys to select Line, Mic, or CD as recording source. Again, if that doesnt work, complain to your sound card manufacturer.

Oh yah, you quit by clicking anywhere in the words "TCMixer", or pressing the "q" button on keyboard.

Since that lameness called DEVFS has been included in the kernel, people might have shit like /dev/bus/pci/slot0/card0/controller0/sound/mixer for their mixer device, so you can use the -m option with tcmixer to specify your own mixer device:

% ./mixer -m /dev/dev/fs/is/lame/sound/mixer

It works for me, with ALSA. It should work with OSS, but I never bothered to test it. Some OSS drivers are known to only have volume steps from say 0 to 64 instead of 0 to 100 like ALSA. Up to this day I dont know which card does this. I have received some reports that this could be your standard SB16 if used with kernel sound drivers under kernel 2.2. If your card does this, you can email me, and tell me the card name, oss version, shit from /dev/sndstat, etc etc - if you want that fixed you will need to tell me as much information as you can possibly find about your sound shit, because the only people who reported this to me so far didnt even bother to tell me what soundcard they have. This 0 to 64 stepping will break the mixer, and since fuckheads who wrote OSS did not provide an API to check the min/max ranges for a particular channel I cannot test for this situation at run-time. Sorry. Use ALSA, it will fake your lame 0 to 64 card into a smooth 0 to 100 curve.

Jokosher project is a simple yet powerful multi-track studio. With it you can create and record music, podcasts and more, all from an integrated simple environment.
Main features:
- Easy to use interface, designed from the ground up. Jokosher uses concepts and language familiar to musicians, and is a breeze to use.
- Simple editing with splitting, trimming and moving tools.
- Multi-track volume mixing with VU sliders.
- Import audio (Ogg Vorbis, MP3, FLAC, WAV and anything else supported by GStreamer) into your projects.
- A range of instruments can be added to a project, and instruments can be renamed. Instruments can also be muted and soloed easily.
- Export to MP3, Ogg Vorbis, FLAC, WAV and anything else GStreamer supports.
- Documentation (User Guide, FAQ, Tutorial) and User Community (Forums, IRC).

MIDI Controller is a program that connects Glade UI files to MIDI parameters.

This is a small program that lets you set MIDI controller values using sliders and buttons in a GTK+ window. The GUI is an XML-based Glade file which can be replaced without rebuilding the program, so you can build your own controller GUIs in Glade.

JXosd is a set of Java bindings for XOSD, a library for displaying information on an X display. It supports the display of text, sliders, and percentage bars through JNI. Almost the entire API has been implemented.

rsjog project is an X11 handler for Sony Vaio jog wheels.
It is designed to work with the /dev/sonypi kernel module.
It provides mousewheel emulation and (optionally) graphical menus you can navigate with the wheel.
Main features:
Simple mode (no menu file)
- Mouse wheel simulation for scroll wheel
- Press scroll wheel for middle button simulation
- Back button (if available) simulates middle button too
Menu mode
- Mouse wheel simulation for scroll wheel
- Press scroll wheel to pop up menu
- menu hides again after a time if not used
- Scroll through menu with scroll wheel
- Press scroll wheel to launch action
- Actions to launch programs
- Action to change volume using the wheel
- Action to change lcd brightness using the wheel
- Actions to simulate mouse button presses
- Back button (if available) simulates middle button if menu is not up but also goes back through menu structure/closes menu if visible
- Configuration file to specify menu structure
- Configuration file to specify vaio FN key bindings, file paths, timeouts, slider granularity, etc.
- Automatically reloads config files when they change

Network Transparent Widgets short from NTW, is a protocol and application framework that allows a single server to serve thousands of remote GUI applications.
The client applications are nearly indistinguishable from local, native applications. The protocol is language and architecture neutral. Server language bindings for C and Java are in heavy development.
Main features:
Speed: Remote apps can run at a speed which is nearly indistinguishable from a locally running application. Since the client draws the widgets natively, its not necessary to transfer graphical data, only widget state data. This can be done asynchronously, so the responsiveness of the UI never suffers.
Persistence: Its just as easy to write the ntw protocol data to disk as it is to the network, so the state of the entire gui application can be easily saved. This also happens transparently, so the developer doesnt have to spend any time loading and saving data. Also, if a network connection dies or the client computer loses power, the application can be restarted from the point of failure at the next connection.
Portability: using the protocol, an ntw server application running on a Unix machine could talk to an ntw client for Windows, and vice versa. So a developer could write a program on Linux that could be run from any OS without any porting necessary. Any language or platform that can read and write data to a network can use the protocol to create gui apps.
Scalability: Since the ntw server does not store or draw widget graphics, the memory and computational overhead of running an ntw application is much less than a comparable X Window application. A low end machine could easily serve hundreds of remote clients.
Productivity: Users can run ntw apps without installing anything but the client. Developers can release new versions of their apps without the users having to do anything, much like a web page.
Reference Implementation:
The current reference implementation of the client implements most of the widgets in the Gtk toolkit, and is written in C using the GTK+ 2.0 toolkit for drawing the widgets and handling events. It compiles and runs on FreeBSD, Linux, and Windows, and likely other Unix variants also. Youll need the GTK+ toolkit installed to run the client, and the GTK+ development headers to compile it.
The source code also include a server reference implementation and a sample server application. The "server" is really a set of C language bindings to functions that create and send ntw widget data. The bindings can be used in much the same way as any other GUI toolkit. See the file "ntwtest.c" for the example application. Its been tested on FreeBSD, Linux, and Windows XP. The server library should compile and run on most systems with a C compiler and support for sockets, without the need for any additional libraries.
The protocol is defined by the two header files, ntw.h and ntw_signals.h. These are C header files that describe exactly the byte layout for each of the widgets and all of the opcodes and events that can be sent.
There are still some widgets missing, and some of the signals raised by GTK are not yet handled in the protocol. This will be fixed in the near future.
Note: Although the reference implementation is coded in GTK, the NTW protocol is designed to be independent of any particular widget toolkit. GTK was picked due to favorable design features and a favorable license.
Enhancements:
- 02JUL06 - Fixed bug in update.c where spin_button was switched with slider
- 02JUL06 - Removed status field from image_buffer widget protocol

AScd is a CD player that can be "docked" with Afterstep and Window Maker with the following features:
Main features:
Advanced CD Player:
- Several modes including loops, intro scan, autoplay, autorepeat
- Hardware volume control with mute and auto-fade in/out
- WorkMan database support with song name scrolling
- all settings can be saved and loaded at startup
- Hardware control based on LibWorkMan
- Multi-platform: tested with FreeBSD, Linux, Solaris, AIX
Fully customizable interface:
- Multiple theme support
- 100% customizable screen layout
- Not restricted to "dockable" sized windows, themes support any window size
- Multi-panels support
- Up to 200 elements per theme
- Horizontal and vertical sliders to use for CD direct access, mixer controls or hardware volume
- Separate designs for main and icon windows
Optional features:
- configuration window using WINGs toolkit
- Workmans database edition
- mixer support (tested with FreeBSD and Linux)