15 Sep
2016
15 Sep
'16
12:25 a.m.
Hello,
The INSTALL file is straightforward. ccmake isn't. What it does is
that it shows a screen with options. Options seems OK, so what is the
next step to go on with the compilation ? ENTER does not do it as it
toggles a selected option. (On the side: why is configuring/making
like this - wasn't the plain ol' configure all right ?)
Cheers.
15 Sep
15 Sep
4:36 a.m.
jonetsu(a)teksavvy.com, Sep 15 2016:
Hello,
The INSTALL file is straightforward. ccmake isn't. What it does is
that it shows a screen with options. Options seems OK, so what is the
next step to go on with the compilation ?
Hey hey,
at the bottom of the screen ccmake should list all the available steps:
Press [c] to configure
etc.
So first you press the letter 'c'. When that is OK, you should also see an option
"generate", so press 'g'. After that ccmake should quit automatically.
Running cmake afterwars appears to be optional.
Good luck!
...
Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
6:37 a.m.
OOn Thu, 15 Sep 2016 06:36:30 +0200 (CEST), Ffanci Silvain wrote:
jonetsu(a)teksavvy.com, Sep 15 2016:
$ wget https://github.com/Yoshimi/yoshimi/archive/1.4.1.tar.gz
$ tar xf 1.4.1.tar.gz
$ cd yoshimi-1.4.1/src/
Isn't there a way to run only
$ cmake ./ -DCMAKE_INSTALL_some_option
?
I didn't "create a separate directory for build", since I only want to
see how to handle options.
However, how to proceed when running
$ ccmake ./
and after pushing "c" to change e.g. the "--prefix" directory?
This is how it's done by an Arch PKGBUILD:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=yoshimi
I would expect some hints provided by yoshimi's INSTALL file.
Regards,
Ralf
The INSTALL file is straightforward. ccmake
isn't. What it does is
that it shows a screen with options. Options seems OK, so what is
the next step to go on with the compilation ?
at the bottom of the screen ccmake should list all the available steps:
Press [c] to configure
etc.
So first you press the letter 'c'. When that is OK, you should also
see an option "generate", so press 'g'. After that ccmake should quit
automatically.
Running cmake afterwars appears to be optional.
6:56 a.m.
Ralf Mardorf, Sep 15 2016:
...
Isn't there a way to run only
$ cmake ./ -DCMAKE_INSTALL_some_option
?
Not having checked, but this should always be possible. When Csound changed to
cmake, they gave exactly those instructions somewhere.
...
However, how to proceed when running
$ ccmake ./
and after pushing "c" to change e.g. the "--prefix" directory?
Once you changed an option and pressed 'c' again to configure it, you will
see the option 'g' for generate at the bottom of the screen.
The rest was described in the INSTALL file:
cmake .
make
sudo make install
Assu8ming, of course, that you don't have missing packages or other errors.
ccmake also offers 'h' for help, which I've never really chcked out though.
...
Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
8:55 a.m.
On Thu, 15 Sep 2016 08:56:06 +0200 (CEST), Ffanci Silvain wrote:
Ok, this is very confusing. Running cmake first could replace pushing
"c".
However, in ccmake the next step seems to push "t" and then to use page
down to search the options. On page 2 there's
"CMAKE_INSTALL_PREFIX /usr/local". Then with "/" it's possible to
search
the variable name, instead of scrolling with the cursor keys. But then
editing it becomes a PITA. I didn't try to read the help and to do it.
Anyway, if running
cmake ./ -DCMAKE_INSTALL_PREFIX=/usr/
and after that
ccmake ./
and pushing "t" and "page down"
CMAKE_INSTALL_PREFIX changed to /usr.
On Thu, 15 Sep 2016 08:45:03 +0100, Will Godfrey wrote:
and after
pushing "c" to change e.g. the "--prefix" directory?
Once you
changed an option and pressed 'c' again to configure it Arguments for and against cmake are rather like the
vi-emacs wars.
Both are a PITA for users who just want to edit an option.
[rocketmouse@archlinux tmp]$ grep -i editor ~/.bashrc
export EDITOR="nano"
;)
Believing the Arch PKGBUIL just changing the prefix doesn't do the job.
-DCMAKE_INSTALL_DATAROOTDIR
-DCMAKE_INSTALL_LIBDIR
seems to be required, too, but the INSTALL file does not clarify how to
at least chose the prefix. IMO you should explain this.
What happens when I try to build from git?
[rocketmouse@archlinux tmp]$ git clone git://git.code.sf.net/p/yoshimi/code
Ok, something like ./autogen.sh seems not to be needed, cmake does the
job. This might be an advantage, but apart from this, from a user point
of view, cmake makes things more complicated.
Regards,
Ralf
7:45 a.m.
On Wed, 14 Sep 2016 20:25:57 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
Hello,
The INSTALL file is straightforward. ccmake isn't. What it does is
that it shows a screen with options. Options seems OK, so what is the
next step to go on with the compilation ? ENTER does not do it as it
toggles a selected option. (On the side: why is configuring/making
like this - wasn't the plain ol' configure all right ?)
Cheers.
Hopefully you've picked up on what the others have said now.
I've been intending to have a look at the Install file to bring it up to date.
Arguments for and against cmake are rather like the vi-emacs wars. A couple of
people have said they think "good ol' automake" was better, but I don't
see
them beating a path to the door to implement it. The whole build structure it
pretty complex, no matter what you use and I don't have time to get into this as
well as working on the very many improvements that are coming along.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
5:28 p.m.
On Thu, 15 Sep 2016 08:45:03 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
Hopefully you've picked up on what the others have
said now.
I've been intending to have a look at the Install file to bring it up
to date.
Thanks Will (and everybody else) - much appreciated.
Yoshimi has compiled and 'make install' was run. The last lines
shows:
-- Up-to-date: /usr/local/share/icons/yoshimi_alt.svg
-- Up-to-date: /usr/local/share/appdata/yoshimi.appdata.xml
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/manifest.ttl
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi.ttl
Checking it out (I'm not saying make install is a liar ! :) :
% ll /usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-rw-r--r-- 1 root root 2479429 sep 15 09:06
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
And so I added the following to Mixbus 32C (Ardour) plugins config:
/usr/local/lib/x86_64-linux-gnu/lv2/
And did a rescan of the plugins. The plugin manager could not
find Yoshimi. Restarted Mixbus, tried again, no. Then I added
the plugin path:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/
Rescanned, and did the same steps. No Yoshimi in sight.
That seems much straightfoward. All other plugins in various
locations (some in directoires from the user home directory) are
seen and can be used.
What gives ?
Cheers.
6:16 p.m.
On Thu, 15 Sep 2016 13:28:08 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
On Thu, 15 Sep 2016 08:45:03 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
Did you use ccmake . at the start?
If not, please do and Check the entry 'LV2_INSTALL_DIR'
I find it works perfectly if set to lib/lv2
I regularly test with ardour, Muse and Qtractor. Anywhere else and there seems
to be all sorts of issues.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hopefully you've picked up on what the others
have said now.
I've been intending to have a look at the Install file to bring it up
to date.
Thanks Will (and everybody else) - much appreciated.
Yoshimi has compiled and 'make install' was run. The last lines
shows:
-- Up-to-date: /usr/local/share/icons/yoshimi_alt.svg
-- Up-to-date: /usr/local/share/appdata/yoshimi.appdata.xml
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/manifest.ttl
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi.ttl
Checking it out (I'm not saying make install is a liar ! :) :
% ll /usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-rw-r--r-- 1 root root 2479429 sep 15 09:06
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
And so I added the following to Mixbus 32C (Ardour) plugins config:
/usr/local/lib/x86_64-linux-gnu/lv2/
And did a rescan of the plugins. The plugin manager could not
find Yoshimi. Restarted Mixbus, tried again, no. Then I added
the plugin path:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/
Rescanned, and did the same steps. No Yoshimi in sight.
That seems much straightfoward. All other plugins in various
locations (some in directoires from the user home directory) are
seen and can be used.
What gives ?
Cheers.
16 Sep
16 Sep
4:31 p.m.
On Thu, 15 Sep 2016 19:16:35 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
On Thu, 15 Sep 2016 13:28:08 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
I use non standard locations such as ~/vst/u-he/ and I simply add that
path to Ardour's or Bitwig's config. Although I can try changing the
default location when building Yoshimi, to lib/lv2.
Once changed and compiled, and with Ardour (Mixbus 32C) being told
about the path, followed by a rescan, Yoshimi is now on an Ardour
MIDI track, a keyboard is connected and assigned. When a note is played
the blue bar in Yoshimi moves, Ardour shows MIDI activity on that track
but, no signal gets to the VU of that track. There is audio, synth
sounds are heard from Yoshimi, but nothing register on the track's VU.
The fader works, though. First time I see this. Fader works but no VU
feedback. The master VU shows audio activity, but not the VU for
Yoshimi's track.
Of course, if I enable Zebra2 for the same keyboard, both the Zebra2
and the Yoshimi sounds are heard. But only Zebra2 shows up on its
track VU. The Yoshimi track VU still shows nothing. It's like
bypassing that VU completly and tapping elsewhere into Ardour.... but
the track fader works.
I wonder what other implications this very strange thing may have.
Cheers.
On Thu, 15 Sep 2016 08:45:03 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
Did you use ccmake . at the start?
If not, please do and Check the entry 'LV2_INSTALL_DIR'
I find it works perfectly if set to lib/lv2
I regularly test with ardour, Muse and Qtractor. Anywhere else and
there seems to be all sorts of issues. Hopefully you've picked up on what the others
have said now.
I've been intending to have a look at the Install file to bring
it up to date.
Thanks Will (and everybody else) - much appreciated.
Yoshimi has compiled and 'make install' was run. The last lines
shows:
-- Up-to-date: /usr/local/share/icons/yoshimi_alt.svg
-- Up-to-date: /usr/local/share/appdata/yoshimi.appdata.xml
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/manifest.ttl
-- Up-to-date:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi.ttl
Checking it out (I'm not saying make install is a liar ! :) :
% ll /usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
-rw-r--r-- 1 root root 2479429 sep 15 09:06
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/yoshimi_lv2.so
And so I added the following to Mixbus 32C (Ardour) plugins config:
/usr/local/lib/x86_64-linux-gnu/lv2/
And did a rescan of the plugins. The plugin manager could not
find Yoshimi. Restarted Mixbus, tried again, no. Then I added
the plugin path:
/usr/local/lib/x86_64-linux-gnu/lv2/yoshimi.lv2/
Rescanned, and did the same steps. No Yoshimi in sight.
That seems much straightfoward. All other plugins in various
locations (some in directoires from the user home directory) are
seen and can be used.
What gives ?
Cheers.
5:54 p.m.
On Fri, 16 Sep 2016 12:31:55 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
Once changed and compiled, and with Ardour (Mixbus
32C) being told
about the path, followed by a rescan, Yoshimi is now on an Ardour
MIDI track, a keyboard is connected and assigned. When a note is played
the blue bar in Yoshimi moves, Ardour shows MIDI activity on that track
but, no signal gets to the VU of that track. There is audio, synth
sounds are heard from Yoshimi, but nothing register on the track's VU.
The fader works, though. First time I see this. Fader works but no VU
feedback. The master VU shows audio activity, but not the VU for
Yoshimi's track.
Never seen that. You must have found some obscure way to disable metering on
that track.
Quick! Write a how-to on it :)
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
6:09 p.m.
On Fri, 16 Sep 2016 18:54:24 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
Never seen that. You must have found some obscure way
to disable
metering on that track.
Quick! Write a how-to on it :)
Unfortunately, can't. Not reproducible. Bummer. :)
This said, surprised by the yoshimi sounds. Must say it's now part of
the arsenal.
What is the difference between:
1) yoshimi and yoshimi-multi ?
2) yoshimi and zynsubaddfx ?
6:24 p.m.
On Fri, 16 Sep 2016 14:09:43 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
On Fri, 16 Sep 2016 18:54:24 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
multi exposes 16 individual track output pairs as well as the main L & R
Never seen that. You must have found some obscure
way to disable
metering on that track.
Quick! Write a how-to on it :)
Unfortunately, can't. Not reproducible. Bummer. :)
This said, surprised by the yoshimi sounds. Must say it's now part of
the arsenal.
What is the difference between:
1) yoshimi and yoshimi-multi ? 2) yoshimi and zynsubaddfx ?
Instrument wise - none.
Control wise - quite a lot.
Here in Yoshimi land we say try both and see what you prefer. I know of some
people who maintain both for different workflows.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
8:02 p.m.
On Fri, September 16, 2016 1:24 pm, Will Godfrey wrote:
Wasn't there a difference in real-time safe functions used by one or the
other? I thought I heard several months ago that one had been making sure
the audio callback routines used only real-time safe system calls, but one
had non-real time safe functions used, which was causing some problems for
someone trying to run a large number of synth instances (not all active,
some were just sitting idle).
--
Chris Caudle
What is the
difference between:
2) yoshimi and zynsubaddfx ?
Instrument wise - none.
Control wise - quite a lot. 
8:11 p.m.
It is my understanding that Yoshimi is Will's attempt to add value to
the original ZynAddSubFx. Why he doesn't contribute to the original
project, I have no idea, instead he splits the development effort
between his fork (Yoshimi), and the original project (ZynAddSubFx).
Zyn is still actively developed, although I see Yoshimi getting more
mentions on this list for some reason.
That is my understanding after talking to some of the Linux Audio
community. If I am wrong, I am open to corrections.
On Fri, Sep 16, 2016 at 4:01 PM, Chris Caudle <chris(a)chriscaudle.org> wrote:
On Fri, September 16, 2016 1:24 pm, Will Godfrey
wrote:
Wasn't there a difference in real-time safe functions used by one or the
other? I thought I heard several months ago that one had been making sure
the audio callback routines used only real-time safe system calls, but one
had non-real time safe functions used, which was causing some problems for
someone trying to run a large number of synth instances (not all active,
some were just sitting idle).
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
What is
the difference between:
2) yoshimi and zynsubaddfx ?
Instrument wise - none.
Control wise - quite a lot.
9:31 p.m.
On Fri, 16 Sep 2016 16:11:34 -0400
Jeremy Carter <jeremy(a)jeremycarter.ca> wrote:
It is my understanding that Yoshimi is Will's
attempt to add value to
the original ZynAddSubFx. Why he doesn't contribute to the original
project, I have no idea, instead he splits the development effort
between his fork (Yoshimi), and the original project (ZynAddSubFx).
Zyn is still actively developed, although I see Yoshimi getting more
mentions on this list for some reason.
That is my understanding after talking to some of the Linux Audio
community. If I am wrong, I am open to corrections.
Your understanding is flawed.
This has been discussed here and repeatedly in other forums in great detail.
I'm not prepared to go through it all yet again.
Google is your friend.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
9:35 p.m.
It is my
understanding that Yoshimi is Will's attempt to add value to
the original ZynAddSubFx. Why he doesn't contribute to the original
project, I have no idea, instead he splits the development effort
between his fork (Yoshimi), and the original project (ZynAddSubFx).
Zyn is still actively developed, although I see Yoshimi getting more
mentions on this list for some reason.
That is my understanding after talking to some of the Linux Audio
community. If I am wrong, I am open to corrections.
Your understanding is flawed.
This has been discussed here and repeatedly in other forums in great detail.
I'm not prepared to go through it all yet again.
Google is your friend.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user 
17 Sep
17 Sep
9:03 a.m.
On 16/09/16 22:35, Jeremy Carter wrote:
The thing I like about mailing lists is the arguments that come up from
time to time!
I think Yoshimi is great! I'm new to Linux Audio, did most of my music
using a Korg X5DR
driven by a home grown sequencer over the serial port (then via a
USB-Serial adapter).
I still use the sequencer, though I have recently been able to adapt it
to use Jack for output.
I've yet to sort out Jack for input. I doubt if it will ever reach a
state where it could compete
with Ardour, which I recently started using, but it's good enough for
much of what I do.
I tried using Yoshimi because it got frequent mentions on this list, and
was available from the
Mint repositories. I've since downloaded and compiled the latest version
and think that it's a
nice piece of work. If I ever get time to try out Zyn I may switch to
preferring that, but for
the moment, Yoshimi sound good, though I also use the Calf plugins as
they support a decent
General Midi patches.
It's like cars (automobiles?): you try one and like it. It probably has
the odd feature that
could be improved, so you try a different make/model, it called choice.
Sometimes we make
bad choices and sometimes good ones, but the nice thing is that we have
choice. Will has
provided us with choice, so don't knock it!
Let's now bury this discussion....
Bill
--
+----------------------------------------+
| Bill Purvis |
| email: bill(a)billp.org |
+----------------------------------------+
.....
"Compared with Zyn 2.4.0 (when the fork was made by Cal), visible changes are:"
It's not a valid comparison to compare Yoshimi's features in 2016
against Zyn's features in 2009. Zyn has put out 9 new release versions
since 2009, and likely has most of the same features now that you
mention.
12:45 p.m.
New subject: yoshimi, zyn and Ardour (was: Re: How to compile Yoshimi)
On Sat, 17 Sep 2016 10:03:41 +0100
Bill Purvis <bill(a)billp.org> wrote:
I tried using Yoshimi because it got frequent mentions
on this list,
and was available from the
Mint repositories. I've since downloaded and compiled the latest
version and think that it's a
nice piece of work. If I ever get time to try out Zyn I may switch to
preferring that, but for
the moment, Yoshimi sound good, though I also use the Calf plugins as
they support a decent
General Midi patches.
I compiled yoshimi because I thought zyn was no longer supported. So I
tried zyn yesterday. First of all I must say I do not program synth
sounds, at least not yet. I will adjust some parameters to fit a piece
but I'm certainly not creating sounds. I use synths as in using a
guitar. I am not making guitars, I am playing instead.
Because of this, I found the sound selections provided with zyn quite
interesting. Especially the Italian sounds, but also others. The rest
I find is identical to yoshimi. So because of this broader choice of
sounds I will use zyn.
It also seems they are working on a major 3.0 update, which brings the
next two comments. Yesterday I played zyn for about 45 minutes,
improvising. During those times I might record ideas as they
spontaneously happen, or I might just forget about then and enjoy the
spur of the moment. This means I run the synth inside a host, Bitwig
or Ardour (Mixbus 32C) (1). The keyboard can be any, this time it was a
Novation mini Launchkey.
While playing it happened about 3 times that the audio output simply
vanished. I look at Ardour's screen, nothing happens, move the mouse
here and there, and then the sound comes back. In those times what I
described yesterday using yoshimi happened: when the audio came back,
the track's VU meter did not show anything while the master bus VU
showed the audio. Then it came back to normal, with all VUs showing
the audio being played.
The other thing is that by 2-3 times I recorded some audio. This went
fine but, when the recording was stopped and I wanted to quickly get rid
of what was just recorded - as I always do using other synths in Ardour
- by pressing spacebar to stop the recording, then quickly pressing
Ctrl-z to get rid of the recorded region, followed by quickly hitting
the 'home' key to get back at the beginning, ready to record again,
Ardour stalled, for seconds.
This means that zyn has the ability to stall Ardour, for any reason.
Which is not looking good. Such an application should not have the
capability to do this by any means. Having recently lost a complex
project in Bitwig due to Bitwig crashing, I am wary about this kind of
suspicious interaction.
The last time the audio stopped was because Ardour has vanished from
CPU existence.
All in all, zyn has a nice set of sounds, which makes me prefer it
but, it has problems at the systemic level which I hope will be
addressed in the upcoming major version. Strange thing though, to know
about this upcoming version one has to register on the web site. Why
isn't it public ?
(1) When improvising, one nice feature I found was in Pianoteq's
ability to memorize the keys being played at all times, available for
recall if one wishes it. I see that zyn has a record option that
surely 'sounds' the same, although it has to be enabled and it asks for
a wav file which means it is not about recording MIDI data. Using MIDI
data would be lightweight.
Cheers.
19 Sep
19 Sep
11:08 a.m.
New subject: yoshimi, zyn and Ardour
(1) When improvising, one nice feature I found was in
Pianoteq's
ability to memorize the keys being played at all times, available for
recall if one wishes it. I see that zyn has a record option that
surely 'sounds' the same, although it has to be enabled and it asks for
a wav file which means it is not about recording MIDI data. Using MIDI
data would be lightweight.
Can't you use a midi recorder (e.g.sequencer, possibly in MIDI THRU mode
towards th Synth) for that? :)
Lorenzo.
18 Sep
18 Sep
6:10 a.m.
On Fri, 16 Sep 2016 17:35:37 -0400, Jeremy Carter wrote:
It's not a valid comparison to compare
Yoshimi's features in 2016
against Zyn's features in 2009. Zyn has put out 9 new release versions
since 2009, and likely has most of the same features now that you
mention.
As a Yamaha TG33 owner I always asked to provide vector control,
already years back. I still didn't use Yoshimi with vector control, but
I'm experienced in using vector control with my Yamaha synth. Does Zyn
provide vector control, too? If not, then IMO Zyn would be missing
one of the most important new features, if not the most important
feature. I recommend to listen to the weak basic sounds of a TG33. It's
unbelievable that the TG33 is able to produce such amazing sounds, just
by mixing volumes and fine tune recorded by a sequence.
Regards,
Ralf
16 Sep
16 Sep
8:34 p.m.
On Fri, September 16, 2016 3:01 pm, Chris Caudle wrote:
Wasn't there a difference in real-time safe
functions used by one or the
other?
I think maybe this is what I was remembering:
http://www.spinics.net/lists/linux-audio-users/msg103851.html
Mark Curry:
"To clarify one other point in this thread, zyn
is not absolutely 100%
realtime safe and stoat can certainly point out the few remaining issues
(there is a single location for memory allocation/deallocation which
needs to be
corrected (NO LOCKS)).
Compared to yoshimi however it is an absolutely night
and day difference.
Based upon checking yoshimi's git again it should be essentially equal
to the realtime safety that zyn had back at its 2.4.4 release."
"As part of trying to correct these long standing
issues within
ZynAddSubFX one of the tools that I wrote starting back in 2012 was
stoat: https://github.com/fundamental/stoat"
The announcement for the 2.5.0 release of Zyn has links to two graphs
showing the number of function calls which are not, or potentially not,
real-time safe. The graph of 2.4.4 is so dense it is unreadable, the
equivalent graph for 2.5.0 is fairly small.
http://lalists.stanford.edu/laa/2015/02/0006.html
"The 2.5.0 Release of ZynAddSubFX is now
available.
"This release is mainly focused on fixing some of the core architectural
flaws that have historically existed.
As a result this release should behave much better under jack
and interfacing with the realtime side of things is *much* easier now.
...
"Additionally the callgraph of the realtime safe
hazards can be seen
in two large images:
http://fundamental-code.com/2.4.4-realtime-issues.png
http://fundamental-code.com/2.5.0-realtime-issues.png "
--
Chris Caudle
9 p.m.
On Fri, 16 Sep 2016 19:24:11 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
> 2) yoshimi and zynsubaddfx ?
Instrument wise - none.
Control wise - quite a lot.
Here in Yoshimi land we say try both and see what you
prefer. I know
of some people who maintain both for different workflows.
Popped up a few screens in yoshimi. Sure looks like what I recall of
zynaddsubfx. Unless zyn has changed radically these days.
Care to mention a few bullet points of what is so different ?
9:27 p.m.
On Fri, 16 Sep 2016 17:00:19 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
On Fri, 16 Sep 2016 19:24:11 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
Compared with Zyn 2.4.0 (when the fork was made by Cal), visible changes are:
Inproved Jack support.
State save and load.
Unified MIDI accessible root, bank & instrument structure.
Extensive NRPN support.
Improved Alsa audio support.
More accurate VU metering.
Enabled independent part audio outputs.
LV2 support.
Multiple instances.
Extended part structure.
Recent load/save history.
Extended (and improved) settings menus.
Command line access (not instrument editors yet).
Vector control.
Improved slider and knob controls and 'home'.
MIDI part channel switching.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
> 2) yoshimi and zynsubaddfx ?
Instrument wise - none.
Control wise - quite a lot.
Here in Yoshimi land we say try both and see what
you prefer. I know
of some people who maintain both for different workflows.
Popped up a few screens in yoshimi. Sure looks like what I recall of
zynaddsubfx. Unless zyn has changed radically these days.
Care to mention a few bullet points of what is so different ?
18 Sep
18 Sep
5:57 a.m.
On Fri, 16 Sep 2016 19:24:11 +0100, Will Godfrey wrote:
Here in Yoshimi land we say try both and see what you
prefer. I know
of some people who maintain both for different workflows.
An important tip for the OP, if they should sound different, when using
the same sounds, compare the interpolation chosen by the settings.
3:34 p.m.
On Sun, 18 Sep 2016 07:56:47 +0200
Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> wrote:
On Fri, 16 Sep 2016 19:24:11 +0100, Will Godfrey
wrote:
>Here in Yoshimi land we say try both and see what you prefer. I know
>of some people who maintain both for different workflows.
An important tip for the OP, if they should sound
different, when
using the same sounds, compare the interpolation chosen by the
settings.
That might be useful to know, to compare precisely. Although before
doing so there are many mix considerations to take care of on one side,
and on the other side, zyn has a repeated tendency of stalling Ardour
(Mixbus 32C) for seconds that borders on not being usable. At least I
have to do more 'test' sessions before attempting to use it in a
real project.
It is as if zyn is taking Ardour for discussions at the Jackd National
Assembly. Only when they settle can Ardour actually come back to work,
showing signs of life to the user.
9:58 p.m.
I used zynaddsubfx and yoshimi stand alone, not as a plugin. At the
beginning I stayed with zynaddsubfx because it sounded better than
yoshimi, but then I noticed that it was related to different default
settings.
On my machine zyanaddsubfx isn't installed anymore.
[rocketmouse@archlinux ~]$ packages zyn
Repositories
community/zynaddsubfx 2.5.4-1
Opensource software synthesizer capable of making a countless number of
instruments.
aur/yoshimi 1.4.1-1 [installed: 1.4.0.1-1] (63) (1.32)
a fork of the ZynAddSubFX software systhesizer
aur/yoshimi-git 785.7927342-1 (1) (0.01)
ZynAddSubFX fork with improved JACK audio & MIDI IO (git version)
aur/zyn-ext-gui-lv2 4.0.6.0-1 (1) (0.69)
Toolkit agnostic LV2 UI for ZynAddSubFx
aur/zynaddsubfx-git 2.5.4.r138.g0776bad-1 (13) (1.02)
A powerful realtime, multi-timbral software synthesizer.
Installed
local/yoshimi 1.4.0.1-1
a fork of the ZynAddSubFX software systhesizer
Btw. right now I added a comment to the AUR yoshimi-git package ;),
https://aur.archlinux.org/packages/yoshimi-git/ .
Regards,
Ralf
2782
days inactive
2786
days old
linux-audio-user@lists.linuxaudio.org
25 comments
8 participants
participants (8)
-
Bill Purvis -
Chris Caudle -
Ffanci Silvain -
Jeremy Carter -
jonetsu＠teksavvy.com -
Lorenzo Sutton -
Ralf Mardorf -
Will Godfrey