Huh! That's really strange.

Rest assured that this is not a common problem. Many, many users have these two applications working together without a hitch (Herb from VSL, for example).

May I please ask you to send this message plus as many system details as possible (OS, CPU, RAM, audio system, graphics card, driver versions ...) to ? They will look into it ASAP.

Thanks!

Kind regards,

 Are you running Windows 7 Enterprise edition?  That could well be an untested OS to use, as it has so much extra security/administrator locked funcionality.

In the meantine try using MIDI tracks and VST instruments rather than instrument tracks, to see if it works that way, as you wouldn't be using instrument tracks with VE Pro, as they only work on one MIDI channel (1)

Yes I am running Enterprise Edition, but absolutely none of the additional encryption or security systems are enabled.  Additionally, as I said every other application works perfectly (I run 5 machines with Enterprise).  Studio One and VSL work hand in hand perfectly, and in both stand alone modes.  It is only when I try to instantiate VE PRO 5 newest build into CUBASE 6.5 and it reads the licenser and fails with the error message.  I am not sitting in front of it this moment but in fact the system that I am typing this from is also Windows 7 Enterprise and works flawlessly with the two of them.

EDIT:  I actually just updated eLicenser and did maintenance and in fact, software Licenser does show up.  I think the Cubase Demo puts it there.  However, I am able to create new tracks, play them, remove them, add new etc and never get it to crash on this system.

I am almost certain the cause is that software eLicenser/demo.  I don't see it in any lists (but I do see a folder, with LLC, not eLLC, which is from 2010).  I think it is trying to read that licenser software.  Interesting thing is, it hasn't ever been there that I noticed until now (but then again, Studio One doesn't use a dongle so maybe it was never an issue).  The last thing to try which I am trying now, is applying the update to 6.5.1 which I did on the main machine.  Maybe the Demo absolutely does not like me updating it since it's not a full blown licensed copy.

Here is a link to the exact error message, on Steinberg forums (of which I cannot communicate with):

http://www.steinberg.net/forum/viewtopic.php?p=28175

Maestro2be

Ok I was able to destroy it on this machine also.  It is the 6.5.1 update.  This thing is plague.  It's is either because I am using a demo, or just a bad update.  Either way, this is the reason for the problems.  Is there a way to roll back to 6.5 or am I looking at a complete uninstall/reinstall?  (Besides a system restore point) :).

Maestro2be

Problem solved, remove the 6.5.1 update and all is fixed.  The update causes much more problems than fixes :).

Is this something I would have to learn to accept from Steinberg?  My Studio One updates never cause me issues.

Maestro2be

@cgernaey said:

Problem solved, remove the 6.5.1 update and all is fixed.  The update causes much more problems than fixes 😊.

Is this something I would have to learn to accept from Steinberg?  My Studio One updates never cause me issues.

Maestro2be

The more complicated a program gets, the more chance of a bug biting you in the a*se at some point. I don't think it's anything to do with Steinberg, per se.

DG

That's quite accurate actually Daryll.  I really love the simplicity and layout of Studio One.  But it is seriously lacking for an orchestral midi programmer.  It's awesome for many other things.  But until it matures more I need something much more powerful.  The workflow and speed of it is incredible.  You can be from nothing to music within seconds.  But as it grows, I am sure it will get more complicated and more bugged.  Cubase isn't nearly as fast to setup, however experience tells me everything can also be done instantly for you, in templates once you take the time to set them up.  So for me this is when the true test will begin for me.  Also, there is much more support and knowledge on the market for Cubase so perhaps easier to get help with it.

If you had the opportunity to purchase Cubase 6.5 for 400-500 dollars, but could buy Nuendo for 600-700 dollars (Version 5.5) would it be best to go all the way and just be done with it and get Nuendo versus Cubase?

Thanks, just looking for some opinions on that.

Maestro2be

@cgernaey said:

If you had the opportunity to purchase Cubase 6.5 for 400-500 dollars, but could buy Nuendo for 600-700 dollars (Version 5.5) would it be best to go all the way and just be done with it and get Nuendo versus Cubase?

Thanks, just looking for some opinions on that.

Maestro2be

Cubase and Nuendo seem to be in a continual state of what the locals like to call leapfrogging. Cubase often gets new, supposedly "music related" features first, and the Nuendians have to wait., However, Nuendo is a much more fully featured program. When I bought it there were features I really needed that weren't available in Cubase. That is no longer the case. However, you have to watch out for the fact that Nuendo is only "Cubase plus" when you buy the Nuendo Expansion Kit, so when you are talking about cost, make sure that this is included, if you wish to use any of the features, such as the Score Editor.

As you can see in my sig I''m still on Nuendo 4.3, because I don't need any of the features that came with N5. Whether or not I upgrade to N6 will depend on what it brings to the table that I think I need.

DG

Thanks DG I will keep that in mind.  Things are getting much better as time goes on.  Had a few hours to play and here is the new results (this is now me at home on my main DAW machine in the studio that began this thread).

1.  The software licenser was put there from the demo, but after I loaded the key on the USB Licenser I didn't need it anymore so I removed the file in this location:

(Windows 7 64bit) C:\ProgramData\Syncrosoft\SeLicenser.sel

2.  After that all the eLicenser conflicts went away.  Then I removed the 6.5.1 patch from using remove updates in control panel.  (this didn't fix anything, so I think I will re-install it later.  See #3).

3.  I was still having serious issues with instruments stopping working etc.  This definitely has to do with some instruments not liking being an Instrument Track.  After I read the don't use that kind of track, I started using VST versions of the ones that were multi-channel (omnisphere, kontakt, VE PRO etc) and the problems went away (thanks to the VE PRO manual teaching me VST Setups :).  Seems Instrument tracks are good for only single instance plugins (like VI PRO2, or Single Instance Kontakt).  That cleared that right up.

I think most of these problems are just user related and noobiness at this point.  Any hints on how to setup my Multiface 2 with Cubase?  No quick tutorials I could find and when I started mucking with it in device setup and vst connections, all my audio stopped working :).  So I reset to a single "Stereo" setup and it's working.  But it is hardly optimized for my RME Card.

I was also thinking of buying the Mega Bundle on macprovideo for the entire Cubase 6 series.  Seems pretty cheap for so much information, but not sure how good the information is.  Definitely still finding Studio One V2 far superior in many ways for my taste.

Maestro2be

 There are many ways to set up your Mutliface. However, none of them are done from the Devices menu. All that you should use this for is to make sure that you are using the proper ASIO driver, and not some Windows cr*p. [;)]

If you can explain what you're trying to do and achieve, maybe I can help. FWIW most input/output stuff is done either via VST Connections (F4) or by the Control room mixer.

DG