How do I avoid this unwanted MIDI Region?

Question

This happens at odd moments, but most recently with the Step Input Keyboard, in the Score Editor.
I added a note to a staff and the following occurred:
--A new treble and bass clef appeared in the staff with a line connecting the two staves (bass and treble).
--In the Arrange window, a new region appeared, labelled "midi region", right next to, but separate from, the existing region.
I have to delete this from the Arrange window and try again; usually the second time it's normal.
Can someone tell me why this happens, and how I can prevent it?

Answer 1

No - this limit is meant to guard the client from malicious servers. It is possible to send valid OData feed which will consume lot of memory to parse. This can be done on the XML level or on the OData level. This limit guards against both.
Servers have other ways to limit amount of data returned to the client, the reason there is to guard against expensive query execution
In general a good way to look at OData is to think about it as the "minimum necessary protocol" to do what is needed. We try to keep it that way anyway. It's also stateless (REST...). So the more coupling between client and server, the worse... so to say.
I can imagine having an HTTP header for this purpose, but I don't think that lot of clients would be interested in it.
I think you should approach this limit from the security point of view (that's what it's for). Set it to the maximum amount of memory you're willing to give up to process the response. At least roughly (the memory consumption should be linear to the size
of the input, cases where it's not are guarded by the other options on the MessageQuotas).
Thanks,
Vitek Karas [MSFT]