ISO9660 timezone byte not being used #431

Closed
opened 2026-01-29 15:18:36 +00:00 by claunia · 0 comments
Owner

Originally created by @mnadareski on GitHub (Jun 25, 2020).

Prerequisites

  • Are you running the latest version?
  • Can you reproduce the problem in the debug version?

Check and fill as appropriate:

  • I was running Aaru under Windows 10...
  • ...using .NET Core 3.1...
  • ...in 64-bit

Description

In the DateHandlers code, the last byte of the PVD is taken in but never used. Instead, it sets DateTimeKind.Unspecified. Of note, the timzone byte is 00 for UTC then adds or subtracts byte per 15 minutes of timezone offset, making UTC +00:1501and UTC -00:15FF`.

Exact command line used:

Aaru media dump E: B:\_TEMP\VS2.aif

Expected behavior:

PVD datetimes in the CICM sidecar to include timezone offset information

Actual behavior:

PVD datetimes in the CICM sidecar are correct, but lacking timezone offset information

Originally created by @mnadareski on GitHub (Jun 25, 2020). ### Prerequisites * [x] Are you running the latest version? * [x] Can you reproduce the problem in the debug version? ### Check and fill as appropriate: * [x] I was running Aaru under Windows 10... * [x] ...using .NET Core 3.1... * [x] ...in 64-bit ### Description In the `DateHandlers` code, the last byte of the PVD is taken in but never used. Instead, it sets `DateTimeKind.Unspecified`. Of note, the timzone byte is `00` for UTC then adds or subtracts ` byte per 15 minutes of timezone offset, making UTC +00:15 `01` and UTC -00:15 `FF`. ### Exact command line used: `Aaru media dump E: B:\_TEMP\VS2.aif` ### Expected behavior: PVD datetimes in the CICM sidecar to include timezone offset information ### Actual behavior: PVD datetimes in the CICM sidecar are correct, but lacking timezone offset information
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#431