>>>it's easy for non-programing people to bring "visions" regarding
>>>interface design. (and i love do so :) as i know programers, it's quite
>>>hard to establish a new standard. but imho the interface standards
>>>(buttons, dropdown boxes, scrolling, menu-structure, etc.) are now a
>>>couple of years old, and there might be better solutions for specific
>>>tasks. audio seems to me like a good point to start.
> i wasn't talking about such rudimentary stuff. of course there are
> alternatives to these basic widgets and several audio applications (even
> free ones) have begun to support them.
> the point about a visual interface is that it acts as a "memory buffer"
> for the user: you do not have to remember much about the structure of
> the session because the structure is made visible on the screen. can't
> remember precisely where you put a certain sound? how many copies of the
> bridge riff did i put in? is the door slam before or after the creak?
> its all there on the screen, just waiting for you to look at it.
> as soon as you move away from a visual UI, you have to find some way to
> avoid requiring the user to remember everything about the session.
when i try to remember a poem my brain creates images and i walk trough
them, when i reproduce it. when i learn a piece of music it does other
stuff (i'm a pianist and singer) but in the end i have a very complex
thing in my mind, just think of a bach fugue. i have the fugue also in
"the fingers". different areas of the brain work together. i have the
same oppinion as you, we are very good in using a visual UI. we trained
it for a long time. but there could be other combinations that work
nearly as good as "mouse-to-eye".
> the visual interface offers another hard-to-replicate feature as well:
> trivially variable precision. if you try doing cut-n-paste based only on
> audio feedback, you will find it quite hard/laborious to be as precise
> as you might want to be. with the visual interface, its much easier to
> use visual information to get the rough location of an edit and then
> get to precisely where you want, without many steps. with audio feedback
> based approaches, i think you will find yourself needing many more
> iterations through the edit-play-edit-play cycle before you get the
> location correct.
i think it's all a matter of training. you do the
"display-keyboard-mouse-combination" for long years and you became
professional in speed and precision. watch a pro-gamer gaming with
mouse.. what's about data-gloves? whats with feet-controlers and other
(sorry for my clumsy english)
I am looking for suitable hardware to handle digital i/o between a Linux
system and an RME ADI-2 ad/da converter that I just bought. I don't need lots
of channels, but reliability of the data transfer is important, including
jitter reduction. An RME card would be excellent but it is somewhat outside my
budget. Also, connectivity to a laptop would be desirable, suggesting either a
USB interface or waiting until http://freebob.sourceforge.net/ (the Alsa
firewire project) matures. I don't plan to run any OS besides Linux with this
hardware, so Alsa support is crucial. As this is for home/personal use I'm not
in a hurry. M-Audio hardware is high on my list of possibilities at the
Now to the software question: does there exist any sound editor with a
non-graphical interface, i.e., one that can be operated from the Linux console
for inserting, deleting, copying and otherwise editing audio? Due to a
vision-related disability I can't use a graphical display and therefore need a
text-only solution - but all the sound editors appear to require X11. Surely
it should be possible to design an audio interface to a digital sound editor.
I've discussed hardware on this list once before, and the USB options weren't
highly regarded at the time.
hello all - got a question - I've only recently been stopping and taking a
look at my studio computer's performance and in the almost year since I
change from Red Hat 9 to gentoo, it's been more solid on some things, but I
notice a huge latency difference - ie: I have to run Jack at -p 8192 to get
anything done in Ardour
Anybody have any tips on what to look at to tweak it? Seems like it should
do better than that... I didn't see it as a problem until in the last few
days I started playing with playing softsynths live directly into Ardour -
you've gotta be running at -p 1024 or there's a latency that screws up your
playing - at 8192 it's a downright 8th note delay...
Here's some vitals that I can think of:
OS: gentoo 2.6.6-rc1 kernel (alsa built in)
jack command line:
jackd -R -d alsa -d hw:0 -r 48000 -p 8192 <------- (or whatever)
io support: 32 bit
use dma on
chip: 2ghz amd (I THINK - not at computer now)
thanks for any ideas! :)
I am having 3 different problems with RG4 on 3 different debian distros.
Xubuntu 32 bit
When I start Rosegarden I get the splash screen then after a while I get an
error message flashing up that's too fast to read. Rosegarden does not
I get the RG splashscreen and then a crash sound output (breaking glass). I
do not get any error message.
Nothing works when I start it up, no keyboard, no mouse, nothing. The only
way out is to hit the system reset button whcih is obvously no good for the
system. I also takes longer to recover from sucha position becasue Demudi
does a system disk check.
I really would like to get Rosegarden up an running as I have ben trying to
do so for about a year now (on and off)!.
Please let me know what info I need to post to get help on this.
Thanks for any help.
View this message in context: http://www.nabble.com/Rosegarden4-Freezes-my-machine%2Cneed-to-system-reset…
Sent from the linux-audio-user forum at Nabble.com.
(I am cc-ing the linux audio user list, in the hope of broadening
the audience and reaching someone able to help me sort this out.)
On Tue, Mar 14, 2006 at 12:02:56PM +0100, Asbjørn Sæbø wrote:
> I am trying to get a Digigram VxPocket sound card working, and really
> need some advice on how to proceed.
> [Rest of previous post far below.]
In addition to what I have done before (see below), I have now created a
/etc/pcmcia/vxpocket.conf according to the description at the bottom of
the alsa-project page for the vxpocket card. And I have added the
necessary lines to /etc/modutils/alsa-base, and run update-modules.
The visible results of this is that
* The vx-* modules now seem to be loaded at boot
* The card is still not recognized by alsa (it is not listed in
/proc/asound/cards, and alsaconf does not find it).
* cardinfo no longer says "unsupported card", but "empty". It does
however list "IO 0x100-0x10f" and "IRQ 5" (or "IRQ 9d" or "IRQ o"(?)).
* "cardctl info" and "cardctl ident" hang when they come to the socket
containing the card.
* Restarting the pcmcia service gives the following error messages:
snegle:~# invoke-rc.d pcmcia restart
Shutting down PCMCIA services: /etc/init.d/pcmcia: line 173: kill: (4040) - No such process
Starting PCMCIA services: cardmgr: watching 2 sockets
cardmgr: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy
cardmgr: could not adjust resource: IO ports 0x800-0x8ff: Device or resource busy
cardmgr: could not adjust resource: IO ports 0xc00-0xcff: Device or resource busy
cardmgr: could not adjust resource: memory 0xc0000-0xfffff: Input/output error
cardmgr: could not adjust resource: memory 0xa0000000-0xa0ffffff: Input/output error
cardmgr: could not adjust resource: memory 0x60000000-0x60ffffff: Input/output error
cardmgr: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy
I am beginning to suspect that I am up against some pcmcia bug. And I
am, at least for now, out of ideas of what to try next to get this card
working. Suggestions, advice and tips are very welcome!
> The system is an ASUS L5000-series laptop running DeMuDi 1.2.1. The
> kernel is 2.6.12-3-multimedia.
> So far, I have installed the pcmcia-cs package and the hotplug package.
> (Do I need both of these? Do they conflict in any way?)
> From what I have read of documentation, it seems that with 2.6-kernels,
> hotplug is the way to go. Does having the "cardmgr" running interfere
> with this?
> I have also downloaded the alsa-firmware corresponding to the alsa
> version installed (1.0.9). (DeMuDi does not distribute this firmware.)
> I ran "./configure --disable-loader", "make" and "make install".
> This resulted in a set of files being placed under
> /usr/lib/hotplug/firmware, among them, it seems, files related to the
> vxpocket cards.
> The PCCard system itself seems to be working. At boot, a Yenta card bus
> bridge is found. And "cardinfo" seems to notice that the card is
> present, but only says "unsupported card".
> "alsaconf" does not find the card. Trying to load the snd-vxpocket
> module gives no errors, and the module seems to be loaded afterwards
> (see below), but the card is still not found by "alsaconf".
> I have tried to run "vxloader" (is that depreceated?), which gives the
> message "no VX-compatible cards found".
> Where do I go from here? How do I get the card to be recognized? And
> what do I do to get the firmware uploaded to the card?
> With kind regards
> Asbjørn Sæbø
> snegle:~# lsmod |grep vx
> snegle:~# modprobe snd-vxpocket
> Restoring ALSA mixer settings ... done.
> snegle:~# lsmod |grep vx
> snd_vxpocket 4288 0
> snd_vx_cs 14080 1 snd_vxpocket
> snd_vx_lib 36480 1 snd_vx_cs
> firmware_class 10624 1 snd_vx_lib
> pcmcia 28480 10 snd_vxpocket,snd_vx_cs
> pcmcia_core 52628 4
> snd_pcm 96580 4
> snd 58404 12
i would like to tell you all that my first (and non finished) howto on
how to configure a mandriva linux system for audio works is online at
it's in italian only at the moment.
mjoo 0.0.4 has just been released.
This is a big leap forward from 0.0.3, as I entirely reimplemented mjoo
in Python, while keeping only the core dsp code in C++. The graphical
subsystem is now powered directly by OpenGL, thus substantially faster
on hardware accellerated video cards.
What you can do with this release is use mjoo as a mixer for jack. You
can add port cells to the view by right clicking into the mjoo window
and picking an object type from the context menu. Use e.g.
QJackCtl (http://qjackctl.sourceforge.net/) to connect other apps to
mjoo and vice versa. Middle-click-drag resizes the cells. By moving a
cell over another cell, the smaller cell has an influence on the larger
cell. e.g. move a small "in"-cell over a larger "out"-cell. "in" will be
routed to "out". The amplitude of the signal depends on how much of "in"
is enclosed by "out".
You can use the Ctrl key to select multiple cells.
This release has also initial support for LADSPA plugins (DSSI plugins
and serialization is supported but broken) and controllers. Click right
on a LADSPA plugin in the view to bring up a new controller for it. I
leave it up to you to find out how it works.
-- leonard "paniq" ritter
> 'm struggling with Scons, trying to build from source. Has anyone seen
> debian packages for this yet?
> Thanks in advance!
Make sure that PKG_CONFIG_PATH is correctly set in you /etc/profile or do it
before in the session doing the scons configure.
Then the thing will find the libraries it needs to compile. If it does not
find stuff it can live without but you want, install them first.
I'm a bit confused about midi note numbers:
1) am I right that the midi note number goes from 0 to 127?
2) which note name corresponds to 0? C0? C-1?
3) which would be the correct range (in note numbers) from a 88 note
peace, love & harmony
hey..another post here... this one to tell u about new stuff...
these days I've been very busy, so, I have not too many time to play
or record, but the other day I've recorded a strange soundcheck with a
small groovebox "a capella"... it has been terrible, but I've decided
to upload it...
4 all those electronica lovers... a very minimal session on my proyect:
( any kind of comment is good, thanks... ) .... :)
... visit always http://perlssdj.blogspot.com 4 cool stuff !!...