Vienna Symphonic Library Forum
Forum Statistics

185,277 users have contributed to 42,390 threads and 255,477 posts.

In the past 24 hours, we have 3 new thread(s), 22 new post(s) and 54 new user(s).

  • Question regarding ".matrix" files and PC - And how do I go beyond 16 VI's in VE3?

    Question 1: Can I take matrix files created on my mac and allow these to be read somehow on my new server PC (XP64)? Question 2: VE3 is awesome... it should be required purchasing for anyone using VI. However (using Logic 8) it does seem that I can go beyond the 16 channels by somehow using a second bank of 16 multitimbral objects (17-32) and then routing these to a Port IN 2 in the next sixteen VI's. However this second 16 does not seem to register in VE3's list of inputs. Am I mistaken (surely not) or is there something I am missing. No mention of how to go beyond this in the manual it seems. Thanks, J

  • I guess the original posters productivity issue is still very valid though. I know that every time I use Logic with VSL and then quit, I need to manually Force Quit all the apps associated with VSL in the background (not sure if this includes Syncrosoft). I've just spent about 2 hours today moving projects from the Mac to run on the PC server which involved opening Logic Files, closing them, transferring the dongle opening VE3, setting up the same VI's, reopening the Logic file (forgetting to transfer the dongle!) then watching Logic hang because it's looking for syncrosoft, then having to reboot, then discovering that syncrosoft wants to update the License software (again!) before it will start working again. The list goes on. I guess I'm getting used to it but it does seem weird that when you quit any of the VSL apps, they leave all this hidden detritus hanging in the background. ------ Its also pretty weird that EVERY time I plug the dongle into the PC it needs to reinstall itself. ------ Mind you its all small fry compared to programming a piece for MaxMSP but still its the most time intensive 'commercial' "plug in" I've experienced. Something tells me that this will get better once I'm working with VE3 fulltime though.

  • last edited
    last edited

    @zentrumsounds said:

    Its also pretty weird that EVERY time I plug the dongle into the PC it needs to reinstall itself
     

    thats only the case if you plug it into a different USB port because the hardware ID changes then ...

     

    dumb question: wouldn't it be possible to save the presets on the local machine, then loading them on the remote machine and simply re-assign the logic tracks to the respective VE3 channel?

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • I'm a bit stumped (both by the answer and the cross pollination of thread info just there!)... your saying what exactly? That there IS a way for the matrix file to be moved between mac and PC? Or am I missing something about the level of interaction along the ethernet connection. At any rate I think you've somehow moved a response to the productivity question from another thread which addressed a slightly different issue. Issue number one: Transferring individual VI's used in one project to a VE3 set up takes a lot of time as one needs to shut down and reboot quite a few times (although once you're used to it I guess only twice) and entails shutting down elements of VSL which are running in the background. Issue number two: I have an extensive library of matrices which I'd now like to transfer to the PC. How? Thanks Christian

  •  i have splitted the other thread because the original topic does not fit to your reply (resp. vice versa) and merged it to this one to keep both related topics under one hood ...

    custom preset & matrix files can be moved from one custom preset folder to another via file-copy (either network shares or USB stick or similar) - doesn't matter what the filesystem is.

     

    assuming now each track has loaded a certain preset just re-assign it in VE3 track by track - wouldn't that work?

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.