MantisBT

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007181ardourfeaturespublic2016-12-19 00:362017-01-11 23:06
Reporter.onkel. 
Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
StatusnewResolutionopen 
PlatformOSOS Version
Product Version5.5 
Target VersionFixed in Version 
Summary0007181: OSC unable to determine master strip ID
DescriptionWhile improvement of my Android app I ran in an issue regarding strip addressing.
On startup I request the current strip list via /strip/list and weakly assign the remote ID of the master strip as max-strip-id + 1. So in case of hidden strips, this calculation leads in a faulty value.

Even if most master controls are accessible via /master/xxxx messages, plugins and sends are not available.
Some deeper investigation didn't result in a robust way to determine the correct ID.

If you have an idea on how to work around this behavior, please let me know.

My suggestion would be to add the master strip information to the end of "/strip/list" result (see attached patch file).
TagsNo tags attached.
Attached Filespatch file icon master_strip.patch [^] (903 bytes) 2016-12-19 00:36 [Show Content]

Sponsor - Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 5

2017-01-11 23:06: .onkel. (US$ 5)

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2016-12-19 00:36 .onkel. New Issue
2016-12-19 00:36 .onkel. File Added: master_strip.patch
2017-01-11 23:06 .onkel. Sponsorship Added .onkel.: US$ 5
2017-01-11 23:06 .onkel. Sponsorship Total 0 => 5


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker