Ultrasound image always overexposed

Support
,
1

Operating system: Windows 10
Slicer version:Slicer4.10.2
Ultrasound: Telemed EchoBlaster
Expected behaviour: Ultrasound setting carried over from Echowave
Observed Behaviour: Ultrasound image is over exposed (Gain appears to default to 100)

Hi, I am using slicerIGT link to combine motion capture from OptiTrack and Ultrasound from Telemed. I am using the Telemed 32 bit version of PLUS. I am trying to set up my ultrasound, however the settings that i select in Echowave (Telemed software) do not appear to be carried over. Most of the other settings appear to be carried over fine, however i believe the Gain is not. In Slicer the the image is always over exposed except when i set the image up in echowave to have a gain of 100 and adjust other variables to account for this. This leads me to believe that the gain is always set to 100 instead of copying the gain from Echowave. I have tried to use the default config that sets gain to -1 as well as trying to set the gain to 10. However this does not appear to have any impact on the image. Please let me know if i am doing something wrong, Thanks

Ultrasound image and settings in echowave - you can see the gain is set to 10

image
image1674×923 127 KB

Ultrasound image in slicer - you can see that the image is very over exposed

image
image1286×730 142 KB

Telemed exerpt from config file. I have tried with the GainPercent removed from the config, GainPercent set to -1 and GainPercent set to 10. None of these changes have made a difference in Slicer

image
image886×746 36.1 KB

2

What you see is just the automatic image window/level feature (brightness/contrast) in Slicer, which works well for static volumetric images, but ideal for live 2D ultrasound you probably want to set it manually. You can adjust display window/level in Volumes module or using window/level mouse mode.

3

Thank you for this advice. This solved my issue. This also solved another issue i had with exposure changing throughout a trial. Manually adjusting this within the Volumes module has fixed both issues

1 Like