INTERACT FORUM
More => Old Versions => Media Center 12 (Development Ended) => Topic started by: hundreds on May 10, 2008, 06:22:53 am
-
ie: close any other applications..
disable any theme changers like windowblinds.
the error persists..
basically the only way I can get to watch a .mov file from boot
is to first go into "Theater View".. launch the file from there.
then i can view any other .mov file no worries from any view.
If I launch if from "Standard View" it just crashes the program.
Its super annoying. I am only using a trial version but if it will be like
this I can do without this application.
Everything about it is good but this is just irritating.
Please help.. and thanks in advance.
-
Have you updated your codecs?
Sounds like there's an issue with Quicktimes initial window resize to me.
A log may also help us to see what is going on- Go to Help, Logging & check the box Output to a log file Now cause MC to crash & then go back to the logging box & click View for the previous file. Post the last twenty lines or so of that one :)
Cheers
-Leezer-
-
My codecs are all up to date.. i have no issues playing .mov files in any other media player including wmp11.
I deleted this gay river thing so problem solved!
I only got impressed by the thumbnail preview within the application.. but the rest is nothing special.
I just use zoomplayer and browser via explorer!
-
My codecs are all up to date.. i have no issues playing .mov files in any other media player including wmp11.
I deleted this gay river thing so problem solved!
I only got impressed by the thumbnail preview within the application.. but the rest is nothing special.
I just use zoomplayer and browser via explorer!
If Zoom Player can play the files then you most likely would have been able to play them with MC too after checking what codecs should be used and adjusting MC's options or waiting for the next fixed MC build in case there really is a bug.
The mov file type itself is a container type and can contain various types of video and audio streams. More specific info would have been needed for solving the problem.
Obviously [because of the deleted comment], you also didn't say what build you were using. The possible problem may well be fixed already.
-
From your [deleted] comment, you had a corrupt version from another source.