Please provide the following info (tick the boxes after creating this topic): Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
2.1.0
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Issue Description
When we checked the raw format file saved with dwSensorSerializer_serializeCameraFrameAsync () with a binary editor,
Data about cameras and rigs existed between the starting address and the image data storage address (000039B0).
Is it correct to understand that the data from the starting address to the image data storage address is a magic number?
We are aware that if there is a problem with the magic number data of the raw file, an error will occur in the image reading.
Is it possible to provide a memory map from the first address to the image data storage address for analysis?
Means you have issue with replaying the recorded RAW file? Is the file recorded and used in different DW version? What error is noticed?
So you plan to to read like a byte memory from the raw image file?
Could you share tool details and how you verified?
Are you asking if raw header is same as magic number?
Can you clarify above queries for better guidance.
Means you have issue with replaying the recorded RAW file?
No, there is nothing wrong with the recorded Raw file itself.
So you plan to to read like a byte memory from the raw image file?
We are planning to arrange continuous frame images in raw format and play them back as raw videos.
When we played back a continuous frame image in RAW format, we got an error saying “Driveworks exception thrown: DW_FILE_INVALID: CameraVirtual: video file has wrong magic number”.
When we checked the raw file generated by dwSensorSerializer_serializeCameraFrameAsync() with a binary editor,
There seemed to be a specific format in the header.
Could you share tool details and how you verified?
We opened the raw file in a binary editor (HxD) and checked it.
Attach a reference image.
Are you asking if raw header is same as magic number?
From the contents of the log, it was interpreted that it was called a magic number.
Should we call it a raw header?
Dear @SivaRamaKrishnaNV
The replayed environment for RAW files is planned to be DW5.10, but we are considering using DW5.14 or later.
For recording, we also plan to replayed RAW files recorded without using the DW SDK.
Since we replayed a raw file that we created without using DW, we think we got a “wrong magic number” error.
If the “wrong magic number” error is determined by the raw header,
We expect that editing the raw header will resolve the error.
Therefore, we ported the header of a raw file created using DW to a raw file created without DW, and replayed.
As a result, the “wrong magic number” error no longer occurred, but the following error occurred:
SIPLClient: checkFrameDiscontinuity, Incorrect frame sequence, current: 0, last: 52
SIPLNotifier: Notification received from pipeline index:0 of type: NOTIF_ERROR_ISP_PROCESSING_FAILURE
We want to solve the above error.
It is assumed that if the format of the raw header is known, this error can be solved.
