[Mlt-devel] [mltframework/mlt] 3938be: Revert query string parsing in 98b25ec.
Branch: refs/heads/master Home: https://github.com/mltframework/mlt Commit: 3938bea46178792996bf9ca4e66579574a70eca6 https://github.com/mltframework/mlt/commit/3938bea46178792996bf9ca4e66579574a70eca6 Author: Dan Dennedy Date: 2018-08-30 (Thu, 30 Aug 2018) Changed paths: M src/modules/avformat/producer_avformat.c Log Message: --- Revert query string parsing in 98b25ec. It parsing breaks file paths with '?'. **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
[Mlt-devel] Colour Correction
After following the melt tutorials on youtube its not clear if its possible to carry out colour corrections in melt? Can I do this on the command line some how? Best, J -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
Re: [Mlt-devel] Colour Correction
I will tell you what I tell all other would be melt users. See one of the MLT-based GUI video editors. They all offer color correction. So, yes, it is possible. You just need to learn more about melt by reading the documentation on the web site and figure out how to translate what the apps are doing to the command line. Yeah, it's not easy. No one should say video editing and filtering on the command line is easy. There are basic example command lines in the demo subdirectory of the source tree. On Thu, Aug 30, 2018 at 9:24 AM Joel Nash wrote: > After following the melt tutorials on youtube its not clear if its > possible to carry out colour corrections in melt? Can I do this on the > command line some how? > > Best, > J > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Mlt-devel mailing list > Mlt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mlt-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
[Mlt-devel] frame count / cut
As I'm editing film on the RPI melt doesn't yet playback smoothly so instead, I use omxplayer to playback film after making edits with melt. To specify a point in time in melt one uses frames. However omxplayer can only go as specific as seconds. So, on playback using omxplayer ill say to start at 02:05 (for example). and this will mean ill have to go (125 seconds * 23.976025 fps) to know where to tell melt to start playback. This was the exact command i used. melt cut1.mp4 in=2997.5 out=3117.4 -consumer avformat:cut2.mp4 vcodec=libxvid b=5000k on playback however of the new cut2.mp4 file with omxplayer the footage includes what previously equated to 122 mabybe 123 seconds omplayer. Why is this inaccuracy happening? Many thanks -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
Re: [Mlt-devel] Melt
So if you have something formulaic, a simple, or even a complex project, you could generate a an XML cultist for Melt and use your Raspberry PI to run the render. This would likely be quite slow given the weak CPU in the Pi, but doable. Note that frame accurate playback when reviewing your cuts may be inconsistent in omxplayer - something like Shotcut on a PC or xjadeo or similar may be a good approach. Again you will likely run into the same issues with HD material as the CPU may struggle to decode h.264 at that resolution in real time (on the Pi). With the Libav consumer, Melt will also always run a transcode. If you just want to top/tail videos and can align yourself with GOP sequences, rewrapping rather than transcoding will be significantly faster. If you want to use Melts more advanced features - such as colour adjustments - maybe an option available to you would be to do your rendering on a server with a more powerful CPU, by running Melt there. Pre-emptible or “spot” Cloud compute instances could be an efficient way to do that provided your files aren’t too huge. YMMV! Whatever it is you are doing sounds interesting! Best of luck, David On Tue, 28 Aug 2018 at 13:28, Joel Nash wrote: > ...It seems to be certainly possible (having just trialed that idea) but > is that a recommended workflow ? > > On Tue, Aug 28, 2018 at 8:14 AM, Joel Nash wrote: > >> Oh I wanted to ask is it possible to have melt be supported by omxplayer? >> >> On Tue, Aug 28, 2018 at 8:13 AM, Joel Nash wrote: >> >>> oh no thats not good. >>> I was looking for a lightweight and effective way to edit film on the >>> RPI. I'm also working pretty much exclusively in the terminal. >>> What could I do next ? I was wondering what you thought of the idea that >>> is it perhaps possible to make edits using melt and create a new edited >>> file which is then separately played back by omxplayer ? >>> >>> On Mon, Aug 27, 2018 at 6:16 PM, David Noble >>> wrote: >>> Hi On Mon, 27 Aug 2018 at 13:46, Joel Nash wrote: > > Thank you very much for getting back to me. Your support is much > appreciated and needed I’m sure ! > > Thats fantastic news if there is a way. I’m using the Raspberry Pi 2, > I do have access to the RPI3 also if need be. > I’m not entirely sure what to say about the rest of the set up. > I’ll mention the RPI2 is within the Pi top hardware. I’m just using > the jack out for sound however, > I do have the pisound soundcard hardware if its required > I’m not entirely sure of whether it’s possible to use the hardware decoder on the Raspberry PI with Melt, but this is definitely the right place to ask. My gut feeling is that there is no OpenMAX (the hardware media acceleration present on the Pi) support in Melt. > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Xuuki10thpromo.mp4': > Metadata: > major_brand : isom > minor_version : 512 > compatible_brands: isomiso2avc1mp41 > encoder : Lavf58.12.100 > Duration: 00:00:45.18, start: 0.00, bitrate: 3077 kb/s > Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), > yuv420p(tv, bt709/unknown/bt709), 1920x1080 [SAR 1:1 DAR 16:9], 2706 kb/s, > 25 fps, 25 tbr, 12800 tbn, 50 tbc (default) > Metadata: > handler_name: VideoHandler > Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, > stereo, fltp, 367 kb/s (default) > Metadata: > handler_name: SoundHandler > So the media is 1080p/25 - you’re unlikely to be able to play this in real-time with CPU decoding on the Pi. You may also have issues with getting frames to display quickly enough unless the framebuffer is handled appropriately. Omxplayer handles this fine, but it’s likely not directly supported in Melt. What is your use case for Melt in this situation by the way? Sorry to bring bad news! David > >>> >> > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
Re: [Mlt-devel] frame count / cut
On Thu, Aug 30, 2018 at 9:35 AM Joel Nash wrote: > As I'm editing film on the RPI melt doesn't yet playback smoothly so > instead, I use omxplayer to playback film after making edits with melt. > > To specify a point in time in melt one uses frames. However omxplayer can > only go as specific as seconds. > > So, on playback using omxplayer ill say to start at 02:05 (for example). > > and this will mean ill have to go (125 seconds * 23.976025 fps) > to know where to tell melt to start playback. > This was the exact command i used. > > melt cut1.mp4 in=2997.5 out=3117.4 -consumer avformat:cut2.mp4 > vcodec=libxvid b=5000k > > You are using frame units for time values, and MLT does not support more than frame precision. Thus, those values are truncated: duration = 3117 - 2997 + 1 = 121 frames ~= 5.05 sec > on playback however of the new cut2.mp4 file with omxplayer the footage > includes what previously equated to 122 mabybe 123 seconds omplayer. > I think you mean frames instead of seconds. You should use something besides omxplayer to get the output duration. Something like melt -consumer xml or ffprobe. > Why is this inaccuracy happening? > > MP4 uses temporal compression with codec delays. This can make outputs slightly longer than expected when draining the codec. One frame in my test using: melt -profile atsc_1080p_2398 noise: in=2997 out=3117 -consumer avformat:test.mp4 ffprobe shows test.mp4 as 5.08 sec and melt shows length 122 frames. If you change the output to intra-only with uncompressed audio (I don't give a shit if raspberry pi can play it or not): melt -profile atsc_1080p_2398 noise: in=2997 out=3117 -consumer avformat:test.mkv vcodec=ffv1 acodec=pcm_s16le Then, ffprobe reports 5.05 sec and melt shows length 121 frames, which is spot on. Next, if I use ffmpeg 4.0.2 to convert that output to H.264/AAC MP4: ffmpeg -i test.mkv test2.mp4 Then, ffprobe shows 5.07 sec and melt shows length 122 frames - same as MLT MP4 output. If that MP4 output bothers you enough, you can take it up with ffmpeg-devel. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
