Can I ask something? What determines the different colors the notes will have during playback? Are they preset or do they vary according to something? If you have the time and dedication, a full list would be useful, but not necessary.
Can I ask something? What determines the different colors the notes will have during playback? Are they preset or do they vary according to something? If you have the time and dedication, a full list would be useful, but not necessary.
Sure.
General:
Width = volume
Brightness = white or black key
2A03/MMC5
Pulse: red for 12.5% duty cycle, yellow for 25% duty cycle, purple for 50% duty cycle.
Triangle: white
Noise: Blue to cyan to green to green-yellow for random noise, red to orange to yellow for periodic noise.
DPCM: Random shades of blue/purple depending on the memory address of the DPCM sample.
VRC6
Pulse: Depends on duty cycle setting: 01234567 (ranging from 6.25% to 50% duty cycle)
Sawtooth: pink
VRC7
All: Colour is a function of the current frequency modulation envelope's volume - maximum volume gives you red, minimum volume (a sine wave) gives you sine wave is magenta. In addition, notes are desaturated towards gray the higher their feedback is. Other properties that could affect VRC7 timbre (mults, wave rectification, etc) are not tracked. As a result, two of the default patches look the same despite sounding different, but usually you see what you need to.
FDS/N163
All: Triangle wave is white, sine wave is magenta. If Synthesia thinks the wave is kinda like a pulse wave if you squint the right way, it colours it that way in a manner similar to VRC6 from hot pink to purple, with increasing desaturation towards gray the more it's uncertain. If Synthesia is convinced your waveform would not produce any tone it colours it black. Finally, if it's none of the above it's coloured pink.
One request: since NSFplay is open-sourced, please release the code. I know it's not obligatory for Apache, but still, it'd be nice.
EDIT: What determines colours for VRC7?
_______________________
"im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to." -omgdonut
[quote=poodlecock]One request: since NSFplay is open-sourced, please release the code. I know it's not obligatory for Apache, but still, it'd be nice.[/quote]
I did release the source code - read the first post again. (It's a diff against nsfplay 2.3's source code base.)
[quote]EDIT: What determines colours for VRC7?[/quote]
Also covered in the first post.
Just came across this. Great job, Pantashu! I do have a request though. It's not going to kill me though if it can't be done.
My request is to clear the synthesia visualizer when you either stop or play a new track in the NSF file.
Maybe it would be possible to add support for the watchdog timer? It's used in a few NSFs like Countdown.
Just came across this. Great job, Pantashu! I do have a request though. It's not going to kill me though if it can't be done.
My request is to clear the synthesia visualizer when you either stop or play a new track in the NSF file.
LOL pantashu
I actually want this myself because when recording in it I have to close and re-open the program. I'll add it to my to-do list.
Doommaster1994 wrote:
Maybe it would be possible to add support for the watchdog timer? It's used in a few NSFs like Countdown.
I don't know 100% what it is, but I know it's used in only a few NSFs. Sesame Street Countdown is one of them. It's some kind of timer that's used in order to play the NSF properly. Gil_Galad would know, as he's ripped them.
I don't know 100% what it is, but I know it's used in only a few NSFs. Sesame Street Countdown is one of them. It's some kind of timer that's used in order to play the NSF properly. Gil_Galad would know, as he's ripped them.
If it's an error in nsfplay itself, you should talk to rainwarrior.
Changelog for 0.53:
-Fixed a crash when you go to Options -> Settings and click OK and Apply (the fix was compiling in Visual Studio 2008 )
-The keyboard visualizer now appears when you open NSFPlay Synthesia, since let's face it, you were going to anyway!
-Time expansion now runs in 0.125x increments instead of 1x increments
-Tracks that are at volume 0 but not disabled (besides triangle and DPCM) will no longer be drawn
-The checkbox beside each channel in the keyboard visualizer mutes/unmutes the track.
-Keyboard Visualizer -> Settings... now has sliders for Synthesia Speed and Synthesia Drum Speed (in pixels per frame from 1 to 8 )
I am very bad and haven't figured out how to make the height of the keyboard synthesia/drums synthesia windows resizeable yet.
It's the same default as for nsfplay proper. The reason why there is a device mixer at all is because the sound difference between two chips is not required to be any ratio, but rainwarrior made the defaults what they tend to be.
I could make the "default" mix a flat line but it would create a loss of precision without putting up a layer of indirection on top of what's already there. I preferred to make the real values more transparently available on the sliders than to hide them. (I might do the indirection later, but it's not high on my priorities.)
The drums aren't displaying for me in the new version.
Make sure that in in_yansf.ini is present a line DRUMS_SPEED=1
OR
that under Settings... in the synthesia window, Synthesia Drum Speed is 1 or more
Is anyone else having them not display by default? Because I just downloaded the .zip and they displayed by default for me. Want to make sure I'm not missing some assumption.
.png)
