Please download the Halion Sonic SE Installer and confirm this strange bug...

https://www.steinberg.net/en/landing_pages/halion_sonic_se_3/halion_sonic_se_free.html

Steps.....

1) Make an instance in VE PRO but do not connect to Cubase 9.5 or 10 on a PC.

2) Load 16 instances of HALION SONIC SE

3) Load VE PRO inside of Cubase and connect decoupled.

Results....  On first attempt to connect it can take around 30 seconds to connect.  Once it connects the first time you can disconnect in less than 2 seconds and you can then re-connect as many times as you want but now it re-connects in less than 2 seconds.

Problem...the first time it tries to connect it takes a very very long time.  

when you have a problem you need to debug the problem asking questions

The main problems with VSL are due to disk I/O, not enought memory or cpu too slow

If you do not want to answer, that is your problem

Bye

So I have been updating my template a bit today and re-tested the HALion Sonic SE FREE problem and to my surprise it seems ok today.....honestly not sure what changed....possibly a Windows update but I don't think so.....

I wish I had more information why after months of trouble it seems fine now.  Keep you posted if the trouble comes back.

Thanks

Originally Posted by: Paul

HI, 

Thanks for the update, that's good to hear. 

Best, 
Paul

So sorry Paul....don't know what I was thinking when I thought everything was ok....it is far from it.  By mistake I retested with only 1 instance of HALION SONIC SE in VE pro instead of 16 instances.  So with 16 instances it is still very bad in VE PRO 16078....I tried the latest version 17226 and everything loaded longer so I am back to 16078.

My template has close to 100 instances of HALION SONIC SE and it takes many minutes to connect to these instruments from Cubase the first time and eberything is decoupled and preserved.  If I close the sequence in Cubase and reload and connect to the same project it is super fast like it should be the first time it connects.  This is a BIG problem and I can't explain why after the first connection all is normal.

What makes this such a big problem for me is that with every TV cue I write I save the VE PRO server project as the cue, i.e., 1M1, 1M2, etc....  So if I have to reopen a cue for some reason I have to load it up before Cubase and then we are back to square 1 where Cubase will be connecting again to a new cue for the first time.  In my case it probably takes about 3 minutes longer to load it the first time than if I close Cubase and connect to it a second time.

Please let me know if you need any more info but I think I have explained what is going on over here.

Thanks....

Originally Posted by: Paul

Hi, 

How many audio Inputs / outputs do you have open in VE PRO?

Any way to reduce those?

Best, 
Paul

Every instance of Halion Sonic SE has just 1 sound and 1 stereo output each.  I split it out this way so I can manage the CPU better by being able to bypass each instance individually. 

I may be forced to go back to using it as a multi-timbral instance with 16 sounds in one to get around this for now but that will be at the expense of not being able to manage the CPU like I can now.....so I rather not do that.

Thanks for th quick reply.

Originally Posted by: Paul

Hi, 

What do my colleagues at Steinberg say regarding this behaviour? Of course the support team at Steinberg has access to VE PRO (and they can also connect with us anytime). 

Would alsoi be interesting to know if these troubles also occur with Vienna Instruments or Kontakt on your system.

TBH, we don't seem to have many Halion sonic users here, or this sample player is very uncomplicated. 

Best, 
Paul

As stated before....this does not seem to happen with Kontakt, UVI, etc.... I just tried HALION 6 and it behaves  the same as the FREE Halion Sonic SE.

I will reach out to Steinberg but I am not sure how much that will help....but I will keep you posted.

Thanks

Hi dlpmusic, 

Thanks for the update. Sorry that I couldn't be of more help. 

Best,
Paul