Fix custom instruments getting empty name and ID #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites
Closes #8
Information
As per issue #8, during the parsing of an NBS file, custom instruments are generated that contain empty
meta.name
(empty string) andid
(NaN
) attributes. This results from the name string being read from the file, but not actually stored in thename
attribute, which receives the default value""
from thedefaultInstrumentOptions
object.Additionally, as the first parameter to the
Instrument
object constructor is passed the return value ofNumber.parseInt
called on the parsed string, which always results inNaN
. As a result, this value is assigned to all custom instruments'id
attributes.This pull request fixes the issue by calculating the custom instrument's ID from the
firstCustomIndex
property and the index of the current instrument being read, and assigning the parsed name string to themeta.name
property.