I’m trying to build a patch for video scratching using MIDI controller no. 12 and the scratch performance is erratic, meaning, I’m only capable of working very slowly with the MIDI controller. High scratch speeds cause very bad behavior.
I’m using MJPEG codecs with keyframe every frame for best scratching performance.
I’ve developed video scratch solutions with other languages before, so I’ve been trying similar technics, but maybe they aren’t suitable for vvvv. For example, you may see my Gephex-based MIDI scratch system (VJ Tailor is my VJing alias while VirtualFlavius is used for research)
Attached is the barebones patch, I’d appreciate it if you could please check with your own videos and provide your ideas on how to make it behave better.
I actually think the problem is with the MidiController On Data and FileStream module Do Seek relationship. From what I’ve noticed, the On Data keeps sending a 1 for a very long time. I have to work very slowly with the controller in order for it to send a 0, which triggers the Do Seek on the FileStream.
you could trigger the DoSeek pin with a Change (Animation) node connected to the MidiController output. i saw that the Buffer Length pin on the MidiController node was set to 100 in your patch. set it to 0 an you should always get the latest value of your controller…
OK I havent actually checked your solutions, but I’ve scratched with mjpg avi’s, but maybe I didnt have such high standards, so what exactly is the erractic behavure you get?
1 thing you should not that if you use do seek with an avi file, you need to make sure that the play pin isnt enabled, this is a bug (i think from 9 onwards) or an anomily at least, if play is checked it tries to play and do seek at the same time, and it goes a bit weird, so a not node with the do seek would help.
I’ll maybe try later with a short avi, all on my laptop are too long for scratching really!
I’ve also had latency problems with my midi controller, is it this you experience?
Also Hard drive speed would make a difference!