Vegaplay for live shows

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
Vegaplay for live shows
by on (#99684)
hello all! i just had some questions about VegaPlay, and was wondering if anyone around here has messed around with it.

im trying to streamline my live sets so there arent as many interruptions between songs. im currently in talks with nick maynard of revengineers about building a pedal similar to the one you see in this depreciation guild video at 0:09 seconds, to start and stop nsfs for live shows.

basically all im trying to do is eliminate the need for me to touch a controller with my hands. it gets a little obnoxious ending a song, picking up the controller and scolling back through to the next song.

i know vegaplay is essentially an nsf "playlist" if you will, so that will eliminate the need for any sort of re-loading of nsfs during our live sets, which will in turn cut down on the awkward silences in between songs.

from what ive read, vegaplay is not able to support any expansion audio, but can be modified to do so, i dont know how to program NES code, so im at a loss, and i believe its creator (NOCARRIER) has stopped all development on it.

i did see a thread on here about CombiNSF, which sounds similar to what im looking for. just a way to combine all my songs into one nsf file, or playlist for live shows.

any ideas/suggestions? thanks!
Re: Vegaplay for live shows
by on (#99693)
elsh wrote:
hello all! i just had some questions about VegaPlay, and was wondering if anyone around here has messed around with it.

im trying to streamline my live sets so there arent as many interruptions between songs. im currently in talks with nick maynard of revengineers about building a pedal similar to the one you see in this depreciation guild video at 0:09 seconds, to start and stop nsfs for live shows.
I did not see the video but yes you could certainly design it to use a pedal to control it.

Quote:
basically all im trying to do is eliminate the need for me to touch a controller with my hands. it gets a little obnoxious ending a song, picking up the controller and scolling back through to the next song.

i know vegaplay is essentially an nsf "playlist" if you will, so that will eliminate the need for any sort of re-loading of nsfs during our live sets, which will in turn cut down on the awkward silences in between songs.
There needs to be some RAM variable to indicate when the song as stopped, if you wish it to automatically advance. (I am working on a similar thing for someone else, and can start once I have 6.nsf; the program will be public domain including source codes so you can use it if you want (but I will not release the pictures and music; the people who hired me will do that).)

Quote:
from what ive read, vegaplay is not able to support any expansion audio, but can be modified to do so, i dont know how to program NES code, so im at a loss, and i believe its creator (NOCARRIER) has stopped all development on it.
I may be able to help to make it support expansion audio; however, you cannot use multiple expansions unless using a custom mapper.

Quote:
i did see a thread on here about CombiNSF, which sounds similar to what im looking for. just a way to combine all my songs into one nsf file, or playlist for live shows.
CombiNSF puts each song at a different track number, so you will still need to advance the track manually.
Re: Vegaplay for live shows
by on (#99695)
zzo38 wrote:
CombiNSF puts each song at a different track number, so you will still need to advance the track manually.


thats what im looking for, i would prefer to advance tracks manually. does combinsf support expansion audio?
Re: Vegaplay for live shows
by on (#99708)
elsh wrote:
zzo38 wrote:
CombiNSF puts each song at a different track number, so you will still need to advance the track manually.


thats what im looking for, i would prefer to advance tracks manually. does combinsf support expansion audio?
Currently only two: MMC5 and Namco 163. The output will additionally use FDS RAM, and will be bankswitched; the input files cannot be bankswitched.

It may be possible to improve it to remove these restrictions. This can be discussed in the proper thread for doing so.