On 6/29/19 3:39 AM, Paul B Mahol wrote:
On 6/29/19, Michael Niedermayer wrote:
On Fri, Jun 28, 2019 at 02:02:29PM +0530, Shivam wrote:
On 6/27/19 9:21 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
On 6/26/19 4:37 PM, Michael Niedermayer wrote:
On We
On 6/29/19 3:35 AM, Michael Niedermayer wrote:
On Fri, Jun 28, 2019 at 02:02:29PM +0530, Shivam wrote:
On 6/27/19 9:21 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
On 6/26/19 4:37 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 09:54:56AM +020
On 6/29/19, Michael Niedermayer wrote:
> On Fri, Jun 28, 2019 at 02:02:29PM +0530, Shivam wrote:
>>
>> On 6/27/19 9:21 PM, Michael Niedermayer wrote:
>> >On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
>> >>On 6/26/19 4:37 PM, Michael Niedermayer wrote:
>> >>>On Wed, Jun 26, 2019 at 09:54:
On Fri, Jun 28, 2019 at 02:02:29PM +0530, Shivam wrote:
>
> On 6/27/19 9:21 PM, Michael Niedermayer wrote:
> >On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
> >>On 6/26/19 4:37 PM, Michael Niedermayer wrote:
> >>>On Wed, Jun 26, 2019 at 09:54:56AM +0200, Paul B Mahol wrote:
> On 6/26/
On 6/27/19 9:21 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
On 6/26/19 4:37 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 09:54:56AM +0200, Paul B Mahol wrote:
On 6/26/19, Michael Niedermayer wrote:
On Tue, Jun 25, 2019 at 01:52:09PM +0530
On Wed, Jun 26, 2019 at 11:33:05PM +0530, Shivam wrote:
>
> On 6/26/19 4:37 PM, Michael Niedermayer wrote:
> >On Wed, Jun 26, 2019 at 09:54:56AM +0200, Paul B Mahol wrote:
> >>On 6/26/19, Michael Niedermayer wrote:
> >>>On Tue, Jun 25, 2019 at 01:52:09PM +0530, Shivam wrote:
> On 6/25/19 2:12
On 6/26/19 4:37 PM, Michael Niedermayer wrote:
On Wed, Jun 26, 2019 at 09:54:56AM +0200, Paul B Mahol wrote:
On 6/26/19, Michael Niedermayer wrote:
On Tue, Jun 25, 2019 at 01:52:09PM +0530, Shivam wrote:
On 6/25/19 2:12 AM, Michael Niedermayer wrote:
On Mon, Jun 24, 2019 at 09:18:13PM +0530
On Wed, Jun 26, 2019 at 09:54:56AM +0200, Paul B Mahol wrote:
> On 6/26/19, Michael Niedermayer wrote:
> > On Tue, Jun 25, 2019 at 01:52:09PM +0530, Shivam wrote:
> >>
> >> On 6/25/19 2:12 AM, Michael Niedermayer wrote:
> >> >On Mon, Jun 24, 2019 at 09:18:13PM +0530, Shivam wrote:
> >> >>Hi!
> >>
On 6/26/19, Michael Niedermayer wrote:
> On Tue, Jun 25, 2019 at 01:52:09PM +0530, Shivam wrote:
>>
>> On 6/25/19 2:12 AM, Michael Niedermayer wrote:
>> >On Mon, Jun 24, 2019 at 09:18:13PM +0530, Shivam wrote:
>> >>Hi!
>> >>
>> >> The code is to add DICOM Support. The patch is only for
>> >> u
On Tue, Jun 25, 2019 at 01:52:09PM +0530, Shivam wrote:
>
> On 6/25/19 2:12 AM, Michael Niedermayer wrote:
> >On Mon, Jun 24, 2019 at 09:18:13PM +0530, Shivam wrote:
> >>Hi!
> >>
> >> The code is to add DICOM Support. The patch is only for uncompressed
> >>dicom files using explicit value repr
On 6/25/19 2:12 AM, Michael Niedermayer wrote:
On Mon, Jun 24, 2019 at 09:18:13PM +0530, Shivam wrote:
Hi!
The code is to add DICOM Support. The patch is only for uncompressed
dicom files using explicit value representation. I would extend it, once i
clarify some doubts. As dicom imag
On Mon, Jun 24, 2019 at 09:18:13PM +0530, Shivam wrote:
> Hi!
>
> The code is to add DICOM Support. The patch is only for uncompressed
> dicom files using explicit value representation. I would extend it, once i
> clarify some doubts. As dicom image files contain lots of metadata about
> t
Hi!
The code is to add DICOM Support. The patch is only for
uncompressed dicom files using explicit value representation. I would
extend it, once i clarify some doubts. As dicom image files contain
lots of metadata about the patient. So, should i display that data while
demuxing or sh
13 matches
Mail list logo