Dear Giacomo, Something else came to my mind regarding the Telemed device: If you can't get it to work with direct MITK connection, you could use the Public software Library for Ultrasound (PLUS) for hardware connection and stream the images to MITK using OpenIGTLink. If you create a new video device in the Ultrasound Support view, you can then choose “OIGTL Client”. If an instance of the PLUS server is running in the background MITK should connect and provide the image stream for further processing in MITK.
Best, Alfred ________________________________ Von: Giacomo De Rossi <giacomo.dero...@univr.it> Gesendet: Samstag, 24. Februar 2024 19:39:01 An: Franz, Alfred Betreff: R: [Extern] - [mitk-users] Issues in MITK versions 2023.04.2 and 2023.12 Dear Alfred, thank you for your response and availability: I'll try to provide to you all the details and support I can to improve the MITK platform. Yes, the issue with the file does occur: it appears to occur at the restart of the video, but that should not occur unless the video file has been damaged. I did not disclose that the version of OpenCV I compiled with both version 2023.04.2 and 2023.12 is version 4.7.0 . regarding the TELEMED, unfortunately we are using a "ArtUS" biplane model which is still in "beta" and not generally available, so it's usage is limited to the most recent versions of the SDK . I was expecting some issues, but i found that possible race condition in both the mitkImage and ImageDescriptor wrapper. I attach a screenshot of the debug where the variable m_NumberOfDimensions changes from its value of "2" assigned right before to a non-initialized value within the scope of the function. I'm trying my best to identify the source of these issues, but I'm just a recent user of MITK, so I'm a bit swamped. For now, all I can try is to revert back to the first available TELEMED SDK version I can use with my probe. Best, Giacomo ________________________________ Da: Franz, Alfred <a.fr...@dkfz-heidelberg.de> Inviato: venerdì 23 febbraio 2024 12:49 A: Giacomo De Rossi <giacomo.dero...@univr.it>; mitk-users@lists.sourceforge.net <mitk-users@lists.sourceforge.net> Oggetto: AW: [Extern] - [mitk-users] Issues in MITK versions 2023.04.2 and 2023.12 Dear Giacomo, Thank you for your message. I use the plugin org.mitk.gui.qt.ultrasound mostly with Framegrabber and have not had these problems so far. However, I have tested the playback of video files with version 2023.04 and the described problem also occurs with me. I have therefore created a bug report for this under the number T30338. With regard to the USTelemed module, as far as I know the connection only works with the older USGFW2 SDK 3.21. I also have problems with the newer USGFW2-SDK-4.2.0. Perhaps you can try the older SDK. Which device do you actually work with? We use the Telemed Logicscan 128 ultrasound device. Best, Alfred ________________________________ Von: Giacomo De Rossi <giacomo.dero...@univr.it> Gesendet: Montag, 12. Februar 2024 14:38:29 An: mitk-users@lists.sourceforge.net Betreff: [Extern] - [mitk-users] Issues in MITK versions 2023.04.2 and 2023.12 Dear recipient, I'm a researcher at the University of Verona, Italy, who's using your SDK "MITK" to develop a custom made interface. I'm running the base code as cloned from your repo in debug mode and testing the MITK workbench application. I'm encountering possible race conditions on the execution of the code as I'm loading a simple video file via the MITKUSVideoDevice module but after a few minutes, it produces a "device or resource busy" fatal error. Please find attached a screenshot of the error. A similar issue seems to happen by testing the USTelemed module with a telemed ultrasound device: this time, again it crashes with an exception error almost immediately as it seems to run into a race condition within the mitkImage class. More specifically, the member variables m_Dimension and m_Dimensions are modified as the code executes within the "Initialize" method, bypassing their initialization values within the method itself. I'm writing to you to ask whether you already encountered these issues. To me they seem to happen in both MITK 2023.04.2 and MITK 2023.12 running in debug mode via Visual Studio 2019 (MSVC v142) on both Windows 10 and 11 (both running the Windows 11 SDK version 10.0.22621). Please contact me at this address for more information. Kind regards, Giacomo De Rossi
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
