[sharing] create thumbnails patch
Greetings,
Here’s a ‘create thumbnails’ patch that grew out of something I was working on. I saw a few posts on the forum looking for solutions so I thought I’d share this approach.
I’m sure the cool kids would use js or poly or something… but I’m not there yet. I saw some patches that manipulated the dstdimstart/dstdimend of a matrix, but they weren't what I thought a thumbnail gallery should look like.
So I started playing with live.tab
It works, but it could use a few more features… and I could be a better patcherer.
How To Use
• Put the patch in a folder of movies, .mov .mp4 .mpg
• Open the patch - it auto loads the movies in the folder. Use prev/next if you want to scan the folder.
• Click MAKE THUMBNAILS
• Clicking the thumbnails updates the the video player
I built this on a Mac so I’m not sure how this works on Windows. Also it uses export image from jit.movie which can’t make thumbnails with the avf engine. The workaround is to use the qt engine to create the thumbs then switch to your preferred video engine.
Happy Patching!
Just realized Copy Compressed strips out some features. Here's the patch opening properly:
Hmmm... it still doesn't post properly. Anyways... just CMD double-click the p thumbs sub patch.
Love that patch! Too bad it doesn't work with Max8 !!!
So exportimage on Max8 is unavailable because I can't use 32 bit?
Gets really complicated that some functions are not working anymore.
Is Max8 working in 64 bit only on Mac?
whole macOS will stop supporting 32 bit code in a few weeks.
Roman do you think this will be the case for Windows?
Here's a bypass for this patch
exportimage is not available in 64 bit and with avf engine with jit.movie but works with jit.matrix I have put a jit.matrix at the output of jit.movie and the output for pGATE from the jit.matrix
not for windows itelf, but for max 8 for sure.
Roman
Is there any documents or explanations available from Cycling74 regarding this subject that you recommand on how it will affect previous objects and patchs?
not sure about resources, but it should be pretty simple:
patches, texts, and various forms of data (audio files, jitter binary data, shaders) are not affected, as long as they do not require any compiled external object which is not available for 64 bit
or with other words: vanilla max is not affected.
that one big point you have to check is: do your patches use third party externals? if yes, you need to upgrade them one by one.
regarding quicktime and avf i wouldnt worry, there will for sure always be a solution.