[NEW] audio/zynaddsubfx

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[NEW] audio/zynaddsubfx

Dimitri Karamazov
This here is a terrific synthesizer and can be put to good use
with some DAW with lv2 support. Can be used with lmms if
carla is ported or just wait until lv2 is supported(ongoing).
https://github.com/LMMS/lmms/issues/562

I've a muse(https://vstwarehouse.com/d/muse/) port with me which
can run this as plugin(both vst & lv2) but it brings along with
it 4-5 dependencies so might release it some other time.

Information for inst:zynaddsubfx-3.0.5

Comment:
synth capable of making a countless number of instruments

Description:
ZynAddSubFX is a opensource software synthesizer capable of making
a countless number of instruments, from some common heard from
expensive hardware to interesting sounds that you'll boost to an
amazing universe of sounds.

Maintainer: Dimitri Karamazov <[hidden email]>

WWW: http://zynaddsubfx.sourceforge.net

Port below adds a nice graphical interface to the synthesizer.
Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
Although there other interfaces available like fltk and ntk, both
are quite cumbersome to use, and very ugly in comparison.

Information for inst:zyn-fusion-3.0.5pre

Comment:
single window & tabbed version of the ZynAddSubFX interface

Required by:
zynaddsubfx-3.0.5

Description:
Zyn was plagued with a difficult to use interface and unstable, unofficial
plugin versions. Fusion blows those issues away with a complete redesign and
rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
any platform. With total separation of the UI from the synthesis engine.

Zyn-Fusion is enabling powerful features such as the new, officially-supported
VST plugin version, remote control of a headless CPU with the UI on
touchscreen, even multiple UI windows controlling a single sound engine. By
fusing 28 windows of fine grained control into one, Zyn is now controlled with
a single window design of tabbed views for a consistent, navigable interface.
You think you've heard the sounds before, but you've never had the precision
control of Fusion.

Maintainer: Dimitri Karamazov <[hidden email]>

WWW: https://github.com/mruby-zest/mruby-zest-build

Both Build & Run tested on amd64

zynaddsubfx.tar.gz (19K) Download Attachment
zyn-fusion.tar.gz (8K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Stuart Henderson
zynaddsubfx picks up bash-completion if present at build time,

$ diff pkg/PLIST.orig pkg/PLIST
--- pkg/PLIST.orig Wed Feb 10 16:31:49 2021
+++ pkg/PLIST Tue Mar  9 19:39:30 2021
@@ -47,6 +47,9 @@ share/applications/zynaddsubfx-alsa.desktop
 share/applications/zynaddsubfx-jack-multi.desktop
 share/applications/zynaddsubfx-jack.desktop
 share/applications/zynaddsubfx-oss.desktop
+share/bash_completion/
+share/bash_completion/completions/
+share/bash_completion/completions/zynaddsubfx
 share/doc/zynaddsubfx/
 share/doc/zynaddsubfx/AUTHORS.txt
 share/doc/zynaddsubfx/COPYING

can you force that either on or off please? either add a build dep on
shells/bash-completion or set BASHCOMP_PKG_PATH.



Nice work on the zyn-fusion Makefile with the distfiles. It hardcodes
gcc somewhere though (and I just noticed it forces -O3 as well),

[...]
configure: creating ./config.status
config.status: creating config.h
cd src/osc-bridge    && make lib
cc -O2 -pipe   -I/usr/local/include -I/usr/X11R6/include -std=gnu99 -Wall -Wextra -I . -O3 -g -fPIC -c src/bridge.c src/cache.c src/parse-schema.c src/schema.c rtosc/rtosc.c
src/parse-schema.c:11:9: warning: 'putchar' macro redefined [-Wmacro-redefined]
#define putchar(x) (void)(x)
        ^
/usr/include/stdio.h:435:9: note: previous definition is here
#define putchar(x)      putc(x, stdout)
        ^
1 warning generated.
ar rcs libosc-bridge.a bridge.o cache.o parse-schema.o schema.o rtosc.o
cd mruby             && MRUBY_CONFIG=../build_config.rb /usr/local/bin/rake27
Environment is:

CPP   src/array.c -> build/host/src/array.i
sh: gcc: not found
rake aborted!
Command failed with status (127): [gcc -E -P -std=gnu99 -O2 -pipe   -I/usr/lo...]
[...]

Looks like you maybe able to steal some bits from ports/lang/mruby.
(Guessing it needs some specific version and can't just use the mruby
port directly?)


The dependencies seem the wrong way round, shouldn't it be zyn-fusion
that depends on zynaddsubfx instead? (For discoverability I'd probably
but zyn-fusion in audio/ instead of x11/).

On 2021/03/07 15:03, Dimitri Karamazov wrote:

> Ping
>
> On Sat, Feb 27, 2021 at 05:32:23PM +0000, Dimitri Karamazov wrote:
> > Ping
> >
> > On Wed, Feb 17, 2021 at 05:39:57PM +0000, Dimitri Karamazov wrote:
> > > This here is a terrific synthesizer and can be put to good use
> > > with some DAW with lv2 support. Can be used with lmms if
> > > carla is ported or just wait until lv2 is supported(ongoing).
> > > https://github.com/LMMS/lmms/issues/562
> > >
> > > I've a muse(https://vstwarehouse.com/d/muse/) port with me which
> > > can run this as plugin(both vst & lv2) but it brings along with
> > > it 4-5 dependencies so might release it some other time.
> > >
> > > Information for inst:zynaddsubfx-3.0.5
> > >
> > > Comment:
> > > synth capable of making a countless number of instruments
> > >
> > > Description:
> > > ZynAddSubFX is a opensource software synthesizer capable of making
> > > a countless number of instruments, from some common heard from
> > > expensive hardware to interesting sounds that you'll boost to an
> > > amazing universe of sounds.
>
> *Polyphonic with support for legato and mono playing modes
> *Three synthesizer engines:
>  -Additive Synthesis for classic synth sounds composed of a variety of voices with powerful modulation.
>   This exposes modulators ranging from LFOs and envelopes to oscillator modulators for FM, PM, and AM.
>  -Subtractive Synthesis for creating variable bandwidth harmonics from filtered white noise
>  -PAD synthesis for creating beautiful pads and other instruments
> *Powerful waveform generator with up to 128 sine/non-sine harmonics
> *A variety of filters including analogue modeled filters, formant filters, and state variable filters.
> *Envelopes can have ADSR (or ASR, etc..) modes or can be free modes (with any shape)
> *Effects for Reverb, Echo, Chorus/Flange, Phasing, Wave-shaping, Equalizing, Dynamic Filtering with
>  flexible signal routing
> *Instruments can be organized in kits, which allows you to make drum kits or layered instruments; this
>  makes possible to use more than one instrument for a single part. It is possible to choose what items
>  from the kit should be processed by the Part's effects.
> *Randomness settings to create subtle differences in each sound to help create that familiar analogue warmth.
> *Microtonal capabilities with any scale, up to 128 notes per octave, and key mapping
> *Extensive MIDI/Audio driver support including JACK, ALSA, OSS, and PortAudio
> *A built-in Virtual Keyboard which can be used even if you don't have a physical midi keyboard
> *The graphical user interface can be completely disabled if the user need so
> *Session Management Support via LASH/NSM
> *Plugin Support via DSSI/LV2/VST
> *Over 1100 high quality instruments included
>
> > >
> > > Maintainer: Dimitri Karamazov <[hidden email]>
> > >
> > > WWW: http://zynaddsubfx.sourceforge.net
> > >
> > > Port below adds a nice graphical interface to the synthesizer.
> > > Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
> > > Although there other interfaces available like fltk and ntk, both
> > > are quite cumbersome to use, and very ugly in comparison.
> > >
> > > Information for inst:zyn-fusion-3.0.5pre
> > >
> > > Comment:
> > > single window & tabbed version of the ZynAddSubFX interface
> > >
> > > Required by:
> > > zynaddsubfx-3.0.5
> > >
> > > Description:
> > > Zyn was plagued with a difficult to use interface and unstable, unofficial
> > > plugin versions. Fusion blows those issues away with a complete redesign and
> > > rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
> > > any platform. With total separation of the UI from the synthesis engine.
> > >
> > > Zyn-Fusion is enabling powerful features such as the new, officially-supported
> > > VST plugin version, remote control of a headless CPU with the UI on
> > > touchscreen, even multiple UI windows controlling a single sound engine. By
> > > fusing 28 windows of fine grained control into one, Zyn is now controlled with
> > > a single window design of tabbed views for a consistent, navigable interface.
> > > You think you've heard the sounds before, but you've never had the precision
> > > control of Fusion.
> > >
> > > Maintainer: Dimitri Karamazov <[hidden email]>
> > >
> > > WWW: https://github.com/mruby-zest/mruby-zest-build
> > >
> > > Both Build & Run tested on amd64



Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
On Tue, Mar 09, 2021 at 07:51:48PM +0000, Stuart Henderson wrote:

> zynaddsubfx picks up bash-completion if present at build time,
>
> $ diff pkg/PLIST.orig pkg/PLIST
> --- pkg/PLIST.orig Wed Feb 10 16:31:49 2021
> +++ pkg/PLIST Tue Mar  9 19:39:30 2021
> @@ -47,6 +47,9 @@ share/applications/zynaddsubfx-alsa.desktop
>  share/applications/zynaddsubfx-jack-multi.desktop
>  share/applications/zynaddsubfx-jack.desktop
>  share/applications/zynaddsubfx-oss.desktop
> +share/bash_completion/
> +share/bash_completion/completions/
> +share/bash_completion/completions/zynaddsubfx
>  share/doc/zynaddsubfx/
>  share/doc/zynaddsubfx/AUTHORS.txt
>  share/doc/zynaddsubfx/COPYING
>
> can you force that either on or off please? either add a build dep on
> shells/bash-completion or set BASHCOMP_PKG_PATH.
The install script uses bash which I've added to BUILD_DEPENDS.

> Nice work on the zyn-fusion Makefile with the distfiles. It hardcodes
> gcc somewhere though (and I just noticed it forces -O3 as well),

I couldn't recreate the gcc issue(after removing ports-gcc) so I've set
CC and LD in MAKE_FLAGS but why will the command fail if gcc is
available in the base?

> [...]
> configure: creating ./config.status
> config.status: creating config.h
> cd src/osc-bridge    && make lib
> cc -O2 -pipe   -I/usr/local/include -I/usr/X11R6/include -std=gnu99 -Wall -Wextra -I . -O3 -g -fPIC -c src/bridge.c src/cache.c src/parse-schema.c src/schema.c rtosc/rtosc.c
> src/parse-schema.c:11:9: warning: 'putchar' macro redefined [-Wmacro-redefined]
> #define putchar(x) (void)(x)
>         ^
> /usr/include/stdio.h:435:9: note: previous definition is here
> #define putchar(x)      putc(x, stdout)
>         ^
> 1 warning generated.
> ar rcs libosc-bridge.a bridge.o cache.o parse-schema.o schema.o rtosc.o
> cd mruby             && MRUBY_CONFIG=../build_config.rb /usr/local/bin/rake27
> Environment is:
>
> CPP   src/array.c -> build/host/src/array.i
> sh: gcc: not found
> rake aborted!
> Command failed with status (127): [gcc -E -P -std=gnu99 -O2 -pipe   -I/usr/lo...]
> [...]
>
> Looks like you maybe able to steal some bits from ports/lang/mruby.
> (Guessing it needs some specific version and can't just use the mruby
> port directly?)
In the present case the mruby interpretor is a internal part of the program
and thus requires the source code to be available during the build.
Developers of zyn-fusion didn't intend this program to be open-source so
everything is static-linked by default the refractoring needed here is immense.

> The dependencies seem the wrong way round, shouldn't it be zyn-fusion
> that depends on zynaddsubfx instead? (For discoverability I'd probably
> but zyn-fusion in audio/ instead of x11/).

zyn-fusion unlike other frontends cannot interact with the backend.
You can check this yourself, executing zyn-fusion gives you an empty
interface and this is by design. So moving zyn-fusion into audio
wouldn't make sense since it is only an x11-interface(like ntk/fltk)
and more like a dependency for zynaddsubfx than the other way around.
It is by executing the zynaddsubfx binary that a user will actually trigger
the usable interface. Ofcourse this goes contrary to how frontends are
actually developed but that is what we are dealing with.
So I think the categories should be kept as is.

I will be introducing MULTI_PACKAGES in zynaddsubfx for the ntk and fltk
interfaces later on so distinctions in the frontend available will be more
clear while installing.

>
> On 2021/03/07 15:03, Dimitri Karamazov wrote:
> > Ping
> >
> > On Sat, Feb 27, 2021 at 05:32:23PM +0000, Dimitri Karamazov wrote:
> > > Ping
> > >
> > > On Wed, Feb 17, 2021 at 05:39:57PM +0000, Dimitri Karamazov wrote:
> > > > This here is a terrific synthesizer and can be put to good use
> > > > with some DAW with lv2 support. Can be used with lmms if
> > > > carla is ported or just wait until lv2 is supported(ongoing).
> > > > https://github.com/LMMS/lmms/issues/562
> > > >
> > > > I've a muse(https://vstwarehouse.com/d/muse/) port with me which
> > > > can run this as plugin(both vst & lv2) but it brings along with
> > > > it 4-5 dependencies so might release it some other time.
> > > >
> > > > Information for inst:zynaddsubfx-3.0.5
> > > >
> > > > Comment:
> > > > synth capable of making a countless number of instruments
> > > >
> > > > Description:
> > > > ZynAddSubFX is a opensource software synthesizer capable of making
> > > > a countless number of instruments, from some common heard from
> > > > expensive hardware to interesting sounds that you'll boost to an
> > > > amazing universe of sounds.
> >
> > *Polyphonic with support for legato and mono playing modes
> > *Three synthesizer engines:
> >  -Additive Synthesis for classic synth sounds composed of a variety of voices with powerful modulation.
> >   This exposes modulators ranging from LFOs and envelopes to oscillator modulators for FM, PM, and AM.
> >  -Subtractive Synthesis for creating variable bandwidth harmonics from filtered white noise
> >  -PAD synthesis for creating beautiful pads and other instruments
> > *Powerful waveform generator with up to 128 sine/non-sine harmonics
> > *A variety of filters including analogue modeled filters, formant filters, and state variable filters.
> > *Envelopes can have ADSR (or ASR, etc..) modes or can be free modes (with any shape)
> > *Effects for Reverb, Echo, Chorus/Flange, Phasing, Wave-shaping, Equalizing, Dynamic Filtering with
> >  flexible signal routing
> > *Instruments can be organized in kits, which allows you to make drum kits or layered instruments; this
> >  makes possible to use more than one instrument for a single part. It is possible to choose what items
> >  from the kit should be processed by the Part's effects.
> > *Randomness settings to create subtle differences in each sound to help create that familiar analogue warmth.
> > *Microtonal capabilities with any scale, up to 128 notes per octave, and key mapping
> > *Extensive MIDI/Audio driver support including JACK, ALSA, OSS, and PortAudio
> > *A built-in Virtual Keyboard which can be used even if you don't have a physical midi keyboard
> > *The graphical user interface can be completely disabled if the user need so
> > *Session Management Support via LASH/NSM
> > *Plugin Support via DSSI/LV2/VST
> > *Over 1100 high quality instruments included
> >
> > > >
> > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > >
> > > > WWW: http://zynaddsubfx.sourceforge.net
> > > >
> > > > Port below adds a nice graphical interface to the synthesizer.
> > > > Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
> > > > Although there other interfaces available like fltk and ntk, both
> > > > are quite cumbersome to use, and very ugly in comparison.
> > > >
> > > > Information for inst:zyn-fusion-3.0.5pre
> > > >
> > > > Comment:
> > > > single window & tabbed version of the ZynAddSubFX interface
> > > >
> > > > Required by:
> > > > zynaddsubfx-3.0.5
> > > >
> > > > Description:
> > > > Zyn was plagued with a difficult to use interface and unstable, unofficial
> > > > plugin versions. Fusion blows those issues away with a complete redesign and
> > > > rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
> > > > any platform. With total separation of the UI from the synthesis engine.
> > > >
> > > > Zyn-Fusion is enabling powerful features such as the new, officially-supported
> > > > VST plugin version, remote control of a headless CPU with the UI on
> > > > touchscreen, even multiple UI windows controlling a single sound engine. By
> > > > fusing 28 windows of fine grained control into one, Zyn is now controlled with
> > > > a single window design of tabbed views for a consistent, navigable interface.
> > > > You think you've heard the sounds before, but you've never had the precision
> > > > control of Fusion.
> > > >
> > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > >
> > > > WWW: https://github.com/mruby-zest/mruby-zest-build
> > > >
> > > > Both Build & Run tested on amd64
>
>
>

zyn-fusion.tar.gz (8K) Download Attachment
zynaddsubfx.tar.gz (19K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Stuart Henderson
On 2021/03/10 14:04, Dimitri Karamazov wrote:

> On Tue, Mar 09, 2021 at 07:51:48PM +0000, Stuart Henderson wrote:
> > zynaddsubfx picks up bash-completion if present at build time,
> >
> > $ diff pkg/PLIST.orig pkg/PLIST
> > --- pkg/PLIST.orig Wed Feb 10 16:31:49 2021
> > +++ pkg/PLIST Tue Mar  9 19:39:30 2021
> > @@ -47,6 +47,9 @@ share/applications/zynaddsubfx-alsa.desktop
> >  share/applications/zynaddsubfx-jack-multi.desktop
> >  share/applications/zynaddsubfx-jack.desktop
> >  share/applications/zynaddsubfx-oss.desktop
> > +share/bash_completion/
> > +share/bash_completion/completions/
> > +share/bash_completion/completions/zynaddsubfx
> >  share/doc/zynaddsubfx/
> >  share/doc/zynaddsubfx/AUTHORS.txt
> >  share/doc/zynaddsubfx/COPYING
> >
> > can you force that either on or off please? either add a build dep on
> > shells/bash-completion or set BASHCOMP_PKG_PATH.
>
> The install script uses bash which I've added to BUILD_DEPENDS.

I don't see it using bash anywhere?

It only looks for the pkg-config file from shells/bash-completion,
installing bash won't have it create the completion files, only installing
bash-completion (or passing the configure arg, but it looks like the
directory may need to exist too, so it's less messy to just build dep
on bash-completion).

> > Nice work on the zyn-fusion Makefile with the distfiles. It hardcodes
> > gcc somewhere though (and I just noticed it forces -O3 as well),
>
> I couldn't recreate the gcc issue(after removing ports-gcc) so I've set
> CC and LD in MAKE_FLAGS but why will the command fail if gcc is
> available in the base?

gcc is only available in base on alpha amd64 hppa sh sparc64, and it
should not be used by anything in base/ports on amd64 (it's only there to
make it easier for people to test building things with old-gcc but really
it causes more problems than it solves now).

> > Looks like you maybe able to steal some bits from ports/lang/mruby.
> > (Guessing it needs some specific version and can't just use the mruby
> > port directly?)
>
> In the present case the mruby interpretor is a internal part of the program
> and thus requires the source code to be available during the build.
> Developers of zyn-fusion didn't intend this program to be open-source so
> everything is static-linked by default the refractoring needed here is immense.

ack. In which case try borrowing patches from the mruby port which
already solved these problems.

> > The dependencies seem the wrong way round, shouldn't it be zyn-fusion
> > that depends on zynaddsubfx instead? (For discoverability I'd probably
> > but zyn-fusion in audio/ instead of x11/).
>
> zyn-fusion unlike other frontends cannot interact with the backend.
> You can check this yourself, executing zyn-fusion gives you an empty
> interface and this is by design. So moving zyn-fusion into audio
> wouldn't make sense since it is only an x11-interface(like ntk/fltk)
> and more like a dependency for zynaddsubfx than the other way around.
> It is by executing the zynaddsubfx binary that a user will actually trigger
> the usable interface. Ofcourse this goes contrary to how frontends are
> actually developed but that is what we are dealing with.
> So I think the categories should be kept as is.

In that case I think there needs to be some user-facing information
about this, maybe a short pkg-readme, or at least in DESCR, otherwise
user experience for someone that has read about zyn-fusion and wants to
try it with "pkg_add zyn-fusion" won't be good.


> I will be introducing MULTI_PACKAGES in zynaddsubfx for the ntk and fltk
> interfaces later on so distinctions in the frontend available will be more
> clear while installing.
>
> >
> > On 2021/03/07 15:03, Dimitri Karamazov wrote:
> > > Ping
> > >
> > > On Sat, Feb 27, 2021 at 05:32:23PM +0000, Dimitri Karamazov wrote:
> > > > Ping
> > > >
> > > > On Wed, Feb 17, 2021 at 05:39:57PM +0000, Dimitri Karamazov wrote:
> > > > > This here is a terrific synthesizer and can be put to good use
> > > > > with some DAW with lv2 support. Can be used with lmms if
> > > > > carla is ported or just wait until lv2 is supported(ongoing).
> > > > > https://github.com/LMMS/lmms/issues/562
> > > > >
> > > > > I've a muse(https://vstwarehouse.com/d/muse/) port with me which
> > > > > can run this as plugin(both vst & lv2) but it brings along with
> > > > > it 4-5 dependencies so might release it some other time.
> > > > >
> > > > > Information for inst:zynaddsubfx-3.0.5
> > > > >
> > > > > Comment:
> > > > > synth capable of making a countless number of instruments
> > > > >
> > > > > Description:
> > > > > ZynAddSubFX is a opensource software synthesizer capable of making
> > > > > a countless number of instruments, from some common heard from
> > > > > expensive hardware to interesting sounds that you'll boost to an
> > > > > amazing universe of sounds.
> > >
> > > *Polyphonic with support for legato and mono playing modes
> > > *Three synthesizer engines:
> > >  -Additive Synthesis for classic synth sounds composed of a variety of voices with powerful modulation.
> > >   This exposes modulators ranging from LFOs and envelopes to oscillator modulators for FM, PM, and AM.
> > >  -Subtractive Synthesis for creating variable bandwidth harmonics from filtered white noise
> > >  -PAD synthesis for creating beautiful pads and other instruments
> > > *Powerful waveform generator with up to 128 sine/non-sine harmonics
> > > *A variety of filters including analogue modeled filters, formant filters, and state variable filters.
> > > *Envelopes can have ADSR (or ASR, etc..) modes or can be free modes (with any shape)
> > > *Effects for Reverb, Echo, Chorus/Flange, Phasing, Wave-shaping, Equalizing, Dynamic Filtering with
> > >  flexible signal routing
> > > *Instruments can be organized in kits, which allows you to make drum kits or layered instruments; this
> > >  makes possible to use more than one instrument for a single part. It is possible to choose what items
> > >  from the kit should be processed by the Part's effects.
> > > *Randomness settings to create subtle differences in each sound to help create that familiar analogue warmth.
> > > *Microtonal capabilities with any scale, up to 128 notes per octave, and key mapping
> > > *Extensive MIDI/Audio driver support including JACK, ALSA, OSS, and PortAudio
> > > *A built-in Virtual Keyboard which can be used even if you don't have a physical midi keyboard
> > > *The graphical user interface can be completely disabled if the user need so
> > > *Session Management Support via LASH/NSM
> > > *Plugin Support via DSSI/LV2/VST
> > > *Over 1100 high quality instruments included
> > >
> > > > >
> > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > >
> > > > > WWW: http://zynaddsubfx.sourceforge.net
> > > > >
> > > > > Port below adds a nice graphical interface to the synthesizer.
> > > > > Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
> > > > > Although there other interfaces available like fltk and ntk, both
> > > > > are quite cumbersome to use, and very ugly in comparison.
> > > > >
> > > > > Information for inst:zyn-fusion-3.0.5pre
> > > > >
> > > > > Comment:
> > > > > single window & tabbed version of the ZynAddSubFX interface
> > > > >
> > > > > Required by:
> > > > > zynaddsubfx-3.0.5
> > > > >
> > > > > Description:
> > > > > Zyn was plagued with a difficult to use interface and unstable, unofficial
> > > > > plugin versions. Fusion blows those issues away with a complete redesign and
> > > > > rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
> > > > > any platform. With total separation of the UI from the synthesis engine.
> > > > >
> > > > > Zyn-Fusion is enabling powerful features such as the new, officially-supported
> > > > > VST plugin version, remote control of a headless CPU with the UI on
> > > > > touchscreen, even multiple UI windows controlling a single sound engine. By
> > > > > fusing 28 windows of fine grained control into one, Zyn is now controlled with
> > > > > a single window design of tabbed views for a consistent, navigable interface.
> > > > > You think you've heard the sounds before, but you've never had the precision
> > > > > control of Fusion.
> > > > >
> > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > >
> > > > > WWW: https://github.com/mruby-zest/mruby-zest-build
> > > > >
> > > > > Both Build & Run tested on amd64
> >
> >
> >



Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
On Thu, Mar 11, 2021 at 11:34:47AM +0000, Stuart Henderson wrote:

> On 2021/03/10 14:04, Dimitri Karamazov wrote:
> > On Tue, Mar 09, 2021 at 07:51:48PM +0000, Stuart Henderson wrote:
> > > zynaddsubfx picks up bash-completion if present at build time,
> > >
> > > $ diff pkg/PLIST.orig pkg/PLIST
> > > --- pkg/PLIST.orig Wed Feb 10 16:31:49 2021
> > > +++ pkg/PLIST Tue Mar  9 19:39:30 2021
> > > @@ -47,6 +47,9 @@ share/applications/zynaddsubfx-alsa.desktop
> > >  share/applications/zynaddsubfx-jack-multi.desktop
> > >  share/applications/zynaddsubfx-jack.desktop
> > >  share/applications/zynaddsubfx-oss.desktop
> > > +share/bash_completion/
> > > +share/bash_completion/completions/
> > > +share/bash_completion/completions/zynaddsubfx
> > >  share/doc/zynaddsubfx/
> > >  share/doc/zynaddsubfx/AUTHORS.txt
> > >  share/doc/zynaddsubfx/COPYING
> > >
> > > can you force that either on or off please? either add a build dep on
> > > shells/bash-completion or set BASHCOMP_PKG_PATH.
> >
> > The install script uses bash which I've added to BUILD_DEPENDS.
>
> I don't see it using bash anywhere?
>
> It only looks for the pkg-config file from shells/bash-completion,
> installing bash won't have it create the completion files, only installing
> bash-completion (or passing the configure arg, but it looks like the
> directory may need to exist too, so it's less messy to just build dep
> on bash-completion).
I've added bash-completion to BUILD_DEPENDS and this patch below to remove
the bash dependency. The script uses mkdir if the directory doesn't exist.

$OpenBSD$

fix bash_completion install

--- cmake/BashCompletion.cmake.orig Sat Feb 23 21:13:37 2019
+++ cmake/BashCompletion.cmake Thu Mar 11 18:06:57 2021
@@ -71,9 +71,9 @@ ELSE()
  SET(BASHCOMP_SCRIPT "${CMAKE_CURRENT_BINARY_DIR}/install_${SCRIPT_NAME}_completion.sh")
 
  FILE(WRITE ${BASHCOMP_SCRIPT} "\
-#!${BASH}\n\
+#!/bin/sh\n\
 set -e\n\
-BASHCOMP_PKG_PATH=\"${BASHCOMP_USER_PATH}\"\n\
+BASHCOMP_PKG_PATH=\"\$DESTDIR${BASHCOMP_USER_PATH}\"\n\
 if [ -w \"${BASHCOMP_PKG_PATH}\" ]; then\n\
   BASHCOMP_PKG_PATH=\"${BASHCOMP_PKG_PATH}\"\n\
 fi\n\

> > > Nice work on the zyn-fusion Makefile with the distfiles. It hardcodes
> > > gcc somewhere though (and I just noticed it forces -O3 as well),
> >
> > I couldn't recreate the gcc issue(after removing ports-gcc) so I've set
> > CC and LD in MAKE_FLAGS but why will the command fail if gcc is
> > available in the base?
>
> gcc is only available in base on alpha amd64 hppa sh sparc64, and it
> should not be used by anything in base/ports on amd64 (it's only there to
> make it easier for people to test building things with old-gcc but really
> it causes more problems than it solves now).
I've tested after removing both ports-gcc and base-gcc(actually renaming the
binary for base-gcc) and I cannot encounter that issue, you can test it
again now. I can think it was an issue with CC CXX and LD not being set.

> > > Looks like you maybe able to steal some bits from ports/lang/mruby.
> > > (Guessing it needs some specific version and can't just use the mruby
> > > port directly?)
> >
> > In the present case the mruby interpretor is a internal part of the program
> > and thus requires the source code to be available during the build.
> > Developers of zyn-fusion didn't intend this program to be open-source so
> > everything is static-linked by default the refractoring needed here is immense.
>
> ack. In which case try borrowing patches from the mruby port which
> already solved these problems.
I've taken the necessary patches.

> > > The dependencies seem the wrong way round, shouldn't it be zyn-fusion
> > > that depends on zynaddsubfx instead? (For discoverability I'd probably
> > > but zyn-fusion in audio/ instead of x11/).
> >
> > zyn-fusion unlike other frontends cannot interact with the backend.
> > You can check this yourself, executing zyn-fusion gives you an empty
> > interface and this is by design. So moving zyn-fusion into audio
> > wouldn't make sense since it is only an x11-interface(like ntk/fltk)
> > and more like a dependency for zynaddsubfx than the other way around.
> > It is by executing the zynaddsubfx binary that a user will actually trigger
> > the usable interface. Ofcourse this goes contrary to how frontends are
> > actually developed but that is what we are dealing with.
> > So I think the categories should be kept as is.
>
> In that case I think there needs to be some user-facing information
> about this, maybe a short pkg-readme, or at least in DESCR, otherwise
> user experience for someone that has read about zyn-fusion and wants to
> try it with "pkg_add zyn-fusion" won't be good.
This is part of zyn-fusion port now.

$OpenBSD: README.template,v 1.7 2019/05/09 17:45:05 ajacoutot Exp $

+-------------------------------------------------------------------------------
| Running ${PKGSTEM} on OpenBSD
+-------------------------------------------------------------------------------

Running zyn-fusion
==================

The zyn-fusion package consist only of a x11-interface for the zynaddsubfx
backend. To run the synthesizer install the zynaddsubfx package and execute the
zynaddsubfx binary.

> > I will be introducing MULTI_PACKAGES in zynaddsubfx for the ntk and fltk
> > interfaces later on so distinctions in the frontend available will be more
> > clear while installing.
> >
> > >
> > > On 2021/03/07 15:03, Dimitri Karamazov wrote:
> > > > Ping
> > > >
> > > > On Sat, Feb 27, 2021 at 05:32:23PM +0000, Dimitri Karamazov wrote:
> > > > > Ping
> > > > >
> > > > > On Wed, Feb 17, 2021 at 05:39:57PM +0000, Dimitri Karamazov wrote:
> > > > > > This here is a terrific synthesizer and can be put to good use
> > > > > > with some DAW with lv2 support. Can be used with lmms if
> > > > > > carla is ported or just wait until lv2 is supported(ongoing).
> > > > > > https://github.com/LMMS/lmms/issues/562
> > > > > >
> > > > > > I've a muse(https://vstwarehouse.com/d/muse/) port with me which
> > > > > > can run this as plugin(both vst & lv2) but it brings along with
> > > > > > it 4-5 dependencies so might release it some other time.
> > > > > >
> > > > > > Information for inst:zynaddsubfx-3.0.5
> > > > > >
> > > > > > Comment:
> > > > > > synth capable of making a countless number of instruments
> > > > > >
> > > > > > Description:
> > > > > > ZynAddSubFX is a opensource software synthesizer capable of making
> > > > > > a countless number of instruments, from some common heard from
> > > > > > expensive hardware to interesting sounds that you'll boost to an
> > > > > > amazing universe of sounds.
> > > >
> > > > *Polyphonic with support for legato and mono playing modes
> > > > *Three synthesizer engines:
> > > >  -Additive Synthesis for classic synth sounds composed of a variety of voices with powerful modulation.
> > > >   This exposes modulators ranging from LFOs and envelopes to oscillator modulators for FM, PM, and AM.
> > > >  -Subtractive Synthesis for creating variable bandwidth harmonics from filtered white noise
> > > >  -PAD synthesis for creating beautiful pads and other instruments
> > > > *Powerful waveform generator with up to 128 sine/non-sine harmonics
> > > > *A variety of filters including analogue modeled filters, formant filters, and state variable filters.
> > > > *Envelopes can have ADSR (or ASR, etc..) modes or can be free modes (with any shape)
> > > > *Effects for Reverb, Echo, Chorus/Flange, Phasing, Wave-shaping, Equalizing, Dynamic Filtering with
> > > >  flexible signal routing
> > > > *Instruments can be organized in kits, which allows you to make drum kits or layered instruments; this
> > > >  makes possible to use more than one instrument for a single part. It is possible to choose what items
> > > >  from the kit should be processed by the Part's effects.
> > > > *Randomness settings to create subtle differences in each sound to help create that familiar analogue warmth.
> > > > *Microtonal capabilities with any scale, up to 128 notes per octave, and key mapping
> > > > *Extensive MIDI/Audio driver support including JACK, ALSA, OSS, and PortAudio
> > > > *A built-in Virtual Keyboard which can be used even if you don't have a physical midi keyboard
> > > > *The graphical user interface can be completely disabled if the user need so
> > > > *Session Management Support via LASH/NSM
> > > > *Plugin Support via DSSI/LV2/VST
> > > > *Over 1100 high quality instruments included
> > > >
> > > > > >
> > > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > > >
> > > > > > WWW: http://zynaddsubfx.sourceforge.net
> > > > > >
> > > > > > Port below adds a nice graphical interface to the synthesizer.
> > > > > > Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
> > > > > > Although there other interfaces available like fltk and ntk, both
> > > > > > are quite cumbersome to use, and very ugly in comparison.
> > > > > >
> > > > > > Information for inst:zyn-fusion-3.0.5pre
> > > > > >
> > > > > > Comment:
> > > > > > single window & tabbed version of the ZynAddSubFX interface
> > > > > >
> > > > > > Required by:
> > > > > > zynaddsubfx-3.0.5
> > > > > >
> > > > > > Description:
> > > > > > Zyn was plagued with a difficult to use interface and unstable, unofficial
> > > > > > plugin versions. Fusion blows those issues away with a complete redesign and
> > > > > > rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
> > > > > > any platform. With total separation of the UI from the synthesis engine.
> > > > > >
> > > > > > Zyn-Fusion is enabling powerful features such as the new, officially-supported
> > > > > > VST plugin version, remote control of a headless CPU with the UI on
> > > > > > touchscreen, even multiple UI windows controlling a single sound engine. By
> > > > > > fusing 28 windows of fine grained control into one, Zyn is now controlled with
> > > > > > a single window design of tabbed views for a consistent, navigable interface.
> > > > > > You think you've heard the sounds before, but you've never had the precision
> > > > > > control of Fusion.
> > > > > >
> > > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > > >
> > > > > > WWW: https://github.com/mruby-zest/mruby-zest-build
> > > > > >
> > > > > > Both Build & Run tested on amd64
> > >
> > >
> > >
>
>
>

zyn-fusion.tar.gz (9K) Download Attachment
zynaddsubfx.tar.gz (19K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
Ping

On Thu, Mar 11, 2021 at 02:19:01PM +0000, Dimitri Karamazov wrote:

> On Thu, Mar 11, 2021 at 11:34:47AM +0000, Stuart Henderson wrote:
> > On 2021/03/10 14:04, Dimitri Karamazov wrote:
> > > On Tue, Mar 09, 2021 at 07:51:48PM +0000, Stuart Henderson wrote:
> > > > zynaddsubfx picks up bash-completion if present at build time,
> > > >
> > > > $ diff pkg/PLIST.orig pkg/PLIST
> > > > --- pkg/PLIST.orig Wed Feb 10 16:31:49 2021
> > > > +++ pkg/PLIST Tue Mar  9 19:39:30 2021
> > > > @@ -47,6 +47,9 @@ share/applications/zynaddsubfx-alsa.desktop
> > > >  share/applications/zynaddsubfx-jack-multi.desktop
> > > >  share/applications/zynaddsubfx-jack.desktop
> > > >  share/applications/zynaddsubfx-oss.desktop
> > > > +share/bash_completion/
> > > > +share/bash_completion/completions/
> > > > +share/bash_completion/completions/zynaddsubfx
> > > >  share/doc/zynaddsubfx/
> > > >  share/doc/zynaddsubfx/AUTHORS.txt
> > > >  share/doc/zynaddsubfx/COPYING
> > > >
> > > > can you force that either on or off please? either add a build dep on
> > > > shells/bash-completion or set BASHCOMP_PKG_PATH.
> > >
> > > The install script uses bash which I've added to BUILD_DEPENDS.
> >
> > I don't see it using bash anywhere?
> >
> > It only looks for the pkg-config file from shells/bash-completion,
> > installing bash won't have it create the completion files, only installing
> > bash-completion (or passing the configure arg, but it looks like the
> > directory may need to exist too, so it's less messy to just build dep
> > on bash-completion).
>
> I've added bash-completion to BUILD_DEPENDS and this patch below to remove
> the bash dependency. The script uses mkdir if the directory doesn't exist.
>
> $OpenBSD$
>
> fix bash_completion install
>
> --- cmake/BashCompletion.cmake.orig Sat Feb 23 21:13:37 2019
> +++ cmake/BashCompletion.cmake Thu Mar 11 18:06:57 2021
> @@ -71,9 +71,9 @@ ELSE()
>   SET(BASHCOMP_SCRIPT "${CMAKE_CURRENT_BINARY_DIR}/install_${SCRIPT_NAME}_completion.sh")
>  
>   FILE(WRITE ${BASHCOMP_SCRIPT} "\
> -#!${BASH}\n\
> +#!/bin/sh\n\
>  set -e\n\
> -BASHCOMP_PKG_PATH=\"${BASHCOMP_USER_PATH}\"\n\
> +BASHCOMP_PKG_PATH=\"\$DESTDIR${BASHCOMP_USER_PATH}\"\n\
>  if [ -w \"${BASHCOMP_PKG_PATH}\" ]; then\n\
>    BASHCOMP_PKG_PATH=\"${BASHCOMP_PKG_PATH}\"\n\
>  fi\n\
>
> > > > Nice work on the zyn-fusion Makefile with the distfiles. It hardcodes
> > > > gcc somewhere though (and I just noticed it forces -O3 as well),
> > >
> > > I couldn't recreate the gcc issue(after removing ports-gcc) so I've set
> > > CC and LD in MAKE_FLAGS but why will the command fail if gcc is
> > > available in the base?
> >
> > gcc is only available in base on alpha amd64 hppa sh sparc64, and it
> > should not be used by anything in base/ports on amd64 (it's only there to
> > make it easier for people to test building things with old-gcc but really
> > it causes more problems than it solves now).
>
> I've tested after removing both ports-gcc and base-gcc(actually renaming the
> binary for base-gcc) and I cannot encounter that issue, you can test it
> again now. I can think it was an issue with CC CXX and LD not being set.
>
> > > > Looks like you maybe able to steal some bits from ports/lang/mruby.
> > > > (Guessing it needs some specific version and can't just use the mruby
> > > > port directly?)
> > >
> > > In the present case the mruby interpretor is a internal part of the program
> > > and thus requires the source code to be available during the build.
> > > Developers of zyn-fusion didn't intend this program to be open-source so
> > > everything is static-linked by default the refractoring needed here is immense.
> >
> > ack. In which case try borrowing patches from the mruby port which
> > already solved these problems.
>
> I've taken the necessary patches.
>
> > > > The dependencies seem the wrong way round, shouldn't it be zyn-fusion
> > > > that depends on zynaddsubfx instead? (For discoverability I'd probably
> > > > but zyn-fusion in audio/ instead of x11/).
> > >
> > > zyn-fusion unlike other frontends cannot interact with the backend.
> > > You can check this yourself, executing zyn-fusion gives you an empty
> > > interface and this is by design. So moving zyn-fusion into audio
> > > wouldn't make sense since it is only an x11-interface(like ntk/fltk)
> > > and more like a dependency for zynaddsubfx than the other way around.
> > > It is by executing the zynaddsubfx binary that a user will actually trigger
> > > the usable interface. Ofcourse this goes contrary to how frontends are
> > > actually developed but that is what we are dealing with.
> > > So I think the categories should be kept as is.
> >
> > In that case I think there needs to be some user-facing information
> > about this, maybe a short pkg-readme, or at least in DESCR, otherwise
> > user experience for someone that has read about zyn-fusion and wants to
> > try it with "pkg_add zyn-fusion" won't be good.
>
> This is part of zyn-fusion port now.
>
> $OpenBSD: README.template,v 1.7 2019/05/09 17:45:05 ajacoutot Exp $
>
> +-------------------------------------------------------------------------------
> | Running ${PKGSTEM} on OpenBSD
> +-------------------------------------------------------------------------------
>
> Running zyn-fusion
> ==================
>
> The zyn-fusion package consist only of a x11-interface for the zynaddsubfx
> backend. To run the synthesizer install the zynaddsubfx package and execute the
> zynaddsubfx binary.
>
> > > I will be introducing MULTI_PACKAGES in zynaddsubfx for the ntk and fltk
> > > interfaces later on so distinctions in the frontend available will be more
> > > clear while installing.
> > >
> > > >
> > > > On 2021/03/07 15:03, Dimitri Karamazov wrote:
> > > > > Ping
> > > > >
> > > > > On Sat, Feb 27, 2021 at 05:32:23PM +0000, Dimitri Karamazov wrote:
> > > > > > Ping
> > > > > >
> > > > > > On Wed, Feb 17, 2021 at 05:39:57PM +0000, Dimitri Karamazov wrote:
> > > > > > > This here is a terrific synthesizer and can be put to good use
> > > > > > > with some DAW with lv2 support. Can be used with lmms if
> > > > > > > carla is ported or just wait until lv2 is supported(ongoing).
> > > > > > > https://github.com/LMMS/lmms/issues/562
> > > > > > >
> > > > > > > I've a muse(https://vstwarehouse.com/d/muse/) port with me which
> > > > > > > can run this as plugin(both vst & lv2) but it brings along with
> > > > > > > it 4-5 dependencies so might release it some other time.
> > > > > > >
> > > > > > > Information for inst:zynaddsubfx-3.0.5
> > > > > > >
> > > > > > > Comment:
> > > > > > > synth capable of making a countless number of instruments
> > > > > > >
> > > > > > > Description:
> > > > > > > ZynAddSubFX is a opensource software synthesizer capable of making
> > > > > > > a countless number of instruments, from some common heard from
> > > > > > > expensive hardware to interesting sounds that you'll boost to an
> > > > > > > amazing universe of sounds.
> > > > >
> > > > > *Polyphonic with support for legato and mono playing modes
> > > > > *Three synthesizer engines:
> > > > >  -Additive Synthesis for classic synth sounds composed of a variety of voices with powerful modulation.
> > > > >   This exposes modulators ranging from LFOs and envelopes to oscillator modulators for FM, PM, and AM.
> > > > >  -Subtractive Synthesis for creating variable bandwidth harmonics from filtered white noise
> > > > >  -PAD synthesis for creating beautiful pads and other instruments
> > > > > *Powerful waveform generator with up to 128 sine/non-sine harmonics
> > > > > *A variety of filters including analogue modeled filters, formant filters, and state variable filters.
> > > > > *Envelopes can have ADSR (or ASR, etc..) modes or can be free modes (with any shape)
> > > > > *Effects for Reverb, Echo, Chorus/Flange, Phasing, Wave-shaping, Equalizing, Dynamic Filtering with
> > > > >  flexible signal routing
> > > > > *Instruments can be organized in kits, which allows you to make drum kits or layered instruments; this
> > > > >  makes possible to use more than one instrument for a single part. It is possible to choose what items
> > > > >  from the kit should be processed by the Part's effects.
> > > > > *Randomness settings to create subtle differences in each sound to help create that familiar analogue warmth.
> > > > > *Microtonal capabilities with any scale, up to 128 notes per octave, and key mapping
> > > > > *Extensive MIDI/Audio driver support including JACK, ALSA, OSS, and PortAudio
> > > > > *A built-in Virtual Keyboard which can be used even if you don't have a physical midi keyboard
> > > > > *The graphical user interface can be completely disabled if the user need so
> > > > > *Session Management Support via LASH/NSM
> > > > > *Plugin Support via DSSI/LV2/VST
> > > > > *Over 1100 high quality instruments included
> > > > >
> > > > > > >
> > > > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > > > >
> > > > > > > WWW: http://zynaddsubfx.sourceforge.net
> > > > > > >
> > > > > > > Port below adds a nice graphical interface to the synthesizer.
> > > > > > > Looks like this:https://zynaddsubfx.sourceforge.io/zyn-fusion.html
> > > > > > > Although there other interfaces available like fltk and ntk, both
> > > > > > > are quite cumbersome to use, and very ugly in comparison.
> > > > > > >
> > > > > > > Information for inst:zyn-fusion-3.0.5pre
> > > > > > >
> > > > > > > Comment:
> > > > > > > single window & tabbed version of the ZynAddSubFX interface
> > > > > > >
> > > > > > > Required by:
> > > > > > > zynaddsubfx-3.0.5
> > > > > > >
> > > > > > > Description:
> > > > > > > Zyn was plagued with a difficult to use interface and unstable, unofficial
> > > > > > > plugin versions. Fusion blows those issues away with a complete redesign and
> > > > > > > rewrite. Powered by a new custom window toolkit: zest, Zyn is now ready for
> > > > > > > any platform. With total separation of the UI from the synthesis engine.
> > > > > > >
> > > > > > > Zyn-Fusion is enabling powerful features such as the new, officially-supported
> > > > > > > VST plugin version, remote control of a headless CPU with the UI on
> > > > > > > touchscreen, even multiple UI windows controlling a single sound engine. By
> > > > > > > fusing 28 windows of fine grained control into one, Zyn is now controlled with
> > > > > > > a single window design of tabbed views for a consistent, navigable interface.
> > > > > > > You think you've heard the sounds before, but you've never had the precision
> > > > > > > control of Fusion.
> > > > > > >
> > > > > > > Maintainer: Dimitri Karamazov <[hidden email]>
> > > > > > >
> > > > > > > WWW: https://github.com/mruby-zest/mruby-zest-build
> > > > > > >
> > > > > > > Both Build & Run tested on amd64
> > > >
> > > >
> > > >
> >
> >
> >

zyn-fusion.tar.gz (9K) Download Attachment
zynaddsubfx.tar.gz (19K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Solene Rapenne
On Thu, 18 Mar 2021 17:36:55 +0000
Dimitri Karamazov <[hidden email]>:

> Ping
>

hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
it seems mandatory to use zyn-fusion.

When I run zynaddsubfx or zyn-fusion, I see no difference, is it
normal?  Both open a X window with a keyboard at the bottom of the
window.  If both binaries could be used for the same result, I would
remove the README file and just add a RUN_DEP.

zynaddsubfx has some -O3 in the build log, this is something that must
be fixed before we can import it.

zynaddsubfx HOMEPAGE can be swiched to https

Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Stuart Henderson
On 2021/03/21 11:30, Solene Rapenne wrote:
> On Thu, 18 Mar 2021 17:36:55 +0000
> Dimitri Karamazov <[hidden email]>:
>
> > Ping
> >
>
> hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> it seems mandatory to use zyn-fusion.

The problem is that the dependency is sort-of circular. zynaddsubfx
requires zyn-fusion or another UI to be useful, and zyn-fusion requires
zynaddsubfx to be useful.

AUR deals with this by including zynaddsubfx in zyn-fusion (and having
them conflict) but that doesn't seem ideal either.

Thinking about what happens if other UIs are added though, having
zynaddsubfx depend on zyn-fusion doesn't work because the user might want
a different UI.

Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
the README to zynaddsubfx ("this package provides the backenx synthesizer,
you must also install a user interface") - or even just including it in
DESCR.

The other way is to use meta-packages but that's messier ..

> When I run zynaddsubfx or zyn-fusion, I see no difference, is it
> normal?  Both open a X window with a keyboard at the bottom of the
> window.  If both binaries could be used for the same result, I would
> remove the README file and just add a RUN_DEP.
>
> zynaddsubfx has some -O3 in the build log, this is something that must
> be fixed before we can import it.
>
> zynaddsubfx HOMEPAGE can be swiched to https
>

Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:

> On 2021/03/21 11:30, Solene Rapenne wrote:
> > On Thu, 18 Mar 2021 17:36:55 +0000
> > Dimitri Karamazov <[hidden email]>:
> >
> > > Ping
> > >
> >
> > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > it seems mandatory to use zyn-fusion.
>
> The problem is that the dependency is sort-of circular. zynaddsubfx
> requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> zynaddsubfx to be useful.
>
> AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> them conflict) but that doesn't seem ideal either.
>
> Thinking about what happens if other UIs are added though, having
> zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> a different UI.
>
> Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> the README to zynaddsubfx ("this package provides the backenx synthesizer,
> you must also install a user interface") - or even just including it in
> DESCR.
>
> The other way is to use meta-packages but that's messier ..
There is a configure option -DGuiModule in zynaddsubfx which can be set to
zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
will not work(restrict our options to zest). Also zyn-fusion has no real
dependency on zynaddsubfx it is not needed during build or runtime. It
is a hollow ui and is supposed to be so.

zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
and ntk are linked with zynaddsubfx. Only one of these frontends can be
installed at a time.

Since files created vary with the value of GuiModule, I will have to use
MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
other frontends with MULTI_PACKAGES.
>
> > When I run zynaddsubfx or zyn-fusion, I see no difference, is it
> > normal?  Both open a X window with a keyboard at the bottom of the
> > window.  If both binaries could be used for the same result, I would
> > remove the README file and just add a RUN_DEP.

The result should not be same. Check the images I've attached.
`zyn-fusion` -  image1.png

This interface has no connection with the backend and hence is utterly
useless.

`zynaddsubfx` - image2.png

Shows all intruments and knobs are connected with the backend.
Hope it is the same for you.
> >
> > zynaddsubfx has some -O3 in the build log, this is something that must
> > be fixed before we can import it.
> >
> > zynaddsubfx HOMEPAGE can be swiched to https
> >

Fixed.

image1.png (49K) Download Attachment
image2.png (92K) Download Attachment
zynaddsubfx.tar.gz (20K) Download Attachment
zyn-fusion.tar.gz (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Stuart Henderson
On 2021/03/21 16:19, Dimitri Karamazov wrote:

> On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:
> > On 2021/03/21 11:30, Solene Rapenne wrote:
> > > On Thu, 18 Mar 2021 17:36:55 +0000
> > > Dimitri Karamazov <[hidden email]>:
> > >
> > > > Ping
> > > >
> > >
> > > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > > it seems mandatory to use zyn-fusion.
> >
> > The problem is that the dependency is sort-of circular. zynaddsubfx
> > requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> > zynaddsubfx to be useful.
> >
> > AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> > them conflict) but that doesn't seem ideal either.
> >
> > Thinking about what happens if other UIs are added though, having
> > zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> > a different UI.
> >
> > Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> > the README to zynaddsubfx ("this package provides the backenx synthesizer,
> > you must also install a user interface") - or even just including it in
> > DESCR.
> >
> > The other way is to use meta-packages but that's messier ..
>
> There is a configure option -DGuiModule in zynaddsubfx which can be set to
> zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
> will not work(restrict our options to zest). Also zyn-fusion has no real
> dependency on zynaddsubfx it is not needed during build or runtime. It
> is a hollow ui and is supposed to be so.
>
> zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
> and ntk are linked with zynaddsubfx. Only one of these frontends can be
> installed at a time.
>
> Since files created vary with the value of GuiModule, I will have to use
> MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
> subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
> allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
> other frontends with MULTI_PACKAGES.
If I understand correctly this setting changes existing built files?
For example bin/zynaddsubfx (or some other file) would be present in
each build but would be different depending on the build option?
If so then that would be FLAVOR not MULTI_PACKAGES.

MULTI_PACKAGES is used when you have a core set of files that are
identical for all build options, and additional/missing files depending
on the build options. For example where you have a bunch of dlopen()'d
.so modules which are present or not depending on the build option,
but the main binary doesn't change.

> The result should not be same. Check the images I've attached.
> `zyn-fusion` -  image1.png
>
> This interface has no connection with the backend and hence is utterly
> useless.

How about the attached set of ports:

meta/zyn-fusion
audio/zynaddsubfx
x11/mruby-zest

(If you unpack in /usr/ports/mystuff you'll need to copy or symlink
meta/Makefile.inc from the main ports tree into mystuff/meta/Makefile.inc)

x11/mruby-zest is your x11/zyn-fusion port renamed, and with the binary
moved into libexec (so it's out of the normal path, which should remove
most confusion). I used just the date in the version number for this.

meta/zyn-fusion provides a "zyn-fusion" meta-package which only depends
on both zynaddsubfx+mruby-zest. It's kind-of pointless but gives something
so that people can pkg_add zyn-fusion.

audio/zynaddsubfx is patched slightly to search in libexec for zyn-fusion.
(Also fixed a 0/nullptr mismatch that is a warning in clang 10 and I guess
might possibly break in clang 11).

I also changed from SUBST_CMD to sed (using /usr/X11R6 / /usr/local in the
patch) so that if you run "make update-patches" after building it doesn't
undo the subst.

If other guis are added later then we would add FLAVORS in zynaddsubfx and
tighten/adjust the dependency in meta/zyn-fusion.

This seems a good balance of not changing too much, and reducing user
confusion (seems better to head off problems by making it so people don't
run into them if possible, rather than hope they will read pkg-readme,
some will but I know many won't and will just think it's broken when they
don't get the bank lists etc showing up..) What do you think? I'm OK with
importing like this.


zyn.tgz (29K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
On Mon, Mar 22, 2021 at 11:34:27AM +0000, Stuart Henderson wrote:

> On 2021/03/21 16:19, Dimitri Karamazov wrote:
> > On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:
> > > On 2021/03/21 11:30, Solene Rapenne wrote:
> > > > On Thu, 18 Mar 2021 17:36:55 +0000
> > > > Dimitri Karamazov <[hidden email]>:
> > > >
> > > > > Ping
> > > > >
> > > >
> > > > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > > > it seems mandatory to use zyn-fusion.
> > >
> > > The problem is that the dependency is sort-of circular. zynaddsubfx
> > > requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> > > zynaddsubfx to be useful.
> > >
> > > AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> > > them conflict) but that doesn't seem ideal either.
> > >
> > > Thinking about what happens if other UIs are added though, having
> > > zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> > > a different UI.
> > >
> > > Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> > > the README to zynaddsubfx ("this package provides the backenx synthesizer,
> > > you must also install a user interface") - or even just including it in
> > > DESCR.
> > >
> > > The other way is to use meta-packages but that's messier ..
> >
> > There is a configure option -DGuiModule in zynaddsubfx which can be set to
> > zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
> > will not work(restrict our options to zest). Also zyn-fusion has no real
> > dependency on zynaddsubfx it is not needed during build or runtime. It
> > is a hollow ui and is supposed to be so.
> >
> > zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
> > and ntk are linked with zynaddsubfx. Only one of these frontends can be
> > installed at a time.
> >
> > Since files created vary with the value of GuiModule, I will have to use
> > MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
> > subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
> > allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
> > other frontends with MULTI_PACKAGES.
>
> If I understand correctly this setting changes existing built files?
> For example bin/zynaddsubfx (or some other file) would be present in
> each build but would be different depending on the build option?
> If so then that would be FLAVOR not MULTI_PACKAGES.
>
> MULTI_PACKAGES is used when you have a core set of files that are
> identical for all build options, and additional/missing files depending
> on the build options. For example where you have a bunch of dlopen()'d
> .so modules which are present or not depending on the build option,
> but the main binary doesn't change.

So I was mistaken. It needs a mix of both, for different options some
common files are differently linked (zynaddsubfx will either call zyn-fusion
or zynaddsubfx-ext-gui) and an additional bin/zynaddsubfx-ext-gui
file is present for fltk and ntk. Not possible?

If it is not, there is no real need to fret at it, aside from the rabbit
hole of tabs the rest of the Gui's will lead you into there is nothing
interesting they offer. Only Zyn-Fusion has been good enough for them to
monetize it.

>
> > The result should not be same. Check the images I've attached.
> > `zyn-fusion` -  image1.png
> >
> > This interface has no connection with the backend and hence is utterly
> > useless.
>
> How about the attached set of ports:
>
> meta/zyn-fusion
> audio/zynaddsubfx
> x11/mruby-zest
>
> (If you unpack in /usr/ports/mystuff you'll need to copy or symlink
> meta/Makefile.inc from the main ports tree into mystuff/meta/Makefile.inc)
>
> x11/mruby-zest is your x11/zyn-fusion port renamed, and with the binary
> moved into libexec (so it's out of the normal path, which should remove
> most confusion). I used just the date in the version number for this.
>
> meta/zyn-fusion provides a "zyn-fusion" meta-package which only depends
> on both zynaddsubfx+mruby-zest. It's kind-of pointless but gives something
> so that people can pkg_add zyn-fusion.
>
> audio/zynaddsubfx is patched slightly to search in libexec for zyn-fusion.
> (Also fixed a 0/nullptr mismatch that is a warning in clang 10 and I guess
> might possibly break in clang 11).
>
> I also changed from SUBST_CMD to sed (using /usr/X11R6 / /usr/local in the
> patch) so that if you run "make update-patches" after building it doesn't
> undo the subst.
>
> If other guis are added later then we would add FLAVORS in zynaddsubfx and
> tighten/adjust the dependency in meta/zyn-fusion.
>
> This seems a good balance of not changing too much, and reducing user
> confusion (seems better to head off problems by making it so people don't
> run into them if possible, rather than hope they will read pkg-readme,
> some will but I know many won't and will just think it's broken when they
> don't get the bank lists etc showing up..) What do you think? I'm OK with
> importing like this.

I'm perfectly fine with your changes.

regards,
  Dimitri

Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Dimitri Karamazov
Ping

On Mon, Mar 22, 2021 at 04:00:36PM +0000, Dimitri Karamazov wrote:

> On Mon, Mar 22, 2021 at 11:34:27AM +0000, Stuart Henderson wrote:
> > On 2021/03/21 16:19, Dimitri Karamazov wrote:
> > > On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:
> > > > On 2021/03/21 11:30, Solene Rapenne wrote:
> > > > > On Thu, 18 Mar 2021 17:36:55 +0000
> > > > > Dimitri Karamazov <[hidden email]>:
> > > > >
> > > > > > Ping
> > > > > >
> > > > >
> > > > > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > > > > it seems mandatory to use zyn-fusion.
> > > >
> > > > The problem is that the dependency is sort-of circular. zynaddsubfx
> > > > requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> > > > zynaddsubfx to be useful.
> > > >
> > > > AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> > > > them conflict) but that doesn't seem ideal either.
> > > >
> > > > Thinking about what happens if other UIs are added though, having
> > > > zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> > > > a different UI.
> > > >
> > > > Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> > > > the README to zynaddsubfx ("this package provides the backenx synthesizer,
> > > > you must also install a user interface") - or even just including it in
> > > > DESCR.
> > > >
> > > > The other way is to use meta-packages but that's messier ..
> > >
> > > There is a configure option -DGuiModule in zynaddsubfx which can be set to
> > > zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
> > > will not work(restrict our options to zest). Also zyn-fusion has no real
> > > dependency on zynaddsubfx it is not needed during build or runtime. It
> > > is a hollow ui and is supposed to be so.
> > >
> > > zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
> > > and ntk are linked with zynaddsubfx. Only one of these frontends can be
> > > installed at a time.
> > >
> > > Since files created vary with the value of GuiModule, I will have to use
> > > MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
> > > subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
> > > allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
> > > other frontends with MULTI_PACKAGES.
> >
> > If I understand correctly this setting changes existing built files?
> > For example bin/zynaddsubfx (or some other file) would be present in
> > each build but would be different depending on the build option?
> > If so then that would be FLAVOR not MULTI_PACKAGES.
> >
> > MULTI_PACKAGES is used when you have a core set of files that are
> > identical for all build options, and additional/missing files depending
> > on the build options. For example where you have a bunch of dlopen()'d
> > .so modules which are present or not depending on the build option,
> > but the main binary doesn't change.
>
> So I was mistaken. It needs a mix of both, for different options some
> common files are differently linked (zynaddsubfx will either call zyn-fusion
> or zynaddsubfx-ext-gui) and an additional bin/zynaddsubfx-ext-gui
> file is present for fltk and ntk. Not possible?
>
> If it is not, there is no real need to fret at it, aside from the rabbit
> hole of tabs the rest of the Gui's will lead you into there is nothing
> interesting they offer. Only Zyn-Fusion has been good enough for them to
> monetize it.
> >
> > > The result should not be same. Check the images I've attached.
> > > `zyn-fusion` -  image1.png
> > >
> > > This interface has no connection with the backend and hence is utterly
> > > useless.
> >
> > How about the attached set of ports:
> >
> > meta/zyn-fusion
> > audio/zynaddsubfx
> > x11/mruby-zest
> >
> > (If you unpack in /usr/ports/mystuff you'll need to copy or symlink
> > meta/Makefile.inc from the main ports tree into mystuff/meta/Makefile.inc)
> >
> > x11/mruby-zest is your x11/zyn-fusion port renamed, and with the binary
> > moved into libexec (so it's out of the normal path, which should remove
> > most confusion). I used just the date in the version number for this.
> >
> > meta/zyn-fusion provides a "zyn-fusion" meta-package which only depends
> > on both zynaddsubfx+mruby-zest. It's kind-of pointless but gives something
> > so that people can pkg_add zyn-fusion.
> >
> > audio/zynaddsubfx is patched slightly to search in libexec for zyn-fusion.
> > (Also fixed a 0/nullptr mismatch that is a warning in clang 10 and I guess
> > might possibly break in clang 11).
> >
> > I also changed from SUBST_CMD to sed (using /usr/X11R6 / /usr/local in the
> > patch) so that if you run "make update-patches" after building it doesn't
> > undo the subst.
> >
> > If other guis are added later then we would add FLAVORS in zynaddsubfx and
> > tighten/adjust the dependency in meta/zyn-fusion.
> >
> > This seems a good balance of not changing too much, and reducing user
> > confusion (seems better to head off problems by making it so people don't
> > run into them if possible, rather than hope they will read pkg-readme,
> > some will but I know many won't and will just think it's broken when they
> > don't get the bank lists etc showing up..) What do you think? I'm OK with
> > importing like this.
>
> I'm perfectly fine with your changes.
>
> regards,
>   Dimitri

Reply | Threaded
Open this post in threaded view
|

Re: [NEW] audio/zynaddsubfx

Stuart Henderson
On 2021/03/29 16:54, Dimitri Karamazov wrote:
> Ping

I need an OK before I can commit it.

> On Mon, Mar 22, 2021 at 04:00:36PM +0000, Dimitri Karamazov wrote:
> > On Mon, Mar 22, 2021 at 11:34:27AM +0000, Stuart Henderson wrote:
> > > On 2021/03/21 16:19, Dimitri Karamazov wrote:
> > > > On Sun, Mar 21, 2021 at 11:46:48AM +0000, Stuart Henderson wrote:
> > > > > On 2021/03/21 11:30, Solene Rapenne wrote:
> > > > > > On Thu, 18 Mar 2021 17:36:55 +0000
> > > > > > Dimitri Karamazov <[hidden email]>:
> > > > > >
> > > > > > > Ping
> > > > > > >
> > > > > >
> > > > > > hello, in zyn-fusion I'd add audio/zynaddsubfx as a RUN_DEP because
> > > > > > it seems mandatory to use zyn-fusion.
> > > > >
> > > > > The problem is that the dependency is sort-of circular. zynaddsubfx
> > > > > requires zyn-fusion or another UI to be useful, and zyn-fusion requires
> > > > > zynaddsubfx to be useful.
> > > > >
> > > > > AUR deals with this by including zynaddsubfx in zyn-fusion (and having
> > > > > them conflict) but that doesn't seem ideal either.
> > > > >
> > > > > Thinking about what happens if other UIs are added though, having
> > > > > zynaddsubfx depend on zyn-fusion doesn't work because the user might want
> > > > > a different UI.
> > > > >
> > > > > Maybe the answer is to have zyn-fusion depend on zynaddsubfx and move
> > > > > the README to zynaddsubfx ("this package provides the backenx synthesizer,
> > > > > you must also install a user interface") - or even just including it in
> > > > > DESCR.
> > > > >
> > > > > The other way is to use meta-packages but that's messier ..
> > > >
> > > > There is a configure option -DGuiModule in zynaddsubfx which can be set to
> > > > zest(zyn-fusion), ntk or fltk. So making zyn-fusion depend on zynaddsubfx
> > > > will not work(restrict our options to zest). Also zyn-fusion has no real
> > > > dependency on zynaddsubfx it is not needed during build or runtime. It
> > > > is a hollow ui and is supposed to be so.
> > > >
> > > > zyn-fusion(zest) is a runtime dependency, while on the other hand fltk
> > > > and ntk are linked with zynaddsubfx. Only one of these frontends can be
> > > > installed at a time.
> > > >
> > > > Since files created vary with the value of GuiModule, I will have to use
> > > > MULTI_PACKAGES, and then set dependencies and CONFIGURE_ARGS for each
> > > > subpackage(like fltk,ntk and zyn-fusion). I see no other possibility to
> > > > allow Gui choices but to make zynaddsubfx depend on zyn-fusion, then add
> > > > other frontends with MULTI_PACKAGES.
> > >
> > > If I understand correctly this setting changes existing built files?
> > > For example bin/zynaddsubfx (or some other file) would be present in
> > > each build but would be different depending on the build option?
> > > If so then that would be FLAVOR not MULTI_PACKAGES.
> > >
> > > MULTI_PACKAGES is used when you have a core set of files that are
> > > identical for all build options, and additional/missing files depending
> > > on the build options. For example where you have a bunch of dlopen()'d
> > > .so modules which are present or not depending on the build option,
> > > but the main binary doesn't change.
> >
> > So I was mistaken. It needs a mix of both, for different options some
> > common files are differently linked (zynaddsubfx will either call zyn-fusion
> > or zynaddsubfx-ext-gui) and an additional bin/zynaddsubfx-ext-gui
> > file is present for fltk and ntk. Not possible?
> >
> > If it is not, there is no real need to fret at it, aside from the rabbit
> > hole of tabs the rest of the Gui's will lead you into there is nothing
> > interesting they offer. Only Zyn-Fusion has been good enough for them to
> > monetize it.
> > >
> > > > The result should not be same. Check the images I've attached.
> > > > `zyn-fusion` -  image1.png
> > > >
> > > > This interface has no connection with the backend and hence is utterly
> > > > useless.
> > >
> > > How about the attached set of ports:
> > >
> > > meta/zyn-fusion
> > > audio/zynaddsubfx
> > > x11/mruby-zest
> > >
> > > (If you unpack in /usr/ports/mystuff you'll need to copy or symlink
> > > meta/Makefile.inc from the main ports tree into mystuff/meta/Makefile.inc)
> > >
> > > x11/mruby-zest is your x11/zyn-fusion port renamed, and with the binary
> > > moved into libexec (so it's out of the normal path, which should remove
> > > most confusion). I used just the date in the version number for this.
> > >
> > > meta/zyn-fusion provides a "zyn-fusion" meta-package which only depends
> > > on both zynaddsubfx+mruby-zest. It's kind-of pointless but gives something
> > > so that people can pkg_add zyn-fusion.
> > >
> > > audio/zynaddsubfx is patched slightly to search in libexec for zyn-fusion.
> > > (Also fixed a 0/nullptr mismatch that is a warning in clang 10 and I guess
> > > might possibly break in clang 11).
> > >
> > > I also changed from SUBST_CMD to sed (using /usr/X11R6 / /usr/local in the
> > > patch) so that if you run "make update-patches" after building it doesn't
> > > undo the subst.
> > >
> > > If other guis are added later then we would add FLAVORS in zynaddsubfx and
> > > tighten/adjust the dependency in meta/zyn-fusion.
> > >
> > > This seems a good balance of not changing too much, and reducing user
> > > confusion (seems better to head off problems by making it so people don't
> > > run into them if possible, rather than hope they will read pkg-readme,
> > > some will but I know many won't and will just think it's broken when they
> > > don't get the bank lists etc showing up..) What do you think? I'm OK with
> > > importing like this.
> >
> > I'm perfectly fine with your changes.
> >
> > regards,
> >   Dimitri