Is it possible to get the groove from Live?


    Jun 03 2015 | 6:45 pm
    I'm making a plugin for someone who uses groove templates a lot in Live and was wondering if there is a way to get the timing info into max for live.
    Any clues,?
    Thanks,
    John.

    • Jun 03 2015 | 6:57 pm
      Are you making a plugin or a M4L device? You can get the groove amount, but as far as the template I didn't see anything after a quick look through the API. They are contained in .agr files, which I'm not really sure what to do with, i tried opening them in text edit, but there was a bunch of nonsense, so as far as getting the timing from the loaded groove, it's gonna be tough.
    • Jun 03 2015 | 7:05 pm
      An M4L device, sorry I wasn't clear on that. Thanks for investigating the API - I had a look at the .agr files too but it looks like the timing info in encrypted.
      The only way i could think of is sending a stream of 16th notes into the plugin and getting the timing info from them in real time.
      Best,
      John.
    • Jun 03 2015 | 7:32 pm
      Yeah that's a possibility. How are you going to use the timing info?
    • Jun 03 2015 | 11:35 pm
      Keep in mind that groove patterns in Live are applied to clips where the timing of notes can easily be moved forward or backward. But if you want to apply a groove to incoming notes on-the-fly, the timing can only be moved forward (delayed).
    • Jun 04 2015 | 2:02 am
      it's essentially a buffer shuffler type of device - so it's important that the groove of the shuffled sections match that applied to any of the other Midi or Audio tracks in the project. I can get this by sending groovy 16th notes into the device and using those to trigger the shuffling but it'd be nice not to have to do that.
    • Jun 04 2015 | 4:09 am
      Well unless you can find a way to grab the .agr files within M4L and decode the information, you'll have to find a workaround. I see no easy solution, unfortunately.
      Good luck.
      Edit: Although, now that I think about it, if you're shuffling audio that's coming into the device, it can already have the groove applied. So applying the groove to the shuffling seems redundant, unless I am not understanding you correctly.
    • Jun 09 2015 | 8:32 am
      I'm shuffling audio that is loaded into the device, I'm using incoming midi notes to trigger slices (these midi notes can have groove applied). This all works fine but I wanted to eliminate the need for the incoming midi notes. I didn't find a way to access groove information so far so I'll just stick with what I've got for now.
      Thanks for your help.
      John.