James Stone:
> >
> > You probably want "vsti" from Kjetil Matheussen (using vstserver) or
> > "jack_fst" from Paul Davis and Torben Hohn (using libfst). Either of
> > these will run a VSTi with GUI as a standalone JACK/ALSA app that can
> > then be driven as an ALSA sequencer client from a MIDI source.
> >
> > You can get vsti at http://www.notam02.no/arkiv/src/, or jack_fst at
> > http://linuxaudiosystems.com/fst/ . I have never tried vsti, but I
> > have used both vstserver-for-plugins and jack_fst with good results.
> >
> >
> > Chris
>
> I use vsti for auditioning vsts but I find that the k_vst~ plugin for pd
> offers more functionality, and also is accessible from seq24 (which is
> not the case with vsti).
The vsti program implements a standard alsa sequencer (just as the
jack_fst program, which infact use the code from vsti (which again use
the code from jack-rack :))), so it is definitely possible to get access
from seq24. Just use aconnect, kaconnect, qjackctl or something to
connect the vsti instrument and seq24. Infact, it should be much simpler
than from pd. I think one of us must have misunderstood something here.
--
Hi,
I'm doing some more mastering. A couple of the songs
have spikes, short duration but high signal level.
Compression fails to hold these signals in place. I
could tweak the compressor but when results aren't
achieved quickly I look for another tool.
Can SWH or anyone else explain what the Declipper
does? In a moment of genius I began to suspect that it
declips. Dah! I guess a definition of clip and an
example for where this plugin is useful would be
helpful.
I've post fader and in front of the compressor
inserted the declipper. In my test track, it doesn't
appear to be doing anything. It's likely the spikes
are not clips. However, the level of the spikes is
probably +6.0dbfs hotter than the average level.
If these spikes aren't clips, maybe I can normalize
and close the level gap between the spikes and the
average signal. I'll try that but suspect it won't do
the job.
Is there a different tool that can be used to control
these spikes? Perhaps a despiker. :)
ron
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
interesting. i bet it is probably a untune IDE driver. i shall try the data=writeback mode out this weekend if i figure out how. :)
--
Marko Dimiskovski
>
> > As an aside, Ardour does have "native raid" which
> > doesn't have the computational overhead of kernel
> > supported raid.
>
> I can't imagine that he's suffering from THROUGHPUT issues. RAID doesn't
> improve latency, for this sort of application. RAID's good for when you
> need higher throughput, and even 8 channels of 16-bit/44.1K audio is very
> low in throughput for modern drives.
>
> > Perhaps it would be useful for systems
> > that have drive related performance issues.
>
> With a 400ms latency, I highly doubt this is his problem especially since
> using the 2.6 kernel makes that alot better. It's either an untuned IDE
> driver (2.6 may have a better chipset tuning setup automatically), or a
> filesystem-related problem. (Try data=writeback mode if using ext3).
>
> A 2.4.2x-preemptible kernel with low-latency engaged and a tuned IDE driver
> with ext3 in writeback mode, or reiserfs should definitely get you JOY with
> audio latency.
>
> Make sure you compile in support for IDE chipsets (VIA, SiS, Intel, etc), so
> Linux can best tune/adjust transfer modes and DMA timings for optimal
> results. Many stock distribution kernels just include generic support.
>
> =MB=
> --
> A focus on Quality.
>
Hi,
I'm having problems with jack_fst. On trying to load any VSTi, I get a
segfault with the following backtrace:
#0 0x406132cb in __errno_location () from /lib/libpthread.so.0
#1 0x40735be3 in ioctl () from /lib/libc.so.6
#2 0x40b30275 in DOSFS_OpenDir (unix_path=0x40d1f024 "/")
at ../../files/dos_fs.c:584
#3 0x40b30a6f in DOSFS_FindUnixName (path=0x40d1f024, name=0x409e0926,
long_buf=0x40d1f025 "", long_len=1023, short_buf=0x40d1f42a)
at ../../files/dos_fs.c:769
#4 0x40b315e9 in DOSFS_GetFullName (name=0x409e0926, check_last=1,
full=0x40d1f024) at ../../files/dos_fs.c:1071
#5 0x40b35fe3 in CreateFileW (filename=0x409e0920, access=0, sharing=3,
sa=0x0, creation=3, attributes=0, template=0x0) at
../../files/file.c:401
#6 0x409a3958 in RtlDoesFileExists_U (file_name=0x409e0920) at path.c:75
#7 0x409a40f2 in RtlDosSearchPath_U (paths=0x409e0668, search=0x40d1fdfc,
ext=0x0, buffer_size=64, buffer=0x40d1fd60, file_part=0x40d1fcf8)
at path.c:302
#8 0x4099f1bb in find_dll_file (load_path=0x409e0668, libname=0x40d1fdfc,
filename=0x40d1fd60, size=0x40d1fd58, pwm=0x40d1fdf8, handle=0x40d1fd5c)
at loader.c:1320
#9 0x4099f269 in load_dll (load_path=0x409e0668, libname=0x40d1fdfc, flags=0,
pwm=0x40d1fdf8) at loader.c:1404
#10 0x4099d024 in import_dll (module=0x40430000, descr=0x404371a0,
load_path=0x409e0668) at loader.c:352
#11 0x4099d507 in fixup_imports (wm=0x409e0870, load_path=0x409e0668)
at loader.c:479
#12 0x409a006d in LdrInitializeThunk (main_file=0x0, unknown2=0, unknown3=0,
unknown4=0) at loader.c:1867
#13 0x40b6fe1d in start_process (arg=0x0) at process.c:751
Can anyone suggest anything? I've tried it with wine versions 20040309
and 20040505.
Thanks
Carl
I actually get very very well latency in the 2.6.3-rc3 kernel... its the only 2.6 kernel i have used so far... and on the 2.4.23 kernel that is patched with low-latency has xrun saying 400+- ms which is crazy... and ll is turned on for sure... for 2.6 the highest i get is around 20 ms. but i am also running fluxbox which uses very little cpu.. my machine is a intel celron 533MHz with 256mb RAM with gentoo installed :)
--
Marko Dimiskovski
> Hi,
>
> torsdagen den 27 maj 2004 19.16 skrev cv223(a)comcast.net:
> > So, based on Fernando's and Malcolm's advice, I decided to quit fussing
> > with the 2.6 kernels and stick with the 2.4.23 that I have working to do
> > some recording last night. The band came over - we were set and ready to
> > go. I hit 'record' to get an idea of the drum mix (we're submixing to
> > stereo) - 3 seconds in, Ardour stops with an 80ms xrun! Arrgh! I sweated
> > through the rest of the evening, fearing another occurence at 3:30 into a
> > 4:00 song. Fortunately, everything went ok.
> >
> > I guess I'm back to trying to figure out what's causing these long xruns,
> > now under the 2.4.23 kernel.
> >
> > Do most people shut off non-essential daemons during recording sessions, or
> > do any other tricks? This is kinda frustrating, as the CPU load seems
> > rather low (< 15% when the xrun happened). I guess I'll test out reiserfs
> > and even ext2 to see if the filesystem is the culprit.
>
> I actually run fullblown KDE most of the time, it works pretty well at 512x2,
> I can run 256x2 but xruns get more frequent, but not unbearably so. I'm
> mainly running MusE and I seldom get kicked out, but it does happen...
>
> There has been talk on the Jack list from time to time about adding a mode
> where you won't get kicked out so easily even if Jack misses a beat.
> For developing jack I think the current approach is good, the audio equivalent
> of an assert, but for real usage it is a little hard on the user. Especially
> if you are doing a performance, then it's devastating.
>
> To return to the subject, I hear others use lightweight window managers and do
> stop all unnesesary services to get better stability, if you have problems it
> will probably help.
>
> /Robert
>
> >
> > Thanks for reading the ramble,
> >
> > Joel
> >
> > > > I guess my main motivation for trying out the 2.6 kernel is laziness.
> > > > Just build the kernel and get the performance and ALSA without patches
> > > > or compiling extra stuff. At least, that was _supposed_ to be the way
> > > > it worked! I'll keep trying the new kernels, but keep the old faithful
> > > > 2.4 kernel around for recording.
> > > >
> > > > I'm _still_ curious about what causes the long xruns, though.
> > >
> > > New versions of alsa can be compiled with the "--debug=full" option (I
> > > don't think the current code in the kernel has that). That will enable
> > > you to tweak a proc variable to dump the kernel stack on each xrun, it
> > > is something like /proc/asound/card0/pcm0p/xrun_debug (for playback,
> > > same for recording in pcm0c). "echo "2">/proc/.../xrun_debug" will turn
> > > reporting on. You will get the stack traces in /var/log/messages.
> > >
> > > Not that you will immediately know exactly what has to be done to get it
> > > fixed, of course :-)
> > >
> > > IMHO stick with 2.4.x, in my tests 2.6.x is not even close to being
> > > ready for pro audio work. It will get better but it will take some time.
> > >
> > > -- Fernando
>
> --
> http://spamatica.se/music/
Hi,
I wonder if this is just my setup. So far I cannot get QJC to show
my MIDI output from Groove Agent. Is this not supported? (That would be
sad...)
Are others able to get any MIDI output?
MIDI input seems to be working fine.
Also no audio from this one yet. The VSTi seems to run perfectly,
but I don't get any sound yet.
Thanks,
Mark
Hi,
I have a VXpocket v2 running under a 2.6.5-gentoo-r1 kernel which is
patched with rt caps.
I find that with jackstart, I can get away with 2 periods of 512 samples
if the communication is 1-way, but in duplex mode I need 2 periods of
4096 samples to avoid xruns. Surprisingly, my on-board soundcard has
better performance!
Is this much different under a low-latency 2.4 kernel?
Would it be better if the card were hw:0 instead of hw:2?
Also, is it normal for the card to distort if the PCM level is above 82?
I wasn't having this distortion problem with W2K if IIRC.
Cheers,
Chris
Hello,
Can someone tell me how Linux selects which swap to use. I know there is
a swap priority, but my problem is a bit more complex.
I have to hard drives, both containing swap partitions. The first hard
drive also contains the OS and ardour sessions. The second hard drive is
'extra space'. I would like to use both drives for recording (not at the
same time), but I'm concerned about how Linux selects which swap drive
to use.
Ideally, when recording to drive 1 the OS would use the swap partition
on drive 2 and vice versa.
I don't know enough about Linux internals, so if someone does, please
could you inform me?
Sampo
Mark Knecht:
> Dave,
> Thanks for the encouragement. Just back from lunch and trying out
> Chris's suggestions about vsti as it looked simple, but so far no luck.
> That's for another thread later today if I cannot get it working myself.
>
> One question about all of this. It appears that if I run vstserver
> it attempts to start EVERY VST (or even every file!) in my vst
> directory?! Is this correct?
Yes, but only once. It caches the information about the plugins parameters
and such. Just let it run. If it seems to hang, Ctrl-C it, and start
vstserver once more.
>
> My version of Snd does appear to have the LADSPA 1.1 stuff built in
> so possibly your example will work for me when I find a VSTi I can trust...
>
Thats not much point. You can't send midisignals to vst-plugins from SND.
James Stone:
> >
> > How does that work? The "accessibility from seq24" bit, I mean.
> > Preferably in terms that make sense to someone who's only passingly
> > familiar with either seq24 or pd.
>
> seq24 will not start if vsti is running!
>
What? I don't have my linux-machine here so I can't test that. But it
sounds very strange that you can't start seq24 if a vsti is running.
What happens? Is there any messages to the console?
Can you start seq24 if jack-rack is running? (the midi code in vsti is
stolen from jack-rack)
I'm sure either/both Rob C. Buse (author of seq24) and/or myself are
interested in some bug-reports here.
--
Hi all,
This is yet another release of what started out as an experiment and has
become a pet project of mine -- desktop sounds for Linux.
Changelog:
*New sounds for Kmail, Kopete, Kdevelop, Ksysguard, exit session & minimize
window.
*Finalized 3 versions of the startup sound.
*New automated install script included
*Changed soundfile names to better reflect their function.
*Rearranged sounds for some events
*Remastered sounds for better balance
*Removed addon packages.
*PLEASE NOTE that Kopete sounds (and some others) are still
work-in-progress...
For those interested, you can find the package at its usual place:
http://www.kde-look.org/content/show.php?content=12584
Best wishes,
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/