Log in

View Full Version : TSM2UHD Discussion and Bug Reporting


Pages : [1] 2 3 4

jdobbs
18th December 2017, 00:06
This thread has been created for discussing TSM2UHD, a program to convert TSMUXER BD formatted structures for use on standalone UHD BD players.

What is TSM2UHD?

TSM2UHD stands for "TSMUXER to UHD".

TSMUXER v2.6.12 has the ability to multiplex HEVC streams into a Blu-Ray disc structure. One might assume, then, that if that structure was created from a 2160p (UHD) HEVC file that is compliant with Ultra HD Blu-Ray (UHD-BD) -- it would playback on a UHD player. Unfortunately, however, that isn't the case. When TSMUXER v2.6.12 was created there was still much that hadn't been decided in the UHD-BD standard.

The purpose of this software is to examine the output of TSMUXER v 2.6.12 and make changes that are required in order to make that structure readable and compatible with a standard UHD-BD standalone player.

Latest Version: v1.12 (Feb 25, 2018)
Click this link (http://www.jdobbs.net/freeware/TSM2UHD_V1.12.zip) to download the latest version in a zip file.

How to use the software:

1. Read the software license text in LICENSE.TXT.

2. Create a set of streams (video/audio/subtitles) that is compatible with UHD-BD. This assumes the video is 3840x2160. Be careful with bitrates! An original stream may not work -- as its maximum bitrate could exceed that of a BD-50 or BD-25 disc. I recommend you make sure the total of all streams does not exceed 50Mbs combined for BD-50 (absolutely no more than 64Mbs) and 35Mbs for BD-25.

3. Open TSMUXER v2.6.12 and select those streams (TSMUXER instructions are available elsewhere -- and details are not included here).

4. Using the TSMUXER software, output a BD compatible structure to a folder on your hard drive. Let it complete its task.

5. Run TSM2UHD, and select the folder you created in step 4. Then press the button to start execution.

TSM2UHD will run. It will make changes to these files in the TSMUXER created folder:

Index.bdmv, MovieObject.bdmv, the .mpls file, .clpi file, and .m2ts file.

NOTES:

1. This is beta software. I tested it on my Sony UBP-X800 player and it works. There is a chance there may still be bugs... if you have issues report them here.

2. Bitrates! Remember, An original stream may not work as is -- as its maximum bitrate could exceed that of a BD-50 or BD-25 disc. I recommend you make sure the total of all streams does not exceed 50Mbs combined for BD-50 (absolutely no more than 64Mbs) and 35Mbs for BD-25.

3. The program has to scan the entire M2TS stream making changes to every video start code and all PMT packets. This can take a while (about 30-40 minutes on my system). I have noticed that on my player, it seems to play ok even when these updates aren't done. For that reason I have added a checkbox on the program's form that allows you to skip those updates. I highly recommend keeping it unchecked for compliance... but if you're in a hurry and want to risk it, it's your choice.

4. I wrote this without access to the UHD-BD standard... so keep that in mind. If you run into an issue, report in this thread and I'll see what I can do. Please, don't keep asking for updates... it's freeware and I'll get to it when I have the free time.

LowDead
18th December 2017, 17:28
Nice one! Thank you! :D

//LD

geheim
19th December 2017, 19:02
Awesome, thank you very much! I'll be doing some tests over the next days and report any issues I may find.

DenisRodman
20th December 2017, 05:36
Well done! :thanks:

iSeries
20th December 2017, 20:42
Great, so this can be used for movie-only remuxes. Does it retain Dolby Vision?

LowDead
21st December 2017, 00:55
I may have come across a bug. Whole movie took only 5min to scan and fix. In the instructions you mention about 30min.. Just to rule out user error, the m2ts box should not be ticked? Will test some more also to rule out bad rip.

//LD

SeeMoreDigital
21st December 2017, 11:21
...Does it retain Dolby Vision?Nope...

jdobbs
21st December 2017, 15:07
I may have come across a bug. Whole movie took only 5min to scan and fix. In the instructions you mention about 30min.. Just to rule out user error, the m2ts box should not be ticked? Will test some more also to rule out bad rip.

//LDIt should not be ticked.

5 mins? How big is the input M2TS? Just reading a 45GB file (with no changes written) on my system takes about 10 mins.

jdobbs
21st December 2017, 15:10
Great, so this can be used for movie-only remuxes. Does it retain Dolby Vision?That would depend on whether TSMUXER handles it. This software doesn't do the muxing, it just corrects type and format flags, version numbers, PMT entries, and start codes in order to make it recognizable by a UHD player.

DenisRodman
21st December 2017, 18:39
jdobbs,
Maybe add support for all files.

Can you add conversion support also for files:

- CERTIFICATE\id.bdmv
- BDMV\AUXDATA\sound.bdmv
- BDMV\BDJO\00000.bdjo

jdobbs
21st December 2017, 20:22
jdobbs,
Maybe add support for all files.

Can you add conversion support also for files:

- CERTIFICATE\id.bdmv
- BDMV\AUXDATA\sound.bdmv
- BDMV\BDJO\00000.bdjoThey don't exist in a structure created by TSMUXER.

It's not that hard to find and replace those version headers, but could you please explain how you are using this S/W that might need that? I could understand if you are talking about the version of BD-RB I'm working on -- but I don't see how those could exist here.

Are you trying to restructure a full disc by hand and then run this on it? If so -- I'd think the version headers would already be correct for those files.

DenisRodman
22nd December 2017, 05:55
jdobbs,

I was thinking of trying to remultiplex a regular Blu-ray disc with a menu under the new format of the UHD BD. To do this, I used your program and saw that your program does not correct all files. So I suggested adding support for other files.

Bandits
22nd December 2017, 11:08
Any chance you can make this work from command line without the gui?

sneaker_ger
22nd December 2017, 12:05
Does it work with x265 output? You mentioned here (https://forum.doom9.org/showthread.php?t=175042) that you encountered troubles.

wolflop
22nd December 2017, 13:50
I have created a BD structure with the tsmuxer (UHD mkv). Then edited as specified with the TSMUhdmuxer. Unfortunately, only audio and no picture is playable on the player

jdobbs
22nd December 2017, 18:35
Any chance you can make this work from command line without the gui?Sure. It may be a little while. though. Definitely after Christmas/New Year.

jdobbs
22nd December 2017, 19:16
Does it work with x265 output? You mentioned here (https://forum.doom9.org/showthread.php?t=175042) that you encountered troubles.Yes, but...

1. I went back through the mux software I'd created when using the X265 stream and found a difference, with a fix to that I got a picture.

2. It played video then, but had serious "stuttering" issues with all of the examples I'd found. So I went through the entire set of CLI values and discovered that my player wouldn't playback smoothly unless the stream had open gops. I also found that I had to disable b-pyramid. That made no sense to me... but there it was. There were also several other tweaks I had to include to get smooth playback (see below)...

3. I couldn't use "--uhd-bd" because it would force settings that cause stutter. So I manually set it's other parameters

So now I'm at a point at which I'm using this line for recording (of course some things like bitrate can change):

ffmpeg.exe -probesize 100MB -i "\path\to\source.m2ts" -an -r 23.976
-pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "x265.exe" -
--preset medium --input-depth 10 --output-depth 10 --vbv-bufsize
30000 --vbv-maxrate 35000 --level-idc 51 --bframes 3 --ref 3
--slices 4 --no-b-pyramid --repeat-headers --chromaloc 2 --aud
--hrd --min-keyint 1 --colorprim bt2020 --transfer smpte2084
--colormatrix bt2020nc --max-cll "1000,400" --master-display
"G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)"
--fps 23.976 --sar 1:1 --qpfile "\path\to\chapters.CHP" --keyint 24
--bitrate 34653 --y4m --output "output.hevc"

4. But... there is still an issue. I can encode (very slowly) with this line, then use TSMUXER and TSM2UHD to create a structure -- and the output plays back fine on my Sony standalone.

If though, I try to use that structure as input to another encode -- it starts stuttering again on the grandchild copy. That makes me suspicious of the "successful" encode. I think it may have something to do with the FFMPEG line -- because I don't have that problem if I use AVS2YUV the second time... (but I do lose 10 bit/HDR since AVISYNTH is 8 bit).

So I'm not 100% there yet. I'm hoping others will try different things, use TSM2UHD, and report back results on other players -- and maybe some of this will become clearer. Maybe they can also find something in this command line that needs changing too.

It sure would be easier if I had the spec.

gonca
22nd December 2017, 20:25
Would you consider using Vapoursynth?

jdobbs
22nd December 2017, 20:53
Would you consider using Vapoursynth?Don't know enough about it to say.

gonca
22nd December 2017, 21:07
You can use AVS filters and still have full depth (>8 bit) support

jdobbs
22nd December 2017, 21:24
You can use AVS filters and still have full depth (>8 bit) supportHow does it compare to AVISYNTH+?

gonca
22nd December 2017, 21:55
Some software, NVEncC is one, doesn't support full depth input from Avisynth and forks (+ included)
In this case Vapoursynth is fully supported, more universal support it appears
It seems to be more actively supported
Only way to determine if AVS+ will do what you need is to try short clips and see
However if you think you will one day support hardware encoding (2x + frame rate encoding for 4k) it might be worth considering

sneaker_ger
22nd December 2017, 23:11
discovered that my player wouldn't playback smoothly unless the stream had open gops. I also found that I had to disable b-pyramid. That made no sense to me... but there it was.
B-pyramid on x264 also has to be restricted for Blu-ray compatibility so it is not that surprising if the one in x265 is not Blu-ray-compatible. But Open-GOP is really strange...

LowDead
23rd December 2017, 17:08
It should not be ticked.

5 mins? How big is the input M2TS? Just reading a 45GB file (with no changes written) on my system takes about 10 mins.

yep, 5 mins with the m2ts box unticked. input file just over 20gb. So something isn't right. I would suspect the input file is corrupt. The resulting output burned on dl bd-rw and running in my k8500 everything is working as it should until the first chapter break. There everything freezes for a second and when it comes back theres no sound. Hmm just thought of trying without any chapters to see if that is what it chokes on. I will also try to encode with your settings for ffmpeg to see if it makes any difference.

Merry Christmas and Happy Holidays! :D

//LD

jdobbs
23rd December 2017, 23:33
yep, 5 mins with the m2ts box unticked. input file just over 20gb. So something isn't right. I would suspect the input file is corrupt. The resulting output burned on dl bd-rw and running in my k8500 everything is working as it should until the first chapter break. There everything freezes for a second and when it comes back theres no sound. Hmm just thought of trying without any chapters to see if that is what it chokes on. I will also try to encode with your settings for ffmpeg to see if it makes any difference.

Merry Christmas and Happy Holidays! :D

//LDIf you could, please let me know how long the encode takes. You could also try changing from "medium" to "superfast" -- that's what I've been using (otherwise I get 1.5fps).

geheim
24th December 2017, 09:56
So, it doesn't work for me unfortuanetly. I tried some original streams, made a BD Folder structure with TSMuxer, and then applied TSM2UHD to the Folder. After it finishes I tried Playback with DVD Fab Media Player (which works fine for everything I tried), but Playback gives me heavy stuttering and "jumping". Don't know what I could be making wrong here...

Thanks for your work and merry Christmas!

SeeMoreDigital
24th December 2017, 11:17
....but Playback gives me heavy stuttering and "jumping". Don't know what I could be making wrong here..Does the actual '00000.m2ts' stream play okay?

geheim
24th December 2017, 14:04
Does the actual '00000.m2ts' stream play okay?

Just tried playing the m2ts directly and while there are lesser Picture Errors, there are still some jumps and stuttering visible during many scenes... Seems like something is still wrong with how files get patched.

SeeMoreDigital
24th December 2017, 15:08
Just tried playing the m2ts directly and while there are lesser Picture Errors, there are still some jumps and stuttering visible during many scenes... Seems like something is still wrong with how files get patched.
Sounds more likely to be a TSmuxer GUI muxing issue...

jdobbs
24th December 2017, 17:06
So, it doesn't work for me unfortuanetly. I tried some original streams, made a BD Folder structure with TSMuxer, and then applied TSM2UHD to the Folder. After it finishes I tried Playback with DVD Fab Media Player (which works fine for everything I tried), but Playback gives me heavy stuttering and "jumping". Don't know what I could be making wrong here...

Thanks for your work and merry Christmas!I'm assuming this is a burned disc? If so, that's more than likely due to the bitrate exceeding what can be used on a BD-25/50. It needs to be reencoded. The only original streams I found that could be used intact were extras -- probably because they were made purposely to work on multiple formats.

I mentioned the bitrate issue twice in the README:2. Bitrates! Remember, An original stream may not work as is -- as its maximum bitrate could exceed that of a BD-50 or BD-25 disc. I recommend you make sure the total of all streams does not exceed 50Mbs combined for BD-50 (absolutely no more than 64Mbs) and 35Mbs for BD-25. It is very unlikely that the original stream is on a BD-50-- and the allowable bitrate on a BD-100 (for example) is almost twice what a BD-50 can handle.

If it isn't a burned disc... than I'm at a loss. TSM2UHD does nothing, repeat nothing, that could modifies the playback itself. It only sets flags in files so that they are recognizable to a UHD-BD player.

As SeeMoreDigital mentioned, it is more likely to be a TSMUXER issue... which would be a lot harder to fix. If you find out more, let me know.

geheim
24th December 2017, 18:14
I'm assuming this is a burned disc? If so, that's more than likely due to the bitrate exceeding what can be used on a BD-25/50. It needs to be reencoded. The only original streams I found that could be used intact were extras -- probably because they were made purposely to work on multiple formats.

I mentioned the bitrate issue twice in the README: It is very unlikely that the original stream is on a BD-50-- and the allowable bitrate on a BD-100 (for example) is almost twice what a BD-50 can handle.

If it isn't a burned disc... than I'm at a loss. TSM2UHD does nothing, repeat nothing, that could modifies the playback itself. It only sets flags in files so that they are recognizable to a UHD-BD player.

As SeeMoreDigital mentioned, it is more likely to be a TSMUXER issue... which would be a lot harder to fix. If you find out more, let me know.

The original stream comes from a UHD66, but I did my tests WITHOUT burning to a BD-R DL. Only played the folder from HDD after modifying with TMS2UHD.
That's why I assumed the bitrate couldn't be the cause of the error. Just for the fun of it I copuld try burning the folder and see what my Sony x800 does with it ;)

I'll re-check my settings in TSMuxer as well, perhaps I did something wrong there. And I'll be checking with some own footage I created myself.

I'll report if I find out anything new of course!

geheim
26th December 2017, 13:31
So I did some more tests and I simply can't get it working... Even tried some of my own UHD stuff which definitely doesn't exceed bitrate limits and I'm getting the same picture errors. So I guess I'm really doing something wrong with TSMuxer - but I don't know what to change.
Can you recommend any settings which worked for you?? Perhaps I need to adjust VBV buffer size??

LowDead
4th January 2018, 13:13
Ok first test with medium went on for appr. 31 hrs.(112500.65s) on a 20gb 1.40hr movie.
Will start next test run when I get back from work tonight.

6 core Intel i7 980x @3GHz

//LD

jdobbs
4th January 2018, 16:06
Ok first test with medium went on for appr. 31 hrs.(112500.65s) on a 20gb 1.40hr movie.
Will start next test run when I get back from work tonight.

6 core Intel i7 980x @3GHz

//LDDid the mux and TSM2UHD produce a working UHD-BD disc?

LowDead
5th January 2018, 02:05
Did the mux and TSM2UHD produce a working UHD-BD disc?

Yes it worked as it should. Do you want me to do a superfast run?

//LD

wolflop
5th January 2018, 05:17
Did you find out something with the samples I sent you (No Picture on UB 900)?

wolflop

no-one
5th January 2018, 16:03
So, it doesn't work for me unfortuanetly. I tried some original streams, made a BD Folder structure with TSMuxer, and then applied TSM2UHD to the Folder. After it finishes I tried Playback with DVD Fab Media Player (which works fine for everything I tried), but Playback gives me heavy stuttering and "jumping". Don't know what I could be making wrong here...

Thanks for your work and merry Christmas!

same promblem, It's stuttering.

pretty sure, it's tsmuxer issue. mpls file has problem.

I try with blade runner uhd.After process tsm2uhd, i check it with bdinfo.

1. movie length is changed
original : 1:57:31.377
result : 1:51:41.486

2. hdr is romoved
original : MPEG-H HEVC Video 0 kbps 2160p / 23.976 fps / 16:9 / Main 10 Profile 5.1 High / 4:2:0 / 10 bits / HDR / BT.2020 /

result : MPEG-H HEVC Video 0 kbps 2160p / 23.976 fps / 16:9 / Main 10 Profile 5.1 High / 4:2:0 / 10 bits / SDR / BT.2020 /

3. i burn into disc and play it on lg up970. It's stuttering, no hdr and video and sound not sync.

jdobbs
6th January 2018, 15:24
Please read the README.TXT file. I've now had to repeat this about four times.

You generally CAN'T KEEP AN ORIGINAL STREAM. The original stream is encoded at a bitrate that is TOO HIGH for a BD-25 or BD-50. For example, if the original came from a BD-100, the bitrate can be almost twice as high as a BD-50 can accomodate. You're going to get stuttering, etc, because the spinning of the disc can't keep up with the encode rate.

Everyone -- please don't make me have to explain this again!

I have no idea how HDR can be removed. You're telling me the stream is unchanged from the original --- so I don't see how that is possible. It might be that TSMUXER is removing some indicator, I don't know. Nothing TSM2UHD does removes it.

ocean
6th January 2018, 16:21
TSMuxer does not recreate the "extension data" HDR in the mpls playlist file, after mux, this is the missing part that you find in the original, you can find it at the end of the mpls file:

"ExtensionData": [
{
"ID1": 3,
"ID2": 5,
"data_block": [
0,
0,
0,
32,
1,
0,
0,
0,
16,
0,
0,
0,
51,
194,
134,
196,
29,
76,
11,
184,
132,
208,
62,
128,
61,
19,
64,
66,
15,
160,
0,
50,
3,
232,
2,
90
I tried the Blu-ray movie worked with TSMuxer and TSM2UHD on Hdisk, read with PowerDVD 17, the movie is recognized regularly and is fluid, without obviously HDR, for audio desync i think it always depends on an incorrect management of the TSMuxer timeline audio/video and the treatment of Gops i-frames.

jdobbs
6th January 2018, 16:33
TSMuxer does not recreate the "extension data" HDR in the mpls playlist file, after mux, this is the missing part that you find in the original, you can find it at the end of the mpls file:

"ExtensionData": [
{
"ID1": 3,
"ID2": 5,
"data_block": [
0,
0,
0,
32,
1,
0,
0,
0,
16,
0,
0,
0,
51,
194,
134,
196,
29,
76,
11,
184,
132,
208,
62,
128,
61,
19,
64,
66,
15,
160,
0,
50,
3,
232,
2,
90
I tried the Blu-ray movie worked with TSMuxer and TSM2UHD on Hdisk, read with PowerDVD 17, the movie is recognized regularly and is fluid, without obviously HDR, for audio desync i think it always depends on an incorrect management of the TSMuxer timeline audio/video and the treatment of Gops i-frames.Well... at least that is something I can add. I already add extension data for 3D in BD-RB. But... the problem is that since it isn't in the folder I need to get the values somehow from the original. If I had a copy of v3.00 of the standard I could have been aware of the extension. Right now I'm just getting my info from dumps. The fact that PowerDVD plays the source probably confirms bitrate as the issue in the stuttering.

ocean
6th January 2018, 17:03
Hi jdobbs, for the HDR static metadata extensions you can see the Standard CEA 861.3 and later document, the values should be read from the main file mpls of the movie, to read them I used BD-Tools.

jdobbs
6th January 2018, 18:25
Hi jdobbs, for the HDR static metadata extensions you can see the Standard CEA 861.3 and later document, the values should be read from the main file mpls of the movie, to read them I used BD-Tools.The problem is that I only work on the output folder. There is no guarantee that TSM2UHD will even have access to the original MPLS file.

ocean
7th January 2018, 23:39
The problem is that I only work on the output folder. There is no guarantee that TSM2UHD will even have access to the original MPLS file.

I understand, for confirmation I replaced the mpls file and clpi with the originals, in the structure created by TSM2UHD, HDR it works.

frank
10th January 2018, 17:15
Use ffmpeg 64 bit
--preset faster --ctu 32 --crf 22
-o output.265

It's good and fast.

Don't use
--slices 4 --input-depth 10 --output-depth 10 --level-idc 51
x265 sets it automatically right. level 50 is sufficient for BD bitrates.

Maybe the --slices instruction is the cause of stuttering. ffmpeg had problems with it (lookahead).
I only make mkv and never had problems with --uhd-bd

ffmpeg64.exe -loglevel warning << info or verbose gives more information about decoding

jdobbs
10th January 2018, 21:35
Use ffmpeg 64 bit
--preset faster --ctu 32 --crf 22
-o output.265

It's good and fast.

Don't use
--slices 4 --input-depth 10 --output-depth 10 --level-idc 51
x265 sets it automatically right. level 50 is sufficient for BD bitrates.

Maybe the --slices instruction is the cause of stuttering. ffmpeg had problems with it (lookahead).
I only make mkv and never had problems with --uhd-bd

ffmpeg64.exe -loglevel warning << info or verbose gives more information about decodingActually, if I recall correctly, I think I added the "--slices 4" in order to get rid of stuttering.

If you made an MKV it doesn't have to be UHD-BD compliant either... I can tell you that using "--uhd-bd" cause problems on my Sony player because it forces settings that cause stutter.

A.Fenderson
11th January 2018, 05:16
I was just doing my semi-annual web search for any free UHD authoring tools and ran across this tool. Of course jdobbs, building on work by the tsMuxeR author(s) of course, is the first person on the internet to get this working at all! :-)

Despite having rushed the test and largely having no idea what I'm doing, I can report success under the following scenario:

Source file info (captured with Sony FDR-AX53 @ 4K/29.97fps):

Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, RefFrames : 2 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 4 min 2 s
Bit rate mode : Variable
Bit rate : 93.7 Mb/s
Maximum bit rate : 100.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS

video reencode to h265 was via HandBrake with custom settings:
x265 (w/ AAC audio reencoded from PCM, inside MKV)
no change to resolution, anamorphic: none.
no filters
constant framerate
35000 kbps avg bitrate, 2-pass encode
(ultrafast, fwiw, to get it done sooner)

Remuxed with tsMuxeR 2.6.11 to Blu-ray folder output.

note: at this point I did burn the raw tsMuxeR output to a BD-RE25, which would play with audio and no video on my Xbox One S.

Processed with the TSM2UHD.

Burned final Blu-ray folder structure to BD-RE25 via ImgBurn 2.5.8.0.

Played back flawlessly in my Xbox One S.

One mistake I noticed I made was to leave Handbrake's framerate at 30fps instead of "same as source" or even 29.97 (I was working from an existing template and neglected to change this). The output file shows as 30.0 fps in MediaInfo, yet when played on the XB1S, it shows as 25fps and outputs at 50fps.

In any case, so far as I can tell this is a major breakthrough in home-authoring of UHD BD content, and therefore I am contributing to jdobbs for his initiative in tackling this issue (if he will kindly PM me the email address to which I can send his donation).

:thanks:

frank
11th January 2018, 16:50
jdobbs: I think I added the "--slices 4" in order to get rid of stuttering.
x265 sets lslices=8, so all my hardware incl. libreELEC TV-Box play 4k streams flawlessly with HW-decoding.

Unfortunately old TsMuxer was not developed and tested with 4k HEVC...

A.Fenderson
12th January 2018, 20:05
I ran another test, again encoding via Handbrake, but this time bumping the bitrate to 50,000 kbps (and keeping source framerate intact), then burning to 50GB BD-RE DL. Source material, as before, is 8-bit (SDR) 4K 4:2:0 output from Sony FDR-AX53.

tsMuxeR didn't detect frame-rate, so set explicitly to 30000/1001 to match source file. Inserted chapter every 1 minute.

Burned the raw remux to BD-RE DL 50GB and attempted to play in XB1S: audio with no video.

Processed tsMuxer's output via TSM2UHD, burned this to BD-RE DL, and attempted to play in my XB1S: overall decent playback, with very occasional stuttering, though any attempt to skip chapters would lock up playback and force me to exit the BD player application entirely. Oddly, the bitrate readout of the XB1S very regularly showed bitrates far in excess of 50 Mbps, sometimes for several seconds at a time. It even hovered in the mid 70s for several seconds once. I don't know whether to chalk these issues up to simply a worthless implementation of bitrate monitor on that system, bad rate control from x265 (highly unlikely), Handbrake not properly passing the rate control parameters off to x265 (also seems unlikely), problems caused by encoding via the Handbrake GUI in the first place without explicitly passing the required parameters to restrict the encode to UHD compatibility, or something else entirely. In any case, to get meaningful results, I'm going to have to quit being lazy with these encodes to ensure the results meet UHD-BD restrictions.

jdobbs: If you will let me know which UHD-BD player(s) you are testing on, I will possibly attempt to purchase a proper standalone player of a different brand and/or model myself so that we can test across as many different players as possible: I've been wanting to get one anyway, and I think it would make for more valuable tests than using the Xbox. Is your Sony player the X800? Also the donation link in your sig doesn't auto-fill your email address.

LowDead
13th January 2018, 00:06
@A.Fenderson: Yes, he has the Sony. I have the Samsung UBD-K8500. So any other then for you ;-)

//LD

jdobbs
13th January 2018, 01:16
I ran another test, again encoding via Handbrake, but this time bumping the bitrate to 50,000 kbps (and keeping source framerate intact), then burning to 50GB BD-RE DL. Source material, as before, is 8-bit (SDR) 4K 4:2:0 output from Sony FDR-AX53.

tsMuxeR didn't detect frame-rate, so set explicitly to 30000/1001 to match source file. Inserted chapter every 1 minute.

Burned the raw remux to BD-RE DL 50GB and attempted to play in XB1S: audio with no video.

Processed tsMuxer's output via TSM2UHD, burned this to BD-RE DL, and attempted to play in my XB1S: overall decent playback, with very occasional stuttering, though any attempt to skip chapters would lock up playback and force me to exit the BD player application entirely. Oddly, the bitrate readout of the XB1S very regularly showed bitrates far in excess of 50 Mbps, sometimes for several seconds at a time. It even hovered in the mid 70s for several seconds once. I don't know whether to chalk these issues up to simply a worthless implementation of bitrate monitor on that system, bad rate control from x265 (highly unlikely), Handbrake not properly passing the rate control parameters off to x265 (also seems unlikely), problems caused by encoding via the Handbrake GUI in the first place without explicitly passing the required parameters to restrict the encode to UHD compatibility, or something else entirely. In any case, to get meaningful results, I'm going to have to quit being lazy with these encodes to ensure the results meet UHD-BD restrictions.

jdobbs: If you will let me know which UHD-BD player(s) you are testing on, I will possibly attempt to purchase a proper standalone player of a different brand and/or model myself so that we can test across as many different players as possible: I've been wanting to get one anyway, and I think it would make for more valuable tests than using the Xbox. Is your Sony player the X800? Also the donation link in your sig doesn't auto-fill your email address.Just a note... I don't think 29.97fps is legal for 2160p. Below is a table I saw in the v3.1 White Paper that can be downloaded for free. Make sure you are setting the MAXIMUM bitrate to 50Mbs, not the average bitrate.

There may be something extra that is needed in order for 2160p chapter skipping to work that TSMUXER doesn't provide. There's already been a report of an extension for HDR that I didn't know about, so it wouldn't surprise me. I'll have to do some comparisons of the original and TSMUXER files and see what I find.

My UHD-BD player is a Sony UBP-X800.