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

@Cyril Blanc said:

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

Hi Cyril, I don't really understand what you mean. I asked at the top for Vienna to try my steps to show the problem. Kontakt, UVI, etc... Don't cause this problem. After trouble shooting this all day it pointed to HALion Sonic SE. It might have this problem with the other HALion products as well but I can say for sure it does this with the Free version. As for disk I/O, not enough memory or CPU problems....I don't think it is any of those as this was tested and confirmed on a new blank instance of VE PRO on a 14 core Intel machine with SSD drives and 128 gb RAM. The blank patches used to demonstrate this load no samples into memory. The behavior of taking long to connect the first time but after that it is normal and only with HALion Sonic SE Free seems like it is probably a VE PRO issues or bug....or something with the HALion SE FREE instrument. The best way would be for Vienna to try my steps and see what their results conclude

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

HI, 

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

Best, 
Paul

@Paul said:

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....

Hi, 

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

Any way to reduce those?

Best, 
Paul

@Paul said:

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.

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

@Paul said:

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

@Paul said:

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

 

Hey Paul,

We have done a lot of testing to try and get to the bottom of this....the problem is so specific that it only does not happen if you set your host sound card to a 512 buffer....really strange and specific problem.  We have isolated it to a particular situation that can happen in HALion Sonic SE.  We believe this is a Steinberg issue and are in touch with them now.

 

Keep you posted if they find out anything else that you would need to look into.

 

Thanks

Hi dlpmusic, 

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

Best,
Paul

Hello Paul. My name is Frank, and have just purchased the Vienna Ensemble Pro 7 plus a few VSL libraries. I seem to be having exactly this same problem, (which I have been discussing with Andreas also).

Essentially, I can easily use VEP7 and the VSynchron Player successfully as standalones. I can connect and run it OK - exactly as per your written manual instructions - to my Pro Tools DAW, Everything works fine if then creating tracks using several different vst products (eg Garritan, Avid XPand, UVI).

BUT, if i then also create and try to connect Steinberg's vst Halion Sonic 3, things go badly wrong. Yes, all of my software is fully licensed and up to date, as is the elicenser. The basic error messages wich arise tell me that both VEP7 and Halion are missing valid id's! and then in Pro tools both items are greyed out saying they are unavailable and/or have an "insufficient resources" error!

So it seems this same issue is still a problem - presumably something to do with Halion, rather than with your product.

PROBLEMSU0020WITHU0020HALIONU0020SONICU0020INU0020VEPROU00207.doc-1696337855373-ec19o.doc