View Full Version : smartLabs tsMuxeR: Transport Stream muxer
jamos
10th April 2009, 00:01
LARGE (over 4 gig.) w64 files get error while muxing to m2ts about 1/4 of the way through..locks up tsmuxer 1.9.4b.
small w64 files work fine.
SmartLabs tsMuxeR. Version 1.9.4 http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1280:720p Frame rate: 23.976
H.264 muxing fps not set. Get fps from stream.
LPCM bad frame detected. Resync stream.
LPCM bad frame detected. Resync stream.
LPCM bad frame detected. Resync stream.
LPCM bad frame detected. Resync stream.
turbojet
10th April 2009, 00:23
The reason for having 2 seperate output modes is that BluRay spec is not the same as AVCHD spec and some players will only play one or the other.
Previously, TSMuxer was outputting a bastardized-hybrid-mongrel version of BD/AVCHD hence it sort of working on most players. Now that it (hopefully) outputs both modes in accordance with spec, all players will be supported with the only challenge being figuring out which output mode your player likes.
The old bluray output (sort of?) works on all but 2 players that are sharps and well known. If sharp's now work with one of the modes I can see it as an improvement but I really doubt they will, as they don't even play retail BD5. AVCHD spec doesn't allow DTS, VC-1, MPEG2 but TSMuxer will output these when avchd is ticked.
roman76r: The panasonic VC-1 hack was figured out and was tested on other players to be working just fine. Why not just apply that hack when VC-1 is in the output and bluray disk is selected as output instead of having these 2 output options?
setarip_old: bluray disk used to be what you use and it never failed as long as it wasn't vc-1 played on a panasonic. Now as you can see it's a guessing game to figure out what works and what doesn't on specific players. I guess what's needed again unless tsmuxer reverts to a single always working output method we'll need another thorough test of what players work for each output method.
jamos
10th April 2009, 01:20
feature request:
ability to run tsmuxer in low priority mode for windows. it would be nice to run in background without hogging resources.
thanks
coolalibaba
10th April 2009, 03:32
feature request:
ability to run tsmuxer in low priority mode for windows. it would be nice to run in background without hogging resources.
thanks
I think you can change the priority in the task manager? hehe
jamos
10th April 2009, 04:07
I think you can change the priority in the task manager? hehe
thats what i do now..heh
rapscallion
10th April 2009, 04:49
@rapscallion
Hi!If your specific brand and model number of standalone BluRay player recognizes hi-def files on standard DVD media (DVD5 and DVD9), use BluRay format...
Hi Setarip !
Yes, my Pioneer 51 recognizes the discs I recorded in prev ver of tsmuxer, that only had blu-ray output option, so I'll continue to use that output/format.
But, my Samsung 1200 did not. So, just out of curiousity, I'll try a small test file with both outputs (1.9.4) and see if the Sammy can play one of them now.
turbojet
10th April 2009, 06:13
Hi Setarip !
Yes, my Pioneer 51 recognizes the discs I recorded in prev ver of tsmuxer, that only had blu-ray output option, so I'll continue to use that output/format.
But, my Samsung 1200 did not. So, just out of curiousity, I'll try a small test file with both outputs (1.9.4) and see if the Sammy can play one of them now.
With newer samsung firmwares/players you have to remove the AUXDATA folder for them to play. I'm not sure it's the same on Samsung 1200 but worth a try.
Good luck on your tests with latest tsmuxer using both outputs on both of those players. Please report back as we have to start fresh with a list of players that each output supports.
Atak_Snajpera
10th April 2009, 06:40
Please report back as we have to start fresh with a list of players that each output supports.
This would be a good idea.
mrr19121970
10th April 2009, 07:03
mrr19121970
I tested wave64 files created in Sound Forge. Can you send me your file?
I PMed you the file link
Did I select the invisible font in my last post? It's now the other way round, you have to use the AVCHD mode in 1.9.4. Bluray mode results in no titles.
Sorry, that was my bug in Clown_BD 0.42b
I'm not using any VB/C/C+/C# in my applications - that's why I asked for it. I'd like to keep multiAVCHD smaller (it is just 400-500kb now) and not dependent on anything but tsmuxer and other tools. No need for .net / other dlls... I can read output but I'd like to have final log for processing and error reporting because my apps call tsmuxer in ways that overcome its limits atp.
you can 'run':
%comspec% /c tsmuxer.exe >log.txt
but the progress % is (or at least was in the past) written to every line.
turbojet
10th April 2009, 07:05
This would be a good idea.
In the long run I hope tsmuxer goes back to what was working fine and saves testers all the grief.
kaid
10th April 2009, 07:24
Totally awesome that Roman updated the Linux-Version to the most current one, finally no more BD mux issues, thanks so much! The Mac-Version is a very very pleasant surprise, too - But why Intel-only? That's like making it only run on Core or Phenom on Windows, you wouldn't shut out Millions of P4 or Athlon-owners, would you? Millions of Mac-Users still have very capable Dual or even Quad G5 PPC-Machines!... I (and many others) would be so glad if you also made it PPC-compatible! I'd be more than happy to test it if you did! ;-)
shon3i
10th April 2009, 07:34
On the other hand some players such as Panasonic does not allows VC-1 video for AVCHD disk and requires blu-ray data type. Well VC-1 in AVCHD is not allowed, only AVC, that why called AVCHD :)
deank
10th April 2009, 10:06
deank
What is purpose of this feature? You can redirect tsMuxeR output to the file by means of pipes. For example (on win32):
tsMUxer test.meta test.ts 1> stdout.txt 2> stderr.txt
No I can't use redirections or stdout/in. I'm restricted to API call to CreateProcessA from kernel32.dll and it allows execution of .exe + parameters. So if you decide to add a log file - it will help me.
turbojet
10th April 2009, 10:59
Actually I was wrong in saying that the VC-1 for Panasonic hack has been tested on other players to play, it doesn't look like it has at least looking at posts and it is basically what new bluray output produces. This is the only scenario I know of that this function has use for. Old tsmuxer create blu-ray disk has been thoroughly tested on BDR's via RipBot264.
Old create blu-ray disk function seems to be almost identical to new avchd function except clpi/mpls headers are different, 200 in old, 100 in new. Is there anything else changed and could this cause problems?
It would be interesting to see if vc-1 can play on panasonic's using the new avchd output and if everything else plays ok with it. Would reverting back to old create blu-ray disk, many programs rely on --blu-ray and using 100 headers on clpi/mpls while getting rid of --avchd be tsmuxer's answer roman76r?
mrr19121970
10th April 2009, 11:58
No I can't use redirections or stdout/in. I'm restricted to API call to CreateProcessA from kernel32.dll and it allows execution of .exe + parameters. So if you decide to add a log file - it will help me.
execution of .exe = %comspec%
parameters = /c tsmuxer.exe meta.meta >log.txt
I'm sure this will work
deank
10th April 2009, 12:12
:thanks: :D
I thought I tried this before and it never worked. So I replaced the the exe with cmd.exe and it is okay now! Thanks again.
Rodger
10th April 2009, 13:35
Let me say/report it clear again.
My Samsung BD-P1400 almost plays ANYTHING I throw into it.
No matter if I choose AVCHD or Blu-Ray.
My Panasonic DMP-BD30 is bit more choosy. But still as far as I tested. No problem here with AVCHD or Blu-Ray setting in tsmuxer.
BUT here comes the bitch of all bitches when it comes to this theme.
The Samsung BD-P2500 !!!
Aspect Ratio? Be careful when you work on that one.
Iīve had small "white lines" on my TV (ca. 1 inch on a 32" TV) when the video was 1920x1080!!! But you can make that work.
What you absolutely canīt get to work, is the unused directories.
This Samsung (European Version) does absolutely refuse to play ANYTHING, if I donīt remove the unsued dirs.
Here is a screenshot, of what does work.
http://www.bilder-space.de/thumb/10.04qWSdJRd57N780KT.jpg (http://www.bilder-space.de/show.php?file=10.04qWSdJRd57N780KT.jpg)
PLEASE change this in the AVCHD "Mode" of tsmuxer.
rapscallion
10th April 2009, 18:45
With newer samsung firmwares/players you have to remove the AUXDATA folder for them to play. I'm not sure it's the same on Samsung 1200 but worth a try.
Good luck on your tests with latest tsmuxer using both outputs on both of those players. Please report back as we have to start fresh with a list of players that each output supports.
Ok, here are the results, using DVD5 RW, 30 min movie clip , 1280*720 :
Samsung 1200 - Will not play discs using either Blu-ray or AVCHD output mode. (btw, the owner's manual does NOT list AVCHD as a format it will play) Also will not play either mode if "aux" dir is removed or using basic structure, per Roger's post above.
Pioneer BDP-51fd : Plays both output modes equally well and player display indicates "avchd" for both.
Samsung 1400 : Before I sold it last week, using prev ver of tsmuxer w/o avchd output option, played fine in blu-ray mode.
turbojet
10th April 2009, 18:54
Samsung 1200 - Will not play discs using either Blu-ray or AVCHD output mode. (btw, the owner's manual does NOT list AVCHD as a format it will play) Also will not play either mode if "aux" dir is removed or using basic structure, per Roger's post above.
I found some info that the latest 2.3 firmware disables AVCHD playback. Others have been having success with previous firmwares though, I don't know if they are deleting AUXDATA directory or not. Deleting all but CLIPINF, PLAYLIST and STREAM is another common hack.
Thanks for the testing.
I have a good feeling AVCHD output in 1.9.x versions is technically more accurate then 1.8.34 and older versions of bluray disk output. But I don't know if it will make any playability difference.
rapscallion
10th April 2009, 19:48
I found some info that the latest 2.3 firmware disables AVCHD playback. Others have been having success with previous firmwares though, I don't know if they are deleting AUXDATA directory or not. Deleting all but CLIPINF, PLAYLIST and STREAM is another common hack.
Thanks for the testing.
I have a good feeling AVCHD output in 1.9.x versions is technically more accurate then 1.8.34 and older versions of bluray disk output. But I don't know if it will make any playability difference.
I have been following the 1200 thread in the AVS forum and just did a search for avchd. You're right, SS removed the "feature" in FW 2.3 and I wasn't trying that format then. There was playabilty with auxdata dir in place, I believe.
Current FW is 2.5, which I have. They claim avchd is a unsupported format on this model so they probably won't bring it back. (They have enough trouble with playback on supported formats, believe me ) I could roll back the FW, but that would cause more problems with BD discs.
I tried the "common hack" and that doesn't work either. Not an issue as I don't use this player for avchd PB.
For my Pio 51, I'll probably stay with the the Blu-ray output mode unless someone finds a significant difference.
Edit : I imagine that the "Blu-ray" tab for chapters should now be renamed "Blu-ray/AVCHD" in order to avoid confusion.
herrde
10th April 2009, 20:41
Hi everybody,
just did a search in this thread but wasn't able to find the answer...
I am using the latest build of mkvtoolnix, especially the new header editor and the chapter editor of mkvmerge. But whenever I change a MKV file by using the header editor or the chapter editor, tsmuxer is unable to load the changed MKV file. It always stops with a "Matroska Parse Error".
I have talked to the author of mkvtoolnix and he explained me the reason. Both the chapter and the header editor of mkvmerge are writing the header information at the END of the file and not at the beginning where tsmuxer is obviously expecting it. But this method is still compliant to the official Matroska specifications because the newly written header information is still indexed via the "meta seek" elements so they can be found easily.
But tsmuxer is obviously NOT able to find them if they are not at the beginning of the file!
This is obviously a huge problem because so many great applications use tsmuxer as their muxing tool (multiAVCHD etc.). And all these applications are unable to do their work if a MKV file has been edited with the chapter editor or the header editor of mkvmerge.
So is there a work-around to this problem? I hope the next version of tsmuxer will include the ability to scan the header information even if it's placed at the end of the MKV. If this is allowed by the MKV specifications, then tsmuxer should really be able to process these files...
All the best,
Gero
roman76r
11th April 2009, 01:08
herrde
Can you send me example of such file?
roman76r
11th April 2009, 01:19
mrr19121970
jamos
I tried to make 5Gb wave64 (w64) file. Mux passed without errors, file playing from begin to the end. Possible you tested PCM files without headers instead w64 files?
Rodger
I am afraid to remove the empty folder becouse the problems may appear on the other players. I can add special option if it necessary
herrde
Also, please try version 1.9.x. Mkv chapters must recognized and imported in this versions. Possible it is solve your problem.
New version of tsMuxeR is available: www.smlabs.net/tsMuxer/tsMuxeR_1.9.5(b).zip
Change list:
- pic_order_cnt_type 2 now supported for H.264 streams. Previus versions shows error message: "SPS picture order 2 not supported". H.264 video stream with this option generate many HD camcorder.
Rodger
11th April 2009, 02:27
Oh YES PLEASE :D
But as much as I can tell....all other players tested have no problem with "the missing" folders, but the BD-P2500 with the existance of the folders.
You may add that option somewhat hidden if you have worries.
Letīs say as an option in the general tab to activate if needed.
It would change the way the AVCHD-Choice in the input tab works.
This way no one interested would be confronted directly with that setting. That should be okay. What do you think roman?
mrr19121970
11th April 2009, 07:44
I'd say it's easier for you to delete them just before you burn.
turbojet
11th April 2009, 11:18
rapscallion: If you are looking for a problem 1.8.35+ blu-ray output doesn't work on PS3's and potentially other players.
There are a few players that need AUXDATA, BDJO, JAR, META directories with older tsmuxer bluray output, unfortunately I can't remember which, I'm thinking panasonic or sony. But maybe the changed mpls/clpi files have fixed that with avchd output. Technically these folders don't exist in avchd.
jamos
11th April 2009, 12:58
jamos
I tried to make 5Gb wave64 (w64) file. Mux passed without errors, file playing from begin to the end. Possible you tested PCM files without headers instead w64 files?
Must be a bug with eac3to then as that is where the file was created from and I used w64 as the output. it is ok though for me as I am waiting on my popcorn hour a110 to arrive as it outputs bitstream through the hdmi so I will no longer need to convert audio for hd m2ts files..
could you test a 8 channel w64 file, roman and make sure its not that..
thanks!
Atak_Snajpera
11th April 2009, 13:17
There are a few players that need AUXDATA, BDJO, JAR, META directories with older tsmuxer bluray output, unfortunately I can't remember which, I'm thinking panasonic or sony. But maybe the changed mpls/clpi files have fixed that with avchd output. Technically these folders don't exist in avchd.
turbojet is right. Those folders are not available in AVCHD structure and therefore it should be removed.
http://www.elurauser.com/articles/avchd_to_bluray.jsp
turbojet
11th April 2009, 13:30
I think it should only be a savable option to delete those folders.
Then again I don't think 2 different outputs that vary little, one that breaks things (PS3 playback) should exist. As far as I know --blu-ray was changed and --avchd added only to solve the VC1 on panasonic issue and that could easily be done automatically with 'if VC-1 headers = 0200 and don't signal IDEX else headers = 0100'
So my opinion means little
jj666
11th April 2009, 13:41
Wouldn't it be a good idea to create a proper thread list of players versus their requirements/compatibilities and the various workarounds that exist?
It must be very hard for Roman to judge what is correct at the moment, and asking him to fix something that breaks another device playback is hardly a way forward overall.
Cheers,
-jj-
turbojet
11th April 2009, 13:51
This thread (http://forum.doom9.org/showthread.php?t=144674) already exists.
This refers only to bluray output in tsmuxer versions prior to 1.8.35 though, newer versions are untested.
No one asked for bluray output (which 100's of guides and numerous software relies on) to change so it breaks playback but that's what we have now.
SeeMoreDigital
11th April 2009, 14:14
turbojet is right. Those folders are not available in AVCHD structure and therefore it should be removed.
http://www.elurauser.com/articles/avchd_to_bluray.jspAgreed..... And as your link suggests, the file structure that TSmuxer generates for AVCHD cards will have to change too...
I have two Panasonic devices (a TV and Blu-ray player) that include AVCHD SD card slot/readers. And sadly neither device is able to play AVCHD muxes generated by TSmuxer :(
To confirm.... The image below shows the "minimum" file structure required for a "fully working" AVCHD file from a Panasonic camcorder: -
http://i44.tinypic.com/2hg68fp.png
Cheers
turbojet
11th April 2009, 14:23
I agree that one of the outputs would make a lot more sense if it was output for a USB device but as we have it now if you own a PS3 avchd is the only output that works.
It would be nice if they fixed by reverting to old style bluray output before they break avchd output.
Atak_Snajpera
11th April 2009, 14:40
I have two Panasonic devices (a TV and Blu-ray player) that include AVCHD SD card slot/readers. And sadly neither device is able to play AVCHD muxes generated by TSmuxer
Does it mean that correct AVCHD structure must start with PRIVATE folder???
It would be nice if they fixed by reverting to old style bluray output before they break avchd output.
I don't mind if we have two structures (blu-ray and avchd) as long as it fully compatible with spec. AVCHD camcorders use PRIVATE -> AVCHD directory ...
turbojet
11th April 2009, 14:51
Does it mean that correct AVCHD structure must start with PRIVATE folder???
http://forum.doom9.org/showthread.php?p=1266479#post1266479
I don't mind if we have two structures (blu-ray and avchd) as long as it fully compatible with spec. AVCHD camcorders use PRIVATE -> AVCHD directory ...
I don't mind if there's two output formats either, but they should keep bluray as it's been over the past 2 years, except fix the clpi/mpls headers and avchd should be geared towards usb devices. I think playability on the most players should be the priority. If it was only about spec DTS, DTS-HD, TrueHD and VC1 wouldn't be allowed in AVCHD so PS3 users couldn't have these.
If people were starting to replace tsmuxer.exe in RipBot264 like they are in BD-Rebuilder you'd have a ton of reports saying it doesn't work on PS3 anymore because --bluray and PS3 = no work. Wouldn't that be fun?
These are only 2 of 100's of things that are affected by tsmuxer's change.
fifteen
11th April 2009, 14:54
Does it mean that correct AVCHD structure must start with PRIVATE folder???
At least seems so for solid state for Panasonic.
Read :http://en.wikipedia.org/wiki/AVCHD#Overview
and http://en.wikipedia.org/wiki/AVCHD#Compatibility_with_Blu-ray_Disc_players
Atak_Snajpera
11th April 2009, 16:02
If people were starting to replace tsmuxer.exe in RipBot264 like they are in BD-Rebuilder you'd have a ton of reports saying it doesn't work on PS3 anymore because --bluray and PS3 = no work. Wouldn't that be fun?
Therefore next version will use AVCHD structure (it works on DVD and BD. Blu-ray works only on BD). I will also remove empty folders which do not belong to AVCHD structure. Then We wait with fingers crossed :)
roman76r
11th April 2009, 16:23
I removed the useless folders in AVCHD mode:
BDMV/AUXDATA
BDMV/BDJO
BDMV/JAR
BDMV/META
CERTIFICATE
BDMV/BACKUP/BDJO
The new version is here:
www.smlabs.net/tsMuxer/tsMuxeR_1.9.6(b).zip
deank
11th April 2009, 16:25
Just a note:
The output with --blu-ray option in tsmuxer versions prior to 1.9.x was NOT BLU-RAY, but AVCHD. Mixed versions in headers (0100 or 0200) does not change anything.
PS3 and many other players won't like the new --blu-ray on DVD because is really is blu-ray, but not AVCHD what they'd play from DVD.
IMO --blu-ray option now works 100% and does what it has to do if user burns the content on BD disc.
AVCHD option works too and is the same as --blu-ray in older versions.
About folders: bluray should output ALL folders, starting with BDMV and CERFITICATE. avchd should output AVCHD as root and BDMV inside it (+ CLIPINF/BACKUP/PLAYLIST) - period.
Then with avchd if user decides to copy the structure to SD he should use the PRIVATE, if to DVD - should use only the contents of AVCHD folder, and if going for USB/MS - leave it as it is.
I think the problem for all is the misguidance with --blu-ray in earlier versions. Since day one tsmuxer should've used --avchd and since 1.9.x --blu-ray.
@SeeMoreDigital: I have two Panasonic devices (a TV and Blu-ray player) that include AVCHD SD card slot/readers. And sadly neither device is able to play AVCHD muxes generated by TSmuxer
To confirm.... The image below shows the "minimum" file structure required for a "fully working" AVCHD file from a Panasonic camcorder: -
It is not the folder structure that makes it fully-working - it is the contents of index.bdmv + *.clpi *.mpls files.
In brief: people should think of what media they'll use with the output of the new tsmuxer. If using DVD/SD/MS/USB - always use --avchd mode. If using Blu-Ray Discs (BD-R/RE) - always use --blu-ray mode. It is simple as that.
It doesn't matter what player you will be using. Just follow this rule. (of course SD playback for Panasonic TV/BD players is different matter).
@turbojet: If people were starting to replace tsmuxer.exe in RipBot264 like they are in BD-Rebuilder you'd have a ton of reports saying it doesn't work on PS3 anymore because --bluray and PS3 = no work. Wouldn't that be fun?
New versions of tsmuxer affect only tools which use tsmuxer's index.bdmv (unlike multiAVCHD).
And I think we're all starting repeating ourselves in other threads.
rapscallion
11th April 2009, 16:41
rapscallion: If you are looking for a problem 1.8.35+ blu-ray output doesn't work on PS3's and potentially other players.
There are a few players that need AUXDATA, BDJO, JAR, META directories with older tsmuxer bluray output, unfortunately I can't remember which, I'm thinking panasonic or sony. But maybe the changed mpls/clpi files have fixed that with avchd output. Technically these folders don't exist in avchd.
Well, at the moment, my Pioneer 51 plays both outputs.
With 1.9.6b, per Dean's post, I'll use avchd out, with dvd9 media. (but, maybe add the "Certficate" dir :))
The SS 1200 isn't an issue, because it's our bedroom player, and I don't plan on using it at all, for avchd playback.
I only tested it out of curiousity.
turbojet
11th April 2009, 17:23
I removed the useless folders in AVCHD mode:
BDMV/AUXDATA
BDMV/BDJO
BDMV/JAR
BDMV/META
CERTIFICATE
BDMV/BACKUP/BDJO
The new version is here:
www.smlabs.net/tsMuxer/tsMuxeR_1.9.6(b).zip
Now to fix the players that do need these folders?
What exactly is the goal of the new bluray mode?
I never saw a report outside of VC1 on panasonic players that didn't play with the old 100 headers and I've already given a simpler (for the enduser) workaround for the VC1 issue.
turbojet
11th April 2009, 17:59
Just a note:
The output with --blu-ray option in tsmuxer versions prior to 1.9.x was NOT BLU-RAY, but AVCHD. Mixed versions in headers (0100 or 0200) does not change anything.
We can debate this forever, in the consumer electronics world bluray comes on optical media, avchd comes on magnetic and solid state drives. Technically you may be right though.
PS3 and many other players won't like the new --blu-ray on DVD because is really is blu-ray, but not AVCHD what they'd play from DVD.
IMO --blu-ray option now works 100% and does what it has to do if user burns the content on BD disc.
new --bluray only helps panasonic players with VC-1 and hurts in other places, it doesn't matter if its burned to DVDR or BDR
AVCHD option works too and is the same as --blu-ray in older versions.
About folders: bluray should output ALL folders, starting with BDMV and CERFITICATE. avchd should output AVCHD as root and BDMV inside it (+ CLIPINF/BACKUP/PLAYLIST) - period.
Then with avchd if user decides to copy the structure to SD he should use the PRIVATE, if to DVD - should use only the contents of AVCHD folder, and if going for USB/MS - leave it as it is.
Perhaps it should but you have to realize this will break a lot of things that relied on the BDMV/CERTIFICATE folders tsmuxer used to output in output directory.
I think the problem for all is the misguidance with --blu-ray in earlier versions. Since day one tsmuxer should've used --avchd and since 1.9.x --blu-ray.
This could be a mistake for years but instead of changing a working command every program I can think of adds commands in order to do what they want to do. Like lame changed to -V function but they still kept --preset intact. Imagine if x264 was to change --crf to fastest possible settings ever while adding --pass 0 to replace the current crf, this is a lot like what tsmuxer has just done.
In brief: people should think of what media they'll use with the output of the new tsmuxer. If using DVD/SD/MS/USB - always use --avchd mode. If using Blu-Ray Discs (BD-R/RE) - always use --blu-ray mode. It is simple as that.
This isn't exactly true as I've pointed out numerous times that VC-1 on panasonic needs bluray output burning on both DVD and BD while NO ONE else does and looking at bug reports already, shouldn't use it. Come to think of it if I remember correctly from first BD-RB versions that used most of the original bdmv files for movie only mode, PS3 can't use bluray for movie only on a BDR either but this may also have been a BD-RB issue.
New versions of tsmuxer affect only tools which use tsmuxer's index.bdmv (unlike multiAVCHD).
Which is everything but multiAVCHD that uses tsmuxer, you have to also consider all the guides.
rack04
11th April 2009, 18:10
Now to fix the players that do need these folders?
Which players are you referring to?
turbojet
11th April 2009, 18:11
Which players are you referring to?
I can't remember exactly but I believe it was some panasonics or sony, it was a name brand and I will try to search for it in this forum somehow.
deank
11th April 2009, 18:12
We can debate this forever, in the consumer electronics world bluray comes on optical media, avchd comes on magnetic and solid state drives. Technically you may be right though.
There should be nothing to debate. AVCHD is also availabe on optical media. And you can think of it as EXTENDED (yet codec restricted) format of Blu-ray specs-wise.
new --bluray only helps panasonic players with VC-1 and hurts in other places, it doesn't matter if its burned to DVDR or BDR
That's not true. All players should handle --blu-ray output of tsmuxer if written to BD disc (including PS3). It will break most if user uses DVD disc. Panasonic's needed to see the disc as BDMV to play VC-1 and the hack was simply using a BD index.bdmv (without the AVCHD IDEX segment) and I'm quite sure this hack was needed ONLY if using DVD, but not a real BD-R/RE disc.
... you have to realize this will break a lot of things that relied on the BDMV/CERTIFICATE folders tsmuxer used to output in output directory.
True, only if you're using DVD media and certain players.
This could be a mistake for years but instead of changing a working command every program I can think of adds commands in order to do what they want to do. Like lame changed to -V function but they still kept --preset intact. Imagine if x264 was to change --crf to fastest possible settings ever while adding --pass 0 to replace the current crf, this is a lot like what tsmuxer has just done.
I agree.
turbojet
11th April 2009, 18:58
Denon 3800 reported not playing without empty directories (http://forum.doom9.org/showthread.php?p=1242263#post1242263)
deank
11th April 2009, 19:02
You should ask jwgallardo if he can see AVCHD support anywhere in his denon user manual - a lot of players do not support AVCHD. There are players as his that would play only BD structures (no matter the media - just like Sony 3xx, which will play everything - no matter the DVD/BD media) but not AVCHD.
So probably I stand to correct myself and add that user should know what his player is capable of and consider the media he's using. I doubt that ANYONE has problems when using BD-R/RE discs. And you're referring to BD-RB output, which is totally different than using tsmuxer alone, so it doesn't count. Full-movie is working for him (which is BD mode) and movie-only is also working for him when folders are present (player going to BD mode because of folders - simply because doesn't support AVCHD mode to act differently).
mrr19121970
11th April 2009, 19:04
I removed the useless folders in AVCHD mode:
BDMV/AUXDATA
BDMV/BDJO
BDMV/JAR
BDMV/META
CERTIFICATE
BDMV/BACKUP/BDJO
The new version is here:
www.smlabs.net/tsMuxer/tsMuxeR_1.9.6(b).zip
whilst you are on the subject I believe that the --blu-ray output should also contain a BACKUP/JAR folder
turbojet
11th April 2009, 19:11
You should ask jwgallardo if he can see AVCHD support anywhere in his denon user manual - a lot of players do not support AVCHD. There are players as his that would play only BD structures (no matter the media - just like Sony 3xx) but not AVCHD.
Both of them have been reported playing old bluray output.
My point is that these 2 output modes are a guessing game for at least 3 players now. While the old bluray worked fine but depending on the player required a hack that could be solved with options in tsmuxer.
Before you could suggest 'output to bluray and remove a directory.'
That's been turned into 'try AVCHD first and remove the directory if that doesn't work try bluray and remove directory, if neither work go back and use the old versions that have a proven method to work'.
I would think the point of a programs progression was to make things easier, not more complex.
Basically anyone that's been helping people play things, like myself, has got a much much tougher job if this tsmuxer starts getting used and it's all just to get VC-1 playback on a panasonic. In fact from a playability standpoint bluray disk output would be more accurately named 'VC-1 for panasonic' and that's all it's good for.
My suggestion on the whole thing is:
- Revert --bluray back to how it was using 0100 headers with IDEX and if VC-1 is output don't use IDEX, well this should really be tested, but at the least have an option such as 'Allow VC-1 on Panasonic players' to set up the bdmv like bluray currently does. another welcome option would be to remove just AUXDATA folder or remove all empty directories. These options hopefully would be saved and stored in registry or ini.
- Use the current --avchd but have the gui display 'AVCHD for USB' which outputs in AVCHD/BDMV structure, has 8.3 file names and splits files at 4 GB that is restricted to H.264, AC3, LPCM and 24 MB/s bitrate.
All the help, guides, tools would still be accurate.
People wanting USB media playback would get it out of the box.
turbojet
11th April 2009, 19:15
whilst you are on the subject I believe that the --blu-ray output should also contain a BACKUP/JAR folder
Looking at some retail BD's this seems to only exist in BACKUP if it uses BD-J which it contains files then. Other times it may exist but also may not exist in root directory.
TSMuxer doesn't use BD-J.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.