[Shane Taylor]

Robbie, this is a great explanation of the question I just had. What brought it up was trying to understand what color space my video files were in from my Nikon D810. I have attached a MediaInfo assessment of one of my files, but it confuses me by listing YUV, BT.601, BT 709, and BT 470M. CAn you make any sense of this information and perhaps explain to me in this context, the flow of data from my Nikon sensor to my MOV file?

I’m assuming like most DSLRs, that the file is ultimately in Rec709, and since that is what Adobe SpeedGrade expects, then I’m OK, but want to be sure (and understand the flow of color data/conversion done in-camera).

Any insight would be appreciated.

Cheers,
Shane

[Shane Taylor]

So, I am curious, why doesn’t AME and Pr and Ae use the same encoders. Wouldn’t that make sense that since all three programs can do encoding, that they would share the code base. I may be missing something here, but wouldn’t that just make sense from a SW development concept?

[Shane Taylor]

Tom, re: your backup/imaging SW, I’ve used Acronis, Paragon, and NovaBACKUP, for both servers and workstations. The best I’ve found is a (little known) product called Macrium Reflect. I’ve ditched all other SW in favor of this and use it exclusively. Macrium is a UK company and their user forum is WELL read by Macrium engineers and responses are usually same day (outstanding). They know their product insight and out and you can usually find any issue address in the their knowledgebase. I had never heard of it before someone on a NovaBACKUP forum turned me on to it. It has the best VSS support for in-Windows imaging that I’ve found, and also has a WinPE boot disk version as well with on-the-fly driver support. I found it to be faster than all the others too. Plus it is less expensive than the others. Acronis, for example doesn’t even support VSS in-Windows imaging (good luck if Windows, a DB, or an app has a file open). You can find out more at https://macrium.com/. At any rate, just another data point…

Also, I have heard, but haven’t experienced myself, that if you CLONE a drive with an imaging app, the Disk ID will not be the same (e.g. Windows can’t have two drives active on the same machine with the same ID), therefore, in some cases it has been reported that Windows complains that you don’t have an ‘official’ version on that disk when you try to boot from it and wants you to activate. It takes some working to get things set straight again. The work-around is to just do a copy of the disk then restore the image to your new disk using the boot disk option with the other disk disconnected. The Disk IDs will be the same.

I’m just one click away on my order of a new z820 too, but it’s not as maxed out as yours. 😉