1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Vokator in Nuendo/Cubase

Discussion in 'VOKATOR' started by Vance Galloway, 8/12/03.

Thread Status:
Not open for further replies.
  1. Vance Galloway

    Vance Galloway New Member

    Messages:
    19
    I am experiencing a large number of issues/problems getting Vokator to function correctly when using it in Nuendo. (Cubase added on subject line because the two apps share so much code that sometimes the same issues pop up in each.

    I am wondering if others are experiencing the same issues or if, perhaps, I have missed some fundamental issues in the documentation.

    Quick Setup info:
    - Macintosh 800Mhz Dual Processor
    - Mac OSX 10.2
    - MOTU 2408 and 308 interfaces
    - Most recent version of Vokator

    A quick overview of issues (details as/if anyone replies)
    - After I open a preset, I cannot change any settings whatsoever. Moving a control knob, or selecting any button results in that control immediately returning to it's old value.

    - I cannot open up any editing panels that were not open when the preset was recalled (Can't open up the Keyboard editor, can't open any of the synth or output panels). Then again, the first problem eliminates any possibility of making any new settings once the panels are open.

    - The processor load of Vokator is absurdly high: It seems to take 30% to 40% of my computer's power (above and beyond that used for the Nuendo session)just to open one copy of Vokator. (Absynth and Reaktor both use absurd amounts of processing power, as well. 4-12 times what they seem to on PC. Apples to orange comparison, though).

    - Even after setting my paths, presets don't seem to find audio files that they were referencing when originally saved.

    - MIDI input is shaky; While this doesn't happen every time, there have been several instances where after I have set Vokator as the recipient of MIDI from a Nuendo MIDI track, no other VST or VSTi can use the same MIDI input. This sounds more like a Nuendo thing, but the ONLY times it has happened is while sending MIDI to Vokator. When the instance of Vokator is closed, MIDI becomes available to other VSTs.

    Anyone else? Anyone having great success?


    Vance

    Basically, it's unusable the way it's set up now.
     
  2. Vance Galloway

    Vance Galloway New Member

    Messages:
    19
    Anybody? Nobody is using Vokator in Cubase? Hard to belive
     
  3. Lynx123

    Lynx123 New Member

    Messages:
    2
    HI - I have been having serious problems with the Vokator VST plug-in for use in Cubase. Like you, I am running a Mac based system.

    The primary problem I am having is with the MIDI assign function.

    Are you doing well on this?

    Thanks - Lynx123
     
  4. Vance Galloway

    Vance Galloway New Member

    Messages:
    19
    I should have posted this earlier - I am now happily up and running. While I have not tested all functions of the Vokator, I am now able to edit patches and stability is greatly improved.

    The main change was downloading a new update from Native. Make sure you have the very latest.

    I have not checked MIDI assignments. What problem are you seeing - perhaps I can try to reproduce it here.

    Best

    Vance
     
Thread Status:
Not open for further replies.