Yoshimi - testers wanted

[folderol]

Think I've got it, and I can't see a way out
Some time back we changed to a minimum of C++14 and your gcc version is (unless I'm mistaken) C++11.
We are using a type of pointer that only came in with 14 (for memory safety), and we're using it in so many places now that the build would be bound to fail somewhere.

[folderol]

Just had a thought, clang is usually ahead of gcc, so if that is available you might do better with it. Yoshimi's CMakeLists.txt file has an option to compile with clang round about line 30.

[bluebell]

Just had a thought, clang is usually ahead of gcc, so if that is available you might do better with it. Yoshimi's CMakeLists.txt file has an option to compile with clang round about line 30.

I am a bit conservative. I upgrade when buying new computers. The price I have to pay is that I can build less and less updated software as time goes on.

It began with Carla, Guitarix, DISTRHO-plugins, Dragonfly reverb and now Yoshimi. Since the versions that could be built on my system run fine I can take a break.

Or I feel like upgrading some day

[bluebell]

I found a solution for me: installing gcc-7 on my Xubuntu 16:

Code: Select all

add-apt-repository ppa:ubuntu-toolchain-r/test
apt-get update

apt-get install gcc-7
apt-get install g++-7

update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-7 7
update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-7 7

Now the most recent Yoshimi from git builds an runs on my system, @folderol.

[folderol]

Great!
I expect you'll notice {cough} one or two {cough} changes

[folderol]

... and there's more
Theme entries have been expanded and put into rational groups (along with a few 'spares').
The order has obviously changed, but won't do so again. The descriptions have also been improved.

[bluebell]

... and there's more
Theme entries have been expanded and put into rational groups (along with a few 'spares').
The order has obviously changed, but won't do so again. The descriptions have also been improved.

If there was a button "Export Theme" it would be made very easy to create a theme based on an existing theme.

[folderol]

Good point! Should be reasonably easy to do.

[folderol]

As I said
So... it's in the latest build, and the User Guide within Yoshimi has been updated, along with a lot of other bits (although it lies about which version it is for)

[folderol]

We now need testers for the current build - identified as Yoshimi V 2.3.0 rc3 - and hopefully the last one before full release.

Envelopes, Filters, LFOs and Resonance all have significant controls converted to a high resolution form. Other sections will be upgraded later.

Knobs and Sliders all show when not at their default - pointer/peg turns red. This should also be correct when loading parts/patchsets/states - even older ones!

Related to this, there is now a pseudo-default for formant filter frequency.
When first created this has always been a random value for each formant. It is now also stored locally (and when the filter is saved), so you can get back to that value if you want to. It is only changed on resets or if you switch the filter to a different type, then back again (as that would be a completely new filter). Obviously the saved state only applies to files saved with V 2.3.0 or later.

Theme work is complete and the theme files self-documenting - including being able to optionally add a colour tint to the grey scale.

Built-in HTML User Guide is fully updated (and Advanced reference Manual should be complete soon).

No electrons were harmed by this work (although some were given a severe talking to)

[folderol]

Just want to add that if anyone has developed a theme they would like included in the V2.3.0 release I need it by mid morning tomorrow (UK time).

As these are plain text, you could probably just paste them into a priv. message.

[j_e_f_f_g]

Just a nitpick:

form of census.

You mean "concensus". "Census" is a count of people. "Concensus" is a majority of agreement among people.

[bluebell]

Theme work is complete and the theme files self-documenting - including being able to optionally add a colour tint to the grey scale.

Woo-hoo, themes can be exported now Great.

[Largos]

Just want to add that if anyone has developed a theme they would like included in the V2.3.0 release I need it by mid morning tomorrow (UK time).

As these are plain text, you could probably just paste them into a priv. message.

I attached a dark theme I made but it has a few problems for dark themes that I couldn't work out how to fix.

1: The numbers for inactive and unselected voice tabs in addsynth are unreadable
2 The slider has no colourable border which makes it blend into the background (same as mentioned before)
3: The Edit button to open envelope and formant windows doesn't seem to have it's own colour. So it doesn't really look like a button.
4: Drop down menu text highlights are different colours depending on where you are, could also do with their own colour setting.

[folderol]

Just want to add that if anyone has developed a theme they would like included in the V2.3.0 release I need it by mid morning tomorrow (UK time).

As these are plain text, you could probably just paste them into a priv. message.

I attached a dark theme I made but it has a few problems for dark themes that I couldn't work out how to fix.

1: The numbers for inactive and unselected voice tabs in addsynth are unreadable
2 The slider has no colourable border which makes it blend into the background (same as mentioned before)
3: The Edit button to open envelope and formant windows doesn't seem to have it's own colour. So it doesn't really look like a button.
4: Drop down menu text highlights are different colours depending on where you are, could also do with their own colour setting.

Thanks for this. You raise some good points.
1) FLTK is playing games with the colours here. I don't (yet) know what we can do about it. Might need to revise the way these tabs are made.
2) FLTK uses the grey scale for generating these. For dark themes the only way round it would be for us to develop our own button border styles
3) These should both be the 'Inverse Link' buttons. Too late for this release but I'll see what's going on here.
4) FLTK interfering again! I think we could get round it but would need a pair of colours - possibly 4 of them

Would you like this included anyway, or would you suggest holding back?