You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using fCal to synchronize data from a frame grabber (Razer Ripsaw X) and the Aurora motion tracking system. Since the frame grabber captures everything displayed on the ultrasound screen, I was trying to apply a clipping process to work exclusively with the ROI of the ultrasound images.
The issue arises when I apply the clipping directly to the input image — I can no longer visualize the image correctly in fCal. However, if I save the image and open it in Slicer, it appears correctly. The problem is that after applying this initial clipping to the received frames, when I try to define a second window in the segmentation parameters, I am never able to do so. It seems that whatever window I define, the system assumes an incorrect one, ultimately crashing the fCal program. I have already tried segmentation windows such as:
ClipRectangleOrigin="575 123" ClipRectangleSize="320 460" or ClipRectangleOrigin="5 5" ClipRectangleSize="310 450", but none of them work as expected.
On the other hand, if I only define the window using the segmentation parameters (i.e., setting ClipRectangleOrigin="x y" ClipRectangleSize="x y"), everything works fine. The only issue is that I am forced to receive the entire ultrasound image beforehand. Please find attached the XML script I am using. I am currently working with version 2.8.0. PlusDevice_fCal_VideoForWindows_NDIAuroraTracker.txt
Would anyone be able to help me with this problem? I would be very grateful!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
I am using fCal to synchronize data from a frame grabber (Razer Ripsaw X) and the Aurora motion tracking system. Since the frame grabber captures everything displayed on the ultrasound screen, I was trying to apply a clipping process to work exclusively with the ROI of the ultrasound images.
The issue arises when I apply the clipping directly to the input image — I can no longer visualize the image correctly in fCal. However, if I save the image and open it in Slicer, it appears correctly. The problem is that after applying this initial clipping to the received frames, when I try to define a second window in the segmentation parameters, I am never able to do so. It seems that whatever window I define, the system assumes an incorrect one, ultimately crashing the fCal program. I have already tried segmentation windows such as:
ClipRectangleOrigin="575 123" ClipRectangleSize="320 460" or ClipRectangleOrigin="5 5" ClipRectangleSize="310 450", but none of them work as expected.
On the other hand, if I only define the window using the segmentation parameters (i.e., setting ClipRectangleOrigin="x y" ClipRectangleSize="x y"), everything works fine. The only issue is that I am forced to receive the entire ultrasound image beforehand. Please find attached the XML script I am using. I am currently working with version 2.8.0.
PlusDevice_fCal_VideoForWindows_NDIAuroraTracker.txt
Would anyone be able to help me with this problem? I would be very grateful!
Beta Was this translation helpful? Give feedback.
All reactions