flowframes
flowframes copied to clipboard
n00mkrad
Scene detection assistant
Scene detection puts this tool so much above the competitors. But it would be nice if there was some sort of pre-processing tab/step/tool that you could use to help fine tuning the sensitivity (rather than having to go back and forth between temporary folders and several testing runs).
In fact, it would be superlative if you could preview the scenes directly into the UI, to manually scrub dupes (so you that you don't have to compromise in accuracy even if there's a lot of fast scenes)
Try Transitionchooser. You can get the latest build from NMKD's Discord server.
The tool is pretty cool, if rough. But that only helps you with (duh) choosing transitions. In other words, how they happen, as opposed to when/if.
Ok, I see it now. You can tinker with that after you enable Show Pics Player. Too bad that I cannot get it to work with the flowframes ini, but I must create a fresh one (probably because I'm using the free version, maybe it needs the json stuff from 1.34.0).
Anyhow, well, it would be great if it could be integrated here. Hopefully it could even work before the interpolation step.
Ok, actually, nevermind. I'm still getting this even with 1.35 (and yes, I did disable autoencode and enabled scene detection)
Count of scenescuts in INI and scenecusts of png folder don't match
Can't get the out-fps value from interpSettings.ini
After some digging, this clearly means that despite nominally having been updated less than a year ago, Transitionchooser FF-edition never moved past the design it had here. The only "native versions" are basically those between 0ed0ca91a4e6b8587b561b1f7292ddd036484d8c and 4048d2f74c35cc29bf3565c0901a9388b915259f.
Ok, actually the magenta cloud link is updated behind the scenes. Latest version is 13.0, which has no problem with my current flowframes. It's pretty nice and smooth looking in fact. But for the love of me I cannot manage to delete any false positive scene change. The readme seems to hint that I should "err on the side of having to few" in FF if any, and then at most add them from TC. Which seems very cumbersome really, given that deleting something that already exists is way faster than having to create it with a precise selection.
I have also a hard time understanding b51ee375e5ce175a0921a9a77d90d0dc4deeb93b, as if interpolation wouldn't greatly benefit from not having to deal with the wrong scene "borders".
Hi transitionchooser 19.2 is there download here: https://magentacloud.de/s/rMCAGfrWLP62gxc
False positives scene changes can easiely be set to "red interpolframes" or deleted. Let me know if you have any questions. It works also with other AIs -tools as Flowframes. But you must have a folder with interp-pics.
I still feel like deleted scene changes should be underlined more clearly Anyway, your tool is really poggers and the icing on the cake to the whole endeavour. It would be cool if source was also available.
Well, the concept is that false transitions should changed to "red interpols". Its the same as if there is no transition. Just for clarity and shorter list, you can delete them. (but they will be lost if you want to change them later for any reason, you must set them again in picplayer) TC doesn't delete scene change that Flowframe has found. It lists them all. They can only be deleted manually.
Transitionchooser is there with many improvements
CHANGES IN 21.0
-Made TC capable also for "jpeg" file extensions. -Import of transitions by image folder was made faster and bug fixed -Import of transitions by thumbnail selection was made faster and bug fixed -Import by buttons (Start / End) was made faster, and a range of 10 000 images is now possible instead of 1000 -The creation of blends can now be cancelled during the process if it takes too long for the users -The list and the slider scrolled together when the mouse wheel was pressed, fixed! -Delete function now deletes ALL marked transitions (not only the red ones) and is now faster with many tranisitons in list -Changing transition "sorts" is now much faster with a large selection using the buttons or keys 1,2,3,4 (left keyboard) -Selecting sorts with LEFT CTRL+1...4 is faster now, but with 100 000 transitions (sick!) it still takes about 10 seconds (otherwise CTRL+A for all is very fast) -less annoying and strict behaviour, if blendpics from a previous run are already in the blends-folder, can bring problems, but the users should take care of that -output of simple cutlist (txt) while saving the edited list disabled for now. (maybe later...)
https://magentacloud.de/s/rMCAGfrWLP62gxc