We're getting very near release for our first CD, which was mixed, edited and overdubbed on Linux in Ardour, and will probably be mastered on Linux as well. Here are some getting-pretty-close-to-finished mixes:
http://lahar.s3.amazonaws.com/scratchmixes-basic/foie-A.ogghttp://lahar.s3.amazonaws.com/scratchmixes-basic/ginseng-A.ogg
What's giving me headaches is bass rolloff on certain systems. On the nice flat Fostex studio monitors I was able to borrow-- and which don't have any bass emphasis--, it sounds well balanced. On crappy iPod earbuds which roll off the bass like crazy, it works well too. But on car stereos or club systems which emphasize the bass, the kick drum and bass guitar are way too hot-- sounds like the whole thing was recorded from inside the kick.
Not sure what to do about this. Would appreciate any advice from the experience mix engineers around.
-ken
Hi folks.
I am looking for a simple commandline tool which offers gain control in
double precision preferably in db on .wav.
Nothing real fancy file-in/file-out, no dither, no src, no nothing - beside
gain control ;) .
Sox and ecasound are working in 32bit precision afaik.
THX
Cheers
Please, help me, i could not solve it!:
On Monday 05 April 2010 00:06:15 Roger wrote:
> Marcos Germán Guglielmetti wrote:
> > Hi
> >
> > I have this PCI soundcard (from "Encore" manufacturer) and I am using
> > debian lenny
> >
> >
> > lspci | grep audio
> > 01:09.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24
> > [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
> >
> > I cant get sound of the 2 channels using neither an old 2.6.18 kernel or
> > a new 2.6.32 from Debian or a 2.6.29 from Musix.
> >
> > There is no problem with the physical output jacks: all headphones play
> > only one channel.
> >
> > Also i tried with all the mixers: alsamixer, gamix, gnome-alsamixer,
> > kmix, etc. enabling and disabling all the things and it does not work
> > well.
>
> I recall a similar problem on a Debian system once, with my Audiophile
> 2496 (same chipset). I think I resolved it simply by installing
> alsa-tools-gui and using the Envy24 Control mixer.
Thanks for your help, but I tried it before and envy24 control said:
no ice1712 cards found
what could i do?
Thanks in advance
> It may have been a
> matter of the correct volume controls not showing in the alsa mixers.
> Although the Envy24 Control mixer did not seem to function completely
> logically, I did manage to get satisfactory stereo output.
>
> Cheers
> Roger
--
Marcos Guglielmetti
▲
:::::::::::::::::: M U S I X :::::::::::::::::::::
▼
www.musix.org.arwww.ovejafm.com
The CLAM project is pleased to announce the first stable release of Chordata.
Chordata is a simple but powerful application that analyses the chords of any
music file in your computer. You can use it to travel back and forward the song
while watching insightful visualizations of the tonal features of the song.
Key bindings and mouse interactions for song navigation are designed thinking
in a musician with an instrument at hands.
Don't miss it working in this video:
http://www.youtube.com/watch?v=xVmkIznjUPE
Downloat it at http://clam-project.org
--
David García Garzón
(Work) david dot garcia at upf anotherdot edu
http://www.iua.upf.edu/~dgarcia
Hi
I'm trying to document my non-trivial live-setup, and would like to traw
some flow charts of audio and midi routing. I tried dia, but it seems to
insist that one "box" can only have one "input" and one "output" (I'm
using the symbols from "flowchart".
Is there a way to do this in dia, or is there something better/different
that I should look at?
I imagine something like this:
______
| |
| FA66 |---- _________
| |----------| JackRack|
| | |_________|
| | ____|_|______
|______| |SooperLooper |
|_____________|
--
Atte
http://atte.dkhttp://modlys.dk
oops, mailing an audio file to the while list was probably a terrible
idea... sorry folks...
Also, forget what I said about noise gating. I forgot my close-reverb
has a predelay bug that introduces a little noise that sounds like bad
gating. Gotta remember to fix that one day.
Monty
James Morris:
>
> $ lame -h --preset cd --ogginput azr3.ogg azr3.mp3
> sorry, vorbis support in LAME is deprecated.
>
> what's with that? are they just being awkward?
>
Workaround:
ogg123 -d raw -f /dev/stdout input.ogg | lame -V2 -r -h - output.mp3
Hi everyone,
A short email to explain why i haven't made any progress neither on
Tapeutape nor on Tranches (and still not released planned new
applications) in several months , just in case someone wonders ;)
I'm writing my phd thesis, which is partly about this:
http://vimeo.com/9206485
It's an immersive environment for hierarchical live-looping (explained
in the video).
All software runs on Gnu/Linux (ubuntu for the graphics, fedora/ccrma
for the audio).
It uses Jack for audio output, Alsa to get the values of the input
device (FSR sensors) , LV2 plugins for effects, and VAMP plugins for
audio analysis.
I have three months paid at the end of the year to clean up the code,
make it more user friendly, and usable without an expensive setup (so it
will have OpenSoundControl input in addition to direct sensors input and
also support for things like ARToolkit for cheap 6DOF tracking).
After that, it will be released on http://tardigrade-inc.com
I'll be in Sydney , June 15th-18th , to present it for the NIME conference.
So if anyone from the list is there, i'll be happy to meet them and talk
about linux audio stuff !
If you have any questions/suggestions , don't hesitate ;)
Regards
Florent
The second milestone is reached and result is a tarball that brave souls
may want to download and try. It can start apps and restore their
connections. Level 1 apps are supported.
Beware that no apps have implemented level 1 yet. If non-level-1 app is
started at level 1, it will probably quit on save, because the default
signal handler for SIGUSR1 terminates the process.
This preview also features a2jmidid support. Run the a2j script as an
app in the studio.
This is a beta quality software, use it with double caution.
I would like to thank the early adopters and especially Frank Kober for
their help with testing the git ladish code and for the valuable
suggestions they gave.
Build will produce three operational components:
* ladishd - The daemon, a D-Bus service
* gladish - GTK GUI interface
* ladish_control - Command-line interface
In the tarball you will also find bundled:
* flowcanvas-0.6.0
* LADI Tools (svn version)
* a2jmidid-6 (contains the a2j script for use in ladish)
* jack2 from the ladi branch
The jack2 ladi branch contains fixes for two important issues:
* Race that causes connection restore to fail sometimes during studio
startup (http://ladish.org/ticket/28)
* A deadlock on studio start (http://ladish.org/ticket/35)
Hopefully, these fixes with be in the next jack2 release (1.9.5).
The jack2 ladi branch also contains the no-self-connect changeset that
adds new engine option, for disabling self connect of apps. Default
value for this option is to allow self connections.
Make sure to configure jack2 with --dbus (and maybe with --classic too).
Download:
http://ladish.org/download/ladish-0.2.tar.bz2http://ladish.org/download/ladish-0.2.tar.bz2.sig
Homepage: http://ladish.org/
Roadmap: http://ladish.org/roadmap
---------------------------------------------------------------------
LADI Session Handler or simply ladish is a session management system
for JACK applications on GNU/Linux. Its aim is to allow you to have
many different audio programs running at once, to save their setup,
close them down and then easily reload the setup at some other
time. ladish doesn't deal with any kind of audio or MIDI data itself;
it just runs programs, deals with saving/loading (arbitrary) data and
connects JACK ports together. It can also be used to move entire
sessions between computers, or post sessions on the Internet for
download.
Project goals:
* Save and restore sets of JACK (audio and MIDI) enabled
applications.
* Provide JACK clients with virtual hardware ports, so projects can
be transfered (or backups restored) between computers running
different hardware and backups.
* Don't require session handling library to be used. There is no need
of such library for restoring connections between JACK clients.
* Flow canvas based GUI. Positions of elements on the canvas are
saved/restored.
* Allow clients to use external storage to save its state. This
includes storing internal state to non-filesystem place like memory
of a hardware synth. This also includes storing client internal
state (client project data) in a way that is not directly bound to
ladish project.
* Import/export operations, as opposed to save/load. Save/load
operate in current system and may cause saving data outside of
project itself (external storage). Import/export uses/produces
"tarball" suitable for transferring session data over network to
other computer or storing it in a backup archive.
* Hierarchical or tag-based organization of projects.
* List of JACK applications. Applications are always started through
ladish to have restored runtime environment closer to one existed
before project save.
* Distributed studio - network connected computers. Netjack
configuration is part of the studio and thus is saved/restored.
* Collaborate with the X11 window manager so window properties like
window position, virtual desktop and screen (multimonitor) are
saved/restored.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>