19 Apr
2007
19 Apr
'07
4:15 a.m.
Announcing the 20070418 release of WhySynth, a DSSI softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysynth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
19 Apr
19 Apr
7:36 a.m.
Sean Bolton wrote:
Announcing the 20070418 release of WhySynth, a DSSI
softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysynth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Great.
I really like this synth. Especially to lay out ideas quickly in
Rosegarden. The only thing I miss is the possibility to control
parameters in realtime.
Is there a way to do this? Maybe via OSC messages from an external app?
Anyway, keep up with the good work.
c.
--
http://www.cesaremarilungo.com
8:03 a.m.
On 4/19/07, Cesare Marilungo <cesare(a)poeticstudios.com> wrote:
Rosegarden. The only thing I miss is the possibility
to control
parameters in realtime.
Is there a way to do this? Maybe via OSC messages from an external app?
MIDI CC will be MUCH better :)
Sean, thanks for the synth!
It is the best softsynth for Linux I know.
Dmitry.
8:22 a.m.
On Thu, 2007-04-19 at 11:34 +0000, Cesare Marilungo wrote:
Sean Bolton wrote:
It's a DSSI plugin, so whether the parameters can be controlled in
realtime or not depends entirely on the host - it has full control over
the parameter values. If it's a host that supports DSSI GUIs you can
also control them over OSC - see the documentation for the protocol on
http://dssi.sf.net .
--ll
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysynth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Great.
I really like this synth. Especially to lay out ideas quickly in
Rosegarden. The only thing I miss is the possibility to control
parameters in realtime.
Is there a way to do this? Maybe via OSC messages from an external app?
8:33 a.m.
Lars Luthman wrote:
On Thu, 2007-04-19 at 11:34 +0000, Cesare Marilungo
wrote:
I knew that. But I haven't figured out how to know the messages
associated with each synth and its parameters.
Is there a utility to do that?
c.
Sean Bolton wrote:
It's a DSSI plugin, so whether the parameters can be controlled in
realtime or not depends entirely on the host - it has full control over
the parameter values. If it's a host that supports DSSI GUIs you can
also control them over OSC - see the documentation for the protocol on
http://dssi.sf.net .
--ll
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysynth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Great.
I really like this synth. Especially to lay out ideas quickly in
Rosegarden. The only thing I miss is the possibility to control
parameters in realtime.
Is there a way to do this? Maybe via OSC messages from an external app?
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
--
http://www.cesaremarilungo.com
20 Apr
20 Apr
5:31 p.m.
On Thu, Apr 19, 2007 at 12:30:58PM +0000, Cesare Marilungo wrote:
I wrote a very unimpressive puredata patch to control the nekobee
dssi synth.. It uses the dssi~ puredata external:
http://www.puredata.org/Members/jb/
You could take a look at that to see how I have assigned
different midi controllers to different dssi parameters, so I can
twiddle the knobs on my keyboard and change the resonance for
example..
The problem with doing the same for whysynth is it has _so many_
parameters!
The dssi~ pd external is nice. You can send it an info message
and it prints out all the control numbers of the parameters..
very useful!
I am happy to distribute my pd file if anyone wants it, but I
don't have ready access to any ftp server at present..
James
It's a DSSI plugin, so whether the parameters can be controlled in
realtime or not depends entirely on the host - it has full control over
the parameter values. If it's a host that supports DSSI GUIs you can
also control them over OSC - see the documentation for the protocol on
http://dssi.sf.net .
--ll
I knew that. But I haven't figured out how to know the messages
associated with each synth and its parameters.
Is there a utility to do that?
5:51 p.m.
James Stone wrote:
On Thu, Apr 19, 2007 at 12:30:58PM +0000, Cesare
Marilungo wrote:
I wrote a very unimpressive puredata patch to control the nekobee
dssi synth.. It uses the dssi~ puredata external:
http://www.puredata.org/Members/jb/
You could take a look at that to see how I have assigned
different midi controllers to different dssi parameters, so I can
twiddle the knobs on my keyboard and change the resonance for
example..
The problem with doing the same for whysynth is it has _so many_
parameters!
The dssi~ pd external is nice. You can send it an info message
and it prints out all the control numbers of the parameters..
very useful!
I am happy to distribute my pd file if anyone wants it, but I
don't have ready access to any ftp server at present..
James
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Yes. I have already experimented a bit with the dssi~ external, but I
haven't thought about it.
Now, I've just tried to load whysynth with it and, yes, I can see all
the paratemers:
print: port in control 1 Osc1 Mode 0 10 0
print: port in control 2 Osc1 Waveform 0 167 0
print: port in control 3 Osc1 Pitch -36 36 0
print: port in control 4 Osc1 Detune -0.5 0.5 0
print: port in control 5 Osc1 Pitch Mod Src 0 22 0
print: port in control 6 Osc1 Pitch Mod Amt -1 1 0
print: port in control 7 Osc1 MParam 1 0 1 0
print: port in control 8 Osc1 MParam 2 0 1 0
print: port in control 9 Osc1 MMod Src 0 30 0
print: port in control 10 Osc1 MMod Amt 0 1 0
print: port in control 11 Osc1 Amp Mod Src 0 22 0
print: port in control 12 Osc1 Amp Mod Amt -1 1 0
print: port in control 13 Osc1->BusA Level 0 2 1
print: port in control 14 Osc1->BusB Level 0 2 1
print: port in control 15 Osc2 Mode 0 10 0
print: port in control 16 Osc2 Waveform 0 167 0
print: port in control 17 Osc2 Pitch -36 36 0
print: port in control 18 Osc2 Detune -0.5 0.5 0
print: port in control 19 Osc2 Pitch Mod Src 0 22 0
print: port in control 20 Osc2 Pitch Mod Amt -1 1 0
print: port in control 21 Osc2 MParam 1 0 1 0
print: port in control 22 Osc2 MParam 2 0 1 0
print: port in control 23 Osc2 MMod Src 0 30 0
print: port in control 24 Osc2 MMod Amt 0 1 0
print: port in control 25 Osc2 Amp Mod Src 0 22 0
print: port in control 26 Osc2 Amp Mod Amt -1 1 0
print: port in control 27 Osc2->BusA Level 0 2 1
print: port in control 28 Osc2->BusB Level 0 2 1
print: port in control 29 Osc3 Mode 0 10 0
print: port in control 30 Osc3 Waveform 0 167 0
print: port in control 31 Osc3 Pitch -36 36 0
print: port in control 32 Osc3 Detune -0.5 0.5 0
print: port in control 33 Osc3 Pitch Mod Src 0 22 0
print: port in control 34 Osc3 Pitch Mod Amt -1 1 0
print: port in control 35 Osc3 MParam 1 0 1 0
print: port in control 36 Osc3 MParam 2 0 1 0
print: port in control 37 Osc3 MMod Src 0 30 0
print: port in control 38 Osc3 MMod Amt 0 1 0
print: port in control 39 Osc3 Amp Mod Src 0 22 0
print: port in control 40 Osc3 Amp Mod Amt -1 1 0
print: port in control 41 Osc3->BusA Level 0 2 1
print: port in control 42 Osc3->BusB Level 0 2 1
print: port in control 43 Osc4 Mode 0 10 0
print: port in control 44 Osc4 Waveform 0 167 0
print: port in control 45 Osc4 Pitch -36 36 0
print: port in control 46 Osc4 Detune -0.5 0.5 0
print: port in control 47 Osc4 Pitch Mod Src 0 22 0
print: port in control 48 Osc4 Pitch Mod Amt -1 1 0
print: port in control 49 Osc4 MParam 1 0 1 0
print: port in control 50 Osc4 MParam 2 0 1 0
print: port in control 51 Osc4 MMod Src 0 30 0
print: port in control 52 Osc4 MMod Amt 0 1 0
print: port in control 53 Osc4 Amp Mod Src 0 22 0
print: port in control 54 Osc4 Amp Mod Amt -1 1 0
print: port in control 55 Osc4->BusA Level 0 2 1
print: port in control 56 Osc4->BusB Level 0 2 1
print: port in control 57 Filter1 Mode 0 6 0
print: port in control 58 Filter1 Source 0 1 0
print: port in control 59 Filter1 Frequency 0 50 50
print: port in control 60 Filter1 Frq Mod Src 0 22 0
print: port in control 61 Filter1 Frq Mod Amt -1 1 0
print: port in control 62 Filter1 Resonance 0 1 0.25
print: port in control 63 Filter1 MParameter 0 1 0.5
print: port in control 64 Filter2 Mode 0 6 0
print: port in control 65 Filter2 Source 0 2 0
print: port in control 66 Filter2 Frequency 0 50 50
print: port in control 67 Filter2 Frq Mod Src 0 22 0
print: port in control 68 Filter2 Frq Mod Amt -1 1 0
print: port in control 69 Filter2 Resonance 0 1 0.25
print: port in control 70 Filter2 MParameter 0 1 0.5
print: port in control 71 BusA->Out Level 0 2 0
print: port in control 72 BusA->Out Pan 0 1 0.5
print: port in control 73 BusB->Out Level 0 2 0
print: port in control 74 BusB->Out Pan 0 1 0.5
print: port in control 75 Filter1->Out Level 0 2 1
print: port in control 76 Filter1->Out Pan 0 1 0.25
print: port in control 77 Filter2->Out Level 0 2 1
print: port in control 78 Filter2->Out Pan 0 1 0.75
print: port in control 79 Volume 0 1 0.25
print: port in control 80 Effect Mode 0 2 0
print: port in control 81 Effect Param 1 0 1 0
print: port in control 82 Effect Param 2 0 1 0
print: port in control 83 Effect Param 3 0 1 0
print: port in control 84 Effect Param 4 0 1 0
print: port in control 85 Effect Param 5 0 1 0
print: port in control 86 Effect Param 6 0 1 0
print: port in control 87 Effect Wet/Dry Mix 0 1 0.5
print: port in control 88 Glide Rate 0.002 1 0.002
print: port in control 89 Bend Range 0 12 0
print: port in control 90 GLFO Frequency 0.05 20 10.025
print: port in control 91 GLFO Waveform 0 167 0
print: port in control 92 GLFO Amp Mod Src 0 2 0
print: port in control 93 GLFO Amp Mod Amt -1 1 0
print: port in control 94 VLFO Frequency 0.05 20 10.025
print: port in control 95 VLFO Waveform 0 167 0
print: port in control 96 VLFO Delay 0 10 0
print: port in control 97 VLFO Amp Mod Src 0 22 0
print: port in control 98 VLFO Amp Mod Amt -1 1 0
print: port in control 99 MLFO Frequency 0.05 20 10.025
print: port in control 100 MLFO Waveform 0 167 0
print: port in control 101 MLFO Delay 0 10 0
print: port in control 102 MLFO Amp Mod Src 0 22 0
print: port in control 103 MLFO Amp Mod Amt -1 1 0
print: port in control 104 MLFO Phase Spread 0 180 90
print: port in control 105 MLFO Random Freq 0 1 0
print: port in control 106 EGO Mode 1 5 1
print: port in control 107 EGO Shape 1 0 11 0
print: port in control 108 EGO Time 1 0 20 0
print: port in control 109 EGO Level 1 0 1 1
print: port in control 110 EGO Shape 2 0 11 0
print: port in control 111 EGO Time 2 0 20 0
print: port in control 112 EGO Level 2 0 1 1
print: port in control 113 EGO Shape 3 0 11 0
print: port in control 114 EGO Time 3 0 50 0
print: port in control 115 EGO Level 3 0 1 1
print: port in control 116 EGO Shape 4 0 11 0
print: port in control 117 EGO Time 4 0 50 0
print: port in control 118 EGO Vel Level Sens 0 1 0
print: port in control 119 EGO Vel Time Scale -1 1 0
print: port in control 120 EGO Kbd Time Scale -1 1 0
print: port in control 121 EGO Amp Mod Src 0 22 0
print: port in control 122 EGO Amp Mod Amt -1 1 0
print: port in control 123 EG1 Mode 0 5 0
print: port in control 124 EG1 Shape 1 0 11 0
print: port in control 125 EG1 Time 1 0 20 0
print: port in control 126 EG1 Level 1 0 1 1
print: port in control 127 EG1 Shape 2 0 11 0
print: port in control 128 EG1 Time 2 0 20 0
print: port in control 129 EG1 Level 2 0 1 1
print: port in control 130 EG1 Shape 3 0 11 0
print: port in control 131 EG1 Time 3 0 50 0
print: port in control 132 EG1 Level 3 0 1 1
print: port in control 133 EG1 Shape 4 0 11 0
print: port in control 134 EG1 Time 4 0 50 0
print: port in control 135 EG1 Vel Level Sens 0 1 0
print: port in control 136 EG1 Vel Time Scale -1 1 0
print: port in control 137 EG1 Kbd Time Scale -1 1 0
print: port in control 138 EG1 Amp Mod Src 0 22 0
print: port in control 139 EG1 Amp Mod Amt -1 1 0
print: port in control 140 EG2 Mode 0 5 0
print: port in control 141 EG2 Shape 1 0 11 0
print: port in control 142 EG2 Time 1 0 20 0
print: port in control 143 EG2 Level 1 0 1 1
print: port in control 144 EG2 Shape 2 0 11 0
print: port in control 145 EG2 Time 2 0 20 0
print: port in control 146 EG2 Level 2 0 1 1
print: port in control 147 EG2 Shape 3 0 11 0
print: port in control 148 EG2 Time 3 0 50 0
print: port in control 149 EG2 Level 3 0 1 1
print: port in control 150 EG2 Shape 4 0 11 0
print: port in control 151 EG2 Time 4 0 50 0
print: port in control 152 EG2 Vel Level Sens 0 1 0
print: port in control 153 EG2 Vel Time Scale -1 1 0
print: port in control 154 EG2 Kbd Time Scale -1 1 0
print: port in control 155 EG2 Amp Mod Src 0 22 0
print: port in control 156 EG2 Amp Mod Amt -1 1 0
print: port in control 157 EG3 Mode 0 5 0
print: port in control 158 EG3 Shape 1 0 11 0
print: port in control 159 EG3 Time 1 0 20 0
print: port in control 160 EG3 Level 1 0 1 1
print: port in control 161 EG3 Shape 2 0 11 0
print: port in control 162 EG3 Time 2 0 20 0
print: port in control 163 EG3 Level 2 0 1 1
print: port in control 164 EG3 Shape 3 0 11 0
print: port in control 165 EG3 Time 3 0 50 0
print: port in control 166 EG3 Level 3 0 1 1
print: port in control 167 EG3 Shape 4 0 11 0
print: port in control 168 EG3 Time 4 0 50 0
print: port in control 169 EG3 Vel Level Sens 0 1 0
print: port in control 170 EG3 Vel Time Scale -1 1 0
print: port in control 171 EG3 Kbd Time Scale -1 1 0
print: port in control 172 EG3 Amp Mod Src 0 22 0
print: port in control 173 EG3 Amp Mod Amt -1 1 0
print: port in control 174 EG4 Mode 0 5 0
print: port in control 175 EG4 Shape 1 0 11 0
print: port in control 176 EG4 Time 1 0 20 0
print: port in control 177 EG4 Level 1 0 1 1
print: port in control 178 EG4 Shape 2 0 11 0
print: port in control 179 EG4 Time 2 0 20 0
print: port in control 180 EG4 Level 2 0 1 1
print: port in control 181 EG4 Shape 3 0 11 0
print: port in control 182 EG4 Time 3 0 50 0
print: port in control 183 EG4 Level 3 0 1 1
print: port in control 184 EG4 Shape 4 0 11 0
print: port in control 185 EG4 Time 4 0 50 0
print: port in control 186 EG4 Vel Level Sens 0 1 0
print: port in control 187 EG4 Vel Time Scale -1 1 0
print: port in control 188 EG4 Kbd Time Scale -1 1 0
print: port in control 189 EG4 Amp Mod Src 0 22 0
print: port in control 190 EG4 Amp Mod Amt -1 1 0
print: port in control 191 ModMix Bias -1.4 1.4 0
print: port in control 192 ModMix Mod1 Src 0 22 0
print: port in control 193 ModMix Mod1 Amt -1.4 1.4 0
print: port in control 194 ModMix Mod2 Src 0 22 0
print: port in control 195 ModMix Mod2 Amt -1.4 1.4 0
print: port in control 196 Tuning 415.3 466.2 440
Nice. ;-)
c.
--
http://www.cesaremarilungo.com
It's
a DSSI plugin, so whether the parameters can be controlled in
realtime or not depends entirely on the host - it has full control over
the parameter values. If it's a host that supports DSSI GUIs you can
also control them over OSC - see the documentation for the protocol on
http://dssi.sf.net .
--ll
I knew that. But I haven't figured out how to know the messages
associated with each synth and its parameters.
Is there a utility to do that?
22 Apr
22 Apr
6:17 a.m.
On Fri, 2007-04-20 at 20:30 +0100, James Stone wrote:
The dssi~ pd external is nice. You can send it an info
message
and it prints out all the control numbers of the parameters..
very useful!
I'm glad you find it useful! For those who don't want to go to the
trouble of installing PD, you can find out the same info using the
'analyseplugin' tool that comes with the Ladspa SDK, which should be
packaged for most distros. For DSSI plugins you need to do:
analyseplugin </path/to/dssi/plugin.so> because it doesn't search the
standard DSSI paths.
Jamie
8:02 a.m.
On Sun, 2007-04-22 at 09:17 +0100, Jamie Bullock wrote:
On Fri, 2007-04-20 at 20:30 +0100, James Stone wrote:
Note: This only works for DSSI plugins that also are LADSPA plugins.
That doesn't have to be the case for all DSSI plugins.
--ll
The dssi~ pd external is nice. You can send it an
info message
and it prints out all the control numbers of the parameters..
very useful!
I'm glad you find it useful! For those who don't want to go to the
trouble of installing PD, you can find out the same info using the
'analyseplugin' tool that comes with the Ladspa SDK, which should be
packaged for most distros. For DSSI plugins you need to do:
analyseplugin </path/to/dssi/plugin.so> because it doesn't search the
standard DSSI paths. 
4:30 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Apr 22, 2007 at 12:00:05PM +0200, Lars Luthman wrote:
On Sun, 2007-04-22 at 09:17 +0100, Jamie Bullock
wrote:
I've been googling around for "analyzeplugin", and haven't come up with
much.
Where might I find this tool? It sounds useful.
- -ken
On Fri, 2007-04-20 at 20:30 +0100, James Stone
wrote:
Note: This only works for DSSI plugins that also are LADSPA plugins.
That doesn't have to be the case for all DSSI plugins.
The dssi~ pd external is nice. You can send it an
info message
and it prints out all the control numbers of the parameters..
very useful!
I'm glad you find it useful! For those who don't want to go to the
trouble of installing PD, you can find out the same info using the
'analyseplugin' tool that comes with the Ladspa SDK, which should be
packaged for most distros. For DSSI plugins you need to do:
analyseplugin </path/to/dssi/plugin.so> because it doesn't search the
standard DSSI paths. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGK6mae8HF+6xeOIcRAqJdAKCQfA/uZdyAdDCCRUUteLyJhLug2ACg3PAv
PV/BORlWsWSx/zBvKhuqjr8=
=XSlH
-----END PGP SIGNATURE-----
4:51 p.m.
On Sunday 22 April 2007 19:29, Ken Restivo wrote:
I've been googling around for
"analyzeplugin", and haven't come up with
much.
Where might I find this tool? It sounds useful.
It's called "analyseplugin", with an "s". It's one of the
standard LADSPA
tools, so antiquated that I can no longer remember where it originally came
from. If you're on a Debian-based system, it's just in the ladspa-sdk
package.
It would be nice to see it support DSSI properly as well. Most DSSI plugins
don't expose a LADSPA descriptor function directly, so it won't work with
them, but it could very easily retrieve the LADSPA descriptor from a DSSI
descriptor (thus providing all the information any DSSI plugin has in common
with LADSPA, with only a couple of extra lines of code) or be extended to
print out DSSI descriptor information as well.
Chris
4:56 p.m.
On Sunday 22 April 2007 19:49, Chris Cannam wrote:
It would be nice to see [analyseplugin] support DSSI
properly as well.
Most DSSI plugins don't expose a LADSPA descriptor function directly,
so it won't work with them
Hm. Empirical evidence shows that in fact many DSSI plugins -- including at
least one of mine -- do work with analyseplugin. I guess that means they do
expose a LADSPA descriptor. Shows what I know.
(If I had a good memory, I could be unstoppable. Or at least less stoppable.)
Chris
23 Apr
23 Apr
6:21 a.m.
On Sun, 2007-04-22 at 19:49 +0100, Chris Cannam wrote:
It would be nice to see it support DSSI properly as
well. Most DSSI plugins
don't expose a LADSPA descriptor function directly, so it won't work with
them, but it could very easily retrieve the LADSPA descriptor from a DSSI
descriptor (thus providing all the information any DSSI plugin has in common
with LADSPA, with only a couple of extra lines of code) or be extended to
print out DSSI descriptor information as well.
Hmmm... interesting. [dssi~] handles both LADSPA and DSSI plugins by
converting the any LADSPA descriptor returned by the descriptor function
to type (DSSI_Descriptor *), so sending it an 'info' message will give
the correct behaviour regardless of the plugin type.
However, as you rightly point out, analyseplugin will only work on DSSI
plugins if they include a ladspa_descriptor function. The problem is,
wouldn't any 'fix' for this require that analyseplugin include the
dssi.h header for the cast to DSSI_Descriptor, so we can retrieve the
LADSPA_Plugin member? Or maybe there is some clever trick to avoid
this...
Jamie
19 Apr
19 Apr
1:09 p.m.
New subject: WhySynth DSSI softsynth 20070418 release
Sean Bolton escribe:
Announcing the 20070418 release of WhySynth, a DSSI
softsynth
plugin.
Isn't linux-audio-announce a more suitable mailing list for such
announcements!?
(Anyway I am subscribed to both...)
Cordially, Ismael
--
Ismael Valladolid Torres m. +34679156321
La media hostia j. ivalladt(a)gmail.com
http://lamediahostia.blogspot.com/
1:35 p.m.
New subject: WhySynth DSSI softsynth 20070418 release
On 4/19/07, Ismael Valladolid Torres <ivalladt(a)punkass.com> wrote:
Sean Bolton escribe:
AFAIK this list is for both announcements and discussion, announce is just
for
announcements.
I would miss out on a lot of stuff if people didn't announce here.
And to get this back on topic, congrats on a nice release. Whysynth is
probably
my favorite linux softsynth! :) Any chance of getting some Access Virus-like
sounds
out of it!!? :)
James
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
Isn't linux-audio-announce a more suitable mailing list for such
announcements!?
1:39 p.m.
New subject: Announce to which list(s)? [was Re: WhySynth DSSI softsynth 20070418 release]
On Apr 19, 2007, at 8:09 AM, Ismael Valladolid Torres wrote:
Sean Bolton escribe:
There was some discussion on this many months back,
but no consensus came out of it that I could discern, so
I just post to DSSI-devel, LAU, LAD, _and_ LAA. Which
means many people get duplicates, but at least I'm
not leaving people out. ;-)
-Sean
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
Isn't linux-audio-announce a more suitable mailing list for such
announcements!?
(Anyway I am subscribed to both...) 
1:56 p.m.
New subject: Announce to which list(s)? [was Re: WhySynth DSSI softsynth 20070418 release]
Sean Bolton wrote:
On Apr 19, 2007, at 8:09 AM, Ismael Valladolid Torres
wrote:
It makes sense to x-post announcements on the linuxaudio.org lists.
only a minority is subscribed to more than one of the lists!
Please remember to an [ANN] tag in the subject of announcements!
subscribers to the linuxaudio.org lists - march 15 2007:
LAU : 1315
LAD : 966
LAA : 560
LAA ^ LAU = 254
LAD ^ LAU = 447
LAD ^ LAA = 246
LAD ^ LAA ^ LAU = 198
2092 unique subscribers.
#robin
PS. the stats were done anonymously with md5-hashed email addresses.
Sean Bolton escribe:
There was some discussion on this many months back,
but no consensus came out of it that I could discern, so
I just post to DSSI-devel, LAU, LAD, _and_ LAA. Which
means many people get duplicates, but at least I'm
not leaving people out. ;-)
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
Isn't linux-audio-announce a more suitable mailing list for such
announcements!?
(Anyway I am subscribed to both...) 
11:45 p.m.
Sean, Thanks for the update.
Also, thanks for the post on LAU. Being a linux audio user for quite a long time I was
very happy to see an update of your fine synth.
Last night I downloaded the 20070418 release and compiled it on both fedora 5 and fedora
6. Fedora 5(32bit) compiled very cleanly(as it has in the past) and ran fine here.
Fedora 6(64bit) presented a few warnings during make, but no show stoppers and whysynth
runs just fine.
Again, thanks.
Tracey.
26 Apr
26 Apr
6:15 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Apr 18, 2007 at 11:17:00PM -0700, Sean Bolton wrote:
Announcing the 20070418 release of WhySynth, a DSSI
softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysyth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
Thanks for this great synth!
I built it for my new system, and the GTK libs were discovered by configure, and the gtk
WhySynth stuff was apparently built and stuffed into /usr/local/lib/dssi/whysynth, as
expected:
checking for GTK+ - version >= 2.0.0... yes (version 2.8.20)
GTK support: yes (version 2.0)
checking for ALSA... yes
checking for COMMON... yes
checking for PLUGIN... yes
checking for GUI... yes
But when I launch whysynth via jack_dssi_host, I get only a headless WhySynth instance, no
GUI.
Mind you, I like headless stuff with no GUI, but in this case, I'd really like to have
some way of adjusting parameters and patches, and the GUI that worked with the old version
was plenty useful.
It appears that the GUI is running, but it too is headless:
ken 3679 0.2 7.1 50460 36144 pts/0 SLl 00:57 0:02 jack-dssi-host
whysynth.so
ken 3684 0.0 2.1 62668 10680 pts/0 S 00:58 0:00
/usr/local/lib/dssi/whysynth/WhySynth_gtk
osc.udp://asus.home.restivo.org:13660/dssi/whysynth/WhySynth/chan00 whysynth.so WhySynth
channel 0
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGMF+Be8HF+6xeOIcRArmtAJ0esFSgIDJzyvFirJkGs8acnvK6WACg81cC
SJ5+Ms4Tn+DZ0EXsKjSYAEs=
=a0+V
-----END PGP SIGNATURE-----
6:36 a.m.
New subject: [ANN] WhySynth DSSI softsynth 20070418 release-- problem solved
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Apr 26, 2007 at 01:14:57AM -0700, Ken Restivo wrote:
On Wed, Apr 18, 2007 at 11:17:00PM -0700, Sean Bolton
wrote:
Nevermind-- the problem was that my system installation had stuck a hard IP address into
/etc/hosts. I yanked that entry, and all is well now.
OSC is weird.
- -ken
Announcing the 20070418 release of WhySynth, a
DSSI softsynth
plugin.
New since the last major release:
* Two new oscillator modes: phase distortion similar to that used
in the Casio CZ series synths, and another FM mode.
* GUI enhancements.
* Improvements to the envelope generators, making them more
responsive to realtime parameters changes.
* A few new patches.
* Some GCC 4 fixes.
Find WhySynth here:
http://home.jps.net/~musound/whysyth.html
More information on the DSSI plugin standard, available hosts
and plugins can be found here:
http://dssi.sourceforge.net/
WhySynth is written and copyright (c) 2007 by Sean Bolton,
under the GNU General Public License, version 2.
Thanks for this great synth!
I built it for my new system, and the GTK libs were discovered by configure, and the gtk
WhySynth stuff was apparently built and stuffed into /usr/local/lib/dssi/whysynth, as
expected:
checking for GTK+ - version >= 2.0.0... yes (version 2.8.20)
GTK support: yes (version 2.0)
checking for ALSA... yes
checking for COMMON... yes
checking for PLUGIN... yesl
checking for GUI... yes
But when I launch whysynth via jack_dssi_host, I get only a headless WhySynth instance,
no GUI.
Mind you, I like headless stuff with no GUI, but in this case, I'd really like to
have some way of adjusting parameters and patches, and the GUI that worked with the old
version was plenty useful.
It appears that the GUI is running, but it too is headless:
ken 3679 0.2 7.1 50460 36144 pts/0 SLl 00:57 0:02 jack-dssi-host
whysynth.so
ken 3684 0.0 2.1 62668 10680 pts/0 S 00:58 0:00
/usr/local/lib/dssi/whysynth/WhySynth_gtk
osc.udp://asus.home.restivo.org:13660/dssi/whysynth/WhySynth/chan00 whysynth.so WhySynth
channel 0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGMGR9e8HF+6xeOIcRAnAGAKCSYVGcH2t4D7wMfGfO9ZdTb3OrWACeKFxx
8zzrwGvae2DlKs1Vj8X2YV4=
=NG1A
-----END PGP SIGNATURE-----
6399
days inactive
6406
days old
linux-audio-user@lists.linuxaudio.org
19 comments
11 participants
participants (11)
-
Cesare Marilungo -
Chris Cannam -
Dmitry Baikov -
Ismael Valladolid Torres -
James Stone -
Jamie Bullock -
Ken Restivo -
Lars Luthman -
Robin Gareus -
Sean Bolton -
Tracey Hytry