> Incidentally, now that it's working, is there a way to make the fonts
bigger?
There are too many ways to do this! I use either the ~/.Xdefaults file
with
lines like:
snd*axisLabelFont: -adobe-times-medium-r-normal-*-18-*-*-*-*-*-*-*
snd*helpTextFont: 9x15
or the init file (~/.snd) with similar stuff:
(set! (axis-label-font)
"-adobe-times-medium-r-normal-*-18-*-*-*-*-*-*-*")
(set! (axis-numbers-font) "9x15")))
You can use the same init file with gtk (which has a different font
naming
convention) -- see grfsnd.html for details.
Hi all,
I'm trying to put together some content for the proceedings of the Modular
2002 conference, where I spoke about the state of Linux Audio, but I need
decent screenshots for Muse, pd and Noteedit, none of which I know well
enough.
Ideally screenshots should be <= 1024x768 - 600x400 is ideal.
Obviously anyone who provides shots gets mentioned in the acnowledgements.
Slighit problem is that I need the shots ASAP, I need to submit the
content in the next 2 hours.
Cheers,
Steve
I can't resist posting this hack, though I doubt it's actually useful.
In
response to the Snd font problem mentioned earlier, I wrote some
xm-module-based code to show what fonts a given widget is trying
to use:
(define (show-font-name font)
"(show-font-name font) shows the Snd-related name and the X-related
name of each font \
in a widget's font list"
(define (show-next-font context)
(let ((next-font (XmFontListGetNextFont context)))
(if (car next-font)
(begin
(if (XFontStruct? (caddr next-font))
(snd-print
(format #f "~A: ~A~%"
(cadr next-font)
(XGetAtomName
(XtDisplay (cadr (main-widgets)))
(list 'Atom
(cadr (XGetFontProperty (caddr next-font)
XA_FULL_NAME))))))
(snd-print (format #f "no font found!~%")))
(show-next-font context)))))
(let ((context (XmFontListInitFontContext font)))
(show-next-font context)
(XmFontListFreeFontContext context)))
So, if it's the minibuffer that's giving trouble:
(define (show-minibuffer-font)
"(show-minibuffer-font) shows what fonts are associated with the
minibuffer"
(show-font-name
(cadr (XtVaGetValues
(list-ref (sound-widgets) 3)
(list XmNfontList 0)))))
If the font name looks ok, try C-z (in the new version), and send me a
description
of what you see.
Hi,
searching the laa/lad/lau web archives is back online!
Let me know if you notice any problems.
links:
http://www.eca.cx/laahttp://www.eca.cx/ladhttp://www.eca.cx/lau
On Sat, 24 Aug 2002, Kai Vehmanen wrote:
> The htdig-installation that is responsible for the search
> functionality of LAD/LAU/LAA web archive, is temporarily disabled.
--
http://www.eca.cx
Audio software for Linux!
Hi,
I dloaded alsa 0.9.0rc3
I have a custom built 2.4.7-10 kernel
My kernel sources reside at /usr/src/linux-2.4.7-10
and my kernel modules at /lib/modules/2.4.7-10custom
I have a CMI8738
I used the following set of commands:
./configure --with-kernel=/usr/src/linux-2.4.7-10/
--with-moddir=/lib/modules/2.4.7-10custom/ --with-cards=cmipci
--with-sequencer=yes
and the regular make and make install.
during make install a lot on unresolved dependancies show up.
I am unable to insert the snd-cmipci module due to these unresolved
dependancies.
any clues to what could be the problem?
One more question... will i be able to play sound from multiple sources
(without using arts/esd) with the alsa drivers.
Thanx,
Nanda
On the Lesstif/Motif business, you can find out which library is loaded
with ldd snd. There's a --with-motif-prefix configure switch if
configure
is finding Lesstif instead of Motif.
I've also noticed the empty-box-where-glyph-should-be-bug even
when all the correct fonts are loaded, but I was putting off looking
into it --
there's always the hope that no-one else would notice...
I'm told that someone is making a real effort to fix Lesstif, so maybe
it will
be usable someday soon.
We are pleased to announce Quicktoot release number 8
----------------------------------
Recording Audio from JACK-Enabled Applications in Ardour written by Tony
Schiavone.
http://www.boosthardware.com/LAU/quicktoots/
If you don't know how to do this you don't know JACK!
Essential reading for anyone who wants to get multiple audio apps
working in realtime with low latency in the Linux environment. JACK is
the Jack Audio Connection Kit - the Linux answer to Core Audio. Ardour
is a professional Digital Audio Workstation. MusE is a professional MIDI
editor. You want to have these working together like Tux needs water.
-----------------------------------
The purpose of the Quicktoots are to provide a community resource of
informative guides for using Linux audio applications.
The Quicktoots are the brainchild of Dave Phillips the man responsible
for the most comprehensive webpage devoted to Linux audio applications.
The Linux Sound and Midi page. Your one stop resource for Linux sound
software.
http://www.bright.net/~dlphilp/linuxsound/
If you are in the position to link to any of the quicktoots please link
to the main page. That way we can keep more accurate statistics on the
amount of people viewing the pages.
If you are interested in contributing to the Quicktoots please let us
know. All work must be submitted to either Dave or myself and we will
give advice or make changes to ensure our publishing standard is met. If
you are not able to send html don't worry because I am willing to format
any braindumps.
Enjoy.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.boosthardware.com/LAU/guide/
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Mark,
> I also use an Audiophile 2496. That's 4 in - 4 out for about
$150-$175. Two analog and two s/pdif.
I could live with that. I do want S/PDIF for interfacing with my
external decoder, the SB on my Windows machine, and my MiniDisc
machine. Old-fashioned analog would be nice because I could connect
directly to my old-fashioned analog mixer.
But I don't see any Linux drivers for the 2496.
If I could get away with AMD, I probably would. Otherwise, I'd
consider plunking for a 1.8 GHz Celeron. Since my two main Windows
computers are running ASUS boards, I certainly have nothing against
ASUS. I just want to head off as many incompatibilities as I can up
front.
Thanks!
Scott
Hi all,
Well, my old soyo mobo seems to have fried.
I see tons of possibilities on the market, but hey,
this is audio... we have weird needs and sometimes it's
hard to tell from a spec sheet..
Can anybody recommend motherboards and/or chipsets
that meet these criteria?
- good for low-latency audio work, e.g. don't
have nasty southbridge bugs (or at least have good
kernel workarounds)
- ATX form factor
- will take a PIII 866 (coppermine, socket 370)
- Dual CPU capability would be nice, that'll probably
be my next upgrade
- will take PC-133 memory, at least 512 MB
- onboard IDE must work with CDDA (ripping)
- no built-in video
- no built-in audio, or at least it can be disabled or safely ignored
- won't fry after a year and a half of routine use :(
--
Paul Winkler
"Welcome to Muppet Labs, where the future is made - today!"