Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
15th March 2020, 14:20 | #641 | Link |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Is there a better way to fix audio that leads the video?
The source IFO has 10 PGCs (program chains).
Beginning with the 9th program, audio leads the video -- programs 1 to 8 were okay. By tedious trial-&-error, I worked out that the audio needed to be delayed by 4400ms. I may encounter something like this in the future. I wonder whether there's a better way than my work flow. Work flow: Step 1: I used MKVToolNix to repackage the VOB as an MKV. Step 2: I viewed the MKV via the MPV player and saw the audio leading towards the end of the MKV. Step 3: I reran MKVToolNix and added an audio delay. Step 4: I viewed the MKV again. I repeated Steps 3 & 4, adjusting the audio delay until it was right. Each time, I had to fast forward to the 9th program to see the result. Between each step, I reran HandBrake to extract the 9th program (based on start/stop times) to verify that, indeed, I was getting what I wanted. (I realize now that rerunning HandBrake in each loop was probably unnecessary and that I could have extracted the 9th program just once, at the end.) Is there a better way to determine the needed audio delay than by trial-&-error? Note that MKVToolNix's "Fix bitstream timing info" check box was unavailable (grayed out). varekai, I haven't tried all your suggested tools (though I already have and use most of them). Warm Regards, Mark. |
15th March 2020, 14:58 | #642 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Quote:
Code:
mtime=$(/usr/bin/stat --format=%Y src.avi) mkvmerge -o out.mkv src.avi src.mp3 touch -d @$mtime out.mkv Alternatively set the segment header's "date" field with mkvpropedit after muxing.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
15th March 2020, 15:01 | #643 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Quote:
There's a separate box for error messages; the don't show up in the regular output box. What does that error box show?
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
15th March 2020, 15:03 | #644 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
When I have something to say I usually respond. Therefore: when I don't respond I don't have anything productive to say or don't want to spend time on it.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
15th March 2020, 15:05 | #645 | Link |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,227
|
If your XviD video streams contain b-frames encoded with 'packed bit-stream' I recommend you remove it first - unless MKVToolNix is able to do this now.
Cheers
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
15th March 2020, 15:15 | #646 | Link | |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,580
|
Quote:
Thanks for your precious hint.
__________________
@turment on Telegram |
|
15th March 2020, 16:52 | #647 | Link | ||
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Thanks for replying.
Quote:
Quote:
|
||
16th March 2020, 13:58 | #648 | Link | ||
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Quote:
Quote:
Click on the "job output" tool on the left. You'll see a tab with three big text boxes labeled "normal output" (the top one), "warnings" (bottom left) and "errors" (bottom right). Whenever an error occurs, the bottom right box should contain something.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
||
16th March 2020, 20:10 | #649 | Link | ||
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Your application is wonderful, but its odd UI and the lack of a log limits usability.
Quote:
I'm fairly new to MKVToolNix, but I'm pretty happy with it. Inclusion of integrated subtitle & chapter tools (involving some processing of IFO files for DVD, and MPLS files for BD (I think)) would be a very welcome addition. Quote:
After I make a MKV using your tool, I use timings from IfoEdit analysis of the IFO to determine the PGCs and then chop the MKV into part-wise MKVs using HandBrake. I'm not really happy with that because HandBrake can't remux and I'm not keen on transcoding. If MKVToolNix allowed me to chop up a source based on the running times shown by IfoEdit, I'd be very happy to do the whole job with MKVToolNix. Regarding the 4400ms audio error, in that case, I remuxed from VOB to MKV using MKVToolNix, then cut the video apart to make 10 MKVs with HandBrake (with acursed transcoding), and finally, for the 9th & 10th MKVs, moved the audio by 4400ms via MKVToolNix. I'd prefer to cut HandBrake out of the process. Last edited by markfilipak; 16th March 2020 at 20:26. Reason: Removed prior PS. |
||
17th March 2020, 03:35 | #650 | Link |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
@Mosu
I owe you an apology. Opening 'Job queue' (not 'Job output', as you said) and right-clicking the 'Description' of the failed remux and selecting 'View output' opens a panel (tab) that has an 'Errors' section. That section says, "Could not write to the destination file: 112 (There is not enough space on the disk.)". So there is a log of sorts ...certainly sufficient to figure out what went wrong (at least, in this case). I complement you for some good documention. May I ask a question? A chap on the ffmpeg-user list said he uses the MKVToolNix "generate timestamps" option. Is that an undocumented feature? Or was the chap in error? Warm Regards, Mark. |
17th March 2020, 19:28 | #651 | Link | ||
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Quote:
Quote:
A couple of possibilities:
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
||
18th March 2020, 05:05 | #652 | Link | |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Quote:
"Current Job Output" ...after a job runs "Current Job Queue" ...before a job runs "Job History" ...previous job outputs I like your style, Mosu. |
|
18th March 2020, 05:20 | #653 | Link | |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Quote:
On 03/15/2020 09:41 AM, Mark Filipak wrote: Last edited by markfilipak; 18th March 2020 at 05:45. Reason: Clarified; "PTS" was "PTC" oops |
|
18th March 2020, 11:39 | #654 | Link |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
Remux file oops!
I discovered (the hard way) that MKVToolNix doesn't handle things well if the input and output are the same file name.
It would be nice if overwriting were possible. |
18th March 2020, 13:02 | #655 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Quote:
The are several reasons, e.g. there's a distinct possibility that data to be written is generated faster than data is read from the source file; in that case data that hasn't been read yet would be overwritten by the output data. Not a good idea.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
18th March 2020, 20:37 | #656 | Link |
李姗倩 Lǐ Shān Qiàn
Join Date: Nov 2002
Posts: 1,340
|
GUI: the default destination file name may cause errors if --title contains a slash
Hi, I'd like to report a possible issue of the GUI.
The default destination file name, auto-generated by GUI, may cause errors or unexpected behaviors, at least on my Windows machine, in some situations related to a slash (possibly also a colon?) in the --title. Example 1 You have "La Rose - Partie 2.264" and want to make "La Rose - Partie 2.mkv". You want to give it a title "La Rose / Partie 2". A command line like this will work fine: Code:
mkvmerge -o "La Rose - Partie 2.mkv" "La Rose - Partie 2.264" "La Rose - Partie 2.ogg" --title "La Rose / Partie 2" Code:
Errors emitted by job 'Multiplexing to file " Partie 2.mkv" in directory "X:\path\La Rose "' started on 2020-03-18 18:26:13 --- The file 'X:\path\La Rose \ Partie 2.mkv' could not be opened for writing: open file error. 1) GUI design: Before and when you click Start, the "Destination file" editbox is saying "X:\path\La Rose - Partie 2.mkv". GUI suddenly changes its mind after you click Start, even though you do want to create "X:\path\La Rose - Partie 2.mkv". If the default destination changes, the editbox showing it should be updated accordingly before the user clicks "Start multiplexing" (e.g. when the "File title" editbox is updated and loses the focus). 2) Technically it's possible to create a file "X:\path\La Rose \ Partie 2.mkv" on Windows (though this is probably not what the user wants to do), but the tools fail to do that: it seems that they can't handle a folder name with a trailing space in this case. Example 2 Suppose the --title should be "Take a 50/50 Chance!" GUI works fine with this title, but if the destination file name is auto-generated, then a sub-folder "Take a 50" is created, in which a file "50 Chance!.mkv" is written. Obviously this is not what the user wants. Like Example 1, the user doesn't know this will happen until after they click the "Start multiplexing" button. |
18th March 2020, 23:22 | #657 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Nice catch, thanks. I'll have to replace all characters Windows doesn't allow in file names before copying the title to the file name.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
19th March 2020, 06:56 | #658 | Link |
Registered User
Join Date: Jul 2016
Location: Mansfield, Ohio (formerly San Jose, California)
Posts: 280
|
As an alternative, you could %-hex the offending characters. For example, "Take a 50/50 Chance!" would become "Take a 50%2F50 Chance!". Or you could simply replace any offending characters with hyphen of course.
Last edited by markfilipak; 19th March 2020 at 06:57. Reason: I know, but I'm not telling |
19th March 2020, 12:41 | #659 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,281
|
Replacing consecutive invalid characters with a single hyphen is what I was thinking about. I don't like % encoding for normal folks as they don't really understand what's happening and what that's supposed to mean.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
19th March 2020, 13:23 | #660 | Link | |
Acid fr0g
Join Date: May 2002
Location: Italy
Posts: 2,580
|
Quote:
Months ago I asked you to set language from filename convention and at the beginning you were reluctant. After some silent months, you coded it and it's really useful. I think it would be useful for a lot of people to have the stream file date and time saved in the mkv container, so being resilient to cuts and other manipulations.
__________________
@turment on Telegram |
|
Tags |
matroska |
|
|