Zynth club. .. There's just one rule in Zynth club

Hope you had an informative and joyful evening. I literally kept my evening free for this event and came home earlier, but then fell asleep on tje couch until midnight. Douh!

2 Likes

Sorry I couldn’t make it but I’m busy on Wednesdays.

Thanks for being part of the meet :wink:

Forgive me to ask;

What does this mean? I tried to click flag, but that seemed not to be the thing to do?

Inform, just bung a message to riban.

Sorry - I just meant that, if someone decides to create a video, let the rest of the community know so that they can avoid doing the same thing. Just post a message in the forum saying, “I am doing this…”.

2 Likes

It feels like a long enough time had elf elapsed… How about Wednesday 27th May?

Seems ok.

I’m probably in. In any case it’s the most likely date I could join.

Where do you do these, and what is the normal time of day/timezone that you aim for?

We agree a time and date ad hoc, but it is usually a weekday at 19:00 UTC. DM me for details on joining.

Wednesday suits me. Look forward to meeting some new peoples.

I should be there about 20:30 bst.

Okay, let’s meet at 19:00 UTC, Wednesday 27th May 2026 (or “today” as some of us may say). DM me for joining details if you need them. Chat later!

And what, pray, is wrong with the old people..?

I think you know the answer to that… :blush:

In an unusually zynthian-focused meeting, we talked long into the night and through to the early hours of the following morning… unless you were in Australia or America. I can barely remember what was said, depsite being the one who said most of it but some subjects were:

  • Preview of new ZS3 handling of MIDI learned CC bindings.
  • Demonstration of ZynVoice, text-to-speech assistive technology.
  • How helpful is the built-in help? We noticed that some of the more complex views like pattern editor were yet to be documented.
  • How to document the variation of control within each view?
  • Should the new Collections feature be more curated to ensure structured presentation of SFZ, e.g. orcestral instruments appear in instrument categories?
  • You can move chains left/right and stick them to the right side.
  • Many orchestral sample packs (SFZ) produce audio output much quieter than many synths. There is insufficient gain in the chain to equalize these so additional gain processors must be manually added. A prolonged discussion on how to automatically resolve this ensued, describing low level detail of how the real-time audio is processed. The answer: you can and should manually resolve this with gain processors but there could be some automated assistance feature to add such processors. That needs to be the subject of a change request with associated (even longer) discussion and design.
  • Fun is being had with Mellotron collection.
  • A tutorial on RipplerX dual resonator synth was given. You hit stuff stuff that makes noise that can be tuned and filtered, etc. Man-hits-thing suits some of us!
  • Lasers are being used to make purposefully silenced bells ring in their agitators’ ears. Some asked, “how?”, whilst others asked, “why?”!
  • More love was shown for @ronsum’s filter GUI widget. Is it log/lin? That depends on the control range. Could it benefit from value labels? Yes and no… it may look better on those processors for which this was implemented but would then be demaned for all processors!
  • Zynthian and its user interface seems to be increasing in complexity, providing challenges to new and existing users. Design does attempt to mitigate this by constraining options to supported workflows, improving documentation, etc.
  • Could the function buttons report their state (via colour) when used as toggle controls? Tricky!
  • Love was shown for the effects send and return via mixbus chains.
  • Further appreciation shown for the ability to export a chain as a snapshot and import / merge snapshots into existing state.

There was much more said but if you don’t attend then you miss out. (Some may say attendance is itself a penance!)

3 Likes

Weve all been VERY naughty…

Eat your soup…

Good question and also in my mind.
The pros:

  • Consistent and unified organization of soundfonts

The cons:

  • Difficult to know what is installed with each package
  • Difficult to have a coherent and unified organization structure that covers everything.
  • Some users can be used to specific organization inside its favorite collection and changing could be annoying. Not to talk of snapshot compatibility.

I vote for leaving things like they are:

  • It’s easier to manage, so less management burden.
  • It’s easier to keep synced with original sources
  • Each “collection” has freedom to organize internally, what could be interesting in some cases. Indeed, it could be part of the “charm” of a collection. I mean, VPO3 or SSO4 have different organization and this is part of the character of the collection too.
  • I like to have an easy way of finding what i just installed.

Of course, the discussion is open.

Regards,

3 Likes