Forum Replies Created

Page 65 of 129
  • Dennis Radeke

    December 18, 2012 at 11:31 pm in reply to: Rendering time?

    You can also try encoding through Adobe Media Encoder. It supports batch encode, multiple presets, etc.

  • Dennis Radeke

    December 18, 2012 at 2:31 pm in reply to: Need Opinions on CS6 Edit Computer Proposal

    Looks fine except I’d suggest more RAM. 32GB is not a stretch.

  • I honestly don’t think it’s a bug from Adobe but something going on in your system. However, I’d request that you try and post the project (or a portion thereof) online somewhere and contact me privately and let me have some Adobe techs look at it.

    Dennis

  • Dennis Radeke

    December 17, 2012 at 7:21 pm in reply to: Importing footage with different ratio & frame rate

    Don’t sweat the frame rates. We mix different frame rates very well. Down load the trial and test it out.

    Dennis – Adobe guy

  • Dennis Radeke

    December 17, 2012 at 2:11 pm in reply to: Relinking lost audio from .m2ts files
  • I agree that moving up to 29.97 is probably the smoothest choice if you must convert to one format. If you have Production Premium, test Adobe Media Encoder for quality. If it passes or is superior to Compressor, it will process your files quickly in the background. Premiere Pro mixes all of the frame rates natively on the timeline and does the proper pull up/down when you’re encoding your final output.

    Dennis – Adobe guy

  • Dennis Radeke

    December 17, 2012 at 12:34 am in reply to: FCP 7 – Huge Edit – Organizing Media

    [Tom Valens] “so theoretically you have more RAM available and are less likely to crash”

    This is true for a number of reasons. Ultimately, every asset in a project takes up a little bit of memory to know where it is, have it ready, etc. Also, RAM is SUPER important for 64-bit applications like Premiere Pro (or FCP X or Avid for that matter) for performance because with FCP 7 you can have 12 cores but only 4GB Of RAM service those 12 cores so you end up starving the CPU’s for RAM. It’s a classic 32-bit bottleneck that Premiere Pro also suffered from prior to CS5.

    [Tom Valens] “One difference is that you can have multiple projects open at the same time in FCP 7, but only a single one at a time in PP (though as I understand it, it is relatively simple to open one project, copy something, close it and them open the main project and copy that in”

    In Premiere Pro, you can import a single sequence or the entire project and add it to an existing project. When you do that, it will bring in all of the assets associated with it in a folder. Also, you can import FCP XML into Premiere Pro to add to a project or get started from an FCP 7 project as well.

    [Tom Valens] “I think PP because I’m guessing the learning curve would be easier than starting from scratch with the different editing model of FCP 10.”

    Each person’s experience must be their own, but in general most people agree with you. One thing Premiere Pro does is provide FCP7 keyboard shortcuts to help shorten that learning curve even more.

    And in the effort of clarity…

    Dennis – Adobe guy

  • Dennis Radeke

    December 16, 2012 at 5:29 pm in reply to: First Two Frames Wrong After Rendering

    Clean your media cache in prefs and delete all renders in the project(?) menu. Sorry, on an iPad at the moment…

    Dennis

  • Dennis Radeke

    December 16, 2012 at 5:27 pm in reply to: Relinking lost audio from .m2ts files

    Try trashing your prefs…

  • Dennis Radeke

    December 16, 2012 at 5:26 pm in reply to: Stereo Audio Track Issue

    You can set up a sequence and project where stereo, interleaved audio can be represented as dual mono. You need to change the default audio handling in preferences and the track settings in the sequence settings. I’m on my iPad at the moment so I would encourage you to google for a tutorial as I know they are out there…

    Dennis

Page 65 of 129

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