VapourSynth Editor 2

[Greenhorn]

Some weird things:
1) The "Close tab" and "Close all tabs" buttons have no icons.
2) The fonts all default to "monospace", which is just MS Shell Dlg.
3) With DPI scaling enabled, most text in buttons overflows the its ui elements. (ex, the frame/time toggle on the timeline reads ram/lime)

Something I'm missing? Library I need to install, something like that?

[no1d]

The program should be able to start even without libp2p. This should be caused by another problem. My guess is the vsedit2.config file? Try rename the vsedit2.config and let the program create a new one and see how it goes.

In my case the program kept crashing because there was no config file.
Renaming vsedit.config to vsedit2.config solved it for me.

[MysteryX]

In my case the program kept crashing because there was no config file.
Renaming vsedit.config to vsedit2.config solved it for me.
huh. I tried again a long while later, perhaps after some reboots.

Now it starts. I haven't changed anything.

[Reclusive Eagle]

Quality of life changes suggestion:
First, its really, really not clear libp2p is required. You have to dig into the repository to find the changelog. I suggest you update the read me with the new dependencies.

2: We need chroma resampling filter viewing options back. They don't need to be in advanced preview like they were before but currently the preview looks as though its based on point filtering.
I see no way to change this at all. If there is please let me know but its extremely difficult to see detailed changes to clips based on point filtering. Even if its slower, I'd rather have slower preview scrubbing than not being able to properly see changes at all. I'd rather it be permanently Lanscoz based or Spline64.

3: Please, I'm begging you. Add the ability to ctrl v the error log. I don't know why we have the ability to highlight text but pressing ctrl v does nothing to the highlighted text. Its so backwards that you can highlight something but to copy and paste text you have to right click and copy. I am actually losing my mind at this point. It would be a 10/10 quality of life change.

Future suggestion:
It would be great if the preview filters got an update to display different color matrix layers.
Currently its just black and white Y U V but if it were able to detect and dynamically change to preview separate RGB layers in color along with color versions-
of the U V blue and red projections that would be amazing.

I know this can be done through other plugins but to have that natively supported without the need to remember additional code make VSE2 even better.

[lansing]

Quality of life changes suggestion:
First, its really, really not clear libp2p is required. You have to dig into the repository to find the changelog. I suggest you update the read me with the new dependencies.

2: We need chroma resampling filter viewing options back. They don't need to be in advanced preview like they were before but currently the preview looks as though its based on point filtering.
I see no way to change this at all. If there is please let me know but its extremely difficult to see detailed changes to clips based on point filtering. Even if its slower, I'd rather have slower preview scrubbing than not being able to properly see changes at all. I'd rather it be permanently Lanscoz based or Spline64.

3: Please, I'm begging you. Add the ability to ctrl v the error log. I don't know why we have the ability to highlight text but pressing ctrl v does nothing to the highlighted text. Its so backwards that you can highlight something but to copy and paste text you have to right click and copy. I am actually losing my mind at this point. It would be a 10/10 quality of life change.

Future suggestion:
It would be great if the preview filters got an update to display different color matrix layers.
Currently its just black and white Y U V but if it were able to detect and dynamically change to preview separate RGB layers in color along with color versions-
of the U V blue and red projections that would be amazing.

I know this can be done through other plugins but to have that natively supported without the need to remember additional code make VSE2 even better.

1. I'll put a check on program start and warns about the dependency.

2. I have not found a valid reason to put chroma subsampling on a zooming feature, which should not have any extras added to the image. And that's how you can see the true differences when comparing frames. Photoshop is doing the same thing on zooming too. You'll have to show me a good reason for it.

3. Will fix. I have noticed this for a long time but it just got over my head time and time again.


For the RGB channels, it was not useful. The only scenario I can think of that shows its usefulness is for monitoring underwater footage, where it has no red and you wanted to add some red back to the red channel.

[Selur]

When opening 'vapoursynth-editor-2/pro/vsedit/vsedit.pro' in QtCreator and running qmake it uses
qmake vsedit.pro -spec linux-g++ CONFIG+=debug CONFIG+=qml_debug
and I get
Project ERROR: failed to parse default search paths from compiler output
also tried to build it using the build instructions without qtcreator, but that failed to.

