![]() ![]() With Silverstack Lab just coming out, I did NOT expect them to have the time to offer me a useable solution. They sent me a custom build within 2 days that fixed the issues for me and got me through the end of the feature I was working on without further incident. I found a few bugs in LiveGrade and emailed them 3 weeks ago. Hey Matt, make sure to email Pomfort's support. Am I safer reverting back to Silverstack 5 from my offloading/dailies transcoding on this next project? I’m supposed to start a new 6-week feature on Tuesday and now I'm not feeling comfortable to use Silverstack Lab again.Īnyone know what the problem could be on those transcodes? Silverstack lab is still only a few months old. Source is set to Debayer and Default (GPU). We were transcoding 3.2K ProRes camera originals from an Arri Amira and an Alexa Mini to ProRes 422LT 1920x1080 editorial proxies. I don’t know the specs on the other DIT’s computer. I have a Late 2015 5k Retina 25-inch iMac with a 4 GHZ Intel Core i7 Processor, 16 GBs of Ram, and an AMD Radeon R9 M390 2048mb processor. The other DIT and myself both used the same Silverstack license, project file, and transcode preset - but we used different computers, both iMacs. Sometimes it’s green rectangles (I've attached an image) and sometime’s it’s a green flash that covers the entire screen. ![]() I just got a message from post that some of both of our editorial transcodes have green artifacts in them (the artifacts flash for a frame or two). I worked the second half of the feature and another DIT worked the first half. I'll see you next Sunday with fresh content.I just finished a feature as a DIT on which I used Silverstack Lab (version 6.0.2) for the first time. If you've been thinking about a similar purchase for similar reasons, I figured you'd appreciate hearing about my initial experience. But since I hope to keep this machine in production for at least 4 years, I think it was a decent purchase, even if it incurs the ever-present ' Apple tax.' I'm unsure if I could have gotten away with the less expensive 16-core GPU. ![]() As I push the controls, the scopes look like they're directly connected to my hands. The few extra millisecond delays are gone. ![]() I am happy to report that I'm not disappointed. So, I ended up spending a little extra on the 19-core GPU on the M2 Pro silicon. Unfortunately, you've got to pick the right GPU at purchase because you're going to live with it for its lifetime. That enclosure was the only gear that made the previous Mac Mini useful for software scopes.Īfter seeing how well the Mac Studio M1 Ultra works (with internal GPUs only), I took a chance on the new MacMini M2. When considering the new MacMini, I was worried about the lack of support for eGPU enclosures on Apple Silicon machines. It was an annoyance that seemed to come and go. I set mine up with an external GPU enclosure, but I always felt there was a barely perceptible lag between my physical inputs on the control surface and the visual update on the scopes. I was never thrilled with the last round of Intel MacMinis. Here's one bit of fresh content: I've spent the past week refreshing my computers, including a new assist station that hosts software scopes. My weekend is occupied catching up on other matters, so I'll return next Sunday with an all-fresh edition. This is a re-send of last week's Newsletter. ![]()
0 Comments
Leave a Reply. |