Edit : woops, I now realize that it’s a windows project … will see if I can find how to make this work natively in/with Linux (no wine)
Thanks @KKnBB for this tool … I’m going to try it, as I currently edit a 4k video … which means stuttering playback at some point.
First question : do you know if filters such as Stabilize (or any other one) could be impacted by this ?
Or does the analysis part is actually redone when exporting the project ?
Maybe @shotcut can also advise
2nd question : why not move
originals to an “unused” folder and the proxy files into the original location when activating the proxy feature
and switch them back / move then the other way around before exporting
Because, using the proxy files right from the beginning actually prevents me from using it with an already started project :-S
If you got time, can you post a random mlt file created in Linux and let me take a look at the “source file location syntax”? So I may improve the “replace proxy back to original” to work better with files created on Linux.
1, okey, that is a simple line of code, I add it today or tomorrow when I got time.
2, maybe, I will quickly review the existing codes, if no conflicts I will add the recurse.
3, it doesn’t remember the “location” simply by change of the text. You have to click some “execute” button. If I improve this, I may do something even better, like a drop down of all history location
1, added, check update
2, will be no recurse, for some reasons.
3, add a “save user config” action on when it exit.
5 posts earlier a forum member say it worked find in wine. Some earlier posts we have discussed if we can make it Linux native, the short answer is: it is easier to rewrite this little tool in python or something.
Most filters will work fine, except some special ones, like Stabilize where the filter needs to analyze the actual picture to auto-setup its own parameters, you have to be careful. Or use 1080p+ high quality proxy to minimize the impacts.
I don’t think the analysis/self-configuration will be redone when exporting.
It is a crime to move around the users existing files’ locations.
Some may get confused after apply it multiple times, some may use this tool against the camera SD card and the camera will reject playback of the converted files…
A new tool, save its shit in a new folder, don’t mess around the existing data, called the Best Practice Principles.
A minor update 2.022 :
remember users folder location / selection etc. for next run, before exit.
some cosmetic text changes: more info, more guide, less confusion.
Download url is the same in the first post.
Hello! I am having trouble with last Shotcut (linux). I create a project 1920x1080, and then use the proxified files. After edition, made the substitutions with the tool, and every zoom in (Rotate and Scale) in the main video track is ‘changed’, not in scale, but in X and Y. This was ok with the 20.02 version.
Actually I noticed this issue since the beginning.(even before I write this gadget)
The first week I use Shotcut, I made a 1080p video, later I decided that I want to publish it in 4K. Changing the video mode mess up all the filter X/Y offsets. (I was used to photoshop it is like when shrinking/resizing everything will follow the scale change, even the font sizes) I realize that Shotcut is using absolute X/Y offsets everywhere.
And that’s why I made the tool with the “1080p intermedia” and “full resolution” convert options.
So basically we have only 2 options here:
1, Edit with 360P proxy, substitutions, open again and fix the clips with offset filters, =>export;
2, Edit with 1080P edit-friendly intermediate, no need to replace, =>export.
@shotcut, if “proxy” is planed in future, maybe you should think about changing all the position offsets (eg. in text filter, rotate and scale filter) into percentage values that relative to video mode resolutions X/Y.