Nintendo 3DS Camera - Revision history

EvilFlight: Clarify Unique ID

2022-11-19T22:50:39Z

Clarify Unique ID

← Older revision		Revision as of 01:50, 20 November 2022
Line 91:		Line 91:
	\| 0x4		\| 0x4
	\| u32		\| u32
	\| ~~Unknown. Seems to some sort~~ of ~~system ID that changes when the system is formatted~~.		\| This is the lower word of [[Cfg:GenHashConsoleUnique]].
	\|-		\|-
	\| 0x1c		\| 0x1c

Tonyzamboney: /* Maker Note */ "System format timestamp" is not a timestamp

2022-11-19T20:19:57Z

Maker Note: "System format timestamp" is not a timestamp

← Older revision		Revision as of 23:19, 19 November 2022
Line 91:		Line 91:
	\| 0x4		\| 0x4
	\| u32		\| u32
	\| ~~System format timestamp~~		\| Unknown. Seems to some sort of system ID that changes when the system is formatted.
	\|-		\|-
	\| 0x1c		\| 0x1c
Line 120:		Line 120:

	The photo timestamp is represented by the number of seconds that had passed since the beginning of the year 2000 in the photographer's 3DS's time zone.		The photo timestamp is represented by the number of seconds that had passed since the beginning of the year 2000 in the photographer's 3DS's time zone.

	The system format timestamp is a UTC timestamp, in milliseconds, of when the photographer's 3DS system had last been formatted. Despite this value's potential usefulness for preventing previously-formatted photos from being viewed, it does not seem to be used.

	The left translation number indicates how many pixels to move the left-eye image to the left before scaling it to fit the entire image on-screen without stretching it. It inversely affects the positions of the right-eye image and the 3D Focus slider. The 3DS Camera clamps this value to prevent the image from moving off-screen. This value is zero in 2D photos, though 3D photos can use a value of zero as well.		The left translation number indicates how many pixels to move the left-eye image to the left before scaling it to fit the entire image on-screen without stretching it. It inversely affects the positions of the right-eye image and the 3D Focus slider. The 3DS Camera clamps this value to prevent the image from moving off-screen. This value is zero in 2D photos, though 3D photos can use a value of zero as well.

Tonyzamboney: Corrected some maker note info

2022-11-07T20:51:40Z

Corrected some maker note info

← Older revision		Revision as of 23:51, 7 November 2022
Line 45:		Line 45:
	The first field, which is identified by tag <code>0x1100</code>, is 80 bytes long. The meanings of its contents are not known, but the first byte Seems to always have a value of 1. The remaining bytes always seem to have values of zero, unless the photo used a sepia filter, in which case bytes <code>0x8</code>-<code>0x1a</code> (inclusive) are set. This field can be excluded from the maker note without invalidating the 3DS Camera maker note.		The first field, which is identified by tag <code>0x1100</code>, is 80 bytes long. The meanings of its contents are not known, but the first byte Seems to always have a value of 1. The remaining bytes always seem to have values of zero, unless the photo used a sepia filter, in which case bytes <code>0x8</code>-<code>0x1a</code> (inclusive) are set. This field can be excluded from the maker note without invalidating the 3DS Camera maker note.

	The second field uses tag <code>0x1101</code>. It is 64 bytes long, although its length can be reduced to as few as 20 bytes without issue~~. The first four bytes must spell "3DS1" in ASCII (with no null terminator)~~.		The second field uses tag <code>0x1101</code>. It is 64 bytes long, although its length can be reduced to as few as 21 bytes without issue.
	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
	\|-		\|-
Line 59:		Line 59:
	\|-		\|-
	\| 0x4		\| 0x4
	\| ~~0x1, 0x2, 0x3, or~~ 0x4		\| 0x4
	\| unknown		\| unknown
	\| Possibly a version number. Seems to always be 1 or 2.		\| Possibly a version number. Seems to always be 1 or 2.
Line 69:		Line 69:
	\|-		\|-
	\| 0xc		\| 0xc
	\| ~~0x8~~		\| 0x4
			\| unknown
			\| Unknown. Seems to always be 0.
			\|-
			\| 0x10
			\| 0x4
	\| unknown		\| unknown
	\| Unknown.		\| Unknown. Seems to always be 516.
	\|-		\|-
	\| 0x14		\| 0x14
