-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extracting sensitivity and gain for SM4 #331
Labels
Comments
Yeah so, I looked at this, I'm part way through extracting the values, but there are still some questions. There are also different values in the so from what I can see there is:
|
atruskie
added a commit
that referenced
this issue
Mar 9, 2023
- Adds high precision timer support for SM4s. Fixes #330 - Adds support for microphone sensitivity reporting for Sm4s partially addressed #331 - Adds make, model, and sensor name for SM4. Partially addresses #296 - BREAKING change: resets channel identifier to match industry standard. i.e. the first channel is 0 (left). We were counting from 1 which is not the most popular format: https://en.wikipedia.org/wiki/Surround_sound#Channel_notation - BREAKING: Fixed a bug with the Location parsing code! Coordinates from WA sensors will now report the correct hemisphere
atruskie
added a commit
that referenced
this issue
Apr 19, 2023
This is a huge change set - everything got mixed together. We now decode the schedule that's embedded in WA files and we've added a `metadata dump` command to show the huge amount of information that's been added. Fixes #331 - now reports gain and sensitivity in metadata command Fixes #350 - now has a metadata dump command Other noteworthy changes: - Added `metadata show` as an alias for `metadata` since `metadata` grew from a command itself into a parent of commands. `show` as a subcommand is more consistent. - Added a new text-base generic object formatter for the default and compact formats - both metadata show and dump commands have been updated to use this format - the default is now prettier and formats subobjects recursively in the same format - the compact format is now genericly implemented and consistent in it's implementation - Reverse engineered the WA schedule file formats, documented the format, and wrote parsers for those files!! - There are few fields for which their purpose could not be guessed at - Added a source generator that reads out fixture data file and generates named constants to use in tests - The WAMD metadata extractor now decodes the DevParams field (the schedule) - Removed the --no-checksum option from global CLI options and instead placed it only on metadata/metadata show commands - Made printing file paths more consistent in all metadata and fix commands - BREAKING: changed `SourcePath` to just `Path` in metadata commands (the shorter name is simpler and more consistent with other terminology used in EMU) - Added a new metadata extractor interface `IRawMetadataOperation` that support the dump command by reading primitive metadata values and does not attempt to merge them into a consistent `Recording` structure - change the ansi output renderer to by default render to a test "console" that has infinite width
Available in the 7.0.0 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SM4 recorders save information about the gain
it would be good to extract this information.
Pelase note that:
the value 42.2 is similar to the sum of the Gain (16) and Preamp (26) values that can be seen when opening the file with Kaleidoscope. But I cannot tell whether that's just a coincidence or what the 0.2 difference mean
In the first part of the wamd chunk there is a value of 45.2 that could also refer to a gain
According to the manufacturer, the sensitivity for the SM4 is -35±4dB (0dB=1V/Pa at 1kHz). I cannot see it in the wamd chunk.
As far as I know the Song Meters have both a manual and a digital gain. But I don't know what the values in the wamd chunk refer to.
Thanks
The text was updated successfully, but these errors were encountered: