[Jim Curtis]

Going from BRU to ArGest is a paid upgrade. In the past Tolis claimed ArGest is required for Catalina. Tolis was extremely slow in the past getting builds for new versions of OSX released. So, IDK if ArGest is supported on Big Sur yet. It has no mention of Big Sur capability on the OWC site.

Tim Jones posted a while back that OWC would honor existing BRU support contracts. But, given the long lapse between the closure of Tolis and the appearance of ArGest on OWC, who knows if the service contracts went into suspended animation during that lapse or not.

[Jim Curtis]

Thanks for your input, Neil.

My ATTO / E8 combo isn’t a JBOD. It’s a RAID, and I’m running it as a RAID6 currently.

You are correct that ATTO has discontinued calling their RAID adapters by that name, and are calling them HBAs. They’ve also discontinued the 6 Gbs line for 12 Gbs products.

If I end up needing a new PCIe HBA, I’m going to need to reformat the drives in my RAID and get a new enclosure and cables. ATTO has also discontinued SAS connectivity for Mini-SAS.

Therefore, having a completely separate backup RAID in my QNAP seems like a keeper of a plan. I’ve only run a few tests editing off the QNAP, and I’m confident the i/o speed will be adequate for 4K editing should I need to use that device for editing should I need to put it in service for that.

Sorry for my tardy reply. I had notifications disabled.

[Jim Curtis]

ArGest Backup has finally appeared on the OWC site: https://software.owcdigital.com/argest/backup/

[Jim Curtis]

It’s been nine days since you posted, and may have figured it out already, but this sounds to me like you have some corruption that’s causing Pr to go into Not Responding mode. First thing I’d do is start a new Project, and Import the old Project entirely, or Sequence by Sequence until the issue recurs, and then you might narrow it down to a Sequence, footage, effect, etc.

Just a few days ago, I was having Ae freeze up whenever I clicked a certain Comp that Ae didn’t like. Pr has frequent corruption issues for me. One bad effect or asset can bring the whole session to a stop.

[Jim Curtis]

It depends. You may have to keep an old computer around to use them. Some OS updates are incompatible with older versions of Adobe (and other) apps.

[Jim Curtis]

You can’t remove the CPU/GPU from the equation for compressed codecs, because there’s an inevitable amount of processing needed to decompress compressed video on the fly. RAW formats are especially hard on processors.

If you’re still shopping, my advice is to buy a lot more computer than you think you’ll need, because every year, it seems, it’s 8K, 12K, 16K, and so on.

My deal is to spend money until it hurts, because I’ll be glad I did later.

[Jim Curtis]

If you invoke the Make Movie command (or whatever it’s called – CMD/CNTR-M), the export window will usually tell you if you have off-line media. Then, you can cancel, and find it.

I’m not sure if Pr does this, but in some NLEs, you can run the Find command (CMD-F) on the timeline, and enter “offline,” and it will highlight them.

[Jim Curtis]

Last week, I had a 14.9 project that I could not re-open. Pr would go into Not Responding during the Open process. I had to start a new project and import the old one in to resume work. I did that eight or ten times.
I tried the usual troubleshoot routines to no avail. What finally fixed it was that I ran the Delete Unused command.

I was also having trouble with Proxies not playing via Transmit. So, deleted all the proxy media completely off my RAID and disconnected the link relationship in Pr, but the original files were still showing up on my Sequence as proxy media. More an annoyance than a job stopper. Just another incidence of one step forward, and two steps back for Adobe Premiere.

Anyway, I haven’t allowed any bugs in Pr to keep me from delivering a project on time, yet. Being able to downgrade to a prior version can be a life saver.

Good to hear you’re back in business.

[Jim Curtis]

Your plug-ins may / probably have preference files. You could try searching for those and deleting them. Sounds like something could have been left over after you uninstalled.

You could also try the trick of importing your project into a clean new project, and/or creating a new Sequence, and copy-paste your problem sequence into the new, clean one.

[Jim Curtis]

Thanks for the tip. Now that the chime is back, I’ve grown to like it. It’s like an old friend returning after a long absence.