Hello everyone,
I'm newly on the journey of switching over from Resolume to vdmx. A handly little quartz patch I use frequently is Coge's beatdetektor.
http://code.google.com/p/cogebeatdetektor/
Now in Resolume I have a little QT comp that normalises the value of the bpm and sends it via OSC to Resolume. I load this comp as a clip in resolume on a layer I never touch. Now from what I have gathered from searching the forums and VDMX updates, instead of OSC i should be using a input splitter that is a number and has reasonable min/max values. From there, I publish the output of the splitter, labeling BPMOut after connecting it to the bpm value of the cogebeatdetektor patch. From there drag to my plugins folder.
Seems refreshingly simple and is quite exciting compared to resolume's workflow. If I have erred in some way hopefully someone can set me straight in that part of the process. Now when i create a new clock in vdmx i'm having a devil of a time getting it to sync to my BPM counter. Is this a incorrect expectation for vdmx workflow? Instead of syncing my clock should i be using BPMOut as a data source? My effect loads with correct min/max sliders which are published inputs. I'm positive its my relative inexperience that is causing this and i'm sure someone can set me straight. I downloaded the sample BPMOut that was provided by one of the mods (SetClockBPM, a helpful little example) and this also is unable to do anything BPM wise in vdmx. Both plugin's show up as data source and do the exact same erratic min/max behaviour if I try to sync something to them(LFO time for example).
All of this really makes me think I'm likely not connecting things correctly within VDMX. If anyone could guide me on syncing up this BPMOut QT comp with the internal clock it would greatly be appreciated.