How do I get rid of the error. while booting up my project? I do not have Halion SE installed.
TIA
AlanRussell
Hi,
Find the track. Click on the HALion Sonic Interment name and select No Instrument (or select the wanted instrument from the list).
Find it and delete it in the project. If it’s not loaded on a track, check the instrument rack.
I’ve looked everywhere and I can’t get rid of it. Maybe if I reinstall Halion SE I could then get rid of it
Is there a chance it is because of a Preference setting?
i.e. if HALion Sonic multi-timbral is selected, while HALion Sonic is not installed, it may throw the error
A very interesting observation and I will definitely check it out when I open up my recording studio tomorrow morning thanks a lot for sharing
1 Like
I only have instrumental track chosen
Can you share the cpr…you could save a version and delete all events.
My Dell 8940 Tower is practically Maxed out there’s no problem with my CPR I’m going to take the temperature inside the case and maybe leave one of the covers off. Clearly
OK…but not sure what that has to do with sharing the cpr (the cubase project file) so someone else can try to locate the plugin for you.
Open the project, find the track using Halion, delete the Halion instance, re-save the project.
That’s weird…I don’t get the Halion Sonic SE missing message which suggests something is referencing it that is not saved at project level. Obviously I don’t then find HSSE anywhere in that project either.
I just can’t think what that could be…control room is global but can’t load instruments, not sure of any other global thing that would be referencing a vsti.
Listen thanks for your help it’s not affecting my project it’s only cosmetic and I will move on from here focusing on my clients. Nice to meet you
Hi,
Do you have an Instrument preset or a MIDI loop selected in the MediaBay by any chance? Maybe, once you are losing the project, the MediaBay item tried to load the HALion Sonic to be able to play the preview back.
First I’ll have to unhide it then I’ll check out your suggestion
Fortunately the error never came back