Forum Replies Created

Page 3 of 6
  • Matt Jones

    April 21, 2009 at 5:49 pm in reply to: Keyspan machine control

    I called Keyspan TS and they sent me the correct drivers. It’s working again. Yeay.

    Matt Jones
    Metro Productions, Inc.
    Raleigh, NC

  • Matt Jones

    March 4, 2009 at 9:21 pm in reply to: crashing during export

    Thanks Wick, I’ll send the report. I’d love to know what happened. I still don’t know why my media changed from nice interlaced DV to steppy dark footage which crashed while exporting.

    Here’s what I did:

    Once I moved the media to a new drive and got the same old crash, I asked my client to bring her drive in with the original media files on it.

    I opened the PGM in a new project and re rendered all of the titles and transitions. I then closed the project and switched out the suspected corrupted files with new copies.

    They had the exact same name, same size, same file (except not corrupt) I re-opened the project and all of the clips from those media files were offline. Not sure why they wouldn’t relink.

    I imported the new copies of the old media and went through and replaced each cut one by one, using the timecode values to make sure I got the edits the same.

    I’m extremely happy to report that I was able to export all files as ref files and make my compressions on time.

    What can we all learn from this? Beats me. I thought I did everything right from the start. DV footage in, DV codecs rendered, export ref files…

  • Matt Jones

    March 3, 2009 at 8:30 pm in reply to: crashing during export

    Nope. same thing. crashola.

    I have the “problem report” Can we work it out from there?

  • Matt Jones

    March 3, 2009 at 7:48 pm in reply to: crashing during export

    Thanks for clearing that up.

    I’m moving 36 GB of media now. Keeping my fingers crossed.

  • Matt Jones

    March 3, 2009 at 7:31 pm in reply to: crashing during export

    It says “DV/DVCPRO – NTSC”

    Which makes me think it’s the same thing.

    In the codec settings you can setthe compression type for aquire and render to 3 settings. They are: “DV”, “DVCPro” and “DVCPro50”. Which makes me think DV and DVCPro (25?) are different.

    So which is it?

    As far as M100HD goes, are they they same or should you use different render settings for each?

  • Matt Jones

    March 3, 2009 at 4:32 pm in reply to: crashing during export

    I’ll try it. Just a couple of questions:

    What about the difference in the original DV footage and the footage in the timeline? (dark, steppy footage in timeline) Has that been rendered to another codec? Is it DV, DVCPro25? What’s the difference? Does M100HD edit DV natively?

  • Matt Jones

    March 3, 2009 at 2:29 pm in reply to: crashing during export

    I agree. something’s not right.

    I have been using the m100i lossless codec exclusively since it was released. I don’t normally work with DV files and when I do it’s files that I have produced. Is there a difference between DV and DVCpro codecs? I know DVCPro50 is different.

    I do think I’ve got at least one corrupt file. Quicktime won’t play the file, but the M100 program containing a clip from that file will play on the timeline. I think it’s playing because it’s playing a rendered file, not the original media.

    I’m all about switching the media to another drive if you think it will help. Exactly how would I “start over”? Is this right?

    1. Delete media locations
    2. close project
    3. move media to new drive (delete rendered files?)
    4. open new project, select new drive and codecs
    5. open old program
    6. render qt/titles/trans

    Many thanks.

  • Matt Jones

    March 2, 2009 at 10:08 pm in reply to: crashing during export

    After crashing and restarting AGAIN, I noticed that all the original files now have gone back to just the .mov extention.

    I imported one of the orignal files back into the project and compared it to the same clip in a program and it looks much different.

    The clip in the timeline is darker, and looks steppy, kinda like the old draft video mode in M100i. So M100HD is doing something to the DV video, and I’m not sure why.

    You can also tell the difference when you’re watching playback and there’s an overlay that’s been rendered in the past. So it’s dark and steppy, hits the rendered overlay, looks like original video with nice overlay, and then goes back to steppy dark video when the overlay fades.

    I’m thinking of dumping all of the “media locations” and “unrendering” all video, closing the project, and then relinking and re rendering all the overlays.

  • Matt Jones

    March 2, 2009 at 9:40 pm in reply to: crashing during export

    Vol verfified. no problems.

    I noticed that the original file titles have been changed. each “.mov” file now has “.mov.rend”

    My customer had DV footage. I selected DV codec for aquire and render. I imported the files. They “updated” as they were imported, rather than building “NTSC track….” So I thought I was editing them in native DV, not transcoding them to another codec.

    So now I’m trying to export them out as DV ref files with titles and dissolves, all rendered in the DV codec. Why does it have to render the video tracks as it exports a ref file? Is this where it’s adding the “.rend” to the end of each video track’s title?

    Could it be an issue with the DV vs.DVCPro codec? It’s showing up as “DV/DVCPro – NTSC” in the bin view and from the Quicktime info window. Is DV the same as DVCPro25?

  • Matt Jones

    March 2, 2009 at 5:18 pm in reply to: crashing during export

    I just went and found the original source file. It won’t open in quicktime. QT says it’s an unrecognized file type. It’s so weird it plays fine from the timeline.

    I guess my last ditch effort will be to record the timeline video to betaSP then redigitize.

    I also thought about running Apple disk utility on the drive which contains that file. Any cautions on running disk utility on my G-SPeed eS RAID to repair permissions?

Page 3 of 6

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