From 0e98b2ad8ec00d3995051f2a9bfb5a5b268704e0 Mon Sep 17 00:00:00 2001 From: wm4 Date: Fri, 20 Dec 2019 09:55:47 +0100 Subject: edl: accept arbitrary paths Until now, .edl files accepted only "simple" filenames, i.e. no relative or absolute paths, no URLs. Now that the origin bullshit is a bit cleaned up and enforced in the EDL code, there's absolutely no reason to keep this. The new code behaves somewhat similar to playlists. (Although playlists are special because they're not truly recursively opened.) --- DOCS/edl-mpv.rst | 3 --- 1 file changed, 3 deletions(-) (limited to 'DOCS') diff --git a/DOCS/edl-mpv.rst b/DOCS/edl-mpv.rst index c5771c2bca..46a25293aa 100644 --- a/DOCS/edl-mpv.rst +++ b/DOCS/edl-mpv.rst @@ -254,6 +254,3 @@ header, the syntax is exactly the same. It's far more convenient to use ``;`` instead of line breaks, but that is orthogonal. Example: ``edl://f1.mkv,length=5,start=10;f2.mkv,30,20;f3.mkv`` - -As a quirks, mpv will accept arbitrary paths in EDLs originating from -``edl://``, while ``.edl`` does not. This makes no sense. -- cgit v1.2.3