Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Timecode always 00;00;00;00

  • Timecode always 00;00;00;00

    Posted by Ray Balhorn on March 25, 2008 at 10:14 pm

    Not sure what is going on.

    Recently, I went to capture in a clip, set the in and out points and capture the clip. Everything seems to work just fine. I look in the project pane and the media start is set to 00;00;00;00! I click on the properties which shows

    AVI File details:
    Timecode: 00;01;37;01
    Reel name: ‘Tape 1 Nuero-ophthalmology Infra-red’
    User Timecode: 00;01;37;01
    Reel name: ‘Tape 1 Nuero-ophthalmology Infra-red’
    Contains 1 video track(s) and 1 audio track(s).
    Interleave: 1 : 29.00

    why wont it show the correct starting time of 00;01;37;01 ? SO now it does this on every tape I try to capture from, if its more than 30 minutes in length. I have a ton of edits that eventually will need to be batch digitized but this will make things very difficult when I need to do that.

    Is there anyway to get Premier to read the correct time code?

    I have tried two different decks for capture an Cannon XL1 and a Panasonic AJ-D250 both giving me the same problems. Timecode is continuous on the tapes. I can capture up to 30 minute chunks and get the time code just fine. If I try to do any more the timecode get set as 00;00;00;00 again. I have also tried different tape stocks (DV and DVCPro) as well as drop frame and non-drop frame.

    Again, if I open up the files in DVMedia I can see the correct timecode.

    As a work around, what I have been doing is manually setting the timecode by going to file > timecode. Once I set it to the correct in time, everything works fine… until I close the program and open up the project again, when it sets everything back to 00;00;00;00. ugh! I am beginning to hate PPro!

    Is there anyway to get the metadata for these clips to be read correctly??!!

    I have also uninstalled and re-installed PPro CS3 which didnt fix the problem. I have made numerous new projects to see if its a corrupt project, and I still get the problems :(.

    Thanks for any help.

    FYI:
    I have a Dell Precision 670. 4x 3.0 Processors, 2 GB Ram, Firewire on board, NVidia 8800GTX. XP Pro.

    Ray Balhorn replied 18 years, 5 months ago 3 Members · 3 Replies
  • 3 Replies
  • Jon Barrie

    March 25, 2008 at 10:35 pm

    I have found this timecode bug a while ago, along with others, and it continues to frustrate the s**t out of me, cutting a long form project from notes made by the producer from a VHS master with BITC – (Done before I got involved).
    I have posted it on adobe’s bug site, but it seems to be not that frequent an issue for them to bother fixing it.
    I want to make a bug listing on the cow so we can use the power of the cow to beef up (pun intended) the voice of PPro users wanting a PROFESSIONAL editing application.
    Will you join me in this protest to adobe to make a fully functional 3.5 version before they even think of releasing a v4?
    – Jon 🙁

    How many editors does it take to change a light bulb?
    http://www.jonbarrie.net

  • Vince Becquiot

    March 26, 2008 at 1:33 am

    Barrie,

    Yes, I think a (moderated) Bug list, as well as a sticky for FAQ would be great. I guess that would be a Ron request…

    There are a couple more I would add. Once being the fact that audio tracks pop sometimes with straight cuts (very annoying), and QT animation import audio seem to go in and out in the preview and on timeline randomely, hmmm… and let’s not forget the issue that doesn’t allow you to put P2 clips offline and back online without a crash.

    Vince

  • Ray Balhorn

    March 26, 2008 at 4:48 am

    “Will you join me in this protest to adobe to make a fully functional 3.5 version before they even think of releasing a v4?”

    of course. I have also submitted a bug report as well as comments to the online help. I am going to check PPro 1.5 to see if the issue is there as well, but there wasnt before. I think this is a PPro 2-3(CS3) bug.

    Sad but honestly PPro 1.5 was the best working version they had (minus the HDV issues which I never use). I wish they didn’t phone in PPro 2/3 they way they did.

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