Replies: 1 comment
-
|
That's odd. Haven't seen one like this in a long time. Thanks for the report. Heads up, I copied the issue over to GitLab: https://gitlab.com/kushview/element/-/issues/566 .... In the process of moving technical happenings there and leaving github for the social aspect! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Howdy!
So this is weird, I installed Element 0.46 to test out in Cubase. It loaded fine and everything and so I made a test patch and saved it...
Then when I re-opened it, it opened the session but the connections between nodes were not recalled, which meant I'd need to manually redo all nodal connections, tiresome and clearly a bug. I also recreated this in the standalone windows version.
So, in an effort to troubleshoot, I saw that you put nightly builds of the latest Element up, so then I went and installed the latest version of Element (v0.47.0_r479). Low and behold, it opens (in the standalone windows app) and it shows all nodes connect correctly when recalling the session I had created (yay!).
However, when I re-opened Cubase, it then re-scanned the vst3 plugins and somehow removed Element from the VST3 FX category and now it shows up in Cubase as a VST3 Instrument.
For some strange reason now it only recognizes both versions of Element as instruments in Cubase (or at least that's how they show up in VST Plug-in Manager in Cubase).
I have an instance of Element open in Cubase in this test project, so I can still copy and paste it as an effect plugin to other channels, and it shows as an insert called 'Element', but I can't find it anywhere in my vst3 folder nor does it show up in scanning for new added VST3s.
Beta Was this translation helpful? Give feedback.
All reactions