[Craig Seeman]

Compressing a video always causes loss and compressing twice is more loss. As to how visible depends on a number of factors.

Very simply put, video compression throws out data repeated from frame to frame. Depending on settings and content, it tries to limit visual impact.

As a rule, don’t create H.264 GOP as an intermediary for post production work. It’s best to work in ProRes or DNxHD or the camera native codec. H.264 compression should only be the last step for distribution.

[Craig Seeman]

Outside of some reviews I’ve not seen any specific training for it. My hunch is that if one has owned other Sony cameras in a similar class, it’s behavior isn’t much different. Of course many people don’t come from that background. I have seen in depth camera profile testing in another forum and there’s some debate over settings regarding natural colors and noise levels.

[Craig Seeman]

Not sure if anyone posted this here yet but Grant Petty posted in the Blackmagic forum about Fusion for Mac as well as doing other things and doubling their engineering team.

https://forum.blackmagicdesign.com/viewtopic.php?f=22&t=29406#p178950

[Craig Seeman]

You may want to examine Sony’s software compatible with Yosemite.
I’d also note Apple’s own video apps (Apple Motion for example) have noteworthy issues with Yosemite.

There are many large companies that aren’t yet compatible. The issues vary depending on the software specifics involved.

As a professional and former video facility engineer, you never upgrade an OS until you’ve gotten confirmation that mission critical software is compatible.

There are people who may test Wirecast and find no issue with Yosemite during testing. The problem with the issues around the OS are by no means consistent. Some can do jobs from end to end several times in a row without a problem which may have been the case during testing.

[Craig Seeman]

[David Intrator] “It’s not like Yosemite wasn’t in beta for 5 months.”

Being compatible with a Beta OS does not guarantee compatibility with the Release version. Betas change.

[David Intrator] “have been stonewalled by both Ustream and Telestream. “

Telestream has not stonewalled anyone. In order to insure compatibility there has to be changes and tests of those changes to ensure compatibility.

Professionally speaking, when an OS is updated and you don’t see an update with a program around the same time, one should be cautious. There are those who are finding intermittent issues with button with Yosemite. That means that sometimes it does work, Some have found things seem to work a bit after trashing preferences.

[Craig Seeman]

Card is recognized. Archive is available and shows engaged when clicked,

[Craig Seeman]

[Jeremy Garchow] ” if the import window recognizes a “camera” card structure, the archive button is then available.”

Just to be clear, it is available. it performs no function though. If I point it to a folder it’s not available (greyed out).

[Craig Seeman]

[Tone Andersen] “My client mounted the files though a memory-stick on his PC, and when he tried playing the clips on windows media player, the larger file only played the sound, no picture, and the smaller file only played the picture , no sound.
“

[Tone Andersen] “The larger file: Apple ProRes 422 (HQ), Linear PCM, (1920×1080)”

This will only play in Quicktime. It’s possible he may need the Apple ProRes playback codec for windows as well.

[Tone Andersen] “The small file: H.264, IMA 4:1 (1280×720)”
For audio try MPEG4 AAC

This will play in either WMP12 or Quicktime.

[Craig Seeman]

I believe I got the BMPCC about Oct 2013.
Mavericks 10.9 came out late October ’13
FCP 10.1 came out in December ’13

So it must have been working at least at 10.0.9 and 10.8.5 or maybe 10.9.0
I remember it working at least through around April ’14
Mavericks 10.9.1 Dec ’13
10.9.2 late Feb ’14
10.9.3 May ’14
10.9.4 late June ’14
FCPX 10.1.1 was Jan ’14
FCPX 10.1.2 was late June ’14

I reported the issue on in July with 10.9.4, FCPX 10.1.2
I confirmed the issues was there with 10.9.3, FCPX 10.1.1

So it looks like maybe 10.9.2, FCPX 10.1 might have been OK but I’m not sure.
Otherwise it was last working 10.0.9 and either 10.9 or 10.9.1.

If someone out there has 10.0.9 on Mavericks it would be an interesting test.

[Robin S. Kurz] “Yes, that was the first and highly bizarre bug concerning the BMPCC only(?) for some weird reason.”

The other variables would be .mov recordings but that would impact some Canon DSLR people although, unlike BMPCC, there’s other metadata.

Someone pointed out on another forum that they used to remove the other metadata from Canon DSLR and Archive still worked but that stopped in Yosemite.

Another check might be someone using ProRes recorded on an Alexa and see if that can use the Archive function.

[Craig Seeman]

[Robin S. Kurz] “what’s the sense or advantage of using the archive feature (which I love and use all the time also) on a disk like that i.e. native ProRes footage?”

One is that I don’t have to leave the FCPX interface. Even if all it where doing is copying it shouldn’t make it more difficult because the camera records ProRes. The other is a visual convenience in that that all my camera masters have an archive icon rather than a folder icon.

In the OS 10.9 variant of the issue, it created an archive complete with .plist. Either the .plist was a problem in the creation or FCPX wasn’t reading it properly.

I should mention this function did work as expected for some time. It’s possible that it worked in 10.0.9 but broke in 10.1. I had been Archiving for some time and suddenly all my past archives and newly created archives showed the same metadata for all the clips.

[Robin S. Kurz] “Maybe that’s why FCP isn’t doing it.”

When FCPX sees a folder the Archive button isn’t active. In this case it is. If it weren’t supposed to work I’d think it would be greyed just as it is when pointed at a folder.