On Max OSX Snow Leopard.

1.  Establish a metafile.  Tried to load and all that shows is the server window.  The VE-PRO Window does not come up and the activity monitor is not showing any memory increase activity.

Rebooted.....

2.  Loaded VE 64 Server followed by loading the program.  After about 3 minutes I got the infamous White box and everything hung.

3.  Pulled boh Steinberg and Vienna dongles before machine would reboot.

One other thing I might mention.....

I've noticed, and I don't understand why it would, but when I load the activity monitor, many times in the past (at least 30), VE/Cubase begin to become unstable (i.e. lock ups, White security box, etc.).  I haven't been able to put my finger on it but I have found that for example, a problem will occur... I had the activity monitor up and running.  Perform a reboot after a hang.  Don't load the activity monitor and everything is ok.  Load the activity monitor to see where my memory is at and things start to again become unstable.  

This has happen several times although I can't seem to get it to repeat itself on a regular basis.

Not sure if any of the VSL team or any of the users have experienced the same.  Don't want to send anyone on a wild goose chase, but I thought I'd throw it out there.........

I know Karl,

I use to think that maybe I was close to my memory limit and the activity monitor put it over the edge.  Now with the 64-bit app, I'm not close but I still am seeing a pattern here.  Just can't replicate (at this point) on a consistent basis.  I thought that maybe the approach that your team is using to access memory may be in conflict with the monitor.  Not sure --- that's why I mentioned it.  

Of course, Cubase is also in the mix.  Not sure if there is something there either considering both use the same security scheme.  Take it for what it's worth.........

File associatons...

I believe the reason there are file association problems with VE Pro is that each of the four applications (VE Pro, VE Pro 64-bit, VE Pro Server and VE Pro Server 64-bit) point to an executable file that has the same name: Vienna Ensemble Pro.  So, once one program is running, trying to launch another application by double clicking on a different mframe file or a viframe file, the OS will think the application is already running because it is pointing to an executable file call Vienna Ensemble Pro and one with that name is already running.  So it tries to load the file, discovers it can't since it is not compatible and either gets and invalid file error or just doesn't load the file.  

Someone correct me if I'm wrong, but in OS X I don't believe you can have different programs with the same name and expect them to work consistent with the way the OS is designed.

@Karel said:

Multi-out with AU is indeed not always trivial to implement properly. I will see what can be done about G-Player.

@Chuck Green said:

n Max OSX Snow Leopard.

1.  Establish a metafile.  Tried to load and all that shows is the server window.  The VE-PRO Window does not come up and the activity monitor is not showing any memory increase activity.

Rebooted.....

2.  Loaded VE 64 Server followed by loading the program.  After about 3 minutes I got the infamous White box and everything hung.

3.  Pulled boh Steinberg and Vienna dongles before machine would reboot.

Karel,

This morning I started by trying to start the Metafile and left it sit for 25 minutes before I returned.  It appears to be working but I do have a question.

In the past, after the sever started the VE Interface would display followed by the turning bars in a circle and the statement that it was loading.  Now the interface doesn't show up and there is no indication that anything is happening.

Is this by design or is it a bug?  Please advise.....

@Karel said:

I've just fixed the showing for next release.

Thanks Karel.

I'm really starting to like working with VSL again especially now on the Mac Platform.  One thing that I personally would really like to see is a way to save each channel strip setup in VE-PRO.  A lot of time is spent tweeking the parameters for each instrument (i.e. pan, reverb mix, effects, etc.) that to be able to save that setup for use in a  new template would allow a great starting place plus improve over-all work flow and efficiency.  

Sonar, Cubase and Logic I know for sure has this setup feature and it would be a real plus to have this available in VE-PRO, especially if one is mixing in VE.  I'm not sure how much work is involved to doing so, nor am I aware of any of the other users feeling about having this feature,  but I would really appreciate having it be considered in a future release.  Thanks again for your consideration.

Are you saying that I would have to save each individual channel strip in it's own VE-Pro template?  Then if I wanted to add to my existing template a previously configured single instruments,  I would merge my existing template with the one that has a single instrument in it?

Sorry if this is a dumb question, but what does "public beta" mean for VSL? From what I understand Beta is when its not an "official" release yet, but users are able to download it to report any bugs that will be fixed on the official release. Is this true with how VSL runs public betas? If so, will users be notified when the release is no longer "public beta?" 

Also, I know PPC macs are not officially supported, so I'm always weary about updating to new versions when the current version is working well enough to use. If/when that time comes that PPC's no longer work at all with VE pro, is it possible that this information will be in the release notes so we know not to install it?

Thanks again VSL team for being so receptive with VE Pro. Its a MONSTER of a program that will truly revolutionize the way we work with sample libraries! I know it must be a lot of effort making sure its compatible with all sorts of 3rd party / computer OS's, and I for one just want to say how much I appreciate the extra work! In fact, I've been telling all my composer friends about VE pro, many of which have now made it their first VSL purchase! 

Hi Jon,

thanks for your kind words - we are doing our best to improve VE PRO every day!

Public Betas: There are so many possible combinations with 3rd party plug-ins, that we figured, a public beta is the fastest way to get your input and to provide you with the next update - asap. A new build is already in the works, and of course the naming of the "public beta" will be changed as soon as a release is "official".

In any case, even public betas have been thoroughly tested before, and you can always downgrade, if you like.

Regarding PCC: We will do our best to keep VE PRO compatible. If that doesn´t work for any reason, it will be mentioned in the changelog, of course. Also, if a build doesn´t work on PPC, it will most probably simply not install. 

Best,

Paul

Hi Paul

The 2 little problems I have report are still there :

- Flashing screen when VE pro is loading

- I have to rebuild the directory each time I run VE pro otherwise VE do not find the samples

Thanks in advance for correcting them

Best

Cyril

I forgot to say : Your programmer are doing a great job

CONGRATULATIONS

Hi Cyril, 

I´m sorry we have not fixed the 2 issues you are having, yet. We simply have to improve VE PRO step by step, and we have to set priorities.

I was not aware of the second bug - and I haven´t heard any other reports about this, I have to say. Anybody else having problems with this??

Now I could scan your many mails again to find out more about your current setup, but it would be great if you could take the time to add these details either in your signature or simply copy the essentials into your post.

Important: OS, Sequencer + version, RAM, soundcard + driver version, Computer specs

Thanks, 

Paul