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. |
27th August 2008, 12:19 | #5941 | Link | |
Registered User
Join Date: Jul 2007
Posts: 48
|
Quote:
|
|
27th August 2008, 15:04 | #5942 | Link | ||
Registered User
Join Date: Jun 2002
Posts: 20
|
Quote:
Quote:
Anyway, the whole point of this was because I have written a menu based wrapper script for eac3to and it was originally my intention to make it so default bitrates were determined according to source if no explicit bitrate is given. However, I thought it better suited as an eac3to suggestion so others benefited. Not only is there some irony in that thought (considering the reaction my suggestion got) but I'm now going to do that anyway and will have it set up in much less time than it took me to write these posts. I guess no good deed goes unpunished! Anyway, it's obviously your right to program eac3to however you like so I won't discuss it further. Cheers, that should at least make it clear that a high bitrate is being used. Thanks for a great program. Last edited by jamieo; 27th August 2008 at 15:11. |
||
27th August 2008, 20:11 | #5943 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
You're trying to see a connection between source and target bitrate which IMHO isn't there. The source bitrate tells us how much loss there was in the lossy encoding done by the studio. The target bitrate defines how much loss we want to add on top of that ourselves. These 2 losses don't relate to each other, they simply add up (loss 1 + loss 2). Now what you're saying sounds to me like: If the "loss 1" is big then you want eac3to to make "loss 2" equally big. That doesn't make much sense to me.
|
28th August 2008, 06:00 | #5944 | Link | |
Registered User
Join Date: Aug 2007
Posts: 1,430
|
http://www.stfcc.org/misc/animusic.clip.vob
Quote:
|
|
28th August 2008, 07:32 | #5945 | Link | |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
Quote:
Edit: Something about that vob file is strange, though. eac3to cannot demux video/audio tracks for whatever reason. Will look into that. But the subtitle track seems to be really empty. E.g. EvoDemux doesn't even list it. Last edited by madshi; 28th August 2008 at 07:40. |
|
28th August 2008, 07:43 | #5946 | Link | |
Registered User
Join Date: Feb 2008
Posts: 14
|
Oh that's great news, I thought I'd read on the forum that if you let EAC3to merge the pieces on a seamless branching disk that you would/could end up with audio sync issues.
Must have misunderstood something I read. Thanks Quote:
|
|
28th August 2008, 07:57 | #5947 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
You got it exactly the wrong way. Actually letting eac3to merge the seamless branching parts *solves* any audio sync issues. If you handle the parts separately, you'll get into trouble because the audio data overlaps slightly, so audio sync will slowly drift out of sync over the course of the movie. eac3to will detect the audio overlaps and correct them for you if you let eac3to handle the merging.
|
29th August 2008, 12:57 | #5950 | Link |
Registered User
Join Date: Jul 2007
Posts: 259
|
Sorry for not posting my new results with The Game Plan sooner.
It must be some kind of mastering error. I tested every m2ts file in the playlist and found the problem(s). Sorry for taking your time with this problem. |
29th August 2008, 13:49 | #5952 | Link | |
Registered User
Join Date: Jul 2007
Posts: 259
|
Quote:
Must be some kind of mastering error. Or some kind of screwed up interactive feature (can't find such feature with the arcsoft player though....and I don't know why you would create m2ts files with audio out of place in this manner) |
|
29th August 2008, 15:04 | #5953 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
The problem is that some broken playlists may be there on the disc but may never be used by the disc's user interface. In such a situation you wouldn't see the problem when playing the disc with an "official" player which shows the full user interface and let's the user decide through the interface which playlist to play. Maybe something like that is what has happened here. Or maybe (as you say) it's some kind of interactivity stuff. Anyway, I'm glad to hear that eac3to is innocent. One bug less to fix for me...
|
29th August 2008, 15:50 | #5954 | Link |
Registered Developer
Join Date: Sep 2006
Posts: 9,140
|
eac3to v2.58 released
http://madshi.net/eac3to.zip Code:
* h264 parser rewritten: framerate, pulldown etc is detected reliably now * h264 pulldown is automatically removed from progressive movie sources now * h264 pulldown removal can be disabled by using "-keepPulldown" * h264 muxing now fully supports streams with mixed 23.976 and 29.970 content * h264 1920x1088 bitstream is now automatically patched/cropped to 1920x1080 * h264 filler data is now already removed during demuxing * h264 sources with funny framerates (e.g. Luxe.tv HD) are patched to 25fps now * mixed video/movie h264 streams are now always muxed with 29.970 timestamps * speedup/slowdown now changes framerate information in the h264 bitstream * options "-24p", "-60i" and "-30p" are no longer supported * fixed Blu-Ray seamless branching subtitle remuxing * added workaround for Blu-Ray playlists with a last small "invalid" m2ts part * bitdepth analyzation is now done for decoded FLAC, WAV, PCM, DTS MA, too * bitrate is now also reported for FLAC, WAV and PCM tracks * when encoding AC3, DTS or AAC, the encoding bitrate is reported * fixed: v2.57 incorrectly decoded 16bit TrueHD tracks to 24bit FLAC/WAV/RAW * (M2)TS discontinuities before the first unit start are ignored now * new option "-progressnumbers" replaces progress bar with percentage numbers Now pulldown removal capability in eac3to is complete: Pulldown can be removed from all 3 supported video codecs (MPEG2, VC-1 and h264). And the performance of the pulldown removal is significantly faster compared to the original tools. Furthermore pulldown removal is now mostly automatically activated by default, even if you only demux a video track. Here's when it's activated and when not: (1) h264: pulldown removal is always activated by default. (2) VC-1: pulldown removal is always activated by default. (3) MPEG2: pulldown removal is activated by default only for EVO and M2TS sources. The "-stripPulldown" option consequently makes sense only for MPEG2 sources. The option "-keepPulldown" can be used to disable the automatic pulldown removal for all 3 video codecs. |
29th August 2008, 18:36 | #5959 | Link |
Registered User
Join Date: Nov 2005
Posts: 85
|
Thanks for the continued awesome work Madshi!!
I noticed that program changes within an h264 stream has been addressed. What about VC-1? I still have problems processing the NIN BD. C:\downloads\TS and EVO Tools\eac3to>eac3to M:\HDDVD\NIN 1) 2:r:/nin.mkv 3:nin.flac The program type (4352) changes from $83 to $81. M2TS, 1 video track, 2 audio tracks, 1 subtitle track, 1:32:21 1: Chapters, 22 chapters 2: VC-1, 1080i60 /1.001 (16:9) 3: TrueHD/AC3, English, 5.1 channels, 48khz 4: AC3, English, 2.0 channels, 256kbps, 48khz 5: Subtitle (PGS), English The program type (4352) changes from $83 to $81. [v02] Extracting video track number 2... [a03] Extracting audio track number 3... [a03] Extracting TrueHD stream... [a03] Decoding with libav/ffmpeg... [a03] Encoding FLAC with libFlac... [v02] Muxing video to Matroska... [a03] This audio track contains more than 16 bits of information. [a03] Creating file "nin.24bit.flac"... [a03] This track is not clean. [libav] Lossless check failed - expected ae, calculated 6c [v02] The pes parser received incomplete data. [a03] The pes parser received incomplete data. [libav] End of stream indicated [a03] The program type (4352) changes from $83 to $81. [v02] The program type (4352) changes from $83 to $81. Aborted at file position 16586463232. |
Tags |
eac3to |
Thread Tools | Search this Thread |
Display Modes | |
|
|