On February 4, 2013 09:28:35 AM Luis Garrido wrote: > On 02/04/2013 02:11 AM, Florian Jung wrote: > > so, is there any way to get extended information like tempo or beats > > inside a plugin (preferably LADSPA or LV2?) > > For LADSPA no way at all. Well, no sane way; you can always work out > ugly hacks, but it is probably not worth the pain. > > For LV2 you would have also to add support for some LV2 extensions: > > http://drobilla.net/2012/11/17/lv2-plugin-transport-synchronisation/ > > Cheers, > > Luis >
Native VST has it. MusE supplies the VST with timebase info via the main VST callback. So for example VST sequencer or beat-matching plugins should work :) Or you could accept midi clock which MusE transmits, into a DSSI plugin. That'll give you tempo. If we ever finish the midi MTC time code features you might also have linear (audio) time at your disposal via the midi. Or how about using a DSSI midi controller, or a LADSPA/DSSI/etc audio controller port in your plugin labeled 'tempo'? And two more for signature? Crazy idea? Hm, it's late. You could also see if Jack is running and maybe ask the server for the current timebase which MusE transmits. But a plugin that relies on Jack? Meh, better let the app pass it. Tim. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
