User Tools

Site Tools


releases:release_4_1_3

Windows 64-bit binaries.

This release is available through the auto-update facility in the Ctrl [A] About Box _if you have v2.2.2 or later and the libeay32.dll and ssleay32.dll files in your MMP folder_.
These release notes can be read from the What's New? button in the About Box after the auto-update has completed.

Use Shift-[\] to open the MMP config dialog

Release Notes v4.1.3

NEW

  • Before editing an audio or video file (Ctrl-[E]), MMP checks whether the path or file name contains characters that will effect the FFMPEG command line process. The most obvious are & and | which have specific meanings on a command line and their presence always breaks the syntax when used in a file path/name other than for their intended purpose. In this case MMP will insist that you rename the media file prior to editing. This is far preferable to allowing the editing session and then discovering that the command line won't run. (In which case you would have to rename all the Timeline Editing files.)
  • The checks that MMP makes have been made more stringent and the entire path and file name are now checked against a set of permissible characters, viz: a-z A-Z 0-9 ! @ # $ ^ ( ) [ ] { } + - = _ . % , ^ and the tick mark `
  • This is particularly useful if the file being edited originated from a non-Windows system, such as Android via Google Drive. In this case it's possible to have a file on your system which looks like it conforms to the rules of Windows file names but contains Unicode characters which will be problematic. E.g. colons, vertical pipes and slashes which look like their Windows equivalents but aren't.
  • Such characters are more likely than not to cause the Export and Join command line operation to fail, simply by making the syntax of the command line invalid. In particular, when FFMPEG reads the .seg file containing the list of exported segments. FFMPEG is very particular about the contents of this file and prone to reject the contents on the [seemingly] flimsiest of reasons.
  • If there any issues with which files MMP will or won't let you edit, please let me know.
  • Video Timeline Editing: as you create more and more segments on the Timeline , the Segments & Streams panel will grow in height so that more of the list is visible without having to scroll manually. The panel's height will be limited to the current height of the main window. This change does not apply to Audio Timeline Editing: the panel has a fixed size.

FIXED

  • Both slideshows were going haywire if there was no meaningful image-display-duration= entry in the mpv.conf file. This seems to be down to previous changes in libmpv-2.dll as mentioned in the previous release. This has now been fixed and the latest enclosed version of libmpv-2.dll correctly defaults to 5 seconds if there's nothing in mpv.conf or if the entry isn't valid. It's recommended that you upgrade to the enclosed version of the DLL if you haven't already.
  • Audio & Video Timeline Editing:
    • fixed some classic OBOEs (Out By One Errors). These may have been responsible for the very occasional and very illusive anomalies exhibited by the timeline editor.
  • the first segment now correctly starts at 1s, not at 0s as reported by MediaInfo.dll
  • allows for potential rounding errors when converting the pixel location of the vertical cursor into seconds.
  • doing a reverse tab (Ctrl-[Tab] or Ctrl-[T]) near the start of a video would wrap around to the end. There being no immediately obvious benefit to the user, this is now prevented.
  • addressed some occasional anomalies with Undo (Ctrl-[Z]) and Redo (Ctrl-[Y]).
  • the previous version broke the audio file editor; my sincere apologies.

Mystery Solved
When including images in release notes such as these, MMP suddenly stopped being able to download the images and include them in the What's New facility in the Ctrl-[A] About Box. After some considerable investigation, there is strong evidence to suggest that when displaying release notes, in the background GitHub transforms the URLs of the images in the release notes into a completely different S3 URL pointing to AmazonAws. Trying to access the original URL directly now results in a 404: Not Found. As a result, if future MMP release notes include images, they will be distributed in the release zip file along with the executable and unzipped to your releaseNotes folder. These are very small PNG files (only a few Kilobytes) and so will require negligible disk space.

« release_4_1_2 | release_4_1_4 »


Quick Install
The quickest way to get up and running with MMP is to

  1. run the mmp-install.bat file which will register all the file extensions that MMP supports*.
  2. rename the example MinimalistMediaPlayer.conf_ file by removing the _ so that MMP uses it.
  3. double-click any media file (audio, video, image) in your File Explorer software.

* mmp-uninstall.bat unregisters them.

Any issues, please let me know Issues


Wiki site
The fully-detailed wiki at minimalistmediaplayer.com continues to grow. The Wiki greatly expands on the brevity of the Ctrl [H] help panels by providing comprehensive info to help you get the most out of using all of MMP's many controls and configurable options.

If there is a particular aspect of MMP that you would like more information about, let me know and I will add a topic to the Wiki or enhance an existing topic.


Feedback
All feedback, issues and suggestions should be raised in Issues or Discussions


Asset files
The “…full.zip” release file below contains everything you need to run MMP: Minimalist Media Player:

- MinimalistMediaPlayer.exe
- MediaInfo.dll
- libmpv-2.dll
- ffmpeg.exe
- libeay32.dll
- ssleay32.dll

N.B. Only MinimalistMediaPlayer.exe will be updated automatically. If the zip file contains newer versions of the other files, you should update and test these for yourself to ensure they will run on your Windows system. MMP will not make that assumption and overwrite your working versions. You are advised to make a copy of the older versions in case you need to revert to them.

releases/release_4_1_3.txt · Last modified: