Repository navigation
WaveFlow QuickPlay v1.4.0
WaveFlow QuickPlay 1.4.0
QuickPlay now opens .m3u and .m3u8 playlists.
New
- M3U playlists: open an
.m3uor.m3u8from the file manager, the open dialog, a drop on either window or the command line, and QuickPlay queues its files in the playlist's order.- Entries can be absolute paths, paths relative to the playlist, or
file://URLs. - A playlist written on Windows, with
\between folders, also works on Linux and macOS. - The text is read in whatever code page wrote it, so an old playlist saved by a Windows player keeps its accented names.
- Web addresses and files that are not there are left out.
- Entries can be absolute paths, paths relative to the playlist, or
- In the menus: on Windows, Play with QuickPlay and Add to QuickPlay playlist now appear on
.m3uand.m3u8files. On Linux, QuickPlay is offered for the M3U types. On macOS, Finder lists it under Open With for playlists. Installing 1.4.0, by hand or by the updater, adds the entries.
Security
- Network shares in a playlist. On Windows, merely opening
\\host\share\…can make Windows authenticate to that host with your current credentials. A playlist downloaded from anywhere could abuse that to capture an NTLM authentication exchange. QuickPlay follows a share only from a playlist on that same host: an.m3uon your NAS listing the NAS's files works, while one in Downloads naming someone else's server does not. Mapped drives are treated as local paths and always work. Device paths and anything not clearly a drive or a share are refused.
Install
- Windows: download
waveflow-quickplay_1.4.0_x64-setup.exe. It installs for the current user without administrator rights and registers the context-menu entries. Run it over an earlier version to upgrade; your settings live in their own file and are kept. - Linux: the
.debfor Debian and Ubuntu, the.rpmfor Fedora, RHEL and openSUSE, or the.AppImagefor any distribution (make it executable and run it). All three carry the desktop entry, so QuickPlay appears in "Open with" for audio files and playlists. - macOS: download
waveflow-quickplay_1.4.0_macos-universal.dmg, open it and drag WaveFlow QuickPlay to Applications. The app is signed ad hoc, not by an Apple Developer ID, so macOS blocks the first launch: open System Settings › Privacy & Security and choose Open Anyway (on macOS 14 and earlier, right-click the app and choose Open).
1.2.0 and 1.3.0, installed from the Windows installer, the macOS app or the AppImage, update themselves to 1.4.0: they download it at launch and install it when you close QuickPlay. 1.0.0 and 1.1.0 do not look for updates, so they are upgraded by hand once.
SHA-256 checksums are in SHA256SUMS-windows.txt, SHA256SUMS-linux.txt and SHA256SUMS-macos.txt. latest.json is what the updater reads: it lists the packages that update themselves (the Windows installer, the macOS app and the AppImage), each with its signature.
Note
The Windows installer is signed with WaveFlow's self-signed certificate, so Windows may still show a SmartScreen warning on first launch.
Known limitations
- Playlists are read up to 16 MiB. A playlist inside a dropped folder is not read, since its files would come twice. Neither is one named by another playlist.
- One hand-over carries up to 10 000 files, in a message of at most 4 MiB (the paths with their line breaks and the command). A larger selection given to a QuickPlay that is already open opens in a window of its own instead.
- Pinned on Wayland, QuickPlay runs under XWayland, which can look softer at fractional scaling unless the compositor scales X11 windows natively. A session without XWayland cannot pin.
- A
.deb, an.rpmand a copy run from a read-only place (the disk image itself, or an app macOS runs from a translocated copy because it was not moved to Applications) are never replaced by QuickPlay: they only say that a new version is out. - On macOS, Finder has no per-app menu entries, so there is no Add to QuickPlay playlist there; Open With replaces the queue, as Play with does on Windows.
- Continue in WaveFlow needs WaveFlow Desktop 2.0.0-beta.1 or later, read from the install's metadata. The button stays hidden for an older WaveFlow, for one whose version cannot be read (such as an AppImage put on
PATHby hand), and for the Flatpak build, whose sandbox cannot see the hand-over file. - The output device is the system default, opened in shared mode.
Full changelog: v1.3.0...v1.4.0