![]() So in that respect I humbly disagree with Hendrik (if that is truly his position).It most certainly DOES make a difference, or at least to me and a ton of other people from AVS (the subject of frame rate doubling has been debated on many occasions, as well as the use of FI in an attempt to mitigate such please be patient. In both cases, there is no option that doubles the frame rate of ANY source frame rate, so to be honest with you, I don't know why such behavior would ever be needed or wanted.maybe it is for some other type of display that I have no familiarity with. ![]() to have the player follow the source encoded frame rate. ![]() to either be "hard wired" to output the max resolution/frame rate regardless of the source resolution/frame rate, orĢ. Maybe the problem exists only with front projectors.I don't really know due to my lack of technical knowledge, but I can UNDENIABLY see the difference between 25 fps and 50 fps, with or without Frame Insertion turned on.Īgain, in my humble opinion, and apparently in the opinion of the hardware player manufacturers, the correct way to handle resolution/frame rate output is to have one control that sets the maximum resolution/frame rate (so that the output never exceeds the capability of the display) and then a second control which allows the player:ġ. When I checked to see what the projector reported as incoming signal frame rates, the 3 devices correctly sent out 25fps, while MC sent out 50 fps, also verified in MC by using the CNTRL/J function. As I hunted down the problem, I found that the very same video displayed by 3 other hardware media devices (Vero 4K+, eGreat, and Zidoo Z9X) were all free of SOE. The first time I ran into this with MC I thought that my front projector had somehow changed settings and was displaying what I considered to be a HUGE amount of SOE.I blamed it on my projector. I am not the most technical person here, but I can assure you that I can very easily see a difference between 25 fps presented at it native rate versus at a doubled rate (50 fps). Many thanks to everyone who understands this situation and has chimed in. It looks like I'll go back to HPC-BE for now as it does not suffer with the same logic issues. Perhaps all of this is a waste of everyone's time as it would appear that many forum members here are only interested in stroking their own ego instead helping with facts like the instructions for how to achieve a work-around for this function's flawed logic. Could you imagine 600 frames of smooth motion in 0.5 seconds and then 0.5 seconds of still motion. the duplicate source frame is ignored otherwise it would make useless any smooth motion frame-tweening. just an answer to a technical question.Īlthough, I am quite surprised here by the number of people who believe that sending a duplicate frame to a TV will actually do anything. Regarding your comments about your opinions. Anyone would believe that I didn't pay for the software. I will also assume by your answer that this forum is the only way to obtain support. This is truly a unique experience and a huge waste of everyone's time here. ![]() Many thanks for your reply and for letting me know that everyone is off for holiday.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |