[Greg Janza]

I know it sounds like heresy since Raid5 has been a default setup on many raids used by video professionals but there’s definitely a vocal group of engineers who believe if you’re going to use a raid option, Raid 10 should be the standard and not Raid 5. I use Raid 0 because my system is continually backing up.

Here’s just one article of many out there explaining why Raid5 is so problematic:

https://www.askdbmgt.com/why-raid5-should-be-avoided-at-all-costs.html

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

[Greg Janza]

Another option, OWC Thunderbays. OWC makes a a great product at a great price. I’d suggest though that you build the raid yourself. Buy the Thunderbay case from OWC and then purchase four matching drives from Newegg. A 12 terabyte Thunderbay 2 can be built for around $700.

OWC now makes Thunderbay 3 raids but keep in mind that you won’t see any speed improvement from TB2 to TB3 unless you purchase SSD drives for the raid which is a significantly higher cost.

I’d also discourage the use of Raid 5. There’s extensive info on the web indicating that Raid5 is problematic and should be abandoned. Since Raids are relatively cheap, I’d simply buy two, use raid 0 and mirror them.

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

[Greg Janza]

Unless something has changed, Premiere has a long-standing bug of not correctly reading media file timecode when applying a window timecode reader. I first noticed this problem at least a year ago.

My workaround when I’ve had to create window burns of media files affected has been to adjust the starting timecode of the window burn. I don’t think the actual media file timecode is incorrectly interpreted by Premiere.

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

[Greg Janza]

I would stick to your plan. yes, proxies will make your workflow easier but when you switch back to the 4k material your computer will come to a grinding halt. Pro res will allow you to have both a fast rough cut and fast fine cut and mastering.

And that’s why converting all problematic footage to Pro res or DNxHD before you start is a great workflow overall.

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

[Greg Janza]

Open up your activity monitor while encoding one of your proxy files and you’ll see that the encoding process takes up nearly 100% of your CPU’s power and much of your GPU power as well.

If you’re going to be using the proxy workflow, plan ahead and batch create proxies overnight. Also, temper your expectations since you’re on a laptop and you’re working with 4k media from a single spinning drive. Premiere works optimally when you have a dedicated cache/render drive separate from your OS drive and a fast raid for media.

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

[Greg Janza]

Thanks for that info. The project I was describing was done at a client location and they must’ve been a version behind.

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

[Greg Janza]

I’ve seen this problem extensively on trashcan macs. the online consensus has been that it’s a byproduct of the graphics cards overheating.

One Solution that’s worked for me in the past is to render your timeline to pro-res and if you run into a problem spot, re-render that clip and re-export. Smart rendering will cause only the changed shot to actually be re-compressed.

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

[Greg Janza]

[Bill Davis] “OFF THE TRACKS was made by ONE guy who was sitting in Utah and had an idea for a story that interested him. Period. It started as a purely personal labor of love and grew organically from there. “

Bill it makes perfect sense why you’d be a strong advocate for the film since you’re in it and the film is mainly focused on the theme that FCPX is a revolutionary piece of software that’s simplifying and democratizing the industry.

I salute Brad for getting his idea from a story that interested him to a finished film that can be rented online. I’ve worked on several docs and I know that each and every doc is a herculean task to get made.

I also like FCPX. I had initial issues with the program but the few projects that I’ve worked on in FCPX have left me with a strong liking for the program and the architecture of it.

But I also think the criticism that has been raised in this thread about the film just being a glorified marketing piece is valid. The biggest failure of the film is it’s lack of a diversity of industry perspective. I don’t know if this was a matter of not being able to get access to Adobe or Avid team members to interview or if Brad really just wanted to stay insular to the FCPX world. To not have any post facility owners talking about the complications of signing onto FCPX and how that decision might affect their bottom line is a glaring omission. The film oversimplifies the myriad of reasons why many professionals jumped ship and went to Premiere and to a lesser extent Avid.

The film also suffers from having a lack of actual diversity. It’s nearly wall to wall white males. I’d also argue that a cut-down version of this film (20-30 mins) could get a lot more people to watch it.

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

[Greg Janza]

You’re posting a question about how to get your Premiere system to work like it did back in 2013 or whenever you had better response time overall. You’re desire to downgrade is a rare request.

Most of us on this forum are here to share info so that we can be better at our professional craft today and on into the future and that almost always involves upgrading. If you don’t get a suitable answer here perhaps you’ll be better served by one of the many facebook Premiere user groups.

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

[Greg Janza]

Going backwards might end up being more work than going forwards but that’s up to you.

Go to ebay and try to find CS6 and then try to find an older Mac OS somewhere on-line. Good luck with that.

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