Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Listening sometimes does not work #36

Closed
jcelerier opened this issue May 31, 2016 · 1 comment
Closed

Listening sometimes does not work #36

jcelerier opened this issue May 31, 2016 · 1 comment

Comments

@jcelerier
Copy link
Member

jcelerier commented May 31, 2016

When loading this score:
https://gist.github.com/bltzr/ce30146e79bd59663066b57df7df5490

Recording does not seem to work (it uses listening).
But when debugging it can be seen easily when trying to change the value on the device explorer.
I checked and :

void JamomaAddress::observeValue(bool enable)
{
  TTAttributePtr attribute;
  mObject.instance()->findAttribute("value", &attribute);

  if (enable)
  {
    attribute->registerObserverForNotifications(mObjectValueCallback);
    //////// ** the code passes here ** ////////
  }
  else
  {
    attribute->unregisterObserverForNotifications(mObjectValueCallback);
  }

  // for Mirror object : enable listening
  if (mObject.name() == kTTSym_Mirror)
  {
    TTMirrorPtr(mObject.instance())->enableListening(*attribute, enable);
    //////// ** the code passes here ** ////////
  }
}

but when I do address->pushValue(...) the callbacks are not called, even if :


bool JamomaAddress::pushValue(const TTValue& value) const
{
  TTErr err;

  if (mObject.name() == "Data")
    err = mObject.send("Command", value);
  else
    err = mObject.set("value", value);      //////// ** the code passes here ** ////////

  return !err;
}
@jcelerier
Copy link
Member Author

I tried changing the protocol to OSC (in the save file, change line 28666 to

"Protocol": "9a42de4b-f6eb-4bca-9564-01b975f601b9"

)
and in this case it works so maybe when the minuit device is not actually connected it is useless to try to send messages to it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant