![]() Resurrecting this old thread to add a possible fix for this common problem: ![]() Given the attitude of the developers that's unfortunately not likely to happen. Hopefully they'll take this seriously enough at some point to actually fix the problem in which case I'll be so very happy to return and become a supporter once again for the app I've evangelized to everyone I know for all these years. No grey screens, no stuttering, no freezing. (the quote above is from a thread in 2009!)Īfter being a loyal VLC user since 2001 I'm sad to say I've been left with no choice but to use other alternatives that are free of these persistent performance issues.Ĭurrently IINA is my movie player of choice. Tried resetting caches and every single other suggestion made in this thread and others and have watched the builds for Mac decline for many years now. If you cannot, don't whine, but buy a faster computer or don't play the videos (/seek alternative versions).įact remains that other players like MVC, DivX, and ElMedia have no problems on the exact same computer with the exact same files that VLC now chokes on every couple of minutes. x264 encoded video is simply CPU intensive to decode. If you want to resolve this issue I'd strongly recommend not to withhold another 40 bucks and buy a very reliable product capable of playing the same formats as VLC is advertised as having ability to. Sorry, guys, 0 improvements on playing ISOs after so many years. Having installed for the second time I see little has changed and my old decision to uninstall it was very much correct. Its bunch of functions that are really useless on Mac as they duplicate iTunes functionality are showing off its bloatness. I already had this software downloaded 2-3 years ago, I then realized it fell short of success to play properly BD content that is not MKV. The key factor for me is ability to play BD disks seamlessly. For CPU usage jumped up to 95% which wasn't the case with Macgo. I have Macgo Blu-Ray Player, it plays the same movie flawlessly, BTW without the need to carry out two separate useless actions: #1 mount the disk image #2 open BDMV folder in the very convoluted way implemented in VLC. It's said a lot in this thread, all these super-geeky prefs, requiring to take at least a 4 year courses in video editing and camera shooting, trying hard to comprehend the meaning of each. The same problem trying to view a movie by opening BDMV folder of ISO (disk image, opened with Disk Mounter Utility). So in summary then, and I apoligise for this lengthy post, anything that slows down or interrupts a VLC read-request is going to cause this problem. If however your on a single disk rig or laptop, IO contention can become a real problem and so I recommend turning off as much IO heavy crap as you can. Now if the movie your watching exists on a separate physical disk than your OS, the impact of these kinds of tasks will be minimal (except a virus scan I guess). I'm sure Macs run the equivalent of at least some of these. Windows 7 comes preconfigured to run several IO heavy task's on a regular schedule and off the top of my head these are: Windows Update, WinDefender, Defrag, WinSAT, RACtask etc. Now a brief note on IO contention but only Windows based i'm afraid. Without reading back over the whole thread, I believe there are a few network streamers with the problem and I will remind them that they need to consider 'link state power management', any potential network interference (little Johnny upstair's copying down something he shouldn't? Hmmm?), wireless interference etc., on top of mechanical drive IO contention and AHCI's HIPM/DIPM. The only other solution on this thread with any legs is increasing the read buffer size, with the caveat that it only serves to mask the problem rather than fix it. If there is a Mac guru out there who knows how to disable HIPM/DIPM on MacOS, I'm sure some of these folks need to hear from you. There is another post on same page where I explained how SATA-AHCI's HIPM/DIPM will also cause the problem, but the best solution is only available on Windows machines as far as i'm aware. I made a fairly detailed post on page 4 of this thread where I tried to explain to someone why IO contention will cause the problem. So i'll start this one by stating that I am 99% certain that the problem is triggered by a delayed or unfulfilled read-request. Well I just tried to explain the likely cause of this problem to someone over on the Windows forum, but alas I think I failed to convince.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |