Cycling 74 » Topic: M4l.api.SaveInteger possible gotcha http://cycling74.com/forums/topic/m4l-api-saveinteger-possible-gotcha/feed Thu, 20 Jun 2013 02:58:56 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/m4l-api-saveinteger-possible-gotcha/#post-56771 <![CDATA[M4l.api.SaveInteger possible gotcha]]> http://cycling74.com/forums/topic/m4l-api-saveinteger-possible-gotcha/#post-56771 Sun, 01 May 2011 21:08:23 +0000 orange_glass I’ve been using M4l.api.SaveInteger to.. well save an integer of an object ID in rather a large set. I’ve been a bit perplexed for a while now as it was saving the correct object ID for most objects, and just wouldn’t work when I tried to save certain objects. The object I was trying to save was a track that had an object ID in the 900s.

My problem was down to M4L.api.SaveInteger being limited to 127, I have now increased this to 999999. I thought I’d share this incase anyone else might be using M4L.api.SaveInteger or M4L.api.SelectDevice.

]]>