Forum Replies Created

Page 5 of 8
  • Thanks for your input, Danny!

    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.

  • When I create a DDP output file set from the project, layer 1 is 3.52 GB; Layer 2 is 3.51 GB. I’ve read that according to the DVD specification, “the lower layer (Layer 0) needs to be as close to 4.1 GB as possible”. Not sure how close “as close as possible” is, but I don’t see any way in Encore to adjust what gets written to the first layer, other than the limited ability to set a layer break point.

  • James Kumorek

    September 9, 2013 at 11:50 am in reply to: ImageRenderer.dll Error / Iris Wipe causes CS6 crash

    I’m seeing the same problem — as soon as I try to change the border width on the Iris Star transition to something greater than 0, Premiere crashes. Did you find a solution to this problem?

  • James Kumorek

    September 8, 2013 at 10:26 am in reply to: Question about syncing audio and video

    Create a sequence that you specifically use just to sync the audio and video together. Then, right-click the sequence in the project window, and pick “Open in Source Monitor”. However, you may not see the audio waveform there. There’s something you can do to get the audio to show up (besides doing a “Render and Replace Audio” in any new sequence you put clips from the first sequence in), but I’ve only managed to do it by accident, and not figured out what it is. 🙁 I also haven’t looked very hard for it — it’s probably listed in the keyboard shortcuts, as it’s when I do something on the keyboard that it has happened.

  • What version of Premiere Pro are you using?
    How much memory does your system have?
    Run the GPUSNiffer.exe program in a CMD window (the program is in the Adobe Premiere installation directory). Does it say it will use your GPU?
    Instead of adding the GPU to the list, simply delete the file of supported GPUs altogether. Or make sure that the name the GPUSniffer program reports is exactly hwo you entered the name in the list.
    What’s your CPU utilization when playing back? What’s your memory utilization when playing back?

  • James Kumorek

    August 21, 2013 at 10:40 am in reply to: Budget Computer build for Vegas Pro

    Speaking more generally about one point — GPUs — how much a good GPU will help depends on what your timelines look like. Vegas has generally been good about being able to play back clips smoothly. Where a GPU can help is when you start scaling, compositing and applying effects — DEPENDING UPON how the application was written. I switched from Vegas to Premiere a year and a half ago, so I don’t know the current state, but I had found that Vegas produced incorrect results with the GPU support turned on often enough that I always had to disable it. Hopefully it’s better now. But many CODECS are not written to make use of the GPU for decoding/encoding, so you might not get an help there. If you’re not scaling and compositing much, you wouldn’t get much help. If you’re doing a lot of color correcting of clips, you might get benefit there. But for simply timelines, it probably would not have a big impact.

    I’m evaluating an nVidia K4000 now, it’s made a huge difference in Premiere’s performance. In one project where I do a lot of laying a color slide on top of video with the color at 50% transparency, then add text slides on top of it, with color correction added to all the clips, the same computer went from very stilted, low frame-rate playback with all six cores maxed out to completely smooth playback with 50% CPU utilization when I put in the K4000. But, if it was just straight cuts with no effects, it wouldn’t have mattered. The built-in CODECs that come with Creative Suite don’t use the GPU, so there’s no help in encoding/decoding.

  • James Kumorek

    August 21, 2013 at 10:07 am in reply to: 1920 renders with black bars on sides.

    If you really want your final output file to have a PAR of 1.333, then you should specify 1440 as your width, not 1920 (there’s probably a preset for this). If you want the full resolution 1920×1080 as your final output, the PAR should be 1.0.

  • James Kumorek

    August 19, 2013 at 10:36 am in reply to: Interview Lighting Gear

    I love kinoflows, but they are pricey. Otherwise, Tungsten lighting with softboxes.

  • James Kumorek

    August 14, 2013 at 1:44 pm in reply to: New Camera Confusion

    I use a Canon 60D and a Canon C100, but also have a Canon XF300, which I love for shoots where a really shallow depth of field isn’t needed, and the ability for the camera to have complete control of the lens (like zoom) is desired. The shots from the XF300 match reasonably well with the Canon DSLRs and the C100.

    I use the XF300 for my general video work, and switch to the C100 for specialty shots or where specialty lenses or shallow depth of field is needed.

    – Jim

  • James Kumorek

    July 24, 2013 at 11:59 am in reply to: Premiere Pro CC not relinking to graded footage

    I’ve only played a little with Resolve, and only gone from Premiere to Resolve, so can’t help with that. But, WRT the clip names in the timeline: when you add media to the timeline, a clip gets created with a default name that’s the same as the name of the media. However, those names are not linked — the clip name is independent from the media name. If you right-click on a clip in the timeline, you can there’s a rename option, which will change the name of the clip, but the media name remains untouched.

Page 5 of 8

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