Vienna Symphonic Library Forum
Forum Statistics

200,869 users have contributed to 43,215 threads and 259,143 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries (legacy)
  4. Mixdown in Logic Platinum 5.3 (PC)

  • Mixdown in Logic Platinum 5.3 (PC)

    D
    D
    I've got a really annoying problem with VI when I'm using it in Logic. I'm still on the PC version and using 5.3 (I had probs with 5.5.1 and Waves) so Apple haven't been very helpful!

    I'm unable to mix down any song I use VI in. I thought it was a memory issue, but I've just tested it with a fresh song, one instance of VI playing 4 notes on a clarinet, optimised. I always get this message when I try to do a bounce on the stereo master...

    "The process cannot access the file because it is being used by another process. Result Code = 32"

    I can play the songs fine. The song I discovered this on has got 10 audio tracks, loads of soft synths (including EXS instruments, GigaStudio and VI), and a tonne of effects plug-ins, all playing fine. Just can't bounce it down. I'd also just finished a string quartet piece (solo strings from the VI Special Edition) which again is playing fine but won't mix-down.

    Any ideas anyone? PC Logic users?
  • C
    C
    Sounds nasty. Can't test this myself (I run Logic on the Mac), but when you click on a VI track, does its Audio Object window (on the left of the arrange page) show the same Device type as the other instruments you use, such as EXS24? On a somewhat unrelated topic, did you mean GVI (Giga Virtual Instrument) rather than GigaStudio?
  • D
    D
    Yes, device is always ASIO.

    I use Gigastudio with the FX-Max Giga VST Adapter (www.fx-max.com). It gives you VST instruments for the 8 Gigastudio ports (i.e. the MIDI connection) and returns for the 32 audio outs (as Aux channels in Logic). GVI is cool, but you can't build your own instruments with it.
  • C
    C
    Could it be a mis-match of sampling rates? The only other thing I can think of is to do a test bounce where you give the bounce file a totally unique name to deter Windows from confusing it with anything else on the hard drive. As a workaround I guess you'll have to record the VI tracks as audio then bounce it all down - what a pain. Agreed about GVI!
  • D
    D
    How would I check for a mismatch of sampling rates? I thought VST handled all that behind the scenes...

    I sat down to record the VI tracks as audio, then realised that I'd need to, erm, bounce them down. Same problem. At the moment, it looks like I'll have to load up some other sequencer that supports VST and then pull the audio mix(es) into Logic afterwards. Very messy. The name of the file doesn't make any difference. It looks to me like one of those Windows errors that doesn't tell you what's [i]really[/i] going on.
  • C
    C
    You're right, this should all just work. However it might just be worth opening a standalone VI and checking its sample rate (and other properties) against the rate you use in Logic. As far as recording the VI goes, you'd have to record analogue audio signal from your desk like you would a vocal or guitar. Very tedious, you have my sympathies!
  • C
    C
    Re. the irritating error message: have you tried 'Ctrl-Alt-Delete' to see what processes are active? It might give a clue as to what's bugging the VI.
  • D
    D
    Well - just an update as I've spent the whole day trying to sort this out (trashing my Windows install whilst doing some performance tweaks included!). Anyway, after getting everything back up and running I still had the same problem but in a fit of randomness decided to change the file format to AIFF on the bounce, instead of WAV. Guess what - worked perfectly first time!!

    If there's any techie nerds out there who could possibly explain why a mixdown to WAV fails every time with weird error message, whilst mixdown to AIFF works every time, then I'd be interested (in a strangely nerdy way), but at least I can get on with things now. Hoorah!
  • C
    C
    Congratulations on cracking it. "Where there's a will . . . " Sounds like a Logic bug, but we may never know.
  • A
    A
    I still have this problem and sometimes i can bounce and sometimes I can't. strange things happens behind logic [*-)]

    I'm shure that not only 2 users still use logic 5 on pc. is there any other user, who can tell us more about this effect?
  • D
    D
    I think it's definitely a Logic "bug" (it's probably part of the design!). This looks like a file handle thing. VI uses a LOAD of file handles, probably part of the fast streaming/sample switching capabilities. For example, if I have a medium complexity Logic song with plenty of audio going on the number of file handles is generally between 3000-6000. Add a string quartet (solo violin,viola, cello, bass) from the VI special edition - with the 8 or 9 articulations available - and the file handles shoot up to about 40-50,000. Doesn't matter whether anything's playing or not. Presumably VI is caching the start of the samples and keeping open file handles ready for use. I also discovered that PC Logic has a 1Gb memory usage limit - so even if you have more memory, it doesn't get used.

    So, it looks like a combination of memory and file handle limits and the way Logic manages these things. All I can suggest is to always optimise the VI instances once you've finished writing, to reduce the memory and file handle usage to a minimum.

    Saving up to replace Logic...... [;)]