Prophet VS group photo

Yahoo Groups archive

Prophet VS

Index last updated: 2026-04-28 23:40 UTC

Message

Re: [prophet_vs] New VS operating system work

2018-07-30 by deano

Excellent work, stickfigurewhore -- I was working on trying to do this myself a few years, but got distracted on other things.

I'd be really interested to hear some more info on this. I didn't quite figure out where the LFO generation was happening in code before I stopped. If this works well, I'm very tempted to burn it and put it into my VS -- be interesting to hear if this makes much difference to the presets (obviously go and turn LFO sync off for each)

Cheers!

//deano


On Mon, Jul 30, 2018 at 3:07 AM, stickfigurewhore@... [prophet_vs] <prophet_vs@...m> wrote:

Here are some v1.3 updates:

Most of this would be way easier if I could rearrange the code without having to change the branch cross references in the entire thing. As it stands I am using empty space at the very end of the eprom.

Figured out most of the panel switch addressing, then coded a way to enable key-synced LFOs while holding down a button ("Enter" for example).

Then, I started using memory addresses basically at random to get the "enable" to latch.. This will take some time... My first memory area would disable key-sync LFO if you hit the Mod Dest button. The second choice would disable if you edited Wave C's fine tuning. With the memory address I'm using now i have not found the bug yet, but it is probably there...

Now for cool stuff... As it stands presently, I can hold "LFO Select" and hit a key... key-sync turns on. Hold "Cartridge" and hit a key, it turns off. The buttons are totally arbitrary and can be changed to anything. The amazing thing though is that right now it SAVES the selection PER PATCH.

There's bound to be a bug somewhere since I'm shooting blind with memory addresses, but it is neat nonetheless. Once I burn some eproms to test on my hardware VS I'll post a video.


Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.