[Brad Bussé]

I was between projects and recently upgraded from 13.1.2 to 13.1.4. Now when I open the latest versions of some of my most recent projects, Pr loads 75% of the way and then crashes but doesn’t give the usual error window with the option to send the log file to Adobe. My associate is also experiencing the same problem on his projects.

We’re able to open versions of the projects from a couple of revisions back, so we think the problem may be a compatability issue with projects that have FabFilter or Waves plugins applied. I updated Waves to latest and reinstalled latest FabFilter and reset Pr cache/prefs, but no go.

[Brad Bussé]

Is the architecture specific to the Core series, “QuickSync”?

What’s the thought behind leveraging the dedicated hardware decoding in the Intel Core series over leveraging the dedicated hardware decoding in GPUs?

[Brad Bussé]

The surround panner (dot in the square grid) is for mixing your channel within a surround space while doing a surround mix within Premiere.

What you want is to setup a designated sequence for delivery. So you need to create a new sequence that is set to multichannel. Take the final 6 channels of the mastered 5.1 mix and arrange them in the first 6 channels as listed in the delivery specs. Then take the final mastered stereo channels and add them to channels 7 (L) and 8(R) respectively.

Then export as a multichannel .mov (or whatever the designated spec asks for). It’s a good idea to reiterate the channel layout in the slating.

[Brad Bussé]

Welcome to the rabbit hole:

https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=73834

[Brad Bussé]

If there’s a possibility that you may switch your workstations to Windows in the future, I’d avoid the Motu and Apollo 5.1 interfaces–their Windows drivers are both terrible. Instead go with the Presonus Quantum TB2 or the Steinberg USB3.

[Brad Bussé]

Did you get any more information about this? I’m running into the same issue with a 4K DNxHR project in Premiere.

[Brad Bussé]

Yeah, I have a toaster but don’t trust it for cloning. I just use it for dual mounting. On Mac OS SuperDuper is good for doing smart backups and cloning. If you’re going bare drives, HGST are good–they come in vanilla, NAS, and Enterprise ratings. I use the NAS rated drives at home since they’re very affordable and middle of the road. You can also get a bare drive and an external case cheaper than a pre-built. If your motherboard supports USB 3.1 you should be able to power a 3.5″ 7200rpm drive through the usb cable just fine without requiring a transformer or brick.

[Brad Bussé]

Thanks, Michael. Yeah, I’d love for Resolve to add support for encoding ProRes too. Hopefully we’ll at least get read support for ProRes Raw in Resolve/Fusion in a couple of months when the Apple/Atomos six month exclusivity deal has passed.

Is there a chart showing which features standalone Fusion has which Resolve Fusion does not? I abandoned node-based compositing for layer-based about 3 years after Shake went eol, but am really looking forward to reintegrating it into my workflow.

[Brad Bussé]

Looks like I finally got this resolved. I added a dedicated SSD drive for Pr and Ae cache and preview files yesterday. That did not fix the problem. Then overnight I was batch transcoding and running parity maintenance on my raid array, and when I came in this morning Windows said it couldn’t see any of my drives. Turns out there is a daughtercard on my Dell Precision 7910 which hosts the SAS and SATA controllers which died overnight. It must have progressively been getting worse over time, creating the issues I’ve been dealing with.

Thanks for the help Roger and Greg.

[Brad Bussé]

So it seems that the amount of frames dropped when playing back a rendered section is directly relational to the data rate of the codec chosen for the sequence. So, the same 30 seconds of clips copied to new sequences, rendered, and played back shows:

AVCHD: 30 dropped frames
DNxHD 8-bit: 90 dropped frames
Cineform 10-bit: 450 dropped frames

But the thing is, I can open a source xavc or a transcoded DNxHR version of the source and both near the start of play will drop 4-8 frames but then play on without any dropped frames. Those sources are both 1080p30 just like the sequences and the source and preview video files are all stored on the same drive, so there’s something specifically about preview files in Premiere that is amplifying the playback problems.