Ditto. There is a product/project known as KV Element that attempts something along those lines, meaning it runs both as a (very primitive) live host, and as a plugin similar to Meta, but its pretty rough around the edges and has gone open source, so not much in support available. That said I’ve experimented with using it to rack up a guitar FX chain for portability and it did work pretty well for that. Its a Juce project so its similar to Meta in how plugins route and midi connectivity, but limited to only eight parms…
1 Like
I’ll take a look when I get chance (hopefully this week some time). In the meantime…
I think the problem here is that cubase/reaper aren’t using the Windows 10+ per-monitor resolution support that Cantabile is using. Cantabile does this to allow Cantabile’s UI to be hidpi and plugins to be mixed/scaled up.
Does the plugin appear correctly when hidpi and/or upscaling is disabled?
Brad
Hi Adrian,
So I read your post on this topic, discovering a fun fact. In 1979 or 1980 I went in Milan during the music fair named SIM. At the time I was a kid, say 18/19, working as demonstrator for Mr. Monzino (now Yamaha Italy) in my area.
I met David Bristow and spent a whole afternoon talking of the CS-80. Also I met Mr. Gigi Tonet (I’m not sure if the name’s correct) and played with the Roland System-700, System 100M and the MC-8 sequencer. He tried to sell me his personal 700, unfortunately it was out of my budget. And, needless to say, I played a lot with the Mini, Micro and Multi Moog and the Taurus 2 pedalboard.
I also should have been in charge of the Lowrey organs, but I totally forget them. 
I still have the “operator” badge in a closet. What a days!
2 Likes
Wow! SIM - that was it! I think I may have done a couple of those fairs - Who knows? Maybe we met! I do remember there was a guy there into the MC8 and System 700, but thinking back, he definitely fell into the trap of programming using Roland’s clunky “tap each command in from a prepared data sheet”. Horrible - took hours. Of course, what they failed to focus on in their manual was that the MC8 could actually record in real time… a WAY faster approach, notwithstanding the fact that it had no quantizing. But…! You could quickly review the recorded values and manually correct them to the nearest ‘sensible’ number. The other drawback was that realtime record killed the output of any other channels. This was corrected in the MC4, a far superior CV/Gate sequencer, which I loved until MIDI came along and killed it. I hung on to the bitter end:-)
I can still remember the very elegant Antonio Monzino. Quite an enterprise there!
There was a certain ‘Maestro’ whose presence on the stand always caused a stir. Not sure about Gigi.
Now you mention it, Lowrey! Norlin used to bring in wonderful organist by the name of Harry Stoneham who was well known as the band leader on the famous ‘Parkinson’ talk show in the UK.
3 Likes
A new version of the script producing pseudo poly-AT from channel pressure is available here:
Gabriel
What’s happening using GX-80 (latest 1.0.9) on Cantabile (4059).
The steps to reproduce:
- Open Cantabile.
- Load GX-80 VST2.
- Play some chords.
- Save song or just exit without saving.
- Cantabile hangs.
Tried on my DAW, works fine.
Seems like Cantabile is unable to access its log.txt file.
Log and dump files already sent to Brad.
Anyone with similar problems?
Paolo
Is VST2 x32 or x64? Same as OS (x32 or x64) or using a wrapper around x32 for Win64?
Edit: Cherry Audio says x64 required, so my question is answered.
Yup, none of Cherry’s VST are 32bit
Just tried it with VST3 and no problems. Don’t have the VST2 installed to try it that way.
This was a good point, but no luck. With the VST3 the same Cantabile hang happens 
Working fine here. I even shut it while the chord was still playing.
First time I installed GX-80 demo, it ran for three weeks without any issue. Then I just updated the PC BIOS, right now this issue only appears loading the GX-80, all my other VSTs, programs and DAWs (the whole PC) are running smoothly.
Hi @cpaolo,
I just tried this here and it works fine for me as well. Seems like there’s something about your system it doesn’t like. Where did you send the logs?
Brad
1 Like
I’d try “Reset PC keeping personal data and programs.” This saved me other times when I couldn’t find any fixes.
I sent the log to your email at Jan, 1 - 11:55PM (Jan, 2 - 9:55AM your time).
Paolo
If anyone has the same problem, I fixed it this way:
- Uninstall all Cherry’ VST.
- Registry clean, deleting every “Cherry Audio” entry.
- Reinstall the plugins.
Careful to not delete “Cherry” entries, the PC keyboards manufacturer!
3 Likes
@cdv_gabriel One thing with their synths like Sines and GX-80… a lot of the patches use the Galactic reverb and that adds to the CPU hit. Also, some had a long release time…if you’re playing chords the long release can mean two or three times as many notes being held. Making a few edits can help.
1 Like
That’s certainly true, @FawltyTenor. Thanks for the tip.
OTOH, shorting the release time did not make much of a difference, when I tried in Sines.
Gabriel
1 Like
I’ve turned of cherrys reverb in everything of theirs I have, especially gx80.
Try some other reverb like voxengo’s old school verb, or valhalla supermassive (delays sound like huge reverb), either of these is a lot less hungry on CPU. Or anything else which is algorithmic reverb.
4 Likes
Absolutely,
Valhalla is wonderful on the GX80.
4 Likes