Brian Beckrest

@suyashkumar Thanks for the reply. Trying the suggestion above causes a panic due to `Frames` only having a length of 1. Not sure why it's not parsing the second pixeldata...

@suyashkumar You are correct. I'm able to get the byte data from the encapsulated frame using the code above. The issue is the JPEG encoding. The encoding of the images...

@suyashkumar It's not necessarily required to be encapsulated into a single go program but having it external would add enough complexity to where it's probably not worth handling right now....

Regarding memory usage, we've recently had our server (32GB RAM) run out of memory while attempting to parse a 1GB zipfile containing dicoms. Using `pprof`, I've benchmarked parsing a 55MB...

Thanks for looking into this! I don't have much experience profiling performance so I appreciate the help. Our prod server that ran out of memory is using v0.4.5, which obviously...

Reading through the [DICOM spec](http://dicom.nema.org/medical/dicom/current/output/html/part05.html), it appears that allocating more than 32 bits is rare. If I'm understanding correctly, 64 bits are only used for Double Float Pixel Data. FWIW,...

@suyashkumar Yeah the proposal in https://github.com/suyashkumar/dicom/issues/161#issuecomment-846706345 would be helpful for my use-case since the volume could be stored as `uint16`. Yesterday, I attempted to implement it but got stuck and...

@bernardopericacho see https://github.com/suyashkumar/dicom/issues/85 for open issue regarding parsing encapsulated images