search

XeresRazor / subler

Automatically exported from code.google.com/p/subler
Other
3 stars 0 forks source link

Editing metadata in iTunes for a movie muxed by Subler takes very long #727

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Rip a Blu-Ray with DVDFab to MP4 including 2 languages in AC3-5.1 and 3 
subtitles.
2. Create a new file in Subler and open the ripped file. Everything on 
passthru, apart from AC3 tracks that get the action "AAC + AC3" and subtitles 
that get the action "Vobsub to Tx3g".
3. Drag the result to iTunes.
4. Open the metadata in iTunes and change something. Now saving that in iTunes 
takes a very long time. 1-2 minutes.
5. NOTE: If you open the file you just created with Subler a second time in 
Subler, select all tracks and press cmd-S to save the file (not queuing it), 
and drag THAT result to iTunes, this does NOT happen. So apparently Subler 
knows the correct format for iTunes, but doesn't manage to put that right 
during the first mux.

What is the expected output? What do you see instead?
I expect that after queuing a file to Subler, the result can immediately be 
used in iTunes and iTunes does not need 1-2 minute processing to save the first 
edit to the Metadata.

What version of the product are you using? On what operating system?
0.25 on iMac with OS X Mavericks.

Please provide any additional information below.
Note that opening/saving the file a 2nd time in Subler also fixes the issue 
that the subtitles are not available in the first file that Subler created. The 
open/save fixes this and now the subtitles are available in iTunes.

Original issue reported on code.google.com by ar...@hiemstras.net on 30 Jan 2014 at 4:26

GoogleCodeExporter commented 9 years ago 
Like I said in the other issue, iTunes tries to keep the moov atom at the start 
of the file, and that means rewriting the whole file even if for a single byte 
change. iTunes might insert a "free" atom to speed up the following edits (if 
they need less space than the free atom). But I won't take any action on this 
issue.

Original comment by damiog on 20 Feb 2014 at 3:41

GoogleCodeExporter commented 9 years ago 
Hi. I don't understand completely. If Subler is done creating the file, this 
issue happens in iTunes.

BUT: If I open the file that Subler created a second time in Subler and switch 
on the last track and then SAVE it (only takes a few seconds), then this issue 
does NOT happen in iTunes.

It looks to me that Subler is capable of preventing this issue?

Original comment by ar...@hiemstras.net on 20 Feb 2014 at 4:29

GoogleCodeExporter commented 9 years ago 
The thing is:
Optimize move the moov atom at the start of the file.
Saving move it at the end of the file.

So if you save in Subler without optimizing iTunes does not need to rewrite the 
entire file because the moov atom is at the end of the file.

Original comment by damiog on 20 Feb 2014 at 4:33

GoogleCodeExporter commented 9 years ago 
Forgive me if I ask stupid questions. =;-)

Is the entire idea of optimisation that the file becomes quasi streamable?

Is optimisation necessary? Could it be turned off and would it still work in 
iTunes?

Could Subler have an option let the user choose if he wants to have 
optimisation with atom at the beginning or optimisation with atom at the end?

It would be great if something like this would be built into Subler, so that it 
produces files that are immediately iTunes compatible.

Original comment by ar...@hiemstras.net on 20 Feb 2014 at 10:10

GoogleCodeExporter commented 9 years ago 
Forgive me if I ask stupid questions. =;-)

Is the entire idea of optimisation that the file becomes quasi streamable?

Is optimisation necessary? Could it be turned off and would it still work in 
iTunes?

Could Subler have an option let the user choose if he wants to have 
optimisation with the moov atom at the beginning or optimisation with the moov 
atom at the end?

It would be great if something like this would be built into Subler, so that it 
produces files that are immediately iTunes compatible.

Original comment by ar...@hiemstras.net on 10 Mar 2014 at 10:15