Notifications
Clear all
Developers & MIDI 2.0 Specifications
6
Posts
3
Users
0
Reactions
212
Views
Topic starter
• As a reply to an Endpoint Discovery message with the 's' bit set in the Filter Bitmap field.
• As a reply to a Stream Configuration Request message.
• As a notification when any property in this message has changed.
Wondering why this "s" bit method is there. A host could just use the configuration request. Now there are two ways to request the same information.
Posted : 28/05/2024 2:04 am
The Stream Configuration Request is stating what you want the set-up to be, and then the notification is a way to confirm that request. On the other hand the 's' bit in the Endpoint Discovery Message allows you to just ask "what is your current configuration?"
Posted : 28/05/2024 4:42 pm
Topic starter
Both expect the same "notification" message. so the device should respond always what its configuration is, In case the device is not able to full the requested configuration, it returns what is has itself configured as, correct?
Posted : 01/06/2024 11:17 pm
In case the device is not able to full the requested configuration, it returns what is has itself configured as, correct?
Correct 🙂
Posted : 02/06/2024 3:16 pm
Topic starter
Thanks, it could mean, worst case, the two end could end up not agreeing on a protocol, and thus no communication ?
An accepted (replied) stream request would also reset/overrule any protocol settings reported before through FB/Endpoint notifications ?
Posted : 15/08/2024 12:02 am
The Stream Configuration Request specifies the desired setup, while the notification confirms that setup. The 's' bit in the Endpoint Discovery Message, however, allows you to inquire about the current configuration without making any changes. This distinction helps manage and verify system settings effectively.
Posted : 21/08/2024 5:46 am
