My Components are gone help
-
i am having this problem just now with 2.1.0 the thing is i created the project in the same version = 2.1.0 the plugin
it's almost like it can't remeber the custom named components for example a ScriptButton renamed to just "button".
this seem to still be a problem any solution. Opening recent archives return the same problem -
@ospfeigrp Did you save your project as XML?
-
@d-healey yes i did using the old one not the one that says "not working"
-
@ospfeigrp Take your UI data xml and run it through an xml validator, you can also do the same with the project xml.
I use this one:
https://www.xmlvalidation.com/Here's a video demo (don't forget to subscribe ;) )
https://www.youtube.com/watch?v=WLiVCi4vMZY -
@d-healey no errors found ..hmm
this is obviously going to happen because it has no reference to the renaming in xml,if i leave the components as the default generated names it's saves fine. -
@ospfeigrp Which branch of HISE did you build?
-
@d-healey scriptnode this is the plugin version and have removed all older builds, it does actually have the naming convention in the ui xml and that seems to fail with errors
<Component type="ScriptButton" id="presetsbtn" x="889" y="18" width="30" height="30" filmstripImage="{PROJECT_FOLDER}presetsbtn.png" ="Enabled"/>
-
Are you building an FX plugin?
-
@d-healey no it's just the drum vsti i was working on. when i compiled HISE i left everything default
-
@ospfeigrp Use the standalone version of HISE.
-
@d-healey that will only give me 1 stereo channel out as far as i know, i need 16 stereo out. Thanks for all help i'll try setting up another project in the plugin version and see if i can reproduce it.
-
@ospfeigrp You can build everything in the standalone version, then do final parts that require more outputs in the plugin version.
-
@d-healey i actually know what went on here - i saved the .xml one folder up from the "XmlPresetBackups" i guess the same would happen in the standalone version. It's user error on my part, thanks.
-
@ospfeigrp Yep that'll be the cause.
-
@d-healey if you put both the ui folder and main xml back into the correct "XmlPresetBackups" it works again fine.