Activity › Forums › Creative Community Conversations › Prores deliveries not making me happy – Glitches
-
Prores deliveries not making me happy – Glitches
Jeremy Garchow replied 12 years, 3 months ago 8 Members · 21 Replies
-
Keith Koby
January 21, 2014 at 5:37 pm[Frank Gothmann] “Up till now we thought it was a dropout related to failing error correction on HDCAM-SR decks, bad cabeling, disks etc. but it’s just weird that it’s always Prores QT, always during the first two or three minutes, never in the middle or the end, and that it’s with all big labs happening time and time again under the same conditions. “
Do all of these files hit the same storage? Does the storage have some kind of flash or ssd cache before it hits spinning disk?
-
Frank Gothmann
January 21, 2014 at 5:43 pm[Keith Koby] “Do all of these files hit the same storage? Does the storage have some kind of flash or ssd cache before it hits spinning disk?”
Don’t know, many different labs with presumably very different set-ups and infrastructures. I have seen it also from clients who said it was a simple internal drive to external Firewire drive copy action.
——
“You also agree that you will not use these products for… the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.”
iTunes End User Licence Agreement -
Shane Ross
January 21, 2014 at 5:49 pmI worked on a half hour series for Investigation Discovery and we had ProRes deliverables. Of the 33 shows delivered, only one had a glitch like you describe. I’ve delivered a countless short form promos and good half dozen hour long shows to other networks with no similar issues.
Frankly I’ve had more issues with DNxHD Quicktime files than ProRes. But DNxHD MXF Op1A…none.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Frank Gothmann
January 21, 2014 at 6:03 pmHalf hour series, 33 Shows delivers. 1 Hit.
Fits my pattern of 1 out of 20 for every 90 minute file delivered to us[Shane Ross] ” worked on a half hour series for Investigation Discovery and we had ProRes deliverables. Of the 33 shows delivered, only one had a glitch like you describe. I’ve delivered a countless short form promos and good half dozen hour long shows to other networks with no similar issues.
Frankly I’ve had more issues with DNxHD Quicktime files than ProRes. But DNxHD MXF Op1A…none.”
We get very little DNxHD QT so I cannot tell with any certainty. But yes, MXF Op1A, error counter ist at zero. Same for our in-house HQX avi format.
——
“You also agree that you will not use these products for… the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.”
iTunes End User Licence Agreement -
Keith Koby
January 21, 2014 at 6:05 pm[Frank Gothmann] “Don’t know, many different labs with presumably very different set-ups and infrastructures. I have seen it also from clients who said it was a simple internal drive to external Firewire drive copy action.”
No I mean at your facility.
-
Jon Smitherton
January 21, 2014 at 7:21 pmHi
Kind of remember this glitch with Perian…do you have it installed?
Jon.
-
Jon Smitherton
January 21, 2014 at 7:24 pmHere you go- Perian and FX Factory perhaps?
https://www.dvinfo.net/forum/final-cut-pro-x/512708-fcp-x-10-0-7-a.html -
Frank Gothmann
January 21, 2014 at 7:31 pmNo Perian, our main machines are not Macs, but the problem is baked in the files, its visible on PCs, Macs and on Linux clients, with us and with the clients who sent the files.
——
“You also agree that you will not use these products for… the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.”
iTunes End User Licence Agreement -
Jeremy Garchow
January 21, 2014 at 7:41 pmThis used to happen with hardware captures and underpowered machines, they simply couldn’t keep up with ProRes.
If you search for “ProRes Green Frames” you will see a lot of posts around the internet about it, but a lot of them were FCS3 specific (as well as Redcode specific).
Jeremy
-
Frank Gothmann
January 21, 2014 at 7:48 pmWhatever caused this in the past, it apparently got carried along because it is very much present today on file deliveries coming from big labs using speced out Macpros. Also, it’s not just related to captures but also to simple file copies.
Also, it’s not present with any uncompressed material and the data rate there is much, much higher.[Jeremy Garchow] “This used to happen with hardware captures and underpowered machines, they simply couldn’t keep up with ProRes.
“——
“You also agree that you will not use these products for… the development, design, manufacture or production of nuclear, missiles, or chemical or biological weapons.”
iTunes End User Licence Agreement
Reply to this Discussion! Login or Sign Up