Scott Goddard
Forum Replies Created
-
Hi Shane, it is not an option in this scenario. The films were transferred mid 2000’s. They probably chose digi over HDCAM on cost or it was simply not offered to them.
Scott Goddard
Neo Verite Limited
https://neoverite.com -
Is anyone successfully using NSF and Adobe Premiere?
Scott Goddard
Neo Verite Limited
https://neoverite.com -
It is tough decision and no body has a looking glass to see the future on this. The BBC recently did a huge study to find the right format to store their digital archive. They ended up using uncompressed MXF.
More details here:
https://www.bbc.co.uk/rd/publications/whitepaper241
Obviously that’s a best case scenario with a HUGE budget. For the rest of us I still feel Prores is the best way to get the right balance. Keep the tapes though…
Scott Goddard
Neo Verite Limited
https://neoverite.com -
Yes, use cyberduck to interface it. Just works like regular FTP but better. You may want to add the additional metadata tags depending on how the files will be used, this is all covered in their manual.
Its free btw..
Scott Goddard
Neo Verite Limited
https://neoverite.com -
Hi Dylan,
I am looking to put together a very similar setup. Other than this driver issue, how do you find the performance for the client machines?
Scott Goddard
Neo Verite Limited
https://neoverite.com -
-
Excellent, thanks for the heads up. Adobe XMP is looking very promising.
Scott Goddard
Neo Verite Limited
https://neoverite.com -
I agree about the contextual element. Photos have it easy!
Video has far more stages and outlets where metadata needs to be specific. I am thinking of using the Dublin Core across all assets even if a lot of it is irrelevant. I am thinking that somewhere down the line the main things like date, title and creator should hold through. It’s really about it’s use beyond CatDV, especially when you are looking from a long term archive point of view.
I have been meaning to work on a Worker task to write metadata to multiple fields. This way we could keep clients on their bespoke field names but have that data transfer to Dublin Core fields. So a mapping task.
User Field 1 (Asset Number) maps to User Field 52 (Dublin Core: Identifier). This would be a simple worker server query that is automated upon field entry. This could then be fields that the clients never need to see, a hidden tab where they are actually adding to ‘standards’ in the background. The advantage of this is that you could write to multiple standards at the same time so if one ‘standard’ does win out in the future the archive will be semi covered for this.
XMP temporal metadata interests me but getting this standardized across all of the apps that will touch a typical video file workflow is a long way off.
https://www.philiphodgetts.com/2012/04/why-is-temporal-xmp-metadata-so-exciting/
Eventually we will have metadata written into every frame. Imagine watching a finished edit and being able to see where every frame and shot came from originally, it’s original shoot date, gps location, creator, file location etc etc.
Scott Goddard
Neo Verite Limited
https://neoverite.com -
Hey Bryson, sounds great. This will be an excellent workflow and there is a big demand for this as you are no doubt aware. Can’t wait to see a prototype.
Anything else in the works? Server 7 sounds like it’s going to be a big improvement.
A new client interface design is desperately needed though…
Scott Goddard
Neo Verite Limited
https://neoverite.com -
We handle proxies on S3 and stream them both to the Client and Web Client. I will be looking into using Glacier to handle offsite backup of the full res. As with the proxy workflow this will require using the Worker and some other third party apps to upload to glacier.
What is your use case exactly?
Scott Goddard
Neo Verite Limited
https://neoverite.com