During measurement, in measure tab:
Sound feedback on measurement actions:
Add Checkbox for enabling sounds during measurements, in measure tab.
Sounds at specific events:
Measurement events:
- tick (default), click, or small ding sound on successful patch read,
- small thump shound when patch outside delta e limit,
- bell on successful strip read,
- "failure" sound if strip read failed,
- error sound on instrument failure or other crash.
- "Slow down" sound if measurement speed too high (see below): Separate intuitive sound indicating to slow down, or voice saying "Slow down" (depending on language selected)
Task complete event:
- Options in pulldown list: Sound for completed action (upbeat trumpet sequence, or drumroll (default), or applause, and maybe some other good options)
This pulldown list should be specified separately for the following completion events, so that the sound used can be selected for each separately:
- Measurement finished
- Building profile finished
Add new "Sounds" tab in preferences: Add frame for "Sounds at measurement actions" and "Sounds at action completion". Add all events above in its appropriate frame, with a pulldown box for each event, where suggested sound is selected as default. The pulldown list is the same for all, except "Slow down" (has special voice sound and special sounds that intuitively gives message to slow down) and "Task complete events", containing 24 to 30 types of sounds, plus "OFF": The above mentioned, and other similar relevant short sounds, at least 3 alternatives for each above event (chimes, bells, tick-sounds, click-sounds, bump-sounds, error sounds, failure sounds, drum-roll, short trumpet sequence for success etc).
Make sure all sounds happen at the exact correct time, not delayed. All sounds only happen during measurement, except.
Describe feature in help icon in measure tab.
Preferences Paths tab must add another reference folder location for the location of "Sounds" files. The name of the sounds in that folder build the list of sounds above, according to the group defined as a sub-folder. The "Slow down event" and "Task complete events" and "Measurement events" should have separate sub-folders defining its available options in the pull-down list.
Live feedback on Measurement Speed
Add Checkbox for enabling speed feedback during measurements, in measure tab.
Add new "Measurement" tab in preferences: Add frame "Measurement Speed". Add Instrument selector, which shall automatically load instrument selected in Create Chart (similar as tab Instrument Limits). Add new Slow Measurement Speed Threshold parameter (which has one threshold for each instrument). The threshold is a minimum value "Minimum samples per patch before slow down message".
Sampling frequency is different for various instruments. Calculate patches per second needed for good measurement results, also taking into account patch length in reading direction and spacer. Speed advice also depends on at least one sample must catch the spacer when passing, thus spacer thickness must also be part of calculation, if spacers exist.
Then give live text advice while measuring, on screen (below strip being measured), if user is too fast and must slow down. The threshold for when message happens is defined in preferences, as mentioned above.
When good speed range, live text feedback is "Good reading speed".
If sound enabled, say words «slow down» (default) in a calm and attractive voice (depending on language).
For ex. for Colormunki/i1Studio: instrument samples 50 times per second, 5-7 seconds to read a strip is usually good, but "slow down" message should happen if less than 20 samples per patch (default value). Range of selection list is 1 to 100.
This allows for different measurement speed depending on patch and spacer size.
i1Pro I think samples 200 times per second. This allows for good patch measurements even with higher speed, but density of samples at a given speed must still be such that spacer is caught. Good speed would normally be 3-5 seconds per strip. Less than 3 seconds is fast, and threshold should be set accordingly. The threshold list range for selection must be reasonable according to the instruments sample speed and what a normal good speed is.
Verify used sampling speed for all supported instruments by searching product datasheets and product information online. Search also online for indicators on what a good normal measurement speed is for each instrument. Compare with suggested values above and set good defaults.
Describe feature in help icon in measure tab.
Proposed solution
N/A
Alternatives considered
No response
Relevant platform(s)
Any / all
Anything else?
No response
During measurement, in measure tab:
Sound feedback on measurement actions:
Add Checkbox for enabling sounds during measurements, in measure tab.
Sounds at specific events:
Measurement events:
Task complete event:
This pulldown list should be specified separately for the following completion events, so that the sound used can be selected for each separately:
Add new "Sounds" tab in preferences: Add frame for "Sounds at measurement actions" and "Sounds at action completion". Add all events above in its appropriate frame, with a pulldown box for each event, where suggested sound is selected as default. The pulldown list is the same for all, except "Slow down" (has special voice sound and special sounds that intuitively gives message to slow down) and "Task complete events", containing 24 to 30 types of sounds, plus "OFF": The above mentioned, and other similar relevant short sounds, at least 3 alternatives for each above event (chimes, bells, tick-sounds, click-sounds, bump-sounds, error sounds, failure sounds, drum-roll, short trumpet sequence for success etc).
Make sure all sounds happen at the exact correct time, not delayed. All sounds only happen during measurement, except.
Describe feature in help icon in measure tab.
Preferences Paths tab must add another reference folder location for the location of "Sounds" files. The name of the sounds in that folder build the list of sounds above, according to the group defined as a sub-folder. The "Slow down event" and "Task complete events" and "Measurement events" should have separate sub-folders defining its available options in the pull-down list.
Live feedback on Measurement Speed
Add Checkbox for enabling speed feedback during measurements, in measure tab.
Add new "Measurement" tab in preferences: Add frame "Measurement Speed". Add Instrument selector, which shall automatically load instrument selected in Create Chart (similar as tab Instrument Limits). Add new Slow Measurement Speed Threshold parameter (which has one threshold for each instrument). The threshold is a minimum value "Minimum samples per patch before slow down message".
Sampling frequency is different for various instruments. Calculate patches per second needed for good measurement results, also taking into account patch length in reading direction and spacer. Speed advice also depends on at least one sample must catch the spacer when passing, thus spacer thickness must also be part of calculation, if spacers exist.
Then give live text advice while measuring, on screen (below strip being measured), if user is too fast and must slow down. The threshold for when message happens is defined in preferences, as mentioned above.
When good speed range, live text feedback is "Good reading speed".
If sound enabled, say words «slow down» (default) in a calm and attractive voice (depending on language).
For ex. for Colormunki/i1Studio: instrument samples 50 times per second, 5-7 seconds to read a strip is usually good, but "slow down" message should happen if less than 20 samples per patch (default value). Range of selection list is 1 to 100.
This allows for different measurement speed depending on patch and spacer size.
i1Pro I think samples 200 times per second. This allows for good patch measurements even with higher speed, but density of samples at a given speed must still be such that spacer is caught. Good speed would normally be 3-5 seconds per strip. Less than 3 seconds is fast, and threshold should be set accordingly. The threshold list range for selection must be reasonable according to the instruments sample speed and what a normal good speed is.
Verify used sampling speed for all supported instruments by searching product datasheets and product information online. Search also online for indicators on what a good normal measurement speed is for each instrument. Compare with suggested values above and set good defaults.
Describe feature in help icon in measure tab.
Proposed solution
N/A
Alternatives considered
No response
Relevant platform(s)
Any / all
Anything else?
No response