-> any hints on how to build vsedit on Ubuntu 20.04 in QtCreator ? (build-essential, qtbase5-dev; qt5-default, qtcreator and all it's dependencies are installed)

Cu Selur

[Are_]

Qtcreator is probably not supported as a build system and with such helpful error messages, it's not exactly easy to help you.

[sl1pkn07]

seems you need build-essentials or something

try to no set `-spec linux-g++`

in any case. fail to biuld for me in my archlinux


g++ -c -pipe -O0 -g -ggdb3 -std=c++17 -Wall -Wextra -Wredundant-decls -Wshadow -pedantic -g -D_REENTRANT -Wall -Wextra -fPIC -DKDSINGLEAPPLICATION_STATIC_BUILD -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_QML_DEBUG -I. -I/usr/include/qt -I/usr/include/qt/QtWidgets -I/usr/include/qt/QtGui -I/usr/include/qt/QtNetwork -I/usr/include/qt/QtCore -I../../vsedit/generated/moc -I../../vsedit/generated/ui -I/usr/lib/qt/mkspecs/linux-g++ -o ../../vsedit/generated/obj-debug-64bit-gcc/vapoursynth_script_processor.o ../../common-src/vapoursynth/vapoursynth_script_processor.cpp
In file included from ../../common-src/vapoursynth/vapoursynth_script_processor.cpp:1:
../../common-src/vapoursynth/vapoursynth_script_processor.h: In constructor 'VapourSynthScriptProcessor::VapourSynthScriptProcessor(SettingsManagerCore*, VSScriptLibrary*, QObject*)':
../../common-src/vapoursynth/vapoursynth_script_processor.h:129:16: warning: 'VapourSynthScriptProcessor::m_cpCoreInfo' will be initialized after [-Wreorder]
129 | VSCoreInfo m_cpCoreInfo;
| ^~~~~~~~~~~~
../../common-src/vapoursynth/vapoursynth_script_processor.h:119:10: warning: 'bool VapourSynthScriptProcessor::m_finalizing' [-Wreorder]
119 | bool m_finalizing;
| ^~~~~~~~~~~~
../../common-src/vapoursynth/vapoursynth_script_processor.cpp:40:1: warning: when initialized here [-Wreorder]
40 | VapourSynthScriptProcessor::VapourSynthScriptProcessor(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
../../common-src/vapoursynth/vapoursynth_script_processor.cpp: In member function 'QString VapourSynthScriptProcessor::framePropsString(const VSFrame*) const':
../../common-src/vapoursynth/vapoursynth_script_processor.cpp:811:25: warning: declaration of 'error' shadows a previous local [-Wshadow]
811 | int error;
| ^~~~~
../../common-src/vapoursynth/vapoursynth_script_processor.cpp:720:9: note: shadowed declaration is here
720 | int error;
| ^~~~~
../../common-src/vapoursynth/vapoursynth_script_processor.cpp: In member function 'VSNode* VapourSynthScriptProcessor::invokeAkarinExpr(VSNode*, std::string)':
../../common-src/vapoursynth/vapoursynth_script_processor.cpp:1072:24: error: '_strdup' was not declared in this scope; did you mean 'strdup'?
1072 | const char* expr = _strdup(a_expr.c_str()); // convert string to char*
| ^~~~~~~
| strdup
make[1]: *** [Makefile:2234: ../../vsedit/generated/obj-debug-64bit-gcc/vapoursynth_script_processor.o] Error 1
make[1]: Leaving directory '/run/media/sl1pkn07/COSAS/aplicaciones/vapoursynth-editor-2/pro/vsedit'
make: *** [Makefile:49: sub-vsedit-vsedit-pro-make_first] Error 2

[lansing]

seems you need build-essentials or something

try to no set `-spec linux-g++`

in any case. fail to biuld for me in my archlinux



Try replacing it with "strdup" instead, Qt complains about it being deprecated, that's why I change it to "_strdup". Seems like _strdup works only with Windows.

[lansing]

Update to version R6.3 (https://bitbucket.org/gundamftw/vapoursynth-editor-2/downloads/)

simplified changelog

- Preview filter UV plane contrast boosted so the chroma noise are more visible. Requires Akarin plugin. If the plugin is not installed, the feature will be turned off
- Resize UV plane in preview filters to match input resolution so that it doesn't look awkward for subsampling formats


And I fixed all reported bugs.

Here's a example about the difference between contrast boosted UV plane

before:
https://i.imgur.com/0wMaB7S.png

after:
https://i.imgur.com/6UYoB8e.png

It should be useful for people trying to clean up the noise in UV plane. The Akarin plugin (https://github.com/AkarinVS/vapoursynth-plugin) is required.

[sl1pkn07]

Try replacing it with "strdup" instead, Qt complains about it being deprecated, that's why I change it to "_strdup". Seems like _strdup works only with Windows.


i remember you can force deprecated thigs in Qt if add -DQT_DISABLE_DEPRECATED_BEFORE=0x050b00" (the hex is changed depend of the version of deprecation). but idk how force it in qmake (the line is for cmake based projects)

https://doc.qt.io/qt-5/qtglobal.html#QT_DISABLE_DEPRECATED_BEFORE

greetings

EDIT: pull changes to 3524b58 can abre to build without problems

but seems not play well with 4K non-Hidpi displays. some text in buttons not fit well and some widgets is bigger than usual

https://i.ibb.co/rpbjX9p/Screenshot-20211024-013523.png
https://i.ibb.co/cvygzh7/Screenshot-20211024-013629.png
https://i.ibb.co/7NNQ08M/Screenshot-20211024-013748.png

greetings

[lansing]

but seems not play well with 4K non-Hidpi displays. some text in buttons not fit well and some widgets is bigger than usual


I haven't touch anything on high dpi support yet. I have a 1440p monitor myself with text scaled to 125%, and the text on the buttons are overflowing too lol. It's not an urgent problem though, so it'll just have to wait a while.

[Reclusive Eagle]

Thank you so much for fixing the copy paste thing and you did it so quickly you are amazing lansing!

May I suggest 1 more crucial thing to implement in future?

So AvsPmod has this amazing feature where you can exit without saving and reopen to where you left off.
By itself its not that amazing. However, a lot of the time scripts can tend to push VapourSynth too far and crash it, it can become permanently not responding etc.
This can also be caused by future and current bugs.
If VapourSynth Editor 2 saved current scripts as temp files like AvsPmod does, it would mean even if VapourSynth crashes you can just reopen it and recover all your code. Potentially saving you hours or even days of work because of a hung program or crash.

[l33tmeatwad]

Pro files need to be updated for it to compile on macOS, change from:

contains(QMAKE_COMPILER, clang) {
QMAKE_CXXFLAGS += -stdlib=libc++
}
To:
contains(QMAKE_COMPILER, clang) {
QMAKE_CXXFLAGS += -stdlib=libc++
CONFIG += c++17
}
In dark mode the text is black on dark gray...and it crashes when previewing or closing the application.

[lansing]

Pro files need to be updated for it to compile on macOS, change from:

contains(QMAKE_COMPILER, clang) {
QMAKE_CXXFLAGS += -stdlib=libc++
}
To:
contains(QMAKE_COMPILER, clang) {
QMAKE_CXXFLAGS += -stdlib=libc++
CONFIG += c++17
}
Added. Thanks.


In dark mode the text is black on dark gray...and it crashes when previewing or closing the application.
The program doesn't have a dark mode.

[l33tmeatwad]

The program doesn't have a dark mode.
I'm referring to macOS dark mode, the newer versions of Qt allow dark mode to adjust the applications. If the text is set to black it won't adjust, but if it's like default it will change to white in dark mode. I actually had to make that adjustment in a program that I've made.

[lansing]

I have corrected the wave form histogram from vapoursynth-histogram (https://github.com/dubhater/vapoursynth-histogram/pull/8). Now it's possible to add the wave form monitor and RGB parade to the program.

[lansing]

Update to version R6.4 (https://bitbucket.org/gundamftw/vapoursynth-editor-2/downloads/)

All bug fixes. Took some time to debug a crash that was caused by using QPixmap created from QPixmap::fromImage(frameImage, Qt::NoFormatConversion). This pixmap doesn't have the shallow copy feature of regular QPixmap. So in cases of a failed script, the framepainter would still look for a saved copy of a frame to paint, and crashed when it couldn't find any. A solution to this is to make a manual copy with framePixmap.copy(), but then 4K playback speed would turns turtle again.

The workaround is to just set a dummy pixmap to the framepainter before the preview call, so when script fails, there would still be a pixmap copy saved in the framepainter.

[motbob]

6.4 crashes when I try to open preview. Windows 10. I can provide logs if you tell me how.

[lansing]

6.4 crashes when I try to open preview. Windows 10. I can provide logs if you tell me how.

How to reproduce it?

[motbob]

How to reproduce it?

Extract contents of R6.4 folder to desktop. Double-click vsedit.exe. Write one of the following scripts:

import vapoursynth as vs
from vapoursynth import core

video = core.ffms2.Source(source=r"C:\Storage\Downloads\funi.mkv")

video.set_output()

Or,

import vapoursynth as vs
from vapoursynth import core

video = core.lsmas.LWLibavSource(source=r"C:\Storage\Downloads\funi.mkv")

video.set_output()

Press preview button or press f5. Program closes. The "Benchmark" function works fine.

EDIT: I'm on R57, should've mentioned.

EDIT2: Oh, I guess you need the LibP2P plugin, or it will crash without an error message. I discovered this by looking at the changelog by chance. Forgive me if this was put somewhere prominent and I missed it, but if not, perhaps put this dependency in the OP or something.

[lansing]

EDIT2: Oh, I guess you need the LibP2P plugin, or it will crash without an error message. I discovered this by looking at the changelog by chance. Forgive me if this was put somewhere prominent and I missed it, but if not, perhaps put this dependency in the OP or something.

I updated the OP on requirements.

The library could be implemented into the program through its API, which makes it works right out-of-the-box. But then as more features are to be added, there is going to be more dependencies anyway, so it doesn't matters.

[lansing]

Update to version R6.4 (https://bitbucket.org/gundamftw/vapoursynth-editor-2/downloads/)

All bug fixes. Took some time to debug a crash that was caused by using QPixmap created from QPixmap::fromImage(frameImage, Qt::NoFormatConversion). This pixmap doesn't have the shallow copy feature of regular QPixmap. So in cases of a failed script, the framepainter would still look for a saved copy of a frame to paint, and crashed when it couldn't find any. A solution to this is to make a manual copy with framePixmap.copy(), but then 4K playback speed would turns turtle again.

The workaround is to just set a dummy pixmap to the framepainter before the preview call, so when script fails, there would still be a pixmap copy saved in the framepainter.

I finally found the reason for the crash. A better explanation quoted from here (https://interest.qt-project.narkive.com/bQJNQHCv/convertion-between-qimage-to-qpixmap-taking-to-much-time):

You construct your QImage from a uchar* right? This constructor does not take a deep copy of the image data you pass in, it just stores it. That means that if you for some reason delete the source data before Qt takes it into use (which happens typically on the next paint cycle or in your custom graphics item), you will have a dangling pointer in the QImage you are drawing and that will typically crash.

The solution is to keep the image data alive before the next paint event, which means keeping the VSFrame alive, just like Yomiko did here (https://forum.doom9.org/showthread.php?p=1951082#post1951082).

[lansing]

Update to version R6.5 (https://bitbucket.org/gundamftw/vapoursynth-editor-2/downloads/)

A new scopes dialog window to display histograms/waveform/scopes/RGB parade. So far I only have the waveform added to see how to user experience goes. There are still many things to consider, for example, how should the graphs be displayed? Should we display each one at a time or with 4 different graphs stitched together? What are people's usage routine? And then there's the decision on the resolution of the waveform, for right now I have it scaled down to 480 x 320.

And then there's the RGB parade implementation, do I implement it right into vsedit2 or the histogram filter? As the latter will lack customization.

I also added a check for dependency plugins when you press preview, so there should be no more crashes on missing dependencies. For the vapoursynth-histogram plugin, use my fork (https://github.com/gundamftw/vapoursynth-histogram/releases) for now as jackoneill haven't been active for a while to update the main one.

[Tima]

R6.5 exits immediately after pressing F5.

Win10, VS r57 portable, LibP2P r2.

from vapoursynth import core
clip = core.std.BlankClip()
clip.set_output()

EDIT: I was using the original vapoursynth-histogram plugin instead of the temporary fork.
Since the silent crash is very confusing, I'd suggest to put the warning instead.

[Tima]

Some more bugs/crashes:

1. As I noticed today, R6.5 still crashes on the sample clip (but works fine on other "real world" inputs, like FFMS2) even with correct LibP2P and vapoursynth-histogram mod:
from vapoursynth import core
clip = core.std.BlankClip()
clip.set_output()

2. R6.5 crashes when trying to output grayscale video:

from vapoursynth import core

<some ordinary processing script>

# Uncommenting the line below crashes VSEdit
clip = core.std.ShufflePlanes(clips=clip, planes=1, colorfamily=vs.GRAY)

clip.set_output()


3. When using prefilter to view a single YUV plane, image contrast jumps up and down on U/V planes when playing back the output (because of the contrast boost?).

4. When you choose some plane in preview filter and then change script and reload the review, the image is shown without filters (but the button is still activated).

5. Feature request: please, make "UV plane contrast boost" "UV plane resize to match input resolution" features to be configurable (maybe just add toggle buttons in Prefilter dialog window?).

[tuanden0]

Help. I couldn't open vpy script.

Downloaded the lastest version and can open it.
Downloaded the LibP2P and extract it to vapoursynth-plugins 64bit folder
Try to run vpy script to check => error missing LibP2P, vapoursynth-histogram, akarin
Try to add vapoursynth plugin path to VSE 2 => unable to open it untill remove config and config2

[~ VEGETA ~]

hello, when i try to see the script by pressing f5 on windows 10 the program stops responding and closes despite vsedit 1 works fine. i made sure to install all dependencies.

[lansing]

Update on my progress, I'm back and currently working on the RGB Parade preview filter. I acknowledged the crash that was created by the waveform monitor. I will have an fixed version in a couple of days.

[~ VEGETA ~]

so can we expect it to work fine with vs57 in couple of days? thanks for your efforts.

plus wanted to ask you if there are any hotkeys for scenefiltering.

[Zarxrax]

Nothing happens when I execute vsedit.exe. No window comes up, no error message, nothing.
R6.5, and I put the LibP2P dll into the vapoursynth 64bit plugins folder.

Edit: I figured it out. I had downloaded the portable vaporsynth, and I didn't realize the files for the editor would have to go in the same folder.

[Zarxrax]

As someone with no experience with C++ programming, could someone tell me what all is required to build and modify this project? I would like to start learning and play around with it, but not sure how to start.

[lansing]

Update to version R6.7 (https://bitbucket.org/gundamftw/vapoursynth-editor-2/downloads/)

simplified changelog

- Added a RGB parade scope to the scope dialog
- Bug fix: grayscale video causing program crash
- Some file and classes renaming to avoid confusion
- Added an beta drag and drop functionality to open video file in new script


A long waited renaming to me is done. No more slotReceiveFrame and receiveFrame function which confused the heck out of me when debugging.

An unpolished RGB parade scope added to the scope dialog, you can now switch between waveform monitor and RGB parade scopes. One issue though is the memory usage. One my 1080p video, the waveform monitor uses about 80 MB while the RGB parade uses about 300 MB. I'm suspecting the reason to be because I'm doing the scale down using Qts' scale function instead of during the script. That'll have to be find out later.

Also I added a drag and drop functionality for video to directly input it into a template script ready for preview. The purpose with this is to make simple tasks like opening a video just to check on stuff as fast as possible like Avspmod. No keyboard intervention, you simply drag and drop a video into the program and it will open as a new script and you click preview, everything done in 2 clicks. Right now the template is hard coded for testing with only "mp4, mkv, mov" as detected extension. There is a "file drop template" function in the program but that was more like an "in-script file drop" rather than "file drop to new script." I'll see if I can merge both into one.

[lansing]

I think the current "file drop template" system needs to go. Its usage is too loose to a point that nobody knows what to do with it. The general use of the file drop functionality in a script should be just to insert a template script for opening media files with a source filter. The "category" field serves no purpose except for grouping of file extensions that share a similar template, which is not user friendly for searching.

[~ VEGETA ~]

I am using latest vapoursynth and vsedit 2 with python 3.10.4 but still vsedit 2 crashes after pressing preview. I noticed it detects script errors when they happen and even make lsmash index file when pressing preview, but when it needs to output the video it crashes.

I am on windows 10.

[lansing]

I am using latest vapoursynth and vsedit 2 with python 3.10.4 but still vsedit 2 crashes after pressing preview. I noticed it detects script errors when they happen and even make lsmash index file when pressing preview, but when it needs to output the video it crashes.

I am on windows 10.

Probably missing plugins for the preview filters.

My fork of the vapoursynth-histogram (https://github.com/gundamftw/vapoursynth-histogram/releases)
The Akarin (https://github.com/AkarinVS/vapoursynth-plugin/releases) plugin.

[~ VEGETA ~]

Probably missing plugins for the preview filters.

My fork of the vapoursynth-histogram (https://github.com/gundamftw/vapoursynth-histogram/releases)
The Akarin (https://github.com/AkarinVS/vapoursynth-plugin/releases) plugin.

ok but which ones? how can I know?

the same scripts work fine with vsedit 1.

[Julek]

ok but which ones? how can I know?

the same scripts work fine with vsedit 1.

As described here (https://forum.doom9.org/showthread.php?p=1919799#post1919799), you need both to use vsedit 2

About the various akarin versions, they all have Expr, so you can choose any one, what changes are the cuda filters.

[~ VEGETA ~]

Now it worked fine after installing those plugins. thanks.

however, I really like to know how to move between scenes using shortcuts or so. please advise.

[lansing]

however, I really like to know how to move between scenes using shortcuts or so. please advise.

The program doesn't have such function. I think it can be achieved by looking for the next I-frame in the output, but I don't know how is the performance when doing it on the fly.

[Tima]

@lansing -- could you pls add an option to disable "UV plane contrast boost" feature to be able to see untouched planes?

[~ VEGETA ~]

I managed to get bookmarks via that python script vsbookmark but I'd like to see how to do this:

1- get these bookmarks to show at timeline.

2- use shortcuts to move between them.

thanks

[lansing]

@lansing -- could you pls add an option to disable "UV plane contrast boost" feature to be able to see untouched planes?

Do you have a reason for that? From my experience, the UV planes are good to let people test their denoiser settings on those planes. However without the contrast boost, they would be so washed out that you couldn't really see anything. As of now, you can remove the akarin plugin and the program will fall back to the regular UV planes display.

[Tima]

Do you have a reason for that? From my experience, the UV planes are good to let people test their denoiser settings on those planes. However without the contrast boost, they would be so washed out that you couldn't really see anything.

The contrast jumps back and forth between consecutive frames -- this is really confusing.

Also, one might need to look at exact UV planes content for reasons other than denoising :)

[Blue_MiSfit]

Any plans to make this friendlier with DPI scaling? I run 150% and the widgets get pretty messed up :)

[~ VEGETA ~]

I managed to get bookmarks via that python script vsbookmark but I'd like to see how to do this:

1- get these bookmarks to show at timeline.

2- use shortcuts to move between them.

thanks

still no answer to my questions. what do you think about them, especially number 2 since I got 1 to work.

[lansing]

still no answer to my questions. what do you think about them, especially number 2 since I got 1 to work.

I don't know what the vsbookmark is, what does it do?

How you tried the bookmark manager in the program?

[~ VEGETA ~]

I don't know what the vsbookmark is, what does it do?

How you tried the bookmark manager in the program?

vsbookmark is this: https://gist.github.com/OrangeChannel/b9666b3650a3448589069d25dd6a394c

mentioned here: https://guide.encode.moe/encoding/scenefiltering.html

However, this doesn't solve the other issue of not having quick keyboard shortcuts to switching between the bookmarks. what do you say about this? any solution?

if this method is not best, then how to do it via the built-in bookmarks manager?

[lansing]

vsbookmark is this: https://gist.github.com/OrangeChannel/b9666b3650a3448589069d25dd6a394c

mentioned here: https://guide.encode.moe/encoding/scenefiltering.html

However, this doesn't solve the other issue of not having quick keyboard shortcuts to switching between the bookmarks. what do you say about this? any solution?

if this method is not best, then how to do it via the built-in bookmarks manager?

The bookmark manager can take in chapter file or text file with number separated by a delimiter. Go into settings->common->bookmark saving settings, check "bookmark" and change delimiter to a comma, then you can load in the text file created by that "generate()" from the vsbookmark script in the bookmark manager. You can jump to certain bookmark by double clicking it.

Highlighting 300+ bookmarks on the timeline though is a big no no, as it will just turn the timeline into a big mess like the original vsedit.

What kind of shortcut are you looking for? I haven't put a lot of thought into it since nobody ask for them.

[~ VEGETA ~]

it didn't work. I generated the bookmarks then opened it and saved it as txt file. when I load it inside vsedit2 it doesn't appear.

Some other times they appear... so I don't know what is going on.

can you kindly test it yourself ?