PurrFX project update 9

Project status overview as of August 26, 2020.

Commits: August 26, 2020.

It is necessary to make sure that no existing NSF file is required to generate sound. So I made a simple but sufficient ready-to-use NSF file stored right inside the PurrFX library. Remember the 4th update in which we made NSF files in the HEX editor? It was exercise for what we did today.
 
In fact, the PurrFX framework is ready for organizing an audio stream based on any desired set of input data. This is very simple:
1. The audio library requires a portion of the sound and refers to your program;
2. Your program refers to one of the implementations of CNes (for example CNesGme);
3. CNesGme starts the emulation process and, as necessary, refers to CFrameDataProducer implementations (for example CFrameDataFileReader).
 
This process can be represented in the form of this diagram:

 
There are still lack of high-level classes to create the required set of frame data, but nevertheless the scheme is already usable.


Related information:
http://obelisk.me.uk/6502/reference.html

 

 

Comments

Post a Comment