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. |
29th October 2008, 10:08 | #2201 | Link |
Registered User
Join Date: Jan 2002
Posts: 581
|
I havent notice that yet. But I have another 'issue' so to speak. I dont know if its a issue and its properly not related to tsMuxer. But after inserted chapters and playing the movie, I sometimes see the last 1-5 frames from the previous scene, if I then shift forward the chapters by 100-200 ms, then they are acurrate. Dont know if it has something to do with -b-pyramid option in x264 encoder or what it is. But its a small bug, I can live with it.
|
29th October 2008, 12:27 | #2202 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
Quote:
I'd look somewhere else for the cause... Last edited by jdobbs; 29th October 2008 at 12:33. |
|
29th October 2008, 12:37 | #2203 | Link | |
Registered User
Join Date: Apr 2008
Posts: 12
|
Quote:
|
|
29th October 2008, 12:58 | #2204 | Link | |
Registered User
Join Date: Mar 2008
Location: Australia
Posts: 246
|
Quote:
I already burnt a disc with a corrected clpi and I plan to take it into work (I help manage an Audio Visual Retail Store) and test it on every Blu-ray Player we have. Previous discs burnt after multiplexing with tsMuxeR did stick a little when seeking and on some players completely froze (mainly the Sony BD players did this). I will report back later. :-) |
|
29th October 2008, 13:40 | #2205 | Link |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
@jeffnoone
Please put your eac3to log files to know the problem. Thanks to odin24 I know: "The TrueHD track on DM & TR Live at Radio City is 96/24" then your: "used DOS commandline, and -i 24 -c 6 -s 48000" is wrong. If your TrueHD track is the 4 (with the logs I can know this) you need: eac3to <your_source> 4: stdout.pcm | Pcm2Tsmu - tsmu.pcm -s 96000 -i 24 -c 6 -s 48000 are defaults and only need the parameter when are distinct. If you want half size and 48 KHz you can use: eac3to <your_source> 4: stdout.pcm -resampleTo48000 | Pcm2Tsmu - tsmu.pcm
__________________
BeHappy, AviSynth audio transcoder. |
29th October 2008, 16:11 | #2206 | Link | |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
Quote:
It seems as if using the original program's chapter points (e.g. 01:23:35.638) with the Re-encoded movie just misses the mark i.e. the original doesn't line-up properly with a keyframe in the new encoding. I wonder if one needs to manually look at the re-encoded .264 recording, prior to muxing w/tsMuxeR, to find the best new I-frame to specify for the chapter point? |
|
29th October 2008, 19:27 | #2208 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
Quote:
Interesting from the referenced post that is seems to always be off by the same amount, though... One way you could make them exact, I guess, would be to encode all the chapters individually and then combine them afterward. I'm not aware of another way to force a keyframe in x264 -- does anybody else know of one? Last edited by jdobbs; 29th October 2008 at 19:37. |
|
29th October 2008, 20:37 | #2209 | Link | |
Registered User
Join Date: Mar 2008
Posts: 2,021
|
Quote:
http://www.ftyps.com/unrelated/asf2vc1/ |
|
29th October 2008, 21:03 | #2210 | Link |
Registered User
Join Date: May 2004
Posts: 185
|
Great!
Still time for a Feature Request asking for a TSRebuilder to rebuild captured DVB-S2 TS supporting kind of the following procedure? a) trim both ends (ok with tsMuxeR) b) cut out unwanted interior parts (possible but complicated with tsMuxeR, involving append with risk of audio sync problems) c) define chapters in the resulting stream (ok with tsMuxeR; finding of suitable chapter locations probably could be done using some other sw like NeroVision) d) supply a simple, table-of-contents-like main and chapters menu (currently not possible with tsMuxeR) c) create an AVCHD structure (like supplied by tsMuxeR, but including chapter menus) More details here Does anybody know of an affordable sw out there which does this WITHOUT excessive re-encoding? |
29th October 2008, 21:06 | #2211 | Link |
Registered User
Join Date: Apr 2003
Location: Totolalandia
Posts: 96
|
roman76r:
Would it be possible to add to TsMuxer "3:2 pulldown" option? At this moment the only tool available that have this option (h264info) doesn't work with all type of h264 files... Thanks... |
29th October 2008, 21:22 | #2212 | Link |
Registered User
Join Date: Jan 2002
Posts: 581
|
I was thinking the same, X264 should have a parameter, so you could include at chapter list and it then could insert an keyframe on those exact location, then I think chapters will be correct. I think CCE does that for Mpeg2, so cant see why it couldnt be built into x264. But I might be wrong.
|
29th October 2008, 21:28 | #2214 | Link | |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
Quote:
1. Apparently most x264 cl's allow use of B-frames as "reference points" and so I observed that many scene changes in my 264 were at B-frames, not I-frames. 2. To find this I had to use Avidemux, as serving VirtualDub 1.8.6 with DGAVCindex .dga file displays each/every frame as a K(keyframe)!!?? 3. Although I'd changed my .meta file for tsMuxeR to reflect the exact scene change point, clearly it was instead finding I-frames on playback. Sorta ugly. 4. When I saw with Avidemux the correct x:xx:xx.xxx codes for the I-frames, and edited the .meta file accordingly, all the chapters now seek to exactly the place I'd selected (which was in every case an I-frame). I would like to know how to not use B-frames as "reference" if I'm interpreting this correctly. Would rather always assert an I-frame if possible at scene changes. All of my scene changes were stark/different/obvious indeed. BTW I used --keyint 24 and --min-keyint 2 and it seems each/every GOP was 24 long, not sure this is right (should have been some GOPs <24???). Thanks jdobbs for fixclpi.exe--tried that also and it seemed to make a difference. Last edited by laserfan; 30th October 2008 at 02:14. |
|
29th October 2008, 21:56 | #2215 | Link | |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
Quote:
They can be shorter GOPs, but there may not be- depends on the encoder. Last edited by kolak; 29th October 2008 at 21:59. |
|
29th October 2008, 22:24 | #2216 | Link | |
Registered User
Join Date: Oct 2006
Posts: 303
|
Quote:
|
|
29th October 2008, 23:03 | #2217 | Link | |
Registered User
Join Date: Mar 2008
Location: Australia
Posts: 246
|
Quote:
|
|
30th October 2008, 00:37 | #2219 | Link |
Registered User
Join Date: Mar 2008
Location: The Great North (the better half of North America)
Posts: 301
|
@jdobbs and GZZ,
Thanks for the clpifix app and GUI, they both work fantastic. My only trial with the app was on a direct port with no recoding, rip --> BD-RE (h264 & DTSHD-MA). Hopefully I'll have the same results from the same source recoded for DVD9 and DTS core, I'll know soon. Playback was on the PS3. Thanks again. EDIT: The recoded DVD9 works just as well with the fixed clpi file on the PS3. Last edited by odin24; 30th October 2008 at 01:32. Reason: More info. and more results |
31st October 2008, 02:42 | #2220 | Link | |
Hey Now!
Join Date: Feb 2006
Posts: 812
|
Quote:
|
|
Tags |
tsmuxer |
Thread Tools | Search this Thread |
Display Modes | |
|
|