Did you know that there is a verticle track limit? I just kept on pasting the same clip in and at track 31 you can’t add any more. Blender then begins stringing them all along track 0. I think that this is a bug…
I guess we will have to lobby for that as he has a full time job and only works on the VSE to fix bugs.
Also, EVERY nle on the market can treat audio and video (from the same source) as linked. It would be excellent if Blender would have a switchable facility for moving linked strips too. The new VSE scripts can allow various selection types but it is just additional button clicking that shouldn’t be necassary.
I agree and I guess that it shouldn’t be too hard to code. That will eliminate one of these little annoyances that the VSE has.
Strangely enough, I’ve become accustomed to it so when I try other editors from time to time (such as Kdenlive or OpenShot) it feels so unnatural!
New Version is out:
Now the Edit Range operator can also be called from the File manager window.
Tip: Add the bpt.edit_range as a new shortcut to the file manager in user preferences input section and assign left double click.
Now you may simply double click any video in the file manager to edit the range. Like in many other NLEs
Really like the double click to open, that’s pretty cool. But silly Blender makes the file stick to my mouse after changing scenes, so I drag it away to the timeline. What have I set wrong?
Update:
Holly cow!!! I’ve just realized that this error is returned by the current script but it references a line from the vse2copositor strip!!!
Are the scripts cross-referencing stuff? Is this to be expected or have I messed things up?
yes, there is some strange thing here, maybe the two scripts are using the same operator name and the eswc one is running instead the other (maybe it is my mistake)
(i assume you pressed the button in the trim videos panel, not the eswc by mistake…)
Carlos I was unaware of such an addon and the funny thing is that I’m unable to find one in my blender installation.
And yes, pressing “get back” from the editing range screen returns this error. Haven’t pressed it while on the editing screen but getting any error(s) there would be reasonable. Any ideas?
Ok, in trying to answer my own question, I looked at the script and realized that eswc is the acronym for the edit strip with compositor addon! :0
Assuming that you referred to “eswc” addon itself, I disabled it and gave the movie editor addon another go.
Interestingly enough, the “get back” button disappeared from the UI. The script remained fully functional though, i.e. trimming in the designated screen and manually switching to the master scene.
I was able to use both scripts in tandem, without any problems, up until the latest script update (say 2-3 days ago).
As always, thanx for coding, debugging, and improving it!
I know that the Get Back button does move you from one VSE timeline to another (notionally both editing paradigms) but it would be conceptually better to make the buttons source/master switches.
That is, people may be confused by seeing just another timeline, but if you called it an edit “Source” the name would imply the function. Similarly if you have a button in the Source panel saying “Master” instead of get back, people will know where they are navigating too.
This would require re labeling the button in the master panel too.
Further to the concept of classifying the windows/setups differently.
When starting, could the script add and modify a theme of another VSE layout, creating a “source viewer”? Even if only to increase the background brightness to a different shade. This way the user would have another indication that they are in a different ‘mode’.
In a Build from yesterday the script works. Though for some reason the Movie Manager does not appear in the sequencer panel sometimes. I haven’t found out why this happens yet.
Little tip if you use the edit range operator from the file browser, assigned it to a mouse click and get the problem that the file gets “dragged” every time:
set two commands: one file.select operator that is activated by press of your mouse event in the File Browser Main section and the usual bpt.edit_range which is executed by release in the file browser (global) section.
On this way you avoid to use a double click to first select the file you want to edit and then call the edit range operator. Double clicking confuses blender in that case…