(I'm not 100% sure if this should go to another forum)
All was well untill I installed VSTHost in order to get a light weight alternative for testing software.
VSTHost worked flawlessly right away, using E-MU and ASIO with default settings.
 
When I tried to use SONAR after that, all audio and MIDI went out of control.
- Terrible latency with both audio and MIDI. MIDI signal on time - resulting audio delayed. (ASIO latency set to 8 ms, actual latency about 400-500 ms)
- I could not find a way to mute dry direct audio (dry guitar heard with no latency, amp sim audio 500 ms later)
- All settings, timing Masters, routing, E-MU templates, buffers,  are as before, but nothing seems to make sense
- When I then tried to use VSTHost after SONAR, similar issues occurred, not latency, but seemingly random
loss of audio and inter-VST-connections.
- VSTHost has two ASIO options: MME:ASIO and ASIO. Never seen or heard about that MME:ASIO anywhere, what is it?
I do not have ASIO4ALL in my PC.
 
I'll try to uninstall VSTHost when I get home today,  and see if it helps.
I must be missing something obvious, due to having such a problem free time with this setup for 8 years already, and I've never tried any other music software/VST host except for Band in a box.
 
All hints and suggestions are welcome!!

Hi,
Probably there are more applications for VSTHost which is developed by the Austrian Hermann Seib. I do use it myself with Sonar X1/X2 Producer.
The version I use comes from The vintage-sounds website of Christian Boileau, together with all kinds of patches for instrumental guitar tunes that are developed by Christian. It is working like a vintage effects chain. To use it in cooperation with Sonar it can be done as a VSTHost Slave.
This means that it uses the ASIO driver of the active Sonar Interface. In my case that is the ASIO driver of the V-Studio 100 interface.
To use it as Slave you need to have installed the plugins Legree.dll and LegreeI.dll and scanned by Sonar as VST.
If you are using VSTHost in full mode you need to have a second interface and use that ASIO driver in VSTHost.
Maybe you mean something else, then forget what I wrote.
 
Jan
 
[EDIT]
You cannot use the same drivers in VSTHost (full mode) and Sonar Simultaneously this will give a lot of trouble. To make things more clear, I use version 1.53 of VSTHost.

Have you installed Patchmix? Wouldn't you mute dry signal there?

Thanks for the comments.
@ jan.ynske:
I'm not trying to use VSTHost and SONAR simultaneously, as a slave or otherwise. I installed VSTHost to have a lightweight alternative for testing software instruments. When I  installed and used VSTHost the couple of first days SONAR wasn't launched at all during those sessions, not before or after VSTHost. And when I tried to use SONAR after that, the PC was started fresh and VSTHost wasn't running.
Basically, shouldn't those both run independantly, if "Share drivers with other programs" is checked in SONAR?
 
@Sanderxpander:
Yes, I have Patchmix in use and running normally, using the exact same Sessions/strip sets as always, but whatever I do there, it doesn't have any effect. Muting the input strip mutes the direct audio, obviously :o), but nothing gets in then.
When I start an existing project, activate a guitar track, and play with Input Echo off, I hear the dry guitar, but meters on the track don't move. When I put Input Echo on, I hear the amp sim half a second after the dry audio, and the meters are moving.
 
I just remembered I've used Kontakt in standalone mode as well, with no issues.
 
 

As far as I know ASIO drivers can only be used in one program at the same time other drivers can be shared. If I am wrong please correct me.
I also was told that the use of ASIO4ALL should be avoided whenever possible. It is much better to use your interface's own ASIO driver.
About VSTHost: The version I use is not using the computer's registry, only the Melda plugins do. So I see no reason why it could cause the trouble you are talking about if it is not even running.
However, you may be using a completely different, maybe newer version that does work differently from the one I use. In that case I would suggest to visit Hermann Seib's website(s) and get support there.
You are probably working with VSTinstruments and I only work with VSTs.
 
Jan

jan.ynske
As far as I know ASIO drivers can only be used in one program at the same time other drivers can be shared. If I am wrong please correct me.
 
Jan

 
AFAIK the ASIO drivers are limited to one interface at a time (except for when they're identical). The number of software running shouldn't be an obstacle. 

On a second thought, there is one thing that might cause problems. If VSTHost has been installed with a number of VSTs and those VSTs have also been scanned by Sonar....and one or more of those VSTs are not compatible it might cause trouble

But it should not matter, because they are not used simultaneously (?).  They do use the same VST library, and SONAR scans only the VST folders it's been instructed to scan. Even if VSTHost had  VSTs included (which it doesn't have in this case) SONAR would not know anything about them.
 

Sonar knows if you instructed it to scan these folders as well, then it is not important whether VSTHost has been started or not. However you write that VSTHost did not install plugins. I see you have Melda didn't that come with VSTHost?
Please tell me which version of VSTHost you use.

Ok. I might be back when I open my music machine next time so i can check the version.
No VSTs whatsoever came with VSTHost. Melda Creative pack that I have in my signature costs something like 200 euros. They don't give such with freeware :o)
On the other hand, I don't think this is a fight worth fighting. I will get rid of VSTHost, and hope it helps. If it doesn't...