Line 78:		Line 83:
	\| Unknown. Seems to always be 20, but any non-zero value seems acceptable. Required.		\| Unknown. Seems to always be 20, but any non-zero value seems acceptable. Required.
	\|-		\|-
	\| ~~0x18~~		\| 0x15
	\| 0x3		\| 0x3
	\| unknown		\| unknown
	\| Unknown. Seems to always be 0.		\| Unknown. Seems to always be 0.
	\|-		\|-
	\| ~~0x1c~~		\| 0x18
	\| 0x4		\| 0x4
	\| u32		\| u32
	\| System format timestamp		\| System format timestamp
	\|-		\|-
	\| ~~0x20~~		\| 0x1c
	\| 0xc		\| 0xc
	\| unknown		\| unknown
	\| Unknown. Seems to always be 0.		\| Unknown. Seems to always be 0.
	\|-		\|-
	\| ~~0x2c~~		\| 0x28
	\| 0x4		\| 0x4
	\| f32		\| f32
	\| Left translation		\| Left translation
	\|-		\|-
	\| ~~0x30~~		\| 0x2c
	\| 0x4		\| 0x4
	\| unknown		\| unknown
	\| Unknown. Seems to always be 0.		\| Unknown. Seems to always be 0.
	\|-		\|-
	\| ~~0x34~~		\| 0x30
	\| 0x4		\| 0x4
	\| u32		\| u32
	\| Photo filter(s)		\| Photo filter(s)
	\|-		\|-
	\| ~~0x38~~		\| 0x34
	\| 0xc		\| 0xc
	\| unknown		\| unknown
Line 114:		Line 119:
	\|}		\|}

	The photo timestamp is represented by the number of seconds that had passed since the beginning of the year 2000 in the photographer's time zone.		The photo timestamp is represented by the number of seconds that had passed since the beginning of the year 2000 in the photographer's 3DS's time zone.

	The system format timestamp is a UTC timestamp, in milliseconds, of when the photographer's 3DS system had last been formatted. Despite this value's potential usefulness for preventing previously-formatted photos from being viewed, it does not seem to be used.		The system format timestamp is a UTC timestamp, in milliseconds, of when the photographer's 3DS system had last been formatted. Despite this value's potential usefulness for preventing previously-formatted photos from being viewed, it does not seem to be used.

Tonyzamboney at 21:39, 7 November 2022

2022-11-07T20:39:28Z

← Older revision		Revision as of 23:39, 7 November 2022
Line 34:		Line 34:
	* Additionally, certain features are only available for valid Nintendo 3DS photographs:		* Additionally, certain features are only available for valid Nintendo 3DS photographs:
	** The left-eye image's Exif metadata must specify a camera make of <code>Nintendo</code>, a camera model of <code>Nintendo 3DS</code>, and a software name of <code>00204</code>.		** The left-eye image's Exif metadata must specify a camera make of <code>Nintendo</code>, a camera model of <code>Nintendo 3DS</code>, and a software name of <code>00204</code>.
	** The zoom feature is only available when viewing any image with an aspect ratio which is no more horizontally dominant than 4:3. For example, a 480x480 image will be zoomable due aspect ratio, but a 480x288 image will not be zoomable because its 5:3 aspect ratio makes the image too wide relative to its height. All zoomable images are initially zoomed in when viewed in the photo gallery.		** The zoom feature is only available when viewing any image with an aspect ratio which is no more horizontally dominant than 4:3. For example, a 480x480 image will be zoomable due to its aspect ratio, but a 480x288 image will not be zoomable because its 5:3 aspect ratio makes the image too wide relative to its height. All zoomable images are initially zoomed in when viewed in the photo gallery.
	** Each 3D image features a faded black border and can be manipulated with the 3D Focus slider, but only if the image is at least 480 pixels wide and contains a valid 3DS Camera maker note in the left-eye image's Exif metadata.		** Each 3D image features a faded black border and can be manipulated with the 3D Focus slider, but only if the image is at least 480 pixels wide and contains a valid 3DS Camera maker note in the left-eye image's Exif metadata.

Tonyzamboney: Image gallery requirements and maker note explanation

2022-11-07T20:38:28Z

Image gallery requirements and maker note explanation

