Forum Replies Created

Page 2 of 62
  • Ericbowen

    December 8, 2014 at 6:36 pm in reply to: New Mac Pro and Premiere

    Adobe right now works far better on Windows and Nvidia cards than OSX and AMD cards. I would suggest you stay on the PC Windows platform if you want less issues. Also keep in mind Adobe has far less control with OSX and Open CL updates than they do with Windows. This means more issues in the future as Apple updates OSX and Open CL based on FCPX versus other software.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • If Avid doesn’t change their R&D and player soon they wont be number 1 much longer.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • I suggest you take a look at the Macvidcards site for some flashed Geforce 700 series cards. Those will far outperform the Quadro.

    https://www.macvidcards.com/index.html

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Ericbowen

    October 31, 2014 at 2:23 pm in reply to: Media Cache on Shared Network

    Yes the 1st is the actual media cache files with the audio conform. That will re-conform every time Adobe doesn’t see them available. The database files should also be local as well though which is the 2nd. I know it takes longer to have those locally but that is what Adobe recommends. You can try them on a network storage but like I said they may be ignored by the Adobe application and then they regenerate anyway. You also have higher latency which can effect your realtime playback.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Ericbowen

    October 30, 2014 at 9:36 pm in reply to: Media Cache on Shared Network

    They put the projects and media on the network storage and the media cache locally. The media cache rebuilds when it’s not present. The preview files that are generated from rendering are on the network storage because those default to follow the project. Adobe has never recommended the media cache be located anywhere but locally even in a shared environment. I am not sure what the issue is there.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Ericbowen

    October 30, 2014 at 7:32 pm in reply to: Media Cache on Shared Network

    You can try storing the media cache on the network storage but it’s not advisable. One the latency is higher and 2 often times the media cache reference is ignored by the application when on a network drive. If you do that be prepared to watch it conform often times again when it’s loaded.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • I have not seen increase in render times with AME if GPU acceleration is working. So I am not sure where that is coming from unless configuration or driver is an issue. If comparing the render time from direct export of Premiere to queue with AME then yes Direct export has always been faster. That is going to be because dynamic link slows the export process down since it’s a network process. There is no way to change that. If you need the fastest export then direct export. However working in Premiere is done until that is finished if you do.

    GPU accelerated debayering significantly increases the data and load the GPU is handling. This means the GPU is in use far more at a higher load. When exporting in AME and the GPU acceleration is enabled, AME has to release the GPU for the GPU acceleration in Premiere. When using the GPU accelerated debayering there is allot less time the GPU is available for releasing to Premiere or vice versa. Therefore Premiere has to interrupt and take the GPU which will cause AME to go into wait status far more or switch to software render. However the major issue is memory management. The GPU accelerated debayering add’s significant more ram usage for data getting buffered for GPU acceleration since that is how it has to work. All of the frame buffers getting setup for AME either have to hold in ram or wipe to free up space for Premiere to use ram for the realtime GPU acceleration. If those buffers wipe then AME has to rebuild them when the GPU becomes available. The complexity here is 2 applications with GPU acceleration running at the same time. Each time the higher priority application requires the GPU then it interrupts the background application stopping the pipeline for rendering in it’s tracks. If the Background application is set to switch to software ie cpu render mode when that happens then all of the buffers have to be wiped and redone. This significantly increases the render time per frame and the load on the system. The only way to alleviate that bottleneck at the ram some is to have far more ram than is required for the realtime application. Even then the memory management the CPU has to handle alone will vastly increase the CPU load which leaves far less CPU processing capability for render frame processing. Hope that helps explain what is going on here.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Ericbowen

    October 29, 2014 at 5:02 pm in reply to: I think my avi file is way too large.

    60 minutes of 1080P 30 frame media is around 500GB to 550Gb or so. So 3 minutes of 1080 30 frame is easily over 32GB.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • If you want GPU accelerated debayering then that is the trade off. GPU acceleration never lowered the spec requirements of a system. Actually it raised them. So yes they made it so a system has to have more processing power and ram to use those features as they were intended.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Last I checked OSX does not support external video card for GPU acceleration yet. That is something you will have to wait on besides the limitation of Thunderbolt bandwidth for GPU usage.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

Page 2 of 62

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy