it automatically adds the track when you click ok on the open button for the SRT...so it *has* changed, in the sense that subler just changed it and you're saving it againjzietman wrote:I've tried removing a subtitle track from and re-adding it it a handbrake-encoded x264-in-m4v file, but I always get an error saying that another app has modified the file since it was opened (if this is true, it certainly hasn't been my doing, I've no other apps doing anything with the file), and then when I try to save, it says that it can't. I've tried Save As as well, but to no avail.
Ideas? What do you need to be able to diagnose the problem? Is there any kind of activity log produced by Subler?
The length of the subtitle track is the same as the one of the video track.LinBrake wrote: 1) Does the software correctly handle the "length" of subtitles or how does that function?
No one, it uses the universal character detector from the mozilla project and the subtitles serialization routine from perian.LinBrake wrote: 2) What preparation (if any) is necessary to import the .srt file before it will correctly work with Subler?
I will upload the source code tomorrow.LinBrake wrote: 3) Can you post the source code to the application and libraries behind it? I would like to help if I can as this is one area where I feel I may actually be able to contribute in a meaningful way.
Yes, but it will change in the next version.jzietman wrote:Same goes for when I delete a track?
I had 3-4 SRTs I was adding to a seasons worth of TV episodes that actually went over the length of the video/audio, because the SRT itself had an additional scene in it that wasn't in my encode. This is easily fixable of course, but I thought I should point out that it does go past the length of the other tracks if you tell it to.Ritsuka wrote: The length of the subtitle track is the same as the one of the video track.
Wow, so I don't have to worry about making sure all my SRTs are UTF-8 now? (Quicktime/iTunes crashes on non-UTF8 encoding)No one, it uses the universal character detector from the mozilla project and the subtitles serialization routine from perian.
It should be quite robust.
Code: Select all
mp4track --list Igor.m4v
track[0] id=1
type = video
enabled = true
inMovie = false
inPreview = false
layer = 0
alternateGroup = 0
volume = 0.0000
width = 823.00000000
height = 448.00000000
language = Undetermined
handlerName =
userDataName = <absent>
track[1] id=2
type = audio
enabled = true
inMovie = true
inPreview = false
layer = 0
alternateGroup = 1
volume = 1.0000
width = 0.00000000
height = 0.00000000
language = English
handlerName =
userDataName = film
track[2] id=3
type = audio
enabled = false
inMovie = true
inPreview = false
layer = 0
alternateGroup = 1
volume = 1.0000
width = 0.00000000
height = 0.00000000
language = English
handlerName =
userDataName = comments
track[3] id=5
type = text
enabled = false
inMovie = true
inPreview = true
layer = 0
alternateGroup = 0
volume = 0.0000
width = 0.00000000
height = 0.00000000
language = UNDEFINED(0)
handlerName =
userDataName = <absent>
track[4] id=6
type = (sbtl)
enabled = true
inMovie = true
inPreview = false
layer = 0
alternateGroup = 2
volume = 0.0000
width = 823.00000000
height = 60.00000000
language = English
handlerName =
userDataName = <absent>Those are some fine looking images.cvk_b wrote:Here's some images of subtitles on my FATNANO made with Subler. Thanks!
…and the same file on the Apple TV Take 2.3
Closed captions are a totally different beast. If i understand correctly QuickTime closed captions tracks are just a wrapper for Line 21 format, so it shouldn't be too hard to implement it if you got a file with the right data. But I live in a pal world and I never seen a dvd or tv channel with closed caption.rhester wrote:Out of curiousity, does Subler distinguish between subtitles and closed captions (by Apple's QuickTime definitions)?
Rodney
we can't see them, periodcvk_b wrote:I know. Not good quality.
A lot of .ssa files are a mess (karaoke, moving text, multiple text lines that have nothing to do with dialogues), but maybe for simple ssa it maybe useful.LinBrake wrote: 1) Internal .ssa to .srt conversions.
Allow import of .ssa, software converts to .srt internally before handing off to other functions to add to the video.
No, it's not a feature I will add.LinBrake wrote: 2) Extracting subtitle tracks from mkv, ogm, or similar formats.
I'll look into this, it doesn't seem too difficult to add.LinBrake wrote: 3) Closed Captions for media.
thanks for releasing the codeRitsuka wrote:Btw, a new version if available on http://code.google.com/p/subler/ . The source code is still quite a mess but who cares
New feature in this release:
Save and Revert to Saved menu items are now working.
Added a way to change the language of tracks and the name (but the name will be saved only if the track already had a custom name).
Is there a character limit per line for Quicktime? (Sorry, not directly related to Subler, but it's easier to just ask here.)Ritsuka wrote:Yup Quicktime is limited to two line. You can edit the srt and split the long line.
