On Sat, Aug 7, 2010 at 6:10 PM, Geoff Beasley
<geoff(a)laughingboyrecords.com> wrote:
> Niels, great that you and Tim have fixed this app ;) One thing, can you
> explain what those 'profiles' are for and how to use them?
Envy24control uses the same mechanism as your system does (see
/etc/asound.state and amixer(1)) to save the state of your ALSA
devices between boots. The difference is this mechanism puts the file
under your control at ~/.envy24control/profiles.conf and allows you to
set eight different profiles: allowing you to save or restore up to
eight different "asound.state"-like configurations per card.
The different profiles are most useful for storing routings set in
"Patchbay/Router" panel, as well as "Hardware Settings" panel clock
rate, or external SPDIF/wordclock sync. On cards with switchable
spdif/optical ins (Terratec/Terrasoniq), you can persist this extra
level of "routing" -- which is useful for "matrix routing" between two
digitally-interconnected and sync'd computers. ( I use profiles named:
44dmix-to-1&2&spdif, 48dmix-to-1&2&spdif, spdmix-to-1&2&spdif,
44all-outs-pcm, 48all-outs-pcm, spdif-all-outs-pcm,
96dmix-to-1&2&spdif and 96all-outs-pcm. ).
When you have a combination of settings in envy24control that you want
to return to, just go to the "Profiles" panel, enter the name of the
profile into the first free text field (initially these will be
numbered "1" through "8"). After entering a descriptive name, click
"Save active profile." To restore a given profile, just click on the
"button" area surrounding the text field, or even click within the
text field. You'll notice the selected profile "button" indicates
activation via coloration. After changing profiles, go to, for
example, Patchbay/Router or "Hardware Settings" panels,and note that
the previously saved state was restored.
Note that significant amounts of setting data gets saved in these files:
> ll ~/.envy24control/
-rw-r--r-- 1 npm npm 115253 2010-08-07 23:10 profiles.conf
For comparison:
> ll /etc/asound.state
-rw-r--r--. 1 root root 128079 2010-08-07 18:15 /etc/asound.state
(That's for a system with two envy24-based cards installed, thus size
is large, causing "save" to produce a brief but noticeable pause in
the metering on a slower system or "ondemand" throttled system).
Niels
http://nielsmayer.com
PS: speaking of envy24 anybody know whether this will work in standard
alsa/linux:
http://www.lionstracs.com/store/msaudio-board-envy24-p-122.html
and are those i2s connectors, or ttl-level spdif? i guess if it's i2s
you have to get:
http://www.lionstracs.com/store/mixer-board-p-210.html (which looks
pretty cool, esp w/ the onboard dream-based hardware synth w/ large
sample ROM).
Hey all,
I'm a bit overwhelmed when I mentally go through the possible ways of
organising and syncing my midi maps in linuxsampler to Rosegarden/how many
midi ports etc to use.
My situation is thus:
I have about 50 or so midi banks comprising of anywhere from 5 to 128
instruments, each in their own seperate midi map (Flame Guitars 1, 2, 3,
General Midi Set etc) and each bank is numbered sequentially throughout the
entire Map (as a side note, this probably isn't the most efficent way of
doing this, but I'm learning!).
Now, in Rosegarden, I've set up Banks in the 'Manage Midi Devices' tab for a
single midi device (I have all 50 banks of the midi maps here, accessed by
sending LSB Change messages to linuxsampler) and entered in each program
name (By hand! I'm going off on tangents left right and center here, but
surely there's a more automated way of entering in Program names for
changing patches?).
So, considering that Midi can only handle 16 channels at any one time for a
single midi port, I'm obviously going to have to use (currently) about 4
midi ports in linuxsampler if I want 1 midi bank on each channel (not
necessarily going to be using all of them at the same time of course).
The question then is:
Should I take 16 midi banks in linuxsampler, and assign them to a single
midi map, which'll then be assigned to 16 channels connected to a single
midi port, accessible by Rosegarden or perhaps group them by instrument type
in groups of 16 etc?
I would appreciate your views on this immensely!
Andrew.
Hello everyone1
There still are some ladspa plugins, which don't have a latency output
control. So I wonder how to measure their latency? I've heard, that Ardour can
do it, so I suppose there is a relatively short process to do it?
Can you suggest a tool, a method to quickly measure the latency of a plugin?
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
in a first attempt on new opensuse 11.3 it seems to me that nouveau behaves similar to proprietary nvidia driver - this means for me nogo for realtime audio and fw-card, due to interrupt issues (Lenovo R61: Yenta and Nvidia share one interrupt). Switching to nv eliminates these constraints.
If nv is subject to be removed in future releases then I will continue to work with my excellent running opensuse 11.2 (plus selfbuilt rt-kernel) till the end of my Laptop (which is not that far cause it's a really hard working machine *lol*).
best
Susanne
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
Hi
Here is a little session with my self-made "cocolele" played and
captured with guitarix(jack_capture).
It's a plain session without any remaster, but I hope you enjoy it.
http://soundcloud.com/brummer/guitarix-coconut
greats hermann
Hey all,
There's a chance I will have some spare time towards the end of August,
while in the Netherlands.
Are there any Linux/Sound events scheduled for around that timeframe?
Appreciate any/all suggestions, -Harry
Hi!
Have started jack-rack and tried to find FCAC sine oscillator. Have not found.
All other variants (FAAA, FCAA, FAAC) are there (from sine.o and cmt.o). Do
FCAC ones exist at all?
Andrew
Hello all,
I'd like to get an idea of how the 'nouveau' driver for Nvidia
graphics cards is working on systems used for audio production.
I have installed it on a number of systems over the past half
year, all of them ArchLinux and using a 'standard' (i.e. non
realtime-patched) kernel, 2.6.32 upto 2.6.34, with Xorg 1.7
and 1.8.
On some systems 'nouveau' seems to work really well, on some
others it produced lots of xruns (using a moderate jack period
size of 256) which went away when I replaced 'nouveau' by the
older 'nv'. I did not try the proprietary driver from Nvidia,
AFAIK it has latency problems as well.
Sooner or later 'nv' is going to disappear, and we will only
have 'nouveau' or the proprietary driver. I'd want to avoid
a situation where no usable Nvidia would be available to users
of audio systems. *If* there is a problem with 'nouveau' we
should identify it and get in touch with the developers.
The first step in this process would be to collect some user
feedback.
Ciao,
--
FA
There are three of them, and Alleline.
After some talks with falktx I publiced new version, which has Makefile and (by my own initiative) Debian-related files.
Since build system may store several builds, e.g. with various prefixes, Makefile manages by default last created build.
To change default build run:
$ ./configure --default-build=build_name
Or run
$ ./configure --builds
to get list of available builds.
Also, install script now has one argument to override install root (default is "/").
E.g., if you type:
./configure --prefix=/usr --buildname=build
./install ~/packages