Bouke Posted December 29, 2025 Report Posted December 29, 2025 Got three files from the onboard recorders of two MTP61 and one MTP60. Metadata is strange. The file creation time suggests a proper setup, but one of the recorders is set to jan 1 2000 (So it was reset on the day of the recorder I presume.) Then, two of the three (Including the fresh resetted one) have BWF timestamps that go over 24 hour. (So instead of expected 16:00:00:00 they are at 40:00:00:00) This I have never seen before. Could have been intentionally to be able to run over midnight, but that's not the case. If I deduct 24 hours they are in sync (ish...) Metadata is very sparse, timestamp is only in the BEXT chunk, iXML has a tiny bit of more info, but not the timestamp. Anyone got an idea what this is about? Quote
humbuk Posted December 29, 2025 Report Posted December 29, 2025 The date is reset after removing the batteries for a long period of time. Quote
Bouke Posted December 29, 2025 Author Report Posted December 29, 2025 Ah, but then the question, how come that it isn't upping while the timestamp has ran over midnight? And, are there more recorders who do not fall back to zero hour (or aka timestamp 1) when running over midnight? That would be kinda logical. (QuickTime used to have an option for TC to be able to run over midnight, and I don't see an issue to write TC has DD HH MM SS FF, where FF also could be samples in case of sound) Quote
fieldsound Posted December 30, 2025 Report Posted December 30, 2025 The MTP60/61 have a known bug wherein the user bits do not jam with the timecode when using a Tentacle sync box to sync via Bluetooth. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.