Greetings:
In the process of providing Tim with an example I found that some
severe instability sporadically occurs with the following setup:
Pd 0.37 (final)
vstserver 0.2.7
k_vst~ (latest)
WINE 20030911 from WineHQ (i.e., not Kjetil's)
Sometimes the server will go into an endless loop of "wine client
error" messages. No problem, I can kill the process with no difficulty,
but it would be nicer if it didn't happen. ;) The spin usually takes
place when I'm setting up the Pd patch for more than one plugin, but
unfortunately it doesn't happen all the time. I'll try Kjetil's version
of WINE later today.
Btw, I agree that it would be good to have a list of VST plugins known
to work in the environment. Alas, I have no time to put into such a
thing, but I will gladly donate my own list and comments.
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://linux-sound.org
The M-Audio MobilePre/Sonica/Transit/Ozone devices need a firmware
download before they can be used with Linux.
I've released a first beta of the madfu-firmware package which tries
to accomplish this.
Please note that I do not have any of these devices, and that the
loader is not tested at all. That's why I'm searching for volunteers.
:-)
To download the beta, go to
http://sourceforge.net/project/showfiles.php?group_id=87777&release_id=1833…
Please send any success/failure reports to
usb-midi-fw-user(a)lists.sf.net
Regards,
Clemens
Subject: LilyPond 2.0 prerelease available
X-Mailer: VM 7.14 under Emacs 21.2.1
Reply-To: hanwen(a)cs.uu.nl
FCC: ~/persoonlijk/Mail/sent
I have just released Lilypond 1.9.8. Relative to 1.9.7, it has a
number of small bugfixes and sports dotted hairpin crescendos.
However, this release also marks the end of my 2.0 release TODO
list. In other words, 1.9.8 is the first (and hopefully only) LilyPond
2.0 release candidate.
Please download and test it as widely as possible, before it is
released some time next week.
Enjoy!
Han-Wen
New features in 2.0 since 1.8
*****************************
* Crescendos can now be drawn dotted or stippled.
* Quarter tones are now supported. They are entered by suffixing
`ih' for a half-sharp and `eh' for a half-flat. Hence, the
following is an ascending list of pitches:
ceses ceseh ces ceh c cih cis cisih cisis
* The following constructs have been removed from the syntax:
\duration #SCHEME-DURATION
\pitch #SCHEME-PITCH
\outputproperty FUNC SYMBOL = VALUE
For `\outputproperty', the following may be substituted:
\applyoutput #(outputproperty-compatibility FUNC
SYMBOL VALUE)
* Clefs may now be transposed arbitrarily, for example
\clef "G_8"
\clef "G_15"
\clef "G_9"
* The syntax for chords and simultaneous music have changed. Chords
are entered as
<PITCHES>
while simultaneous music is entered as
<<..MUSIC LIST..>>
In effect, the meanings of both have been swapped relative to
their 1.8 definition. The syntax for lists in `\markup' has
changed alongside, but figured bass mode was not changed, i.e.:
\markup { \center <..LIST OF MARKUPS..> }
\figure { <figures> }
As chords the more often used than simultaneous music, this change
will save keystrokes.
* Each music expression can now be tagged, to make different printed
versions from the same music expression. In the following example,
we see two versions of a piece of music, one for the full score,
and one with cue notes for the instrumental part:
< \tag #'part <
{ c4 f2 g } % in the part, we have cue-notes
\\ R1 >
\tag #'score R1 % in the score: only a rest
>
The same can be applied to articulations, texts, etc.: they are
made by prepending
-\tag #YOUR-TAGS
to an articulation, for example,
c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
This defines a note, which has a conditional fingering and a
string-number indication.
* The settings for chord-fingering are more flexible. You can
specify a list where fingerings may be placed, eg.
\property Voice.fingeringOrientations = #'(left down)
This will put the fingering for the lowest note below the chord,
and the rest to the left.
* The script previously known as `ly2dvi' has been renamed to
`lilypond'. The binary itself is now installed as `lilypond-bin'.
* Markup text (ie. general text formatting) may now be used for
lyrics too.
* Two new commands for grace notes have been added, `\acciaccatura'
and `\appoggiatura',
\appoggiatura f8 e4
\acciaccatura g8 f4
Both reflect the traditional meanings of acciaccatura and
appogiatura, and both insert insert a slur from the first grace
note to the main note.
* Layout options for grace notes are now stored in a context
property, and may now be set separately from musical content.
* The `\new' command will create a context with a unique name
automatically. Hence, for multi-staff scores, it is no longer
necessary to invent arbitrary context names. For example, a
two-staff score may be created by
\simultaneous {
\new Staff { NOTES FOR 1ST STAFF }
\new Staff { NOTES FOR 2ND STAFF }
}
* Octave checks make octave errors easier to correct. The syntax is
\octave PITCH
This checks that PITCH (without octave) yields PITCH (with octave)
in \relative mode. If not, a warning is printed, and the octave is
corrected.
* All articulations must now be entered postfix. For example,
c8[( d8])
is a pair of beamed slurred eighth notes.
* The definition of `\relative' has been simplified. Octaves are
now always propagated in the order that music is entered. In the
following example,
PRE
\repeat "unfold" 3 BODY \alternative { ALT1 ALT2 }
POST
the octave of BODY is based on PRE, the starting octave of ALT1 on
BODY, the starting octave of ALT2 on ALT1, and the starting octave
of POST on ALT2.
The same mechanism is used for all other music expressions, except
the chord. Backwards compatibility is retained through a special
program option, which is set through
#(ly:set-option 'old-relative)
--
Han-Wen Nienhuys | hanwen(a)cs.uu.nl | http://www.xs4all.nl/~hanwen
Sorry Folks if you are not German, but i am looking
for someone in Cologne who wants to exchange some
experiences:
Also Hallo !
Sollte da drau�en irgendejemand sein, der in K�ln lebt
und sich mit Linu-Audio besch�ftigt und sich
austauschen m�chte - Mir auch ein bi�chen helfen, beim
Installieren, Jmax, Ardour, PD etc.
Der melde sich doch mal bei mir. Ich geb n Essen aus,
wenns dann l�uft !!!
Gru� Luigi
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Hello -
I was wondering if someone could help me along with getting VST's running
under Linux.
I have installed the version of WINE from the vstserver download area. I
have also built vstserver and can in fact run it. Finally, I have built
ladspavst.
This is where I am stuck. The ladspavst README didn't have any info to help
figure out how to run it.
Building ladspavst made vst.so. What now?
What I would like to try is getting VST's running with Ardour. Is this
possible?
Also, do any VSTi's work with vstserver?
Thanks for any and all info...
-- N
From: Dave Phillips <dlphilp(a)bright.net>
>
> "Kjetil S. Matheussen" wrote:
>
> > > Perhaps Kjetil can provide a working example ?
> > >
> >
> > The help2-k_vst~.pd patch in the k_vst~ tar file works for me. (last time
> > I tried at least). Press the "click to hear" button.
>
> Thanks, Kjetil. I got the mda_JX10 synth and tested the patch, it worked
> fine (but no GUI, alas). I also tried the compakt and Barking Wombat
> synths again with that example, both worked fine and both showed their
> GUIs (after I added the opengui/closegui messages to the patch).
> However, I still haven't figured out how to sound the patch via my MIDI
> keyboard.
>
> The vstserver is still very shaky. It often crashes after changing the
> DLL name in the k_vst~ object. I can start the whole thing again with
> the revised patch and it will work fine (until I try changing the DLL
> again). Btw, I built and installed your version of WINE (from the NoTAM
> site) and rebuilt the vstserver.
>
It seems like the newer wine-versions doesnt work quite as well with
the vstserver as the nov-dec2002 versions. I have experienced more
strange behaviour after upgrading too. But it might be coincidental.
> I tried utilizing the MIDI input components from the audio/MIDI test
> patch but even though it shows MIDI data coming from my keyboard I'm
> still not sounding the VSTi plugin. Suggestions ?
>
Hmm, no. I'm unfortunately not sitting at a linux machine right now.
Cant think of anything. Ask the pd-list perhaps? There seems to
be quite many that use the k_vst~ external on that list.
--
> > Also, do any VSTi's work with vstserver?
>
Yes. There are very few differences between the
VSTi and the VST format.
> according to the pd k_vst~ readme, pd supports
> midi note on/off, controllers, pitchbend, aftertouch, and
> program change for vsti's!
>
Thats right.
> i cant personally verify that :-)
>
I can. :)
> From: Dave Phillips <dlphilp(a)bright.net>
> To: linux-audio-user(a)music.columbia.edu
> Subject: Re: [linux-audio-user] Running vstserver & ladspavst
> Reply-To: linux-audio-user(a)music.columbia.edu
>
> Tim Orford wrote:
>
> > > Also, do any VSTi's work with vstserver?
> >
> > according to the pd k_vst~ readme, pd supports
> > midi note on/off, controllers, pitchbend, aftertouch, and
> > program change for vsti's!
> >
> > i cant personally verify that :-)
>
> I tried running the Barking Wombat and the compakt synths with k_vst~.
> Both GUIs popped up without complaint, but neither worked. Furthermore,
> when I quit Pd (after closing the synths) the vstserver crashes (with
> each synth tested).
>
> Perhaps Kjetil can provide a working example ?
>
The help2-k_vst~.pd patch in the k_vst~ tar file works for me. (last time
I tried at least). Press the "click to hear" button.
--
What's your soundcard? I think being able to open a sound device multiple times is dependent on if the hardware supports that. I can run jack and xmms (without the jack plugin) concurrently on my sb512.
Taybin
-----Original Message-----
From: Dave Phillips <dlphilp(a)bright.net>
Sent: Sep 18, 2003 7:54 AM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] JACK splat
Robert Jonsson wrote:
> Thursday 18 September 2003 14:19 skrev Dave Phillips:
> > Greetings:
> >
> > I'm having an interesting problem with JACK (0.81.1). When running it
> > I can't start non-JACK apps, e.g., after starting JACK (with Rui's neat
> > qjackctl) I'm unable to open Snd until I stop JACK. Is this expected
> > behavior ? I hope not...
>
> Are you sure you could do it with other versions of Jack?
Now that I think about it, no, I'm not sure about that. I've usually
reserved JACK use for Ardour, so I might not have ever tried running a
non-JACK app with the server open.
> I don't know how Snd works, but it seems probable that it opens the
> sound-device on startup. And if it is occupied by a sound-server, any
> sound-server, the app may not start.
I'm pretty sure Snd operates in just that manner, and I understand what
you're telling me. I also tried opening it with jacklaunch but got no
joy. :(
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://linux-sound.org
Greetings:
Is anyone on this last using CheeseTracker 0.8.0 ? I like it, but I've
run into a number of problems. I've already mentioned some bugs to reduz
and I'll prepare a better report for him. But meanwhile I wondered if
anyone else here is even using it.
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://linux-sound.org
As far as I know, the paint feature is still in there. I don't know if it still works though. There are a lot of features, and we might not know if something is broken until someone tries it out.
Taybin
-----Original Message-----
From: Mark Knecht <mknecht(a)controlnet.com>
Sent: Sep 17, 2003 11:37 AM
To: linux-audio-user(a)music.columbia.edu
Subject: RE: [linux-audio-user] Loops
>
> Why is this difficult? Are you looking for something like fruity
> loops that
> makes it easy to assemble the loops themselves? What sort of
> functionality
> are you wanting?
>
Check the Ardour archives. We had this discussion back around last January.
Actually, someone did a patch for Ardour that painted loops much like Acid
does. You placed the loop where you wanted it to start and then did a drag
to the right. If you went farther than the length of the loop then Ardour
put in a second copy of the loop, just like Acid.
Ardour was actually sort of nicer than Acid in that you could put multiple
loops on the same track. Acid doesn't allow that.
I think that none of this eventually made it into CVS, but I could be wrong.
maybe the functionality is there somewhere. (I don't use Ardour.)
- Mark