|
|
|||||||
| RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
 |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
March 3rd, 2012
|
#1 |
|
Task Group Member
Join Date: Aug 2008
Posts: 390
|
This did get me thinking about the behavior of PARAMETER_DESCRIPTION. Because of the section 6.2.10.2 language, I'd previously said that to save time, you could send a GET PARAMETER_DESCRIPTION to one responder in the rig, and apply the response to all fixtures from the same manufacturer that declare support for that PID.
But the text only requires that they have the same "meaning", not the identical response. Different fixtures could have the same meaning, but have different values for Min/Max or similar. |
|
|
|
March 3rd, 2012
|
#2 | |
|
Task Group Member
Join Date: May 2010
Location: San Franciscio
Posts: 57
|
Quote:
When we reopen E1.20 and clean up the PARAMETER_DESCRIPTION PID we should fix this. Scott can you add it to the TODO list? Simon |
|
|
|
|
|
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Usage of PARAMETER_DESCRIPTION for manufacturer-specific PIDs | R.Schladör | RDM General Implementation Discussion | 9 | September 26th, 2018 12:04 PM |
| Refreshing "parameter_description" ? | theguenni | RDM General Implementation Discussion | 0 | February 29th, 2012 02:36 PM |
| Refreshing of paramters need Queued Messages? | berntd | RDM General Implementation Discussion | 33 | May 25th, 2010 02:09 PM |
| PARAMETER_DESCRIPTION data type semantics | tim_ecue | RDM Interpretation Questions | 4 | October 14th, 2009 10:47 AM |
Hybrid Mode
