INTERACT FORUM

Antivirus?  What are you using?  Did you configure Windows Defender?

This happens all the time in portions of subtitles that are in italics.

To get another view of what is going on:
Do a binary side-by-side comparison of the contents of the two files.  For example, the program Beyond Compare can easily do this.  BC shows a line-by-line view using its intelligent alignment algorithms which are pretty effective at detecting gaps or large sections of differences.

The file compare allows you to see if file differences are restricted to the header section, the music section, or appear in both.

Thanks for the tip, I will take a look at Beyond Compare. It would be interesting to see which parts of the files are different.

Do you have two copies of the same album/track on the source NAS which were ripped with different FLAC compression ratios, or contain different embedded images?

No, there is only one version of the song on my NAS.

With the hashes being different, that means the files are different to each other. The question now becomes why... is it metadata? Embedded artwork? Or something else? More importantly does it happen again if you straight copy the file from the NAS to the other drive? If it only happens once maybe it's a fluke but if it happens again that's a brain scratcher.

The file was copied twice. Once when the process was paused and then resumed later, and once to check what might have caused the difference in file size between the first copy and the original. I'm not sure what you mean by straight copy, but I guess it would be what I did the second time?

I have tried to recreate this by doing another copy process, pausing it for several hours, and then resuming. This issue did not occur then. We can call it a fluke – but I think it's an interesting one. 

Width >= 3840 || Height >= 2160 -> 4K

I've noticed some of my 4k videos with dimensions like 3836x1602 or 3832x2152 that seem to just miss MC's definition of 4k. They end up with the 1080p icon vs. the 4k icon.

Another video with dimensions = 3590x2160 gets the 4k icon, so the rule above must be an "OR" rule.

Can that definition be loosened by a few pixels? Maybe make the width rule Width >= 3830 or something like that?

Sorry folks I have sorted the issue, "A trap for young players".....

When I was first testing the new manual stretch (weeks ago) just from the keyboard before we intergrated it into the system, JRVR Profiles > Output > Auto/toggle- stretch on - off.... On two 70mm films I left them on Default Profile by mistake rather than resetting them to Auto. Weeks ago I didnt know they should be on Auto as I hadent set that up back then. So those two 70mm titles were locked on Default Profile which is 16.9, activating stretch when locked on Defauly Profile is a waste of time as its locked!
A trap for young players, but now it cant happen since I no longer are testing stretch. (see image)

The difference in size is more like a lower resolution image file.

I have tested the typical cropping and stretching settings and they work fine for me. You should always first verify your profile is actually active. Any active profiles will be listed in the JRVR OSD as well (Ctrl-J).

I originally thought the same thing too, that it could be a difference in FLAC compression, but with the changes being within 800kb I thought that might be too small of a change to account for a different compression level.

With the hashes being different, that means the files are different to each other. The question now becomes why... is it metadata? Embedded artwork? Or something else? More importantly does it happen again if you straight copy the file from the NAS to the other drive? If it only happens once maybe it's a fluke but if it happens again that's a brain scratcher.

Beyond Compare is excellent for doing binary analysis of multiple files. You can also open both files in a hex editor and do a comparison between them to see the differences.

Try disabling auto-import and see if it stops crashing. If so, you likely have bad files and would need to enable logging, reproduce a crash, then look towards the end of the log to see what file(s) are causing it.

MC 32 has tended to crash more on my Windows 11-64 system than prior versions. Just had another crash after adding albums that the program read into its database. MC just blinks out: no error catching.