Quantcast
Channel: Adobe Community: Message List
Viewing all articles
Browse latest Browse all 97529

Prelude frustrating to use for large projects

$
0
0

Rather than improving my workflow, Prelude is frustrating to use and I'd currently rather ingest media directly into Premiere.

 

1) It sometimes takes over a minute for Prelude to become responsive after switching back focus from another application (ie Premiere).  I can't afford to sit at my computer for a minute while Prelude polls all the media slowly.  This was happening with media on a local drive and is getting worse with media on external drives.  This media polling needs to be faster.

2) When sending media from Prelude to Premiere, Premiere creates duplicates bins. It seems the Prelude to Premiere workflow is only intended to be used once when all media for a project has been created and is ready to ingest all at once.  If I send media in two separate sessions from Prelude to Premiere, Premiere creates duplicate bins and I'm forced to manually merge all the bins or have a very confusing bin structure in my Premiere project.

3) Prelude seems to recreate peak files for media when I load a project.  This reduces it's performance (and my computer's performance dramatically) when it's constantly generating peak files.  Maybe Prelude just never generates all the peak files upon ingest and decides to do the rest of them the next time you load the Prelude project?  Regardless, something is wonky with peak file generation.

4) 'Sending' media from Prelude to Premiere takes too long and there is no status bar.... just an unresponsive Prelude and Premiere application.  Why does sending meta data for 60 media files take 30 seconds for a powerful computer to process?  Something seems very inefficient and this will only get worse as the media for our project grows.

 

Has anyone at Adobe tested Prelude with feature film projects with lots of Red r3d media?


Viewing all articles
Browse latest Browse all 97529

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>