Maybe still an interesting topic.
The Sony R220/320 in so far is special as that it allows to trigger a separate validation process. Which also means, that validation is not necessarily part of the ingest process.
Now, I have never worked on a Sony 220/320, but we do operate a new Sony R515. We never had any issues importing commercial DCPs or DCPs created with DCP-o-matic. BUT - when listing up ingested content in the library, the Sony shows a weird mix of DCPs being validated/non-validated, and it is not clear to me why certain packages receive an 'OK' and others not. Even the commercial DCPs are all over the place.
That said - we recently received a commercial DCP through broadband, which ingested fine (that is, no errors). But it suffered playback issues (for the first time on our Sony). The DCP was bad, we received a new disc, deleted the old content (had to, because the Sony would not ingest from the disc as it thought the existing feature was complete), reingested, and it played fine.
Now, this SHOULD never had happened, because broken files should be detected in the ingest/validation process. The DCP came from a commercial mastering facility, it contained hashes. So, the only assumption I can make is, that the Sony R515 is not (always) doing a proper validation on/after ingest. Unlike the R220/R320, the R515 does not have a separate option to validate files. Really wondering what goes on there.
As far as I know, Doremis validate DCPs in realtime during ingest.
I recently did various tests with different methods in DCP-o-matic to see wether the Sony accepts one of them with an 'OK' in the validation tab. Haven't succeeded yet.
See attached screenshot. All these DCPs, regardless of OK or NG (not good) play fine on our server, and ingest without any errors/warnings. They just list up in the library with either an 'OK' or 'NG'.
- Carsten
validation_sony.jpg
You do not have the required permissions to view the files attached to this post.