← Older revision		Revision as of 23:38, 7 November 2022
Line 27:		Line 27:

	Put the file in DCIM\xxxNINxx		Put the file in DCIM\xxxNINxx
			== Image Requirements ==

			The photo gallery implements various restrictions on its images:

			* A 4:3 image must have an image resolution of at least 160x120 to appear in the photo gallery. (Minimum image resolutions for other aspect ratios are currently unknown, as are maximum image resolutions for any aspect ratio.)
			* Additionally, certain features are only available for valid Nintendo 3DS photographs:
			** The left-eye image's Exif metadata must specify a camera make of <code>Nintendo</code>, a camera model of <code>Nintendo 3DS</code>, and a software name of <code>00204</code>.
			** The zoom feature is only available when viewing any image with an aspect ratio which is no more horizontally dominant than 4:3. For example, a 480x480 image will be zoomable due aspect ratio, but a 480x288 image will not be zoomable because its 5:3 aspect ratio makes the image too wide relative to its height. All zoomable images are initially zoomed in when viewed in the photo gallery.
			** Each 3D image features a faded black border and can be manipulated with the 3D Focus slider, but only if the image is at least 480 pixels wide and contains a valid 3DS Camera maker note in the left-eye image's Exif metadata.

			== Maker Note ==

			Every Nintendo 3DS Camera photo contains a maker note in its Exif metadata. 3D images contain two maker notes - one for the left-eye image, and one for the right - but only the left-eye image's maker note is used. Two maker notes within the same 3D image may be identical to one another, but they are not guaranteed to be. The maker note of a 2D JPEG image seems to always contain an identical maker note to one of its respective 3D image's individual images, but which one it is identical to is not consistent.

			The maker note consists of two custom TIFF fields that both have a type of <code>UNDEFINED</code>. Regardless of the Exif metadata's endianness, which the TIFF fields must match, the fields' contents are encoded in little endian.

			The first field, which is identified by tag <code>0x1100</code>, is 80 bytes long. The meanings of its contents are not known, but the first byte Seems to always have a value of 1. The remaining bytes always seem to have values of zero, unless the photo used a sepia filter, in which case bytes <code>0x8</code>-<code>0x1a</code> (inclusive) are set. This field can be excluded from the maker note without invalidating the 3DS Camera maker note.

			The second field uses tag <code>0x1101</code>. It is 64 bytes long, although its length can be reduced to as few as 20 bytes without issue. The first four bytes must spell "3DS1" in ASCII (with no null terminator).
			{\| class="wikitable" border="1"
			\|-
			! Address
			! Size
			! Type
			! Description
			\|-
			\| 0x0
			\| 0x4
			\| char[4]
			\| Spells "3DS1" in ASCII. Required.
			\|-
			\| 0x4
			\| 0x1, 0x2, 0x3, or 0x4
			\| unknown
			\| Possibly a version number. Seems to always be 1 or 2.
			\|-
			\| 0x8
			\| 0x4
			\| u32
			\| Photo timestamp
			\|-
			\| 0xc
			\| 0x8
			\| unknown
			\| Unknown.
			\|-
			\| 0x14
			\| 0x1
			\| u8
			\| Unknown. Seems to always be 20, but any non-zero value seems acceptable. Required.
			\|-
			\| 0x18
			\| 0x3
			\| unknown
			\| Unknown. Seems to always be 0.
			\|-
			\| 0x1c
			\| 0x4
			\| u32
			\| System format timestamp
			\|-
			\| 0x20
			\| 0xc
			\| unknown
			\| Unknown. Seems to always be 0.
			\|-
			\| 0x2c
			\| 0x4
			\| f32
			\| Left translation
			\|-
			\| 0x30
			\| 0x4
			\| unknown
			\| Unknown. Seems to always be 0.
			\|-
			\| 0x34
			\| 0x4
			\| u32
			\| Photo filter(s)
			\|-
			\| 0x38
			\| 0xc
			\| unknown
			\| Unknown. Seems to always be 0.
			\|}

			The photo timestamp is represented by the number of seconds that had passed since the beginning of the year 2000 in the photographer's time zone.

			The system format timestamp is a UTC timestamp, in milliseconds, of when the photographer's 3DS system had last been formatted. Despite this value's potential usefulness for preventing previously-formatted photos from being viewed, it does not seem to be used.

			The left translation number indicates how many pixels to move the left-eye image to the left before scaling it to fit the entire image on-screen without stretching it. It inversely affects the positions of the right-eye image and the 3D Focus slider. The 3DS Camera clamps this value to prevent the image from moving off-screen. This value is zero in 2D photos, though 3D photos can use a value of zero as well.

			Take, for example, a 640x480 3DS photograph. The 3DS Camera will scale the photo down to 50% of its original size to fit the top 3DS screen, which is 240 pixels tall. This leaves a gap of 40 pixels on both the left and right sides of the image. If these gaps were resized to match the photo's original scale, which is twice as large as its on-screen scale, the gaps would be 80 pixels wide. As such, the left translation value can effectively range from +80.0, which will move the image to the left edge of the screen, to -80.0, which will move it to the right edge. Despite this range working as expected for an image of this size, the 3DS Camera's image gallery does not allow the user to move any photo to the very edge of the screen. For the example above, the maximum absolute value seems to be somewhere within the mid-to-low 50s.

			The left translation value can be changed by moving the 3D Focus slider while zoomed in, or by readjusting the photo's position while zoomed out. This will update the left translation value held in the left-eye image's maker note as well.

			The photo filter(s) value seems to specify information about photo filters that were applied to the image. Some filters seem to use the same values. When filters are not present, this value is 0.

Ryccardo: outdated picture

2016-04-23T14:32:08Z

outdated picture

