The release notes mention fixing a transcode issue where things have long file names. I’m not aware of a way to see the bug details…
Can anyone shed some light on the specifics of the bug? I just realized that some files I have been running into issues being played back on certain clients…I think they do all have longer file names, and as a result probably long-ish file paths (although none should be longer then MAX_PATH since Explorer still has issues with it then AFAIK). I’ll install and test it, but it’d be helpful to know if this is explicitly expected to fix the issue I’m seeing.
Thanks!
@MasterChiefmas said:
The release notes mention fixing a transcode issue where things have long file names. I’m not aware of a way to see the bug details…
It only applies on Windows, when the Windows user account has a long name and/or doesn’t follow the legacy Windows restriction of ‘no space characters’ and ‘no special characters’.
This is AFAIK not connected to the issue when you have very long folder paths to your media files. That is still an issue when you are exceeding the 255 character limit for folder and file names, but is is more rooted in Windows and/or Python and cannot be solved easily.
Oh…reading comprehension fail on my part. DOH
