Re: [linux-audio-dev] Some more Muzak
On Mon, 19 Apr, 2004 at 06:29PM +0100, Steve Harris spake thus: > On Mon, Apr 19, 2004 at 06:43:46PM +, [EMAIL PROTECTED] wrote: > > All chopping and munging was done in cheesetracker, even the crunchy > > bass was made from the smooth one by over amplifying and then > > filtering out the nasties. Lots of ladspa effects helped, too, > > although the ones I most want to use (compressors, etc) are too slow > > to be used "inline" like that. > > > > Are there any VERY fast LADSPA compressors about? > > "Barrys Satan Maximiser", but its so fast it counts as distortion :) > > SC4 set to peak detection mode should be able to go as fast as is > sensible, if not, give me an example audio file and I'l change it. Thanks. James. > - Steve >
Re: [linux-audio-dev] jack_fst: a JACK client to run VST's
Paul Davis wrote: Torben Hohn and I are pleased to announce the initial release of jack_fst, a small JACK client designed to run VST FX and VST/i's with connections to the rest of the JACK world, and, for VST/i's the ALSA sequencer. Tarball is available at: http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz You will need the recently announced FST, a recent version of Wine, GTK+2 and JACK (from CVS at this time). Here is a list of VST plugins (actually) that are known to run successfully with jack_fst: I'm getting the following error with jack_fst make all-am make[1]: Entering directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2' if gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/vst -MT jfst.o -MD -MP -MF ".deps/jfst.Tpo" \ -c -o jfst.o `test -f 'jfst.c' || echo './'`jfst.c; \ then mv -f ".deps/jfst.Tpo" ".deps/jfst.Po"; \ else rm -f ".deps/jfst.Tpo"; exit 1; \ fi In file included from jfst.c:25: /usr/include/vst/aeffectx.h:934: parse error before "VstFileType" /usr/include/vst/aeffectx.h:951: parse error before '}' token make[1]: *** [jfst.o] Error 1 make[1]: Leaving directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2' make: *** [all] Error 2 Commenting out the VstFileType line allows it ito build and run ( at least with the two VST plugins Ive tried so far) -- Lawrie Abbott
Re: [linux-audio-dev] jack_fst: a JACK client to run VST's
>Our Wine based VST hosting app is doing much better with very recent >Wine's: we are happy with the April 4th build. Most of the compatibility >issues are with GUIs. oh, absolutely. i have yet to find a VST that i can't run if i don't open the editor. admittedly, i am deliberately only trying free VSTs, but the contrast is remarkable. and for ardour users: ardour can build its own GUIs for most VST plugins if you need it to. >Also if you're using threading, they recommend a not-too-recent 2.3.2 >glibc to help with threading issues. We are using 2.3.2-4.80.8 and it >looks good so far. Apparently getting threading to work between wine and >glibc has been tricky. heh. thats where libfst comes in. we started from the mono hack, which was known to not support threads. i then managed to apply some rather deep experience i have had with threading on x86 systems to the problem. nothing particularly clever, but libfst allows us to take a thread created outside of wine and get wine to "adopt" it, thus allowing win32 code to be executed by it. ok, so its pretty clever :) we are at least 50% optimistic that this part of libfst will make it into wine at some point in the not too distant future. i will be talking about this work at ZKM in less than 2 weeks. --p
Re: [linux-audio-dev] MuSE 0.9 codename "COTURNIX" - out now with documented API!
At Mon, 19 Apr 2004 07:55:59 +0200, Robert Jonsson wrote: > > There is an unfortunate fact in that there are TWO muse projects, > differing only in the use of capital letters. I was staring at the webpage for a full ten minutes before I realized what was going on. MusE with a GTK-2 interface? What? Uncool. Somebody should rename their project to "The Project Formerly Known as Muse," or perhaps some sorta whiz-bang symbol. [pb]
Re: [linux-audio-dev] jack_fst: a JACK client to run VST's
Our Wine based VST hosting app is doing much better with very recent Wine's: we are happy with the April 4th build. Most of the compatibility issues are with GUIs. Also if you're using threading, they recommend a not-too-recent 2.3.2 glibc to help with threading issues. We are using 2.3.2-4.80.8 and it looks good so far. Apparently getting threading to work between wine and glibc has been tricky. For what it's worth... mo On Mon, 2004-04-19 at 18:44, Fernando Pablo Lopez-Lezcano wrote: > Can you elaborate in terms of which version of wine you have used > successfully? (ie: wine = x.y.z or wine >= x.y.z?) > > -- Fernando > >
Re: [linux-audio-dev] jack_fst: a JACK client to run VST's
>Can you elaborate in terms of which version of wine you have used >successfully? (ie: wine = x.y.z or wine >= x.y.z?) i am using wine 20040309. i think torben has a slightly earlier version than this which has worked for him to the same extent. --p
Re: [linux-audio-dev] jack_fst: a JACK client to run VST's
On Mon, 2004-04-19 at 13:11, Paul Davis wrote: > Torben Hohn and I are pleased to announce the initial release of > jack_fst, a small JACK client designed to run VST FX and VST/i's with > connections to the rest of the JACK world, and, for VST/i's the ALSA > sequencer. > > Tarball is available at: > > http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz > > You will need the recently announced FST, a recent version of Wine, Can you elaborate in terms of which version of wine you have used successfully? (ie: wine = x.y.z or wine >= x.y.z?) -- Fernando
Re: [linux-audio-dev] initial release of libfst - in-process VST support
On Mon, Apr 19, 2004 at 05:29:00PM -0400, Dave Robillard wrote: > Should we maybe organize a letter-writing campaign or something like > that to attempt to convince Steinberg to make VST free? My understanding was that they would do it, except that the SDK doesn't work in g++. GMPI will (maybe) obsolete that all, one day. Until then, a free VST is a great answer.
Re: [linux-audio-dev] initial release of libfst - in-process VST support
On Mon, 2004-04-19 at 15:58, Paul Davis wrote: > To build the library from source, you will need the Steinberg SDK > header files AEffect.h and aeffectx.h. These cannot be redistributed > by us or anyone else. The configure script will tell you where to get > them. The registration process with Steinberg points you to an FTP URL > that does not have the VST SDK on it. Use this instead: > > ftp://ext2asio:[EMAIL PROTECTED]/SDK > > Please do NOT bypass the Steinberg registration process. It is > important to show them whatever level of interest the Linux world has > in VST. > > --p Should we maybe organize a letter-writing campaign or something like that to attempt to convince Steinberg to make VST free? -Dave
[linux-audio-dev] jack_fst: a JACK client to run VST's
Torben Hohn and I are pleased to announce the initial release of jack_fst, a small JACK client designed to run VST FX and VST/i's with connections to the rest of the JACK world, and, for VST/i's the ALSA sequencer. Tarball is available at: http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz You will need the recently announced FST, a recent version of Wine, GTK+2 and JACK (from CVS at this time). Here is a list of VST plugins (actually) that are known to run successfully with jack_fst: Ambience.dll AnechoicRoomSimulator.dll BarsStripes.dll Big Tick Hexaline.dll BLOCKFISH.dll Boss DS-1.dll Boss SD-1.dll Classic EQ.dll Crystal.dll Cyanide2.dll DebaserDemo.dll DeeLay_sm.dll Delay Lama.dll deloizer095.dll DFX Transverb.dll dominion v1.2.dll Drumatic_22.dll endorphin.dll E-Phonic XPressor.dll FLOORFISH.dll Frohmage.dll GoldenGate.dll H2O.dll JS Vibrato V1.0.dll LoopaZoid.dll mabento.dll MadShifta.dll mda DX10.dll mda ePiano.dll mda Piano.dll MjMultibandCompressor.dll MjRotoDelay.dll ParisEQ.dll relofter.dll resolator_1.03_demo.dll RetroDelay.dll SIR.dll sloper.dll SoloString_v10.dll SPITFISH.dll Stretch & Squash.dll SupaPhaser.dll Syntar.dll Tape Delay.dll THD.dll themodulator2.dll Trancemitter.dll
[linux-audio-dev] initial release of libfst - in-process VST support
Torben Hohn and I are pleased to release an initial version of libfst, a small GPL'ed C library that provides support for using win32/x86 VST plugins (FX and VST/i) within native Linux applications, with the assistance of the Wine project's libwine. == We expect there will be several minor problems with this initial release. Please help us fix them! == How is this different from VSTserver? - This work differs from Kjetil Mattheusen's VSTserver because the plugin is loaded into the address space of the program using the library, not into a server. As a result, it is a more appropriate solution for audio applications that might support many VST plugins, where the context switches required in the VSTserver case do not scale well. The downside, of course, is that a misbehaving plugin will crash the host application, which VSTserver avoids. Why is it called FST? - In case you wonder, "fst" stands for FreeST. Imagine saying "VST" with an odd lisp. Where do I get it? -- The tarball is available from http://linuxaudiosystems.com/fst/fst-1.5.tar.gz How do I know it works? --- Ardour and gAlan are already using this technology, and please read my next announcement. Dependencies The library is very small. You will need a recent version of Wine. The configure step (which uses stuff built by Wine) takes much longer than the compilation. To build the library from source, you will need the Steinberg SDK header files AEffect.h and aeffectx.h. These cannot be redistributed by us or anyone else. The configure script will tell you where to get them. The registration process with Steinberg points you to an FTP URL that does not have the VST SDK on it. Use this instead: ftp://ext2asio:[EMAIL PROTECTED]/SDK Please do NOT bypass the Steinberg registration process. It is important to show them whatever level of interest the Linux world has in VST. --p
linux-sound.org's data as csv was: Re: [linux-audio-dev] Linux soundapps pages updated
On Mon, 2004-04-12 at 18:29, Paul Winkler wrote:
> FYI, I'm still planning to implement my own proposal which has
> been discussed quite a lot in the L-A-U archives.
> I do somewhat similar sites for a living. It just needs me to block out a
> chunk of time (1 or 2 weekends) to bang it out.
Hi Paul,
I'd like to assist so I've written a little script to automatically
extract all the links from linux-sound.org.
It depends on Ruby, wget, lynx and sed.
The output is tab separated csv (tsv) containing three fields per row:
text, urls and category.
Some of the s contain more than one url. For these the urls are
separated by blanks ' '.
The category is either the title () of the subpage or the text which
belongs to the list item containing the current ().
The script expects at least one url from linux-sound.org as arguments
(one of the subpages). So you'll also need a working internet
connection.
A '-H' prints an additional csv header.
I also attached a bash script to extract all the subpages from
linux-sound.org.
If you have any problems with this script I can send you all the data
off list.
HTH,
Jan
P.S. Follow-up to LAU?
#!/usr/bin/env ruby
# This little piece of software is free in every sense of the word.
# Mon, 19 Apr 2004, Jan Weil <[EMAIL PROTECTED]>
if ARGV.include?("-h") || ARGV.include?("--help") || ARGV.size == 0
puts "usage: #{File.basename($0)} [-H] URL..."
puts "-H --header\tadd csv header"
exit
end
if ARGV.include?("-H") || ARGV.include?("--header")
$print_header = true
ARGV.delete("-H")
ARGV.delete("--header")
end
def extract_urls(str)
urls = []
url_regex = /\[(\d+)\](\S.+)/
loop do
if str =~ url_regex
urls.push($reference[$1.to_i])
str.sub!(url_regex){|s| $2}
else
break
end
end
if not urls.empty?
return urls.join(" ")
else
return false
end
end
def push_li(line, level, regex)
next_line = ""
loop do
next_line = $lines.pop
if next_line =~ regex
line += " #{$1}"
else
break
end
end
$lines.push(next_line)
urls = extract_urls(line)
$data.push({"text" => line, "urls" => urls, "cat" => $cat[level] || "None"})
if urls
$cat[level+1] = line
end
ARGV.each do |url|
$reference = []
$cat = []
$data = []
# XXX this works, at least for linux-sound.org
url =~ /(\w+\.\w+)$/
loc = $1 or raise("Help me at XXX!")
`wget #{url}`
if $? != 0
exit 1
end
tmp = loc + ".dump"
# unset locales (we need ^References$)
ENV["LANG"] = "C"
`lynx -dump #{loc} > #{tmp}`
if $? != 0
STDERR << "calling lynx failed! Is it installed?\n"
exit 1
end
# extract link list (legend)
out = `sed -n '/^References$/,$p' #{tmp} | sed -n '3,$p'`.split(/$/)
if $? != 0
STDERR << "calling sed failed! Is it installed?\n"
exit 1
end
out.each do |line|
ary = line.split
$reference[ary[0].to_i] = ary[1]
end
# extract data
$lines = `sed -n '1,/^References$/p' #{tmp}`.split(/$/)
File.delete(tmp)
# we need a stack
$lines.reverse!
# traverse all lines
loop do
line = $lines.pop
break if not line
# title
if line =~ /^ (\S.*)$/
$cat[1] = $1
next
end
# li level 1
if line =~ / \* (\S.*)$/
line = $1
push_li(line, 1, /^ (\S.*)$/)
next
end
# li level 2
if line =~ / \+ (\S.*)$/
line = $1
push_li(line, 2, /^(\S.*)$/)
next
end
# li level 3
if line =~ /^ o (\S.*)$/
line = $1
push_li(line, 3, /^ (\S.*)$/)
next
end
# li level 4
if line =~ /^# (\S.*)$/
line = $1
push_li(line, 4, /^ (\S.*)$/)
next
end
# there is no higer level, right?
end
$data.sort! do |a, b|
Re: [linux-audio-dev] Some more Muzak
On Mon, Apr 19, 2004 at 06:43:46PM +, [EMAIL PROTECTED] wrote: > All chopping and munging was done in cheesetracker, even the crunchy > bass was made from the smooth one by over amplifying and then > filtering out the nasties. Lots of ladspa effects helped, too, > although the ones I most want to use (compressors, etc) are too slow > to be used "inline" like that. > > Are there any VERY fast LADSPA compressors about? "Barrys Satan Maximiser", but its so fast it counts as distortion :) SC4 set to peak detection mode should be able to go as fast as is sensible, if not, give me an example audio file and I'l change it. - Steve
[linux-audio-dev] Some more Muzak
Jon, Andy, LAD people, http://www.dis-dot-dat.net/dasub.mp3 Playing about with a classic sampled beat - something I normally try to avoid. Still, I think I broke it enough that it doesn't sound repetetive. In case your interested, there is only one beat sample, I use cheesetracker's offset copmmand (Oxy) to pick out the bits I want and munge the beat, kind of like recycle, but all done by hand. You can probably guess, but the vocals are taken from Thundercats. The voice of Mumm-Ra and a snipet explaining the eye of Thundera (the one that now goes: THE EYE, The Eye, the eye...). All chopping and munging was done in cheesetracker, even the crunchy bass was made from the smooth one by over amplifying and then filtering out the nasties. Lots of ladspa effects helped, too, although the ones I most want to use (compressors, etc) are too slow to be used "inline" like that. Are there any VERY fast LADSPA compressors about? James
Re: [linux-audio-dev] Anyone planned a GTK2-based Multitracker?
Hi again, revisiting an old thread. <...> > > It would be nice as you could see your entire piece from the main window, > > and see where things evolve, how control changes relate to each other, > > etc. > > > > The one (significantly more simple) feature I'd like to see in the MusE > > control editor is a line-drawing option like seq24. Just load up seq24, > > plug in a few notes and play with the control editor, you'll see what I > > mean. > > > > It would be nice to hilight all my kick drums, then draw a nice line to > > set all their velocities, for example. I found out that this infact is already possible in MusE, I'm not sure if it works as seq24 (have not come around to try it), but the feature is there. Highlight the kickdrum, draw a line, done. /Robert
Re: [linux-audio-dev] Can software authors make allowances for packagers?
On Mon, 2004-04-19 at 09:23, Erik de Castro Lopo wrote: > On Mon, 19 Apr 2004 09:50:55 +1000 > Conrad Parker <[EMAIL PROTECTED]> wrote: > > packages using automake should only set AM_CFLAGS, AM_INCLUDES, AM_LDFLAGS > > etc. in Makefile.am. Resetting CFLAGS, INCLUDES, LDFLAGS etc. is a bug > > (which I've also been guiltly of many times :) > > I often do: > > CFLAGS="$CFLAGS -Wall-sorts-of-warnings" > > Is that OK? Note that it only appends stuff the CFLAGS, it does not modify > stuff that is already there. > It potentially _does_ modify stuff that is already there. If someone puts a '-w' (inhibit all warning messages) in CFLAGS your '-Wall' will result in the opposite. The last occurrence of an option on the command line counts so CFLAGS="-Wall-sourts-of-warnings $CFLAGS" would be better but it still does not meet automake's rules of not touching user variables. Stuff like warnings are not really evil but imagine you'd append a '-O3' this way. It would no longer be possible to make sure that the compiler does not apply any optimization by calling 'make CFLAGS=-O0'. So if you asked me I'd say yes, it's still a bug. :) Jan
Re: [linux-audio-dev] Can software authors make allowances for packagers?
On Mon, 19 Apr 2004 09:50:55 +1000 Conrad Parker <[EMAIL PROTECTED]> wrote: > On Sun, Apr 18, 2004 at 08:11:08PM +1000, Luke Yelavich wrote: > > > > > >If a package's configure script doesn't recognize CFLAGS, it is a bug. > > >Report it as such. > > > > The configure scripts do recognise CFLAGS, however the custom CFLAGS either > > replace CFLAGS necessary for the package, or the package uses the same > > flags with different parameters, eg -march and -mcpu flags. > > packages using automake should only set AM_CFLAGS, AM_INCLUDES, AM_LDFLAGS > etc. in Makefile.am. Resetting CFLAGS, INCLUDES, LDFLAGS etc. is a bug > (which I've also been guiltly of many times :) I often do: CFLAGS="$CFLAGS -Wall-sorts-of-warnings" Is that OK? Note that it only appends stuff the CFLAGS, it does not modify stuff that is already there. Erik
