Did anyone get synth1 with yabridge working on MusE?
Moderators: MattKingUSA, khz, spamatica
-
- Established Member
- Posts: 57
- Joined: Tue May 04, 2021 11:28 am
- Has thanked: 4 times
- Been thanked: 31 times
Did anyone get synth1 with yabridge working on MusE?
Hey,
I am trying to get https://www.kvraudio.com/product/synth1 ... chiro-toda working with Yabridge, but no luck so far. MusE cannot recognise the plugin. Did anyone get it working?
Cheers,
Castle
I am trying to get https://www.kvraudio.com/product/synth1 ... chiro-toda working with Yabridge, but no luck so far. MusE cannot recognise the plugin. Did anyone get it working?
Cheers,
Castle
-
- Established Member
- Posts: 219
- Joined: Mon Mar 01, 2021 10:56 pm
- Has thanked: 51 times
- Been thanked: 92 times
- Contact:
Re: Did anyone get synth1 with yabridge working on MusE?
(continuing from the Discord to make this more confusing)
You did not get any warnings when you ran `yabridgectl sync`, right? And you're still 100% sure that you added `~/.wine/drive_c/Program Files/Steinberg/VstPlugins/` to MusE's VST2 search path, checked the rescan on next start checkbox, and restarted MusE? And your MusE prints `Init native VST plugins...` during startup? MusE seems to hide all output during the plugin scan which makes things a bit more complicated than they'd need to be.
You did not get any warnings when you ran `yabridgectl sync`, right? And you're still 100% sure that you added `~/.wine/drive_c/Program Files/Steinberg/VstPlugins/` to MusE's VST2 search path, checked the rescan on next start checkbox, and restarted MusE? And your MusE prints `Init native VST plugins...` during startup? MusE seems to hide all output during the plugin scan which makes things a bit more complicated than they'd need to be.
-
- Established Member
- Posts: 582
- Joined: Mon Feb 08, 2010 10:38 am
- Has thanked: 86 times
- Been thanked: 101 times
Re: Did anyone get synth1 with yabridge working on MusE?
Hi,
I've been meaning to give yabridge a serious run. It looks to be making good progress!
This far I've been sort of blocked by wrong wine version so it's been too much work getting going. I'll get there...
Anyway, I'm not sure what the problem is here but regarding plugin scanning I just wanted to mention that this can be done separately, in case it gives any insight.
Here's an example I just did:
I've been meaning to give yabridge a serious run. It looks to be making good progress!
This far I've been sort of blocked by wrong wine version so it's been too much work getting going. I'll get there...
Anyway, I'm not sure what the problem is here but regarding plugin scanning I just wanted to mention that this can be done separately, in case it gives any insight.
Here's an example I just did:
Code: Select all
ddskrjo @ ~ $ touch test.output
ddskrjo @ ~ $ muse_plugin_scan -f /usr/lib/vst/Dexed.so -o test.output
ddskrjo @ ~ $ cat test.output
<?xml version="1.0"?>
<muse version="3.3">
<plugin file="/usr/lib/vst/Dexed.so" label="Dexed">
<filetime>1615841803000</filetime>
<type>16</type>
<class>3</class>
<uniqueID>1147500644</uniqueID>
<name>Dexed</name>
<description>Dexed</description>
<version>0.0.100</version>
<maker>Digital Suburban</maker>
<apiVersionMajor>2400</apiVersionMajor>
<pluginVersionMinor>100</pluginVersionMinor>
<pluginFlags>3</pluginFlags>
<portCount>156</portCount>
<outports>1</outports>
<ctlInports>155</ctlInports>
<requiredFeatures>4</requiredFeatures>
<vstPluginFlags>56</vstPluginFlags>
</plugin>
</muse>
MusE DAW
-
- Established Member
- Posts: 582
- Joined: Mon Feb 08, 2010 10:38 am
- Has thanked: 86 times
- Been thanked: 101 times
Re: Did anyone get synth1 with yabridge working on MusE?
No time like the present...
Not on my studio computer and it turns out I already were half way to getting it up and running on this one.
I got synth1 working with wine-staging, the most recent yabridge and a recent muse version.
I was first tripped up by already having .wine created with an older wine version. Wine did not complain, just updated the prefix, but the result did not work. I got a long weird message from 'yabridgectl sync' that the wine version <blank> was not supported. The message scrolled from the history so I sadly can't show it.
As I didn't have anything in the prefix I wanted to save I simply deleted it. Running the sync again caused wine to recreate it.
The output from muse_plugin_scan is as follows:
I started MusE and opened the synth there and it makes sound anyway.
Not on my studio computer and it turns out I already were half way to getting it up and running on this one.
I got synth1 working with wine-staging, the most recent yabridge and a recent muse version.
I was first tripped up by already having .wine created with an older wine version. Wine did not complain, just updated the prefix, but the result did not work. I got a long weird message from 'yabridgectl sync' that the wine version <blank> was not supported. The message scrolled from the history so I sadly can't show it.
As I didn't have anything in the prefix I wanted to save I simply deleted it. Running the sync again caused wine to recreate it.
Code: Select all
ddskrjo @ ~/.vst/Synth1 $ ~/.local/share/yabridge/yabridgectl list
/home/ddskrjo/.vst/Synth1
Code: Select all
ddskrjo @ ~/.vst/Synth1 $ ~/muse_debug/bin/muse_plugin_scan -f $PWD/Synth1\ VST.so -o out.txt
<removed a lot of log data that yabridge outputs>
ddskrjo @ ~/.vst/Synth1 $ cat out.txt
<?xml version="1.0"?>
<muse version="3.3">
<plugin file="/home/ddskrjo/.vst/Synth1/Synth1 VST.so" label="Synth1 VSTi">
<filetime>1623516928910</filetime>
<type>16</type>
<class>3</class>
<uniqueID>1395742323</uniqueID>
<name>Synth1 VSTi</name>
<description>Synth1 Soft Synth</description>
<version>0.0.1</version>
<maker>Daichi</maker>
<apiVersionMajor>2400</apiVersionMajor>
<pluginVersionMinor>1</pluginVersionMinor>
<pluginFlags>3</pluginFlags>
<portCount>257</portCount>
<outports>2</outports>
<ctlInports>255</ctlInports>
<requiredFeatures>4</requiredFeatures>
<vstPluginFlags>24</vstPluginFlags>
</plugin>
</muse>
MusE DAW
-
- Established Member
- Posts: 219
- Joined: Mon Mar 01, 2021 10:56 pm
- Has thanked: 51 times
- Been thanked: 92 times
- Contact:
Re: Did anyone get synth1 with yabridge working on MusE?
What likely happened was that your old default Wine prefix at ~/.wine was somehow created with WINEARCH=win32 set, so it would only be able to run 32-bit applications. As part of yabridgectl's post-setup checks it tries to run the 64-bit yabridge-host.exe application, so if your default Wine prefix doesn't support that Wine will error out with an `0024:err:process:exec_process` error instead.spamatica wrote: ↑Sat Jun 12, 2021 5:17 pm I was first tripped up by already having .wine created with an older wine version. Wine did not complain, just updated the prefix, but the result did not work. I got a long weird message from 'yabridgectl sync' that the wine version <blank> was not supported. The message scrolled from the history so I sadly can't show it.
-
- Established Member
- Posts: 57
- Joined: Tue May 04, 2021 11:28 am
- Has thanked: 4 times
- Been thanked: 31 times
Re: Did anyone get synth1 with yabridge working on MusE?
I got this error:
muse_plugin_scan -f .vst/Synth1/Synth1\ VST64.so -o test.output
20:23:15 Error during initialization:
20:23:15 locale::facet::_S_create_c_locale name not valid
ERROR: Failed to instantiate plugin in VST library ".vst/Synth1/Synth1 VST64.so"
muse_plugin_scan: writeLinuxVstInfo(.vst/Synth1/Synth1 VST64.so) failed
At least I know now that the problem is not yabridge or Synth1... it's my system.
muse_plugin_scan -f .vst/Synth1/Synth1\ VST64.so -o test.output
20:23:15 Error during initialization:
20:23:15 locale::facet::_S_create_c_locale name not valid
ERROR: Failed to instantiate plugin in VST library ".vst/Synth1/Synth1 VST64.so"
muse_plugin_scan: writeLinuxVstInfo(.vst/Synth1/Synth1 VST64.so) failed
At least I know now that the problem is not yabridge or Synth1... it's my system.
-
- Established Member
- Posts: 219
- Joined: Mon Mar 01, 2021 10:56 pm
- Has thanked: 51 times
- Been thanked: 92 times
- Contact:
Re: Did anyone get synth1 with yabridge working on MusE?
You have one of the LC_* environment variables set to a locale that either doesn't exist or that is not enabled.oldcastle wrote: ↑Sat Jun 12, 2021 6:24 pm I got this error:
muse_plugin_scan -f .vst/Synth1/Synth1\ VST64.so -o test.output
20:23:15 Error during initialization:
20:23:15 locale::facet::_S_create_c_locale name not valid
ERROR: Failed to instantiate plugin in VST library ".vst/Synth1/Synth1 VST64.so"
muse_plugin_scan: writeLinuxVstInfo(.vst/Synth1/Synth1 VST64.so) failed
At least I know now that the problem is not yabridge or Synth1... it's my system.
-
- Established Member
- Posts: 582
- Joined: Mon Feb 08, 2010 10:38 am
- Has thanked: 86 times
- Been thanked: 101 times
Re: Did anyone get synth1 with yabridge working on MusE?
Can't find the origin of the error
As robbert-vdh says, it should be possible fix this in the environment settings on your computer.
but it looks very likely it is wine that produces it and thus fails the instantiation.20:23:15 locale::facet::_S_create_c_locale name not valid
As robbert-vdh says, it should be possible fix this in the environment settings on your computer.
MusE DAW
-
- Established Member
- Posts: 219
- Joined: Mon Mar 01, 2021 10:56 pm
- Has thanked: 51 times
- Been thanked: 92 times
- Contact:
Re: Did anyone get synth1 with yabridge working on MusE?
It's libstdc++. The iostream API uses the current locale for formatting numbers, so when your locale is messed up then you won't be able to use any application that tries to format things based on your locale (or they might fall back to LC_ALL=C, but in GCC's C++ implementation it's a hard error).spamatica wrote: ↑Sat Jun 12, 2021 10:27 pm Can't find the origin of the errorbut it looks very likely it is wine that produces it and thus fails the instantiation.20:23:15 locale::facet::_S_create_c_locale name not valid
As robbert-vdh says, it should be possible fix this in the environment settings on your computer.
-
- Established Member
- Posts: 57
- Joined: Tue May 04, 2021 11:28 am
- Has thanked: 4 times
- Been thanked: 31 times
Re: Did anyone get synth1 with yabridge working on MusE?
You are 100% right. My locale is totally messed up. I'm using (or trying to) different locales at the same time. I use English for display language and numbers, currency and time formatting in another language. I'm mostly wondering about: and
Are those the default?
Code: Select all
LC_COLLATE=C
Code: Select all
LC_ALL=
-
- Established Member
- Posts: 219
- Joined: Mon Mar 01, 2021 10:56 pm
- Has thanked: 51 times
- Been thanked: 92 times
- Contact:
Re: Did anyone get synth1 with yabridge working on MusE?
LC_ALL should be empty by default, since that's really an override for everything. I don't have LC_COLLATE set at all (KDE Plasma manages the LC_ and LANG environment variables for me), but LC_COLLATE=C should be safe although you'd probably want all of those locale environment variables set to an actual locale for consistency's sake. And of course make sure that locale is enabled and generated.oldcastle wrote: ↑Sun Jun 13, 2021 8:36 am You are 100% right. My locale is totally messed up. I'm using (or trying to) different locales at the same time. I use English for display language and numbers, currency and time formatting in another language. I'm mostly wondering about:andCode: Select all
LC_COLLATE=C
Are those the default?Code: Select all
LC_ALL=