Forum Replies Created

Page 43 of 107
  • Greg Janza

    May 31, 2018 at 5:58 am in reply to: Glitchy/Stuttering after rendering

    [Andre Cruz] “Well, someone’s not reading properly… I said i am an Editor for the channel, so i have no control over the source material and it being 900p.”

    As the editor, you need to communicate your needs to the content creators so that the edit can have a smooth workflow.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 30, 2018 at 2:42 pm in reply to: Glitchy/Stuttering after rendering

    Thanks for the stills.

    Premiere doesn’t support VFR. Also, you’re adding potential problems by not capturing in 1920×1080.

    Change your capture software and capture in HD with CFR.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 30, 2018 at 4:28 am in reply to: Glitchy/Stuttering after rendering

    There’s so much going on in the frame in each video that it’s nearly impossible to spot the issue.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 28, 2018 at 1:15 am in reply to: Premiere crash… and crash… and crash

    Possible solutions:

    Start a new project, import a few sequences from your main project into the new project and attempt to work with isolated sequences to see if the crashes end.

    Also, can you consolidate some of your media so that you’re not dealing with such a large amount?

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 27, 2018 at 3:53 pm in reply to: Premiere crash… and crash… and crash

    Your computer is very underpowered which may be contributing to your problems.

    Any chance you can move to a more robust computer?

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 24, 2018 at 12:16 am in reply to: The Real Menace of FCP X

    [Simon Ubsdell] “It has also, to my mind, all but killed what was worthwhile in this forum, which at its best has hosted some outstandingly good discussions – conversations that grew out of a shared appreciation of the endlessly fascinating plurality of the world, conversations that are strangled at birth by the tyranny of a single dominant ideology.”

    Those that continue to be obsessed with spouting endlessly about the greatness of one NLE over another are losing sight of the forest for the trees. Editing is all about the craft of storytelling and so whatever device allows one to tell a great story is the right device.

    I also agree that speed is not the end goal. Putting video pieces together takes time. Not because the equipment used is slow but rather because you need to look through the material over and over and over to get a feel for what it is you want to build. Then you have to revise and revise and revise to make it good. This takes time and it’s ok. I don’t judge my success on how many pieces I edit in a year. I want the pieces I do cut to be as compelling to a viewer as possible because if they aren’t then I haven’t done my job very well.

    Many editors who don’t use FCPX as their main edit tool at least respect that it has a lot of to offer. End of story.

    Now back to the real thing that we do as professionals – tell stories. A conversation about how folks approach building story arcs and how they assemble pieces for maximum impact on the viewer is about a thousand times more interesting and relevant to me than which NLE they use to create that story.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 23, 2018 at 1:12 pm in reply to: Calling all Super PC and Adobe CS5 Nerds

    Go to the Adobe hardware forum and search out dual GPU. There’s a fair amount of discussion as to whether you’ll see any real performance improvement. The number of GPU CUDA cores is a primary determiner of efficiency along with your GPU being able to utilize the maximum lanes- i.e., 16x

    Also on that forum there’s been numerous posts advocating that putting your OS on a m.2 is not optimal. Save the m.2’s for media.

    If you’re going to be working with 4k media I’d advocate upping your RAM to 64 gigs.

    Lastly, you can save yourself a lot of future frustration if you think in terms of transcoding all 4k H264 and H265 media to an edit friendly codec prior to edit.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 22, 2018 at 2:46 am in reply to: Towards a better NLE

    I now edit everything pancake style and I think it makes for much more efficient editing. I also think it’s faster to drag and drop clips instead of loading the timeline into the source side and editing it into my real timeline.

    Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Greg Janza

    May 21, 2018 at 2:30 pm in reply to: PP extremely slow despite decent HW

    [Mike Tyler] “- 16 GB 1600 MHz DDR3
    – NVIDIA GeForce GT 650M 1024 MB / Intel HD Graphics 4000 1536 MB”

    These are the two weak aspects of your setup. If you’re working with 4k media you need at least 32 gigs ram and you need a powerful GPU.

    Also, transcode the 4k if it’s H264.

    Windows 10 Pro | i7-5820k CPU | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • [Neil Goodman] “trip down memory lane.. 6 years later – here we are stuck in virtually the same place.”

    If FCPX is truly the greatest thing since sliced bread it’s sure taking a long time to get the word out.

    Windows 10 Pro | i7-5820k CPU | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
    Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

Page 43 of 107

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