Vienna Symphonic Library Forum
Forum Statistics

184,670 users have contributed to 42,366 threads and 255,356 posts.

In the past 24 hours, we have 1 new thread(s), 6 new post(s) and 75 new user(s).

  • Compatible GPU needed for Power House

    Hi,

    I have a GTX 1060 3GB GPU. Would using Power House benifit my CPU at all. Or is it absolutely necessary to have at least 8GB of VRAM. If so, would this GPU do the trick? https://www.mwave.com.au/product/asus-geforce-rtx-3060-dual-oc-12gb-video-card-v2-ac45603


  • 3 GB would theoretical work, but just for a few instruments, especially if you go surround or immersive.
    I would not recommend using it with Vienna Power House.

    Yes, the RTX 3060 12G will work and has a great price/performance ratio.


    Ben@VSL | IT & Product Specialist
  • last edited
    last edited

    Hi JBuck,

    Best to try with a 30-days demo license! 3GB VRAM is definitely on the very low end, vastly limiting the capabilities of this technology. Yes, the RTX 3060 is one of the recommended graphics cards listed under the product system requirements.

    Best regards,
    Andreas


    VSL Team | Product Specialist & Media Editing
  • last edited
    last edited

    @JBuck said:

    Hi,


    I have a GTX 1060 3GB GPU. Would using Power House benifit my CPU at all. Or is it absolutely necessary to have at least 8GB of VRAM. If so, would this GPU do the trick? https://www.mwave.com.au/product/asus-geforce-rtx-3060-dual-oc-12gb-video-card-v2-ac45603


    Hi JBuck,

    You can definitely work with 3GB GTX 1060, but you need to offload all the GUI work from this GPU to any other of your system to make it run smoothly, e.g., to your iGPU using Nvidia Control Panel. We do this automatically when launching our software, but please note that it's necessary for your current setup.

    One more note about the memory usage. 3GB is sufficient to run a Dolby Atmos 12ch setup for about 29 instruments (about 350 channel instruments running 2 convolutions per channel), if I am not mistaken. You can also do a stereo equivalent of this amount for a stereo setup, giving you about 175 instruments before you go to the out-of-memory limit of your current setup*.

    *The 78 instruments 12ch Dolby Atmos configuration takes about 7.1GB in our reference audio project, so this is how I came up with the numbers above.


  • Welcome @Sasha T, great to see you here! Thanks a lot for chiming in.

    @Sasha-T said:
    *The 78 instruments 12ch Dolby Atmos configuration takes about 7.1GB in our reference audio project, so this is how I came up with the numbers above.

    Maybe I'm missing some basic facts - but wouldn't this number depend mainly on the length of the IR ...?

    Kind regards,


    /Dietz - Vienna Symphonic Library
  • last edited
    last edited

    @Dietz said:

    Welcome @Sasha T, great to see you here! Thanks a lot for chiming in.


    @Sasha-T said:
    *The 78 instruments 12ch Dolby Atmos configuration takes about 7.1GB in our reference audio project, so this is how I came up with the numbers above.

    Maybe I'm missing some basic facts - but wouldn't this number depend mainly on the length of the IR ...?


    Kind regards,

    Hey Dietz,

    Yes, it is, if you just run small and/or stereo projects.

    For multichannel projects or large stereo projects the factor of total channel quantity comes into play. It depends on how many instruments or instruments / channels will be initialized. The IR length gives you some X memory utilization, but the way you scale it is by N channels multiplied 2 convolutions per channel (so for 7.1.4 Dolby Atmos, one instrument can give you X of IR length multiplied 12 multiplied 2 of the memory usage),

    so imagine you have 4MB of memory utilized for the object (not just for the IR itself but the entity that has everything stored on the GPU including the IR data) per channel for the given IR length, for stereo, it goes 4x2x2 = 16 channel convolutions (64MB) in total, for 12ch (Dolby Atmos 7.1.4) it goes 4x12x2 = 96 channel convolutions (almost 400MB). For large orchestras where you typically have 80-100 (let's say 100) instruments involved, to process Dolby Atmos 7.1.4 it might take 100x12x2 = 2400 convolutions to offload (which will easily consume almost 10GB). So, again, 0.064GB stereo, a few instruments => 0.4GB 12-channel, a few instruments => 10GB for large 12-channel orchestra when the orchestra grows to a large number of channels. If you change the IR length from 2s to 7s, it may be multiplied by 7s/2s factor (or less, since we store not just IRs but lots of other data), so it will be something like 0.2GB stereo, a few instruments => 1.2GB 12-channel, a few instruments => 20GB or even 30GB for large 12-channel orchestra.

    So above is just another perspective on how memory usage depends not just on the IR length but also on the channel configuration, and it's more important for large orchestra use cases.


  • @Sasha-T said:
    You can definitely work with 3GB GTX 1060, but you need to offload all the GUI work from this GPU to any other of your system to make it run smoothly.

    Hi,

    So hitting the GPU Power button does or does not do this automatically? And if not, how would I go about verifying that the processing has indeed been offloaded to the GPU?

    Also, can you please confirm that 3GB is sufficient to run up to 175 instruments which is 2 stereo mic arrays x 175?


  • Hi JBuck,

    Best solution (like Andreas said at the start of this thread): Give it a (free!) try with a demo license!


    Paul Kopf Product Manager VSL