I think I've run it on both, and end up either taking a cell phone photo of it on my TV screen, or taking a screenshot of the Uzem window so I have a "hard copy" of my patch file, and then I look at that photo while I'm translating and typing it into my .inc file.
After making a longer than usual patch, I was thinking "Damn, I wish there was a better way to turn this into code without having to translate and type it all in!" And then I got to thinking, well maybe I could do OCR on the screenshot, and then write a script to expand the abbreviations, but to be honest, that sounded pretty gross too.
But what if you used the two whisper ports:
Code: Select all
#define UZEMCHR _SFR_IO8(26) //uzem whisper port for outputting characters to the console
#define UZEMHEX _SFR_IO8(25) //uzem whisper port for outputting hex bytes values to the console
Code: Select all
const char patch[] PROGMEM = {
0,PC_WAVE,1,
0,PC_ENV_SPEED,20,
1,PC_PITCH,95,
1,PC_NOTE_UP,2,
1,PC_NOTE_UP,2,
1,PC_PITCH,100,
1,PC_NOTE_DOWN,2,
1,PC_NOTE_DOWN,2,
1,PC_PITCH,95,
1,PC_NOTE_UP,2,
1,PC_NOTE_UP,2,
1,PC_PITCH,106,
1,PC_NOTE_DOWN,2,
1,PC_NOTE_DOWN,2,
1,PC_PITCH,95,
1,PC_NOTE_UP,2,
1,PC_NOTE_UP,4,
1,PC_NOTE_UP,8,
1,PC_NOTE_UP,16,
1,PC_NOTE_CUT,0,
0,PATCH_END
};
Then it would just be a matter of copying and pasting that into your patch.inc file, changing the name of the patch, and you'd be done!
IIRC, the Uzem from the uzem140 branch always has the whisper ports enabled, while they can be enabled with a flag in the Makefile of the Uzem from the master branch.