-
WARNING – 10.6.8 Problems
Posted by Robert Stone on June 25, 2011 at 10:43 pmIt seems that the update kills all media files with Media 100 codec – they play BLACK in Quicktime and cause bad video frame errors within Media 100 Suite 10.6.3 – other quicktime codecs seem to be okay.
Also happens on a Macbook without Kona card.Blessings,
Robert Stone
https://www.TaylorCampFilm.com
https://www.youtube.com/MauiFilmsDave Mccarthy replied 14 years, 9 months ago 5 Members · 7 Replies -
7 Replies
-
Dave Mccarthy
June 26, 2011 at 8:25 pmA quick unofficial test on my home system appears to confirm this. We’ll have to investigate which rug Apple pulled from beneath us this time; in the meanwhile please avoid Mac OSX 10.6.8.
Of course in general it’s a good idea to hold off on OS updates for a few days, to give us a chance to run some tests.
-
Peter Dearmond
June 27, 2011 at 6:19 pmI’m on OS 10.6.8, using M100 Suite 2.0.1. I’m using ProRes most of the time, but after I saw this I imported a file using the Media 100 HD codec. No problems, plays fine. Just so I understand the problem, are you saying that the problem will occur if I export the file using the Media 100 HD codec? Have you tried using QuickTime Player 7?
-
Olof Ekbergh
June 27, 2011 at 6:27 pmI am seeing black on Media100 SD lossless codec in 2.0.1.
Prores422 seems OK.
Olof Ekbergh
-
Dave Mccarthy
June 27, 2011 at 7:00 pmWe haven’t qualified 10.6.8 so I really don’t want to start saying “XXX works” but the reported issue is playback of NTSC 601 media in the Media 100 i codec.
-
Robert Stone
June 27, 2011 at 7:31 pmSorry about the typo – Media 100 Suite 1.6.3
Robert Stone
https://www.TaylorCampKauai.com
https://www.youtube.com/MauiFilms -
Jaeson Koszarsky
July 5, 2011 at 4:33 pmI have this problem with Media100 Suite 2.0 and MacOS 10.6.8.
We just got new Mac Pros and Media100 Suite2. I tried brining in some projects from our old G5 systems, all used the Media100i Codec, and I get the black thumbnails and “bad video frame” error message.
Jaeson Koszarsky
Comcast Spotlight -
Dave Mccarthy
July 26, 2011 at 12:17 pmThe 10.6.8 “Supplemental Update” released today does not fix this problem.
Reply to this Discussion! Login or Sign Up