TS-Doctor 2.0 www.cypheros.de

Neueste Beiträge

Seiten: [1] 2 3 ... 10
TS-Doctor 2.0 / Re: Nex user - some problems and questions
« Letzter Beitrag von Cypheros am Heute um 00:40:29 »
Hmm, found a strange value:
Speed: 1,7 MBytes/sec
That's the slowest processing speed I ever saw. What recording medium do you use?

The bitrate is very very low for over 2 1/2 hours of a full HD recording.

I guess it's DVB-T, isn't it?

What channel?
TS-Doctor 1.2 / Re: mkvtoolnix - neue Version
« Letzter Beitrag von ErichV am Januar 15, 2018, 22:33:53 »
Version 20.0.0 (32-bit)
Version 20.0.0 (64-bit)

Zitat von: Changelog
Important notes
  • Feature removal: several deprecated features have been removed:
    • mkvmerge: the deprecated options --identify-verbose (and its counterpart -I), --identify-for-gui, --identify-for-mmg and --identification-format verbose-text
    • all command line tools: support for the deprecated, old, proprietary format used for option files
    • all command line tools: support for passing command line options via the deprecated environment variables MKVTOOLNIX_OPTIONS, MKVEXTRACT_OPTIONS, MKVINFO_OPTIONS, MKVMERGE_OPTIONS and MKVPROPEDIT_OPTIONS
  • mkvinfo: most of its code was re-written in order to lay the groundwork for including its functionality in MKVToolNix GUI but with more features than the existing mkvinfo GUI. The result is that a lot of its output has been changed slightly while keeping the basic layout. Changes include but aren't limited to:
    • Several element names are a bit clearer (e.g. Maximum cache instead of MaxCache).
    • All timestamps and durations are now output as nanoseconds in formatted form (e.g. 01:23:45.67890123). All additional formats (e.g. floating point numbers output in seconds or milliseconds) were removed.
    • Element names for chapters and tags are now translated if a translation is available.
    • Elements located in wrong positions within the Matroska document are handled better.
    While mkvinfo's output is mostly kept very stable, it is not designed to be parsed by other utilities. Even though I've tried hard to cram all changes and cleanups into this version, additional changes may be made in the next couple of releases depending on user feedback and bug reports.
New features and enhancements
  • mkvmerge: AVC/h.264 packetizer (framed): access unit delimiter NALUs will now be removed. Implements #2173.
Bug fixes
  • mkvmerge: AVC/h.264 parser: when fixing the bitstream timing information mkvmerge will now use exact representations of the desired field duration if possible. For example, when indicating 50 fields/second num_units_in_tick is set to 1 and time_scale to 50 instead of 5368709 and 268435456. Part of the fix for #1673.
  • mkvmerge: AVC/h.264 parser: mkvmerge no longer assumes that encountering sequence parameter set or picture parameter set NALUs signal the start of a new frame. Fixes #2179.
  • mkvmerge: AVC/h.264 packetizer (framed): when mkvmerge is told to fix the bitstream timing information, it will now update all SPS NALUs, not just the ones in the AVCC. Part of the fix for #1673.
  • mkvmerge: MPEG TS reader: TS packet payloads will only be treated as PES packets if the payload actually starts with a PES start code. The prior behavior led to wrong timestamps and potentially broken frame data. Fixes #2193.
  • mkvmerge: MPEG TS reader: mkvmerge will now drop incomplete PES packets as soon as an error is detected in the transport stream instead of passing the incomplete frame to the packetizer. An error is assumed either if the transport_error_indicator flag is set or if the value of the continuity_counter header field doesn't match the expected value. Fixes #2181.
  • mkvmerge: Opus: when re-muxing Opus from Matroska mkvmerge will now write "block duration" elements for all block groups where a "discard padding" is set, too. Fixes #2188.
  • mkvmerge: SRT reader: mkvmerge can now handle SRT files with timestamps without decimal places (e.g. 00:01:15 instead of 00:01:15.000).
  • mkvmerge: read buffer I/O class: the class could get out of sync regarding the file position of the underlying file I/O class causing wrong data to be returned on subsequent read operations. One result was that trying to identifying MPLS files that refer to very short M2TS files caused mkvmerge to segfault.
  • mkvmerge: multiplexer core: if there's a gap in audio timestamps, a new block group/lace will be started for the first frame after each gap. Before the fix the frame after the gap was often stored in the previous block group causing the gap to be in the wrong place: at the end of that block group. Fixes #1700.
  • mkvextract: AVC/h.264: if two consecutive IDR frames with the same idr_pic_id parameter and no access unit delimiters are found between them, mkvextract will insert an access unit delimiter in order to signal the start of a new access unit. Fixes #1704.
  • MKVToolNix GUI: update check dialog: Markdown links will now be converted to clickable links. Fixes #2176.
  • build system: fixed a race condition when creating new directories if rake is run with -jN in newer versions of Ruby/rake. Fixes #2194.
Build system changes
  • cmark, the CommonMark parsing and rendering library in C, is now required when building the GUIs.
TS-Doctor 2.0 / Re: Nex user - some problems and questions
« Letzter Beitrag von Nicolas58 am Januar 15, 2018, 21:49:27 »

The attached log file is one of which that have the timer issues on both my TV and my Xeobox.
On my Xeobox the false end time is at 10'57" and on my TV the "breaking" time is at 9'21".
I say breaking time on the Samsung TV because the displayed total time seems to be OK, but the navigation is not possible after this time.

Thanks for looking at my issue.
TS-Doctor 2.0 / Re: 1 bug and 2 suggestion
« Letzter Beitrag von barbatrukko am Januar 15, 2018, 20:50:45 »
Hi, thanks for your answ.

So, bug is really a little bug.

1) ok. i did, but i leave for error also "remember last used folder" so, in some dialog work this option and in som eother work "source folder". Now removed "last user folder" and works!

2) Thank! now is very useful.....
TS-Doctor 2.0 / Re: Cutting area problem
« Letzter Beitrag von Ich lese hier nur am Januar 15, 2018, 17:45:02 »
OK, wenn ich das richtig verstehe, gibt es keine Probleme, wenn Du nur eine Datei erstellst. Teilst Du die Aufnahme auf mehrere Dateien auf, gibt es Probleme im Log?

In der letzten Aufnahme hatte ich  nur Werbung rausgeschnitten  und als 1 Datei gespeichert . Alles ok.
Dann mal Testweise alle Schnitte als einzelne  Dateien abgespeichert,  Fehlermeldung im Log vorhanden.

Ich weiß nicht wie lange es schon in den Logs drinsteht da ich fast immer 0 Fehler und 0 Warnungen hatte , habe ich eigentlich nie die logs angeschaut.
Hier noch mal die 2 logs  vielleicht hilft es ja weiter.


TS-Doctor 2.0 / Re: Import von MP4
« Letzter Beitrag von Caribe am Januar 15, 2018, 16:48:42 »
OK, ich habe inzwischen mehrere Tests gemacht. Bei einigen Aufnahmen (ca. 1,5 GB) hatte ich zuvor auch die genannten Probleme. Jetzt hab ich mit einer anderen Aufnahmeeinstellung alle erfolgreich in den TSD2 importieren können.
Werde damit auch noch versuchen, eine größere Videodatei zu erstellen und importieren.
Bin sehr zufrieden mit dem neuen Doctor.
TS-Doctor 2.0 / Re: cutting late
« Letzter Beitrag von rockipoki am Januar 15, 2018, 16:13:52 »
Hard to decide. Did you try the same file with an older version?

 now is good, something was wrong with my installation or something like that

I uninstalled it from a computer ts doctor and then installed one of the old versions and updated with the latest version

TS-Doctor 2.0 / Re: Nex user - some problems and questions
« Letzter Beitrag von Cypheros am Januar 15, 2018, 00:34:05 »
Hi, could you post the log of such a problem file?

TS-Doctor creates a log for any new file. Same filename but with file extension .log

Makes it easier to see the technical details.
TS-Doctor 2.0 / Re: Import von MP4
« Letzter Beitrag von Cypheros am Januar 15, 2018, 00:17:41 »
Nein, es gibt da keine 2GB Grenze. Habe testweise mal eine 3,9GB MP4-Datei importiert und kein Problem festgestellt.
TS-Doctor 2.0 / Re: Cutting area problem
« Letzter Beitrag von Cypheros am Januar 15, 2018, 00:04:36 »
OK, wenn ich das richtig verstehe, gibt es keine Probleme, wenn Du nur eine Datei erstellst. Teilst Du die Aufnahme auf mehrere Dateien auf, gibt es Probleme im Log?
Seiten: [1] 2 3 ... 10