Vienna Symphonic Library Forum
Forum Statistics

200,655 users have contributed to 43,206 threads and 259,114 posts.

In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 77 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries (legacy)
  4. Vienna Ensemble ready for download
  • S
    S

    Hi !

    I don't have enough time to test Vienna Ensemble right now, but I've one question :

    If you use a x64 os with a 32 bits vst host, does the client/server allow us to use the x64 VE ?

    I don't think so, but... 

    Hmm, sorry, another (technical) question :

    Why do we need to manually set the latency compensation ? 
  • PaulP
    VSL Team
    PaulP

    HI Stéphane,

    yes, you have the advantages of the 64 bit application when working with a 32 bit host on Vista64 and XP64.

    You don´t necessarily need to set the laency compensation, youu can also use synchronous Processing (it needs more CPU, though).

    Plugin´s latency is checked on startup of the host. The Vienna Ensemble is an application outside of the host, connected via VST. As it starts AFTER the host, you need to manually set the latency (once, if you don´t change the buffer settings of your soundcard). There´s no other way to do it, technically.

    Steve, the bug you mention with Waves is on XP SP2? We will check that!

    Sonicether, Markus: What exactly are the error messages? The more informations we get, the better we can work on a solution!

    Best,

    Paul 

    Paul Kopf Head of Product Marketing, Social Media and Support
  • S
    S

    I have the same problem, if I save a project when I close and then re-open it I am asked for the Waves Fx I want to use (WXP sp2)

    ciao

    Sergino
  • S
    S
    last edited
    last edited

    @Another User said:

     

    You don´t necessarily need to set the laency compensation, youu can also use synchronous Processing (it needs more CPU, though).

    Plugin´s latency is checked on startup of the host. The Vienna Ensemble is an application outside of the host, connected via VST. As it starts AFTER the host, you need to manually set the latency (once, if you don´t change the buffer settings of your soundcard). There´s no other way to do it, technically.

    So if I understand correctly, when manually set, The Vienna Ensemble Engine doesn't worry about the host latency, and if Synchronous processing is checked it "read" the latency when it starts then doesn't dynamicaly change this latency if you choose to change the host latency. So I don't understand why it use more Cpu.

    btw : Is the cpu needs for Synchronous Processing relative to the polyphony ? Fixed ?

    One last question :

    When you use Vienna Ensemble on a slave computer with Fx-Teleport, which latency is the correct one ? Host latency ? FXT latency ? 
  • PaulP
    VSL Team
    PaulP

     Dear Stéphane,

    so many questions, so little time [;)].

    Synchronous Processing takes more CPU power - I´m the wrong guy to ask for the technical reason, but I guess that the buffers are adapted in realtime, and this adaptation takes CPU power. I´m not a programmer...

    All other questions I will check (or maybe you find a little time to find out yourself... I´m not using FXT in my setup here, so this information may take a little time. 

    Thanks for your patience!

    Best,

    Paul 

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D
    last edited
    last edited

    @Paul said:

    I´m not using FXT in my setup here, so this information may take a little time. 

    Thanks for your patience!

    Best,

    Paul 

    FXT is a potential can of worms. I will do some testing this weekend on XP64, but it remains unclear whether to use the 64bit version of FXT or not. Max has always said that to run 64bit plugs you need FXT64, to run 32bit plugs you need FXT32. However, as VE somehow runs outside the sequencer in normal operation, does it do the same with FXT? I don't know, but it really should have been tested by VSL. We shouldn't have to wait for answers, they should have the info. Were none of the beta testers using this configuration? If not, why not?

    DG
  • H
    H
    Sorry to ask this again if it's already been asked .. but having slept for 10 hours I don't know .... when's the OS X VE coming out. .... only version I see is for Win XP
  • C
    C
    HI, this is what Paul wrote today:"yes, there will be a new public beta version online within the next hours if everything goes our way Thanks for your patience, everybody!"
  • S
    S
    last edited
    last edited

    @Another User said:

    All other questions I will check (or maybe you find a little time to find out yourself... I´m not using FXT in my setup here, so this information may take a little time. 

     

    DG,

    As Paul said, we can use VE 64 bits with a 32 bits host. So I think that we could stay with FXT server 32 bits and use more than 4gb in the Vienna ensemble (different process). 
  • D
    D
    last edited
    last edited

    @Stéphane said:

    DG,

    As Paul said, we can use VE 64 bits with a 32 bits host. So I think that we could stay with FXT server 32 bits and use more than 4gb in the Vienna ensemble (different process). 

    This is what I'm going to try first. I really hope that it works, because currently with FXT you can't mix and match 32bit and 64bit plugs. I guess that in the end it all rests on who has the memory; VE or server.exe

    DG
  • A
    A

    Hi - just to confirm: it works flawlessly on my setup:

    Master DAW: dual XEON X5355 (8-core), Tyan S5380, 8 GB FB-DIMM 667, RME 9632 HDSP, 3x250 GB RAID w WD Caviar RE, 3xMatrox Parhelia APVe, 74 GB WD Raptor boot, 500 GB backup HD, Vista 64, Cubase 4. Slave (FX-TELEPORT) DAWs: Q6600 (P5B-VM DO, 4 GB, XP x32) and E6600 (P5B-VM DO, 8 GB, XP x64, RAID 900 GB) system.

    Have installed VE on my slave E6600, free space for samples more than 7 GB, using Reaper/C4.1 (x32) on the Master DAW with FXT wrapper, ViennaEnsemble"Wrapper"Plug-in (x32) opens correctly in FXT Server on the slave machine (16 stereo channels to be streamed to Master DAW) and starts x64 VE. MIDI and audio via FXT works without problems.

    Well done! Congratulations.

    AM
  • PaulP
    VSL Team
    PaulP

    Hi SvK,

    I have installed and uninstalled the Vienna Ensemble on different PC´s, couldn´t reproduce the behaviour your described.

    Uninstalling the Vienna Ensemble didn´t affect the licenses and the Vienna Instruments. 

    Did you try on a second machine?

    Thanks,

    Paul 

    Paul Kopf Head of Product Marketing, Social Media and Support
  • D
    D
    last edited
    last edited

    @am_wagner2000_25428 said:

    Have installed VE on my slave E6600, free space for samples more than 7 GB, using Reaper/C4.1 (x32) on the Master DAW with FXT wrapper, ViennaEnsemble"Wrapper"Plug-in (x32) opens correctly in FXT Server on the slave machine (16 stereo channels to be streamed to Master DAW) and starts x64 VE. MIDI and audio via FXT works without problems.

    Well done! Congratulations.

    AM

    Good to know. Can you say yet how much memory 1 instance of VE with 16 instances of empty VI uses?

    DG
  • S
    S
    last edited
    last edited

    @Paul said:

    Sonicether, Markus: What exactly are the error messages? The more informations we get, the better we can work on a solution!

    Best,

    Paul 

    I don't know if you are familiar with Windows XP, but it is just the traditional error message whenever any application encounters a violation/problem and crashes. The classic, " ___ has encountered a problem and needs to close. We're sorry for the inconvenience..." You are provided with the option of sending the error report to microsoft or not.

    It also provides you with a log of what processes violated what, so if you want me to give you the txt of the log (it's VERY long) just ask!

    Thanks for your help.