Some functions previously incorrectly used the (moving) index of the track in the table of tracks. * Fix audio and video track selection: The constant track identifier is now always used. * Fix crash with local statistics disabled * Fix Reveal-in-Finder for files with non-Western file names * Fix Mpeg-2 audio and video encoders initialization * Fix crash in Freetype with embedded fonts * Fix SWF potential crash on malformed files. * Fix some MKV crashes when ordered editions have empty or broken links * Improve reliability for RTSP streams sent by some IP cameras * Fix buffer overflow in HTML subtitles parser * Fix crash with some embedded subtitle fonts * Fix file output bug affecting floating point on big endian systems Even those that use add-ons, all of the popular add-ons I checked out either had 32-bit and 64-bit required files included or were lua files (which are universal). I would certainly agree that you are "not the average Videohelp member".* Fix playback initial synchronization with PulseAudio (however similar bugs in PulseAudio version 2.0 and later still exist) As for 32-bit vs 64-bit in terms of VLC, while VLC is more than a media player, a very small percentage of users use it as such. I'm guessing that your concept of "due time" was >5 years ago. All while completely understanding that there will still be plenty of users who cannot or will not benefit from the (overall) change, due to economic and other pragmatic reasons. One area that of video that should benefit is in compression, so I thoroughly welcome advances there. It makes very much sense for video FILE FORMATS to be 64bit, but the code for the editor/player apps don't necessarily HAVE to be (though most of the good ones are already anyway). Hence, along with technological evolution, the demand for fast computing and multi-tasking gained prominence, and this required processors with much more ability to perform. voice) - that's where it will really be helpful. In this computing world, we are introduced to two variants of processors: 32 bit and 64 bit. Does your Word Processor work faster? Would anyone care if it could handle text documents larger than even 4GB? Maybe only for speedy 1000+ page re-indexing or something.ģD graphics, modeling, AI & pattern recognition (incl. I am glad things are going the 64bit way, but I am not so gung ho that I avoid the reality of the current situation and what that means in TCO for those transitioning.Īlso, there are many data objects and computing domains that really don't benefit from going 64bit. However, 64bit imposes an equipment level burden that is higher than 32bit, so there is a penalty of sorts (including memory, $), until "everything" is above that bar. 64bit is only faster when the whole system is optimized for it.Ħ4bit is USUALLY more efficient (less seeks), unless badly coded, or a mixed-bitspace subsystem exists (still quite common).
0 kommentar(er)
