michael19rp / subtitleedit

Automatically exported from code.google.com/p/subtitleedit
0 stars 0 forks source link

export vobsub #186

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
(enter only *ONE* issue in each report)
What steps will reproduce the problem?
1.export titles to vobsub works fine
2.merge vobsub (step 1) into mkv with mkvtoolnix works fine
3.handbrake: convert mkv (step 2) to m4v with vobsub burned in crashes. The 
vobsub causes the problem. May be a compatibility issue or may be incorrect 
setting by me when exporting subs to vobsub (in subtitle edit).

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
3.3.9 on Windows 8 Pro 64-bit

Please provide any additional information below.

Original issue reported on code.google.com by yrob...@gmail.com on 28 Nov 2013 at 9:13

GoogleCodeExporter commented 8 years ago
What version of Handbrake are you using?
What does the Handbrake activity log  
(https://trac.handbrake.fr/wiki/ActivityLogWin) say?

Original comment by nikse.dk@gmail.com on 28 Nov 2013 at 10:35

GoogleCodeExporter commented 8 years ago
Handbrake 0.9.9.5530 64 bit
see attached logs

Original comment by yrob...@gmail.com on 30 Nov 2013 at 1:10

Attachments:

GoogleCodeExporter commented 8 years ago
I use Handbrake 0.9.9.3055 64 bit
See the attached handbrake log files. I must say the issues does not occurs
when I try to burn in the SSA subtitles. It just occurs when want the vobsub
subtitle track burned in (preferred because of uniformity/standardization)

-----Oorspronkelijk bericht-----
Van: subtitleedit@googlecode.com [mailto:subtitleedit@googlecode.com] 
Verzonden: donderdag 28 november 2013 11:36
Aan: yrobryn@gmail.com
Onderwerp: Re: Issue 186 in subtitleedit: export vobsub

Original comment by yrob...@gmail.com on 30 Nov 2013 at 1:37

GoogleCodeExporter commented 8 years ago
Should be fixed in next release: 
https://github.com/SubtitleEdit/subtitleedit/commit/790dd5a2e569ee34f33fdfb9a5db
50378c3f160b

Original comment by nikse.dk@gmail.com on 11 Mar 2014 at 8:18