Can someone comment on what is newsworthy about this?
Someone using JPEGXL in a real world product
Philips announces digital pathology scanner with native DICOM JPEG XL output
21–30 of 56 posts
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#22Earlier quoted context omitted.
Strange that Mozilla is going to rely on an internal team at Google to build a decoder for them in Rust, when Google is the one trying to kill JPEGXL.
It's two different teams inside Google. Some part of the Chrome team is trying to quash JPEG XL.
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#23Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#24Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#25Earlier quoted context omitted.
It's two different teams inside Google. Some part of the Chrome team is trying to quash JPEG XL.
Sure, but if it becomes political I expect the Chrome team to fully quash the JPEG XL team to hurt Firefox and JPEG XL in one go.
JPEG XL was written in C++ in a completely different part of Google without any of the safe vanity wuffs style code, and the Chrome team probably had its share of trouble with half baked compression formats (webp)
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#26Ugh, Pathology image processing is really annoying. IF Philips is going to stick to the DICOM format, and not add lots of proprietary stuff, _and_ it's the format that it uses internally, then this will be good. For example, folks can check out OpenSlide ( https://openslide.org ) and have a look at all the different slide formats that exist. If you dig in to Philips' entry, you'll see that OpenSlide does not support…
Worse, you have to do it manually one by one in their interface, it takes like 30 minutes per slide and you only have like 20 minutes after it's done to pick it up and save it somewhere useful otherwise the temporary file gets lost.
DICOM is of course the way to go, but it does have its rough edges - stupid multiple files, sparse shit, concatenated levels and now Philips is the only vendor who makes JPEG XL (next to jpeg, jp2k and jpeg xr).
We learnt to live with iSyntax (and iSyntax2), if you can get access to them that is. In most deployments the whole system is a closed appliance and you have no access to the filesystem to get the damn files out.
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#27My first ever job in software was working for PathXL (a Belfast startup implementing digital pathology software). Lots of fond memories working there, including how cool it was working on what was effectively Google Maps but for massive tissue sample images. PathXL actually ended up getting acquired by Philips, seems like a great match if they're building the hardware for this.
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#28Always impressed when someone does anything with DICOM, it's a bit complex format IMHO.
Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#29Re: Philips announces digital pathology scanner with native DICOM JPEG XL output
#30Can someone comment on what is newsworthy about this?