Forum Replies Created

Page 2 of 9
  • Gina Sarentino

    February 6, 2015 at 7:10 pm in reply to: Exporting errors

    My render settings are my usual, H.264 HD 1080 with min bitrate 30 and max being 35.

    Im running on a HP elitebook 8770w 8 cores
    4GB Nvidia graphics card
    32GB RAM

    I tried rendering it in Ae queue and it will reach a certain point after 15 secs and the estimated time will stop moving ahead and so does the elapsed time.

    Im running adobe Ae and Pr and AME CC 2014. My AME is 8.2.0.54

  • Gina Sarentino

    January 10, 2015 at 10:29 pm in reply to: Rendering issues

    Thanks for the help Tim. Ill most likely interpret all the footages to 24fps and go ahead from there.

  • Gina Sarentino

    January 10, 2015 at 1:52 pm in reply to: Rendering issues

    Im only working in CC, I was just using Cs5.5 to see if I had any issues with my exports there.

    Im going to outputting to cinema and I have my 23.976fps with a few 24fps clips from Red camera, that’s basically what my sequence consists of.

  • Gina Sarentino

    January 10, 2015 at 1:43 pm in reply to: Rendering issues

    Thanks for the help Tim, just one last question. Do you think this glitch is just a problem with my CC, or is there an issue in the encoding and exporting process?

    Also for cinema I need 24fps, do you think itll be an issue if I export it as 23.976fps?

  • Gina Sarentino

    January 10, 2015 at 12:08 pm in reply to: Rendering issues

    Hi Tim sorry for the late reply,

    I ran the tests, here are the results:

    I brought the exported 24fps file from Cs5.5 to CC:

    1.the timecode goes up to 29frames in the source panel. In the Project window it shows that the video goes up to 24secs and 28frames.

    2.When I drag for it to create a new sequence, it creates this :

    ———————————————————————

    I now did the 3rd part. I exported a 23.976 video from Cs5.5, brought it over to CC.

    1.In the source panel it goes up to 23 frames, and in the project panel it displays the file as 24 secs 22 frames.

    2. I made a new sequence by dragging the file onto the new item tag, here are the results:

    I hope this helps, do let me know if anything further is needed.

  • Gina Sarentino

    January 6, 2015 at 11:26 am in reply to: Rendering issues

    Yes when I put double click the video it shows the 29 frame count on the source window.

    The file that I open in the source window isn’t in any sequence, but when I put it in my custom sequence (its a 23.976 fps sequence) it displays everything correctly in the source window. Am I making sense?

    I have myself created the sequence settings according to the files Im working with.

    I really appreciate your help Tim, if you could just guide me on what to do further to solve this issue it would be great.

  • Gina Sarentino

    January 6, 2015 at 6:45 am in reply to: Rendering issues

    Hi Tim

    I wanted to add a small note, as I was working today I noticed a small detail in this issue. Now im posting a photo below of what my timecode looks like when I bring in a exported 24fps file (the same file that shows upto 29 frames)

    Notice how the breakers are semi colons (;). I realized that usually these breaks between the numbers are colons (:). I hope this is not confusing.

    So then I put that 24fps exported clip into my timeline and I double clicked it to show it in the viewer, and everything is fine, in the viewer it displays a correct timecode, and the breakers are colons (:). But in the project window it displays it inaccurately.

    I hope this is not confusing.

  • Gina Sarentino

    January 5, 2015 at 12:28 pm in reply to: Rendering issues

    The photos after the cs 5.5 settings are what I get when I take that cs 5.5 export into cc2014.

  • Gina Sarentino

    January 5, 2015 at 6:18 am in reply to: Rendering issues

    Settings in Cs5.5

    Results in CC 2014

  • Gina Sarentino

    January 4, 2015 at 11:29 am in reply to: Rendering issues
Page 2 of 9

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