You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I used to work with Metadata Extractor in version 2.7.x and got QuickTime locations values.
I switched to the latest code from main and the locations aren't parsed anymore.
I traced the error to this line in QuickTimeMetadataReader, in the UserDataHandler function:
I created a PR that changes the type checking to use the int value instead of the converted string.
That should work across .NET versions and locales.
Can you please have a look? #433
Hey,
I used to work with Metadata Extractor in version 2.7.x and got QuickTime locations values.
I switched to the latest code from
main
and the locations aren't parsed anymore.I traced the error to this line in
![Image](https://private-user-images.githubusercontent.com/112394801/411319930-29e30542-2672-46b0-8013-824dffed7776.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MjgzOTEsIm5iZiI6MTczOTYyODA5MSwicGF0aCI6Ii8xMTIzOTQ4MDEvNDExMzE5OTMwLTI5ZTMwNTQyLTI2NzItNDZiMC04MDEzLTgyNGRmZmVkNzc3Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQxNDAxMzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zMTVmN2VhMmNiOTM1MDE3YjNhYTA4MTBkNjM5OGEwYWY0ZTBjOWI0MmM4ZmI5MDdlMTkzNDQzNTc1ODI5N2E1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.UEzjg5SiodYEeYNi23WO_PP8JChlRLNG-aBQctB0fu8)
QuickTimeMetadataReader
, in theUserDataHandler
function:It's trying to read the "type" as a string and it comes out as
"©xyz"
. The code is expecting?xyz
.The binary value is 0xa978797a and the
0xa9
byte is the culprit. Since it's defined "outside of the ASCII" range, it gets interpreted differently in some cases.I'm not sure if my locale (en-GB) or switching from .NET framework to .NET 7 cause this, but at least some users beside me are going to experience it.
The text was updated successfully, but these errors were encountered: