• Adding audio to images
• Fading
• Resizing (video dimensions and audio length/tempo)
• Rotating/flipping
• Audio amplification
• Track removal/replacement/addition
• And more! If you're reading from the future, that is.

• Renaming - Just type a new name in the text box at the bottom and press enter to instantly rename your file
• Deleting/recycling
  • Mark files for later deletion (so you can change your mind later), or instantly delete the file you have open
  • Whether deleted files are truly deleted or only recycled can be adjusted in the settings (they're recycled by default)
• Enhanced drag-and-drop
  • Drag media, drag folders, drag subtitles
  • Hold Ctrl/Shift/Alt while dropping to instantly concatenate files together or add audio tracks
• Snapshotting
  • Customize the size and aspect ratio of snapshots
  • Customize the naming format, image format, and quality (if applicable) of your snapshots
  • Use crop-mode to only snapshot the cropped region
  • Shift/Alt-click the snapshot button to view the most recent snapshot

PyPlayer supports custom themes in the form of Qt Stylesheets, which can come as .txt, .qss, or .css files. To add a custom theme, place it in the themes directory in the same directory as pyplayer.exe.

PyPlayer themes have minor differences from standard stylesheets and use their own "Theme" section. View the included themes to get started with making your own.

PyPlayer's code is designed to provide a more human-friendly implemenation of VLC that can be built on and expanded easily, so contributions are very welcome. Translations, documentation (where necessary), tests, missing VLC features, better cross-platform support, and new editing features are all especially welcome. If you're wondering where to start, there's well over one hundred TODOs dotted around the project, ranging from interesting to tedious to probably impossible. Most of these TODOs, ideas, and known issues are right at the top of main.pyw.

Here are some basic guidelines:

• If you're new to contibuting in general, you can use this guide.
• Follow the seven rules of a great commit message.
• Try to match the style of the code surrounding your addition. Don't let your code stick out like a sore thumb.
• Try to keep your commits isolated to one general issue. Don't mash too many ideas into one commit, and avoid frivolous edits like changing the whitespace of a random in-line comment (I do a LOT of frivolous edits in my own commits, but that's because I'm a hypocrite).
• Code should be as self-documenting as possible - or if it's truly that complicated - have minor explanatory comments/docstrings.
• bin/configparsebetter.py is currently off-limits (part of a future project).
• bin/updater.py is not off-limits, but you'd need a very good reason for changing it.
• Avoid changing the default themes unless it's to fix bugs or to add support for a new feature.
• Avoid introducing new, heavy dependencies where possible.
• Avoid relative paths where possible (use constants.CWD for the root folder).
• Be mindful of constants.REPOSITORY_URL. Make sure it points to the original repository when you make your commits, if you happen to change it while testing a feature.