Forum Replies Created

Page 1 of 3
  • Tom Small

    September 5, 2015 at 11:58 pm in reply to: Can’t access source settings on some R3D clips

    I found out adobe moved the settings in CC 2015. in the effects window you’ll see the red source settings under the Master tab. Keep in mind any changes will affect the entire master clip.
    Hope that helps

    Tom

  • Tom Small

    August 14, 2015 at 5:33 pm in reply to: Can’t access source settings on some R3D clips

    Same thing is happening to me. Can’t get to source settings from project window or timeline anymore in 2015. just tried reinstalling red cine x too.
    Anyone have any ideas?

    Tom

  • Tom Small

    June 19, 2014 at 1:35 am in reply to: PSD import problem

    Thank God for this answer. I’ve been pulling my hair out with the same problem.

    Tom

  • Tom Small

    May 26, 2014 at 7:17 pm in reply to: Premiere CC + Canon C300 MXF files

    I got 1080 to work by just copying the entire “contents” folder off the card onto my drive, and then just right-clicking in project window and importing it. Sequence settings confirm 1080 resolution.

    HOWEVER, when I tried using Canons backup xf utility I could not get it to work correctly. FYI

    Tom

  • Just got another new crash message:

    [../../../ASL/Foundation/API/Inc/ASLSharedObject.h-299]

    What gives?!?

    Tom

  • Ok it just crashed again. i’ve worked through that area once or twice successfully, but not tonight. crashed twice. the second time I got a new error message: [/ppro721/releases/2013.10/shared/adobe/MediaCore/AudioRenderer/Make/Mac/../../Src/AudioRender/AudioRenderContextConstructor.cpp-110]

    any thoughts?

    i just uninstalled the x264pro codec trial today. I don’t know if that has had anything to do with it but it should be gone now and the problem remains…

    Tom

  • One other note, I have a GTX 780 video card, and I updated the nvidia driver yesterday right after I got the one cuda error message, to see if it helped. so it’s the latest cuda driver.

    Tom

  • Thanks for the response Todd. I don’t know of any other multiprocessing choices in Premiere?
    I seem to have gotten the project working by doing several things, many of which I found on this site.

    deleted all cache/preview files.
    reset Premiere preferences.
    I pulled the files I don’t need for premiere out of user/library/quicktime/
    this seemed to fix the qt32 server that I kept seeing not responding in my Activity Monitor.
    I switched premiere from cuda to openCL since one time I had an error message about cuda (out of about 50 crashes).

    I re-exported the problem last 6 minutes of the show out of FCP7 and reimported that XML into premiere.
    repaired disk permissions on Mac HD.
    restarted and booted premiere, which rebuilt all conform and pek files.

    Seems to be working ok now. sometimes it lags when i jump around in the timeline and scares me, but seems to work eventually.

    Please let me know if you have any other thoughts. I reverted back to Premiere 7.2.1 as well, and actually have the desktop creative cloud app uninstalled at the moment since I thought that might be the problem. So who knows what the problem actually was. i spent about 10 hours working on this problem trying ever configuration and step i could find/think of.

    thanks
    Tom

    Tom

  • Thanks for the info. That makes sense… I’m not using many effects yet until I’ve got the animation all built, just key light so far.
    Yes I’m not sure why they sent me H.264 to work with- I would never choose that codec myself for AE…

    Good to know. Thanks again!
    Tom

    Tom

  • The audio is baked into h.264 files I received. I’m guessing this was shot on an EX-1, so not sure exactly the audio specs on that.

    When I turn of MP, ACTUALLY I just tried it again and it does keep the frames. Definitely a clue! Does MultiProcessing normally act like this?

    I have 96GB RAM, 12-core 3.46 xeon, GTX 780 3gb GPU.

    Thanks

    Tom

Page 1 of 3

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