NotePerformer vs Other String Libraries — What Is the Difference?
So far, we have looked at the underlying concepts and mechanisms of NotePerformer.
But in actual music production, how does it differ from other string libraries?
Here, I would like to organize and clarify these differences.
Broad Categories of String Libraries
Modern string libraries can be broadly divided into three categories:
- Sample-based libraries (MSS / TSS / LASS, etc.)
- Modeling-based instruments (SCES / SWAM, etc.)
- Score-interpretation systems (NotePerformer)
Each takes a fundamentally different approach in terms of where music is actually “created.”
Sample-Based Libraries
Sample-based libraries such as MSS, TSS, and LASS are built on recorded audio samples.
Since they are driven by MIDI data, elements such as
- timing
- dynamics
- articulation
must be carefully shaped by the user.
Although automation features have improved in recent years, they are essentially tools for “constructing a performance.”
Modeling-Based Instruments
Modeling-based instruments such as SCES and SWAM generate sound in real time.
This allows continuous control over elements such as
- vibrato
- bowing
- note attack
resulting in a very high level of expressiveness.
However, this also means that the user is required to actively “perform” the music.
In that sense, they are closer to instruments than to conventional sound libraries.
The Position of NotePerformer
NotePerformer occupies a different position from both of these approaches.
It neither relies on detailed MIDI programming nor on real-time performance input.
Instead, it analyzes the score itself and constructs the music from it.
In other words,
- Sample-based libraries → create performances
- Modeling-based instruments → create sound
- NotePerformer → interpret music
his is the fundamental difference.
The Role of Lookahead
An important point here is the role of lookahead.
Although it may appear to be the same “lookahead” function, its purpose differs significantly depending on the type of library.
For example:
- In sample-based libraries (such as TSS), it is mainly used to compensate for legato latency
- In modeling systems, it functions as an internal process to maintain continuity of performance
In contrast, in NotePerformer, lookahead is used to determine aspects of musical structure itself, such as:
- the direction of a phrase
- points of natural resolution
- the relative importance of voices
In other words,
“Even though it is called lookahead, its role is fundamentally different.”
How to Use Them in Practice
In actual production work, it is important to choose the appropriate tool depending on the goal.
For example:
- To understand the structure of a score → NotePerformer
- To shape detailed and realistic string expression → SCES / SWAM
- To work within a conventional flow such as CC Control → MSS / TSS
The appropriate sound source will vary depending on the purpose. Therefore, it is easier to think of these as differences in roles, rather than superiority or inferiority.
Conclusion
NotePerformer is not a tool for “creating performances.”
Rather, it is better understood as “a system that interprets music.”
In this respect, NotePerformer is in a different position from conventional string instruments.
In this respect, it occupies a fundamentally different position from conventional string libraries.
In the next article, I will take a closer look at how NotePerformer actually produces its sound, based on these differences.
Japanese version is abailable here.