This repository has been archived by the owner. It is now read-only.

DVB-T2/HEVC playback issue #1957

Closed
ChristophRadtke opened this Issue Apr 23, 2017 · 4 comments

Comments

2 participants
@ChristophRadtke

ChristophRadtke commented Apr 23, 2017

Hi,

I am facing one last (I hope) issue with my HEVC recordings. The majority of the recordings now work great with the latest versions but a few recordings are ending up corrupt (unplayable or jittery) once they were processed by mkvmerge.

I've uploaded another sample and the command line parameters used.

Thanks a lot!

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 23, 2017

Owner

Thanks, I'll look into it.

Owner

mbunkus commented Apr 23, 2017

Thanks, I'll look into it.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 24, 2017

Owner

New pre-builds for Windows are currently being compiled and will be available shortly. Build numbers 01478 and higher contain the fix.

Owner

mbunkus commented Apr 24, 2017

New pre-builds for Windows are currently being compiled and will be available shortly. Build numbers 01478 and higher contain the fix.

@ChristophRadtke

This comment has been minimized.

Show comment
Hide comment
@ChristophRadtke

ChristophRadtke Apr 24, 2017

Thanks as always for the quick fix! For some files it works now. For the remaining files we still have our old friend:

Error: memory.cpp/safemalloc() called from file src/common/memory.h, line 209: malloc() returned nullptr for a size of 4294967289 bytes.

I'll upload another sample file tonight. You want me to create another issue ?

ChristophRadtke commented Apr 24, 2017

Thanks as always for the quick fix! For some files it works now. For the remaining files we still have our old friend:

Error: memory.cpp/safemalloc() called from file src/common/memory.h, line 209: malloc() returned nullptr for a size of 4294967289 bytes.

I'll upload another sample file tonight. You want me to create another issue ?

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 25, 2017

Owner

Yes, please. It's quite possible that it's the same issue as #1945, but as I haven't received any sample files for that issue yet let's treat yours as a separate one.

Owner

mbunkus commented Apr 25, 2017

Yes, please. It's quite possible that it's the same issue as #1945, but as I haven't received any sample files for that issue yet let's treat yours as a separate one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.