[Tod Hopkins]

Providing any credit is a courtesy unless contractually obligated. I believe in credits when possible, but most of my films have no credits at all. In the case of public domain materials, the creator is probably dead, so a credit is meaningless to them. You could provide a general credit to WikiMedia or Creative Commons as a courtesy but that’s for providing the service, not the image.

[Tod Hopkins]

The symbol you refer to, the C with a circle slash simply means no copyright (aka public domain). That is, Wikimedia has determined based on the age of the original object, that it is no longer covered by copyright under the law. If you look at the license area, you’ll see something like this “This work is in the public domain in its country of origin and other countries and areas where the copyright term is the author’s life plus 70 years or fewer.” Which is their reasoning behind the public domain assertion.

The easiest way to determine that something is in the public domain is age, though the laws are complicated for anything not at least 100 years old. You can look up the details if you like. If a digital image is a faithful representation of the original, that is it has no added artistic value, then the age of the original is the only issue. You can’t copyright a photo or scan that is merely a faithful reproduction of the original. However, if there is added artistic value, say it’s colorized, or re-painted (forgery even) or collaged with other elements, that is a new work and the copyright of the new work is dated to when the new work was created.

It’s reasonable to assume these are both faithful reproductions of originals that are too old to retain copyright under US law, therefor they can be assumed to be in the public domain.

[Tod Hopkins]

In theory you don’t need a license for something in the “public domain.” Public domain means that there is NO existing copyright claim (for whatever reason) and therefore no license is required. Public domain status generally must be inferred from the facts. The most common examples are works that are simply too old to be protected by existing law. The only entity that can actively place something in the public domain is the copyright holder.

And this is where Creative Commons comes in. They have created a mechanism for explicitly placing a work in the public domain, known as the CC0 “designation.” This is not a “license” but rather a declaration by the copyright holder. CC is merely acting as the witness and record holder, making the declaration public and formal.

https://creativecommons.org/about/cclicenses/

“CC0 (aka CC
Zero) is a public dedication tool, which allows creators to give up
their copyright and put their works into the worldwide public domain.”

This may or may not be what you are seeing. Copyright is not simple.

[Tod Hopkins]

I doubt it’s the chip that is causing your specific problem. It sounds like playback buffer delay, which is likely software not hardware, and probably something specific to your project or sequence. Though I would check to see if any of your components have firmware or driver updates you should install. You should also start the process of elimination. Create a new project and new sequence. Throw some random stuff in, bit by bit until you see the problem. If it happens right away, probably system and not project or media. If it appears after you’ve added something specific, that may be your problem. If it doesn’t appear, it’s specific to your project or timeline. In the original project, try new sequences. Try dividing up your existing sequence or cutting and pasting portions into a new sequence. If it happens in some versions and not others, there’s something in the sequence causing the problem. Divide and conquer. Does it happen if you are fully rendered? Does it happen anywhere in the timeline or only in some places?

[Tod Hopkins]

Yes, Playback Buffer Delay is definitely an Avid thing. Here’s a discussion of some possible reasons, including a mention of early Ryzen CPUs.

https://community.avid.com/forums/t/198737.aspx

Cheers, tod

[Tod Hopkins]

Soundly appears to be designed to work as you describe so it seems unlikely that it is causing the problem, but I am not familiar.

[Tod Hopkins]

Your audio may be the problem. This is out of left field, but I had similar problems caused by multi-channel source audio that the NLE (not Avid) found particularly difficult to handle, even when only the video track was included in the sequence without the audio. The fact that the original clips were very long also contributed. I solved the problem by converting the clips to standard stereo. There were only two active channels in the source so this was not a problem for the workflow.

In short, never discount the possibility that the problem is your source audio. It happens.

[Tod Hopkins]

Larry Jordan just released a good article specifically answering this question. It does not contradict the advice given here but is a much more detailed explanation of the whys, wherefores, and options to consider. https://larryjordan.com/articles/configure-a-new-mac-studio-for-video-editing/

[Tod Hopkins]

Not necessarily. The speed difference between the internal and a fast external is not enough to outweigh using two drives. It is faster to pull from two drives than one drive. Asking your single system drive to do ALL the work is not ideal. Keeping projects and media on a separate storage device from your system drive is still the recommended practice.

[Tod Hopkins]

The internal drive will be faster than any USB3 drive and most other externals. You need thunderbolt-connected NVMe or an array to get faster. That said, you should still separate your data from your system. Apps and caches on system, but projects and media on external drives. You want to spread the drive load, even on fast drives. I’d also advise the 1TB for space. Mac OS and its apps love to default to the system drive for everything. My system drive has 440GB and I avoid storing data on it and periodically clean it. My App folder alone is 90GB, and that’s just the apps, not all their associated support files, preferences, caches, and so on. If you want to play World of Warcraft (or anything like it) that’s easily 50GB by itself.