There is little to no difference. You will be fine. Plus you will be using a more open standard (MXF) and your students will benefit from that.
Apple claim a slight superiority of quality – there is a document here http://tinyurl.com/mtfvupw - in terms of PSNR at the higher data rates (although tellingly not at the lower ones you are discussing) so make of that what you will.
Rupert Watson
+44 7787 554 801
www.root6.com
From: Avid-L2@yahoogroups.com [mailto:Avid-L2@yahoogroups.com] On Behalf Of mikejshen@gmail.com
Sent: 05 September 2013 05:43
To: Avid-L2@yahoogroups.com
Subject: [Avid-L2] moving our school to DNxHD from ProRes
Hi all,
I teach editing at a journalism graduate school. Last year I helped the school switch over from FCP to Avid Media Composer. We'll be continuing with Media Composer 7 this year.
We edited and finished in ProRes (regular) MXF last year, to good results. This year, we're considering switching over to DNxHD 115 for students working in 1080p 23.98, and DNxHD 145 for students working in 720p 59.94. Students shoot primarily with the Sony NX70, the Panasonic HPX500, Panasonic HPX3100, and various Canon DSLRs. We prefer not to up-rez, but to edit at broadcast resolution.
Is there any quality difference between ProRes reg and the Avid codecs I've named? My research (including a similar query I posted to the L2 last year) suggest that the Avid codecs will be of equal quality at a reduced file size. We lack a good broadcast monitor at the school, so it's difficult for me to run true tests. I'd appreciate your opinions. I don't see any difference on my computer monitor on the limited tests I've run.
Thanks in advance for your time and opinions!
www.root6.com/blog
Our resource for the latest news, support tips and articles
root6 ltd
www.root6.com Registered in the UK at: 4 Wardour Mews, London W1F 8AJ
Tel: +44(0)207437 6052
Company No. 03433253
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
No comments:
Post a Comment