← Older revision		Revision as of 18:32, 23 April 2016
Line 1:		Line 1:
	== Overview ==		== Overview ==
	[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot]]		[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot (pre 4.0-7)]]
	This application allows the user to ~~record/play videos and~~ take/view photos. The resolution of the top-screen on the 3DS is 400x240		This application allows the user to take/view photos and, since the 4.0.0-7 update, videos up to 10 minutes.

			The resolution of the top-screen on the 3DS is 400x240.

	== How to convert and split video.ext into 10 minute pieces ==		== How to convert and split video.ext into 10 minute pieces ==

Arizvisa at 06:37, 16 November 2014

2014-11-16T05:37:32Z

← Older revision		Revision as of 08:37, 16 November 2014
Line 5:		Line 5:
	== How to convert and split video.ext into 10 minute pieces ==		== How to convert and split video.ext into 10 minute pieces ==
	<code>		<code>
	ffmpeg -i video.ext -ss ~~600~~ -t 600 -y -r 24 -vsync 1 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -async 1 -ac 2 /DCIM/xxxNINxxx/HNI_%04d.AVI		ffmpeg -i video.ext -ss 0 -t 600 -y -r 24 -vsync 1 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -async 1 -ac 2 /DCIM/xxxNINxxx/HNI_%04d.AVI
	</code>		</code>

Arizvisa: Updated the ffmpeg commands with the ones I decided on in my shellscript

2014-11-15T15:54:57Z

Updated the ffmpeg commands with the ones I decided on in my shellscript

← Older revision		Revision as of 18:54, 15 November 2014
Line 1:		Line 1:
	== Overview ==		== Overview ==
	[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot]]		[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot]]
	This application allows the user to record/play videos and take/view photos.		This application allows the user to record/play videos and take/view photos. The resolution of the top-screen on the 3DS is 400x240

	== How to split ~~a movie file~~ into 10 minute pieces ==		== How to convert and split video.ext into 10 minute pieces ==
	<code>		<code>
	ffmpeg -i video.ext -~~acodec copy~~ -vcodec ~~copy~~ -~~f segment~~ -~~segment_time 600~~ -~~map 0~~ -~~an HNI_1~~%~~03d~~.AVI		ffmpeg -i video.ext -ss 600 -t 600 -y -r 24 -vsync 1 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -async 1 -ac 2 /DCIM/xxxNINxxx/HNI_%04d.AVI
	</code>		</code>

	== How to convert 2D Video for 3DS ==		== How to convert 2D Video for 3DS ==
	<code>		<code>
	ffmpeg -i video.ext -~~s 480x240~~ -~~aspect 2:~~1 ~~-r 20~~ -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -ac 1 /DCIM/~~xxxNINxx~~/HNI_nnnn.~~avi -t 10~~		ffmpeg -i video.ext -r 24 -vsync 1 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -async 1 -ac 2 -vf scale=min(400\\,240*a):-1,pad=400:240:abs(ow-iw)/2:abs(oh-ih)/2 /DCIM/xxxNINxxx/HNI_nnnn.AVI
	</code>		</code>

Arizvisa: Added example shellscript to split a file into 10 minute intervals.

2014-11-15T10:08:19Z

Added example shellscript to split a file into 10 minute intervals.

← Older revision		Revision as of 13:08, 15 November 2014
Line 2:		Line 2:
	[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot]]		[[File:Nintendo 3DS Camera scnshot.png\|thumb\|right\|Nintendo 3DS Camera Screenshot]]
	This application allows the user to record/play videos and take/view photos.		This application allows the user to record/play videos and take/view photos.

			== How to split a movie file into 10 minute pieces ==
			<code>
			ffmpeg -i video.ext -acodec copy -vcodec copy -f segment -segment_time 600 -map 0 -an HNI_1%03d.AVI
			</code>

	== How to convert 2D Video for 3DS ==		== How to convert 2D Video for 3DS ==

Arizvisa: /* How to convert 2D Video for 3DS */

2014-11-15T01:04:55Z

How to convert 2D Video for 3DS

← Older revision		Revision as of 04:04, 15 November 2014
Line 4:		Line 4:

	== How to convert 2D Video for 3DS ==		== How to convert 2D Video for 3DS ==
	~~single screen~~

	<code>		<code>
	ffmpeg -i video.ext -s 480x240 -aspect 2:1 -r 20 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -ac 1 /DCIM/xxxNINxx/HNI_nnnn.avi -t 10		ffmpeg -i video.ext -s 480x240 -aspect 2:1 -r 20 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -ac 1 /DCIM/xxxNINxx/HNI_nnnn.avi -t 10
	~~</code>~~

	~~double screen~~

	~~<code>~~
	~~ffmpeg -i video.ext -s 960x240 -aspect 2:1 -r 20 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -ac 1 /DCIM/xxxNINxx/HNI_nnnn.avi -t 10~~
	</code>		</code>