Forum Replies Created

  • Alyssa Barber

    January 29, 2009 at 7:13 pm in reply to: Timeline crash-up! Argh!

    Hi, Tim,

    Yes, I found a solution, but not before having to do some searching. Apparently, there’s some annoying features of Encore that you have to read the fine print of the Sys. Req. on the box to really understand. One of those was about the video card or the processor on the computer–something like SSDE enabled (I don’t have the box right in front of me, but it says something close to that). In searching a few older forums, I find out that before a certain date, the Athlons, one of which I have, were not compatible and to this day at least one model is still known to have a few issues. But, my Athlon made the cut-off date, so it was enabled, but still a problem. What to do? Just update the driver. It was a hardware issue all around–I was trying to run super-new software on hardware that hadn’t been updated since 2005. If you’re really into updates after you get started, there’s lots of programs online that will tell you which drivers are out of date, and download the updates for you (saving the old ones in case of an error). There’s also a lot of registry repair software, too, if your machine seems a bit sluggish. Just be sure to get a reputable one if you go that route.

    Not to be off-topic, but since we’re on the subject of hardware, what’s the best way you’ve found of archiving data before removing it from the hard drive? An external drive, or DVD? And don’t DVD’s also degrade over time?
    Sincerely,
    Alyssa

  • Alyssa Barber

    December 19, 2008 at 3:24 am in reply to: Timeline crash-up! Argh!

    Hey,
    Thanks, Joe. I’m using version CS4. I did just what you said, got rid of the .xml file, and when I tried Encore again (creating a Timeline in a totally new project file), I got to actually see what the timeline looked like this time before it crashed, same way–just a total immediate shut-off. I wonder… Premiere crashed on me until I updated Quicktime to the most recent version. Is there a program I should be updating for Encore that I don’t know about (I did update Java, if that helps)? Again, my plea–has anyone ever had this type of problem, and if so, what did you do?
    Sincerely,
    Alyssa

  • Alyssa Barber

    October 15, 2008 at 6:04 pm in reply to: Exporting to HDCam framerate

    Dear Tim and Jeff,

    I’ve been talking to a couple of people who work at Adobe, and I’ve tried what they suggested as well. They were of a different mind on interpreting the footage, for instance. Nothing seemed to help. Even in the tests I ran, with blank frames added to the sound, it still ended up mis-timed. In the end, they suggested that I might have discovered a bug in the program, and that I try the upgrade. They also think it might be the codec. I did not tell them that I had run the render at 23… both with and without the codec, and the sync/length came up the same both times.
    Undoubtedly you’re using a more advanced version than I am. Is the functionality with regard to frame conversion to HD and sync any better in CS4?
    Thanks again for giving my problem so much of your time.
    Sincerely,
    Alyssa

  • Alyssa Barber

    October 13, 2008 at 5:17 pm in reply to: Exporting to HDCam framerate

    Hi, Tim,

    Thank you so much for answering my post. I tried what you said and did the following:
    1) Render an .avi from the 24 fps (synced) composition, at 24 fps, no codec.
    2) I imported it into a composition set for 23.976 fps, “Video for Windows” editing mode (I only get that or DV mode, no “Desktop”).
    3) Then, I interpreted the 24 fps movie as 23.976 and dropped it into the comp window.
    4) Now, the picture was indeed longer, longer than the original soundtrack, but my mixer provided me with a mix that was stretched by 8 frames. That one fit.
    5) There were only two small areas where the sound was off by two and one frame respectively. I added/subtracted a couple frames in those areas without affecting the overall length.
    6) I re-rendered the 24 fps .avi with edits–at 23.976 fps, using the codec. After importing that one into the comp, though, I found it to be three frames shorter than the edited 24 fps .avi. This 3-frame discrepancy is consistent with what I have been seeing all along–the 23.976 .avi is always 3 frames shorter than its 24-fps counterpart, with or without codec. Right now, I am going to import some other sound mixes with slight length variations to test them against this new .avi. But I’m not really confident this is going to work. Have I done everything you said correctly?
    Thanks again! If you have any other suggestions, please don’t hesitate to write.
    Sincerely,
    Alyssa

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