Very good news and great improvements! Thanks a lot, VSL-Team!
[:)]
-
Couple of problems with this release.
1. I get a "Project file is invalid or inaccessible" message when trying to double click a metaframe file. Sometimes they load, other times they don't with this message. I can always launch the server and then open the file from within the server to get it to work.
2. The file associations are closer, but still not working correctly. If I have no Servers running, and I double click a metaframe file (for either 32-bit or 64-bit metaframe file) then the file launches the correct server and the file opens fine (exepct for issue 1 above). If one of the servers is already running and I double click another metaframe file (different server type) the file won't launch the server and load. However, If I right click and select Open with... then it loads fine.
3. Exiting the server app always asks if you want to save the metaframe file. It should only do this if something has changed.
4. Please change the menu title to reflect the program name of the selected window e.g., when the server is selected the menu title is still Vienna Ensemble Pro. Should be Vienna Ensemble Pro Server (or something).
5. If I have my instances minimized to the dock and I double click an instance in the server window, it maximizes, then minimizes, then maximizes the instance. End result is correct, but the behavior is like nothing I've seen before. It's kind of amusing actually.
6. Newest version of eLCC (10/22/09) still doesn't work on boot up. It does work on login assuming it was working when logged in previously. Once the computer goes into reset state, trying to load a server during boot up always fails the eLCC white screen that says it can't find a valid license.
7. If I try to delete a track in Logic Pro 9 that is connected to a VE instance, I get a spinning beach ball. Don't know if this is a Logic issue or VE Pro issue.
Note: I'm running OS X 10.6.1
-
i've been testing http://www.midevice.com/Products.aspx?ProductID=0 again.. (just the demo). and it seems to be working a lot better then the previous release, but still crashes when you click on the setup button or change patches in gladiator wraped. also, the d16 nepheton outputs other than the first one don't work...
-
" Improved overall plugin compatibility "
So, has this latest update fixed the compatibility issue with 'PLAY' (Mac and PC) ?
-
G-Player fix is not working. While I can see the 16 stereo outs in the dropdowns of additional audio ins in vienna ensemble pro - I still can't choose another out in the plugin itself than out1/2.
This does work when G-Player is running directly in Logic, so it's definetly a host problem.
It seems that the AU does not get feedback how many channels are available. This is - by the way - the same in Reaper OSX. There the G-Player AU does show only one stereo out but the VSTi version of G-player can address 16 stereo channels. Multiout with AUi seems to be tricky.
-
Gave the beta a spin..
It wasn't mentioned in the update notes but I was hoping this update would fix the issues of VE PRO crashing on a remote PC when loading a project. I know in another thread you guys mentioned this was on your radar, is a fix for this still in the works? Its kind of a pain to have load/reconnect all the remote instances each time.
Cheers, David
-
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.
-
Could you also look into the Linuxsampler AU (http://download.linuxsampler.org/packages/osx/LinuxSampler-1.0.0-OS_X.universal.dmg)? It's the only 64bit Giga-playback-AU-Plugin. It works perfectly in VPro 64bit but has the same problem as G-Player. Although it has 32(16 stereo) outs I can only choose one stereo out in the Gui (Fantasia). If you need help with Linuxsampler's Gui (it's not too easy to find the routing to the outs...) drop me a line.@Karel said:
Multi-out with AU is indeed not always trivial to implement properly. I will see what can be done about G-Player.
-
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.
