Forum Replies Created

Page 4 of 8
  • I imagine you checked this, but any chance you have your program window view zoomed in for this sequence so that it’s actually larger than the program window? I’ve accidentally done this before, and scaled my video so that it “fills” the screen, only to realize later (like when rendering) that while it was filling the preview window, it was scaled smaller than the actual sequence size.

    How are you scaling it? Are you using the motion controls and manually adjusting the size? If so, try resetting the scale back to 100% and right-clicking on the clip(s), and picking the option that’s something like “scale to frame” (sorry — don’t have premiere in front of me at the moment). Does that give you the same result?

  • James Kumorek

    January 20, 2014 at 12:05 pm in reply to: Canon C300 footage into Premier Pro CC

    I have the C100, and have no problem using the MXF files in Premiere. However, if you are shooting progressive footage, Canon encodes progressive into the MXF file format in an odd way that confuses Premiere. After importing the MXF files into the Premiere project, right click on the clips (you can select them all and right-click just once), pick Modify, Interpret Footage, and force Premiere to use it as Progressive. Without doing this, Premiere will treat it as Interlaced, and you’ll get ugly aliasing artifacts.

  • James Kumorek

    January 13, 2014 at 6:28 pm in reply to: Echo in image after render

    Yes, this is likely the problem. Your media is 23.97 fps; you are rendering at 30 fps. So, a mismatch. You could also chance the render frame rate to 23.97fps and see what that does — it’s always best to render out the same frame rate as the project.

  • James Kumorek

    January 13, 2014 at 1:08 pm in reply to: Echo in image after render

    I’ve seen exactly this when Vegas things that the frame rate doesn’t match up with the frame rate being rendered, or frame rate of the project. For example, if I took 59.94 fps 720p footage and put it on a 29.97 timeline, and set the clip speed to 50%, I saw exactly this, because Vegas thought it had to “resample” the footage to get the right frame rate.

    Try right-clicking on the video clip being used, pick Switchers, and the Disable Resample, and see what happens.

  • I’ve done this for audio tracks, but subtitle tracks ought to work the same way.

    In the audio setup menu, when the user selects the audio track they want to listen to, the button links to the main menu, picking the selected audio track. Even though the main menu doesn’t have more than one audio track, the setting “sticks” for future selections, and thus plays the correct audio (or subtitle) track when a timeline is played containing that audio track.

    hope that helps!

  • James Kumorek

    November 26, 2013 at 12:46 pm in reply to: Something weird

    Pretty strange, at least that it’s playing through twice and not continuously. Any chance the “play video” button is set to auto-activate?

  • James Kumorek

    November 23, 2013 at 12:07 pm in reply to: Blu-Ray to DVD correct workflow

    I work in NTSC and not PAL, so these ideas may not be relevant…

    First, will the camera do progressive instead of interlaced? Shooting 25p and converting to DVD resolution in interlaced should look fine. That’s what my normal HD to DVD workflow is and it’s always produced excellent results.

    Another thing gto try is rendering your DVD video file as upper field first. The default for DVD is lower field first, but upper field first is also valid, and will match the HD media better.

    I hope one of those helps!

  • With the unsupported card, did you delete the text file in the installation folder that lists the supported GPUs? I don’t recall the name (because I have deleted it so that my K4000 card would e recognized), but at least on Windows it has “gpu” in the name, and contains a textual list of supported cards. If you don’t delete this file (or add the GPU name precisely into the list — but deleting the file is better), then Premiere will not use the card.

    Note that the supported list isn’t a list of the ponly cards that work — it’s just a list of the cards that Adobe has had time to extensively test. My k4000 (and K2000m) cards work great with Premiere and After Effects, once you delete the supported GPUs file in the case of Premiere, or add the card to After Effect’s card list (deleting the after effects file doesn’t seem to work).

    And, you have to do this again after each time Premiere or After Effects gets updated.

    Hope that helps!

  • After importing the clips into the project, right click on any or all of them, pick Modify, and then Audio Channels. You can them customize which audio channels get used, and in what way, when you add the clip to a sequence.

  • Thanks Bill, I appreciate the advice!

    I discovered what the issue was last night. I was burning the DVD+R DL media with my Blu-ray burner, which burned correctly and verified successfully. However, the DL media wasn’t being recognized by the players. When I burned the exact same ISO image with a DVD burner instead of a Blu-ray burner, it worked perfectly.

Page 4 of 8

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