Solo: A Star Wars Story Segment Map

[theshadraq]

I have the Walmart BluRay of Solo: A Star Wars Story. There are 3 files that have the correct runtime, all with different segment Maps.

Has anyone ripped this yet? Any idea what the correct segment mapping is?

Thanks,
Shadraq

[Woodstock]

Disney release. The play list with 800 in its name is English. 801 and 802 are French and Spanish (may be the other way around).

Only difference is the titles and credits, which are printed in the appropriate language.

[rivey]

I can confirm Woodstocks response. I just ripped the BluRay and UHD versions Wednesday and that is exactly what I found also.

[theshadraq]

Thank you. Appreciate the timely response.

[Heliosone]

UHD rip fails instantly with the following error:
Saving 1 titles into directory W:/Movies using profile 'AAC-stereo' from file 'C:\Program Files (x86)\MakeMKV/appdata.tar:aac-st.mmcp.xml'
DEBUG: Code 1551 at @i4{@\MO3SC>q8/Q>M'\t:29395172
DEBUG: Code 1599 at @i4{@\MO3SC>q8/Q>M'\t:213131525
DEBUG: Code 0 at @i4{@\MO3SC>q8/Q>M'\t:213131824
DEBUG: Code 0 at k%b$mnt,in%nSSf:3K-<:29393884
DEBUG: Code 0 at %8fGpH0QOCGc~ K:121264441
DEBUG: Code 0 at %8fGpH0QOCGc~ K:213133020
DEBUG: Code 4 at W9aA-J[o$f3zN?GxD':121263498
DEBUG: Code 1 at W9aA-J[o$f3zN?GxD':29395402
LIBMKV_TRACE: Failed to attach audio mix filter on top of (78:A_EAC3->AAC)
DEBUG: Code 1 at W9aA-J[o$f3zN?GxD':29396805
DEBUG: Code 0 at W9aA-J[o$f3zN?GxD':121266902
DEBUG: Code 0 at W9aA-J[o$f3zN?GxD':121269133
DEBUG: Code 0 at W9aA-J[o$f3zN?GxD':121269754
Failed to save title 21 to file W:/Movies/Solo_ A Star Wars Story (4K).mkv
0 titles saved, 1 failed

[Woodstock]

Are you running v1.12.3 of MakeMKV?

If so, you might want to start here: Avoid v1.12.3 (opinion)

[spinkham]

For anyone else who comes here looking for Code 1599, seems to be an issue with the AAC transcoding. As soon as I switched to a non-AAC profile, the error went away.

[Woodstock]

For anyone else who comes here looking for Code 1599, seems to be an issue with the AAC transcoding. As soon as I switched to a non-AAC profile, the error went away.

Are you still running version 1.12 all these years later?