# ComParser network file 'bass1.network'  demonstrating failure of recognition.
# Learns only the 'bright sounding' scale that starts on the A string. When the
# 'darker sounding' scale that starts on the E string is presented, it may not 
# be fully recognised.

# Low feature vector rate will suffice for electric bass guitar.
fps=21.5332

#nodename: [response]
#           filename

0:
            bass_hi.aiff
1:

########################################################################
#
# In a network file, empty lines and lines starting with a # character 
# are ignored.
# The first line not starting with a # should specify the number
# of feature vectors per second ('fps') during analysis, which also
# affects the base frequency of the spectral analysis.
# Some possible 'fps' and 'sr' (samplerate) combinations are:
#
# fps= 5.3833 : sr=11025
# fps=10.7666 : sr=11025 | sr=22050
# fps=21.5332 : sr=11025 | sr=22050 | sr=44100 <-- best for bass guitar.
# fps=43.0664 :            sr=22050 | sr=44100 <-- seems best for violin
# fps=86.1328 :                       sr=44100     (then bfq=86.1328 Hz).
#
# but one may invent others, based on 8, 16, etc. kHz samplerates.
#
# After 'fps', node lines and avalanche lines may appear. One must always
# start and end a network with a node. The first node must be numbered 0.
# Node numbers must increment, not skipping any natural number.
# Between nodes, one or more, but at least one, avalanche must be present.
# A node line starts with a node number followed by a colon, optionally 
# followed by a series of rew decimal midibytes.
# A avalanche line starts with one ore more horizontal whitespace characters 
# followed by a pathname relative to the executable, optionally followed 
# by starttime and endtime.
#
# ALERT: For the MIDI sequences, running status is not supported yet!
#
###########################################################################