Forum Replies Created

Page 25 of 413
  • John Pale

    November 30, 2017 at 2:06 am in reply to: CC 2017 is absolutely driving me nuts!

    Try updating your Kona firmware.

    FWIW, I sold my AJA Kona on my home system because it performed poorly with Adobe CC. Random freezes and issues stopped when I switched to Blackmagic. AJA was better with Avid and FCP, but with Adobe it just wasn’t great. At my day job, they use AJA iO 4K’s. They were glitchy too, but a bit better with recent versions of driver/firmware. On Adobe CC2018 now.

  • John Pale

    November 28, 2017 at 5:12 am in reply to: “Intel Iris Pro GPU with 128 MB”

    It shares your system RAM instead of dedicated VRAM.

    This is not a great computer for video editing.

  • If the audio layout of the proxy doesn’t precisely match the original clip it does not work. Make sure the proxies were correctly created and named (with _proxy appended at end)

  • John Pale

    November 23, 2017 at 4:04 pm in reply to: Show me your BINS

    As an aside…

    Seems like every editor…no matter what NLE…has to do little tricks with numbers or odd characters to get the folders and bins to sort in the order they want them. Would seem by now we be able to do that without such nonsense. For instance, in Premiere, you can drag individual workspace names so they appear in a certain order in the interface….why not extend that to bins and folders in the project pane?

  • Jimmy,

    You cant change a stereo sequence into a multi channel sequence. You can create a new empty sequence that is multichannel, then copy and paste the entire old sequence into the new one.

    In the future, make a preset that is multichannel (Sequence Settings/Audio/Channel Format/Multichannel) , and only edit using that, even when working in stereo. Just set the output to 2 in the lower left corner of the timeline or in the track mixer, when working in stereo. Don’t use stereo sequence presets anymore. Just multichannel.

  • Definitely don’t keep the panel off. The case is designed to direct airflow in specific ways.

  • John Pale

    November 14, 2017 at 4:16 am in reply to: Timecode effect on Adjustment layer bug

    I just tested it. You are right. It appears to be a bug. If it wasn’t meant to work with transparent video or adjustment layers, why does it have a selector for the source video layer?

    For what its worth, I tried it directly on clips, and occasionally, its still reading the wrong timecode. WTF?

  • I upgraded my home system from a 2.23 x 8 core to a 2.93 x 12 core. Currently have an Nvidia GTX970 GPU.

    This system outperforms the Mac Pro trashcan I use at my day job. I got the 12 core CPUs cheap and I did the upgrade myself. It was very much worth it, in my opinion.

    You are upgrading to even faster CPUs, so the performance should be better. My one worry on what you are doing is power consumption and heat issue. If you are using multiple PCIe cards, a beefy GPU and maxing out the RAM, you might run up against what the Mac Pro tower was designed to handle.

  • John Pale

    November 13, 2017 at 12:58 am in reply to: Timecode effect on Adjustment layer bug

    I see what you are saying now. Sorry for misunderstanding.

    The timecode effect in Premiere has a source track setting. Are you saying that when you apply it to the adjustment layer and set it to Video 1 , it does not display the correct timecode? Not able to test myself at the moment.

  • John Pale

    November 12, 2017 at 7:04 pm in reply to: Timecode effect on Adjustment layer bug

    This can be added in Media Encoder. You don’t need to add an effect to the sequence.

Page 25 of 413

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