I would like to completely disable velocity on my Kurzweil K2000R ...
Usually each program is designed to respond to velocity in some
appropriate way, but if you really want the whole K2000R to be velocity
insensitive, then this is what I would try:
1. go to the MIDI / Receive page
2. select the Velocity Map parameter
3. press Edit
4. make a "flat" velocity map, maybe setting all velocity levels to 64
(mid-range) or 100?
5. select the new map for the Velocity Map setting on the MIDI / Receive page
Now the velocities of all incoming notes will be "flattened" by your new
flat map.
I hope I got those steps right. Check the manual for details; I'm pretty
sure there's a section on the vel-map editor towards the end of the book.
When I turn the unit back on I see the programs on the screen but no
sound unless I reload theatero.krz from the SCSI again.
Yes. The sample data is lost on power down, but the program are retained.
They are two different kinds of data, in two different places - one is
used by the sound engine, the other by the controller.
Or, think of the PCs in 1995 ... some BIOS settings were in battery backed
ram, but those memory SIMMs went blank when you turned the power off. The
same memory SIMMs are used in the K2000R.
Is this just a battery issue not keeping the sounds in Ram
No, the fact that your programs are retained after power down means that
the battery is probably good.
To check, once the unit is on, press 4-5-6 to enter the panel diagnostics.
One of the items on the screen should be the battery voltage level. It
should be around 4 volts or so. Check it every few months or so. Once I
let mine go way too long and the batteries leaked, and I had to replace
the battery holder. So - check your voltages people! :-) (the screen
will say how to exit diagnostics).
or do I have to load it every time I start up the unit?
Yes, the samples need to be loaded every time we power up.
The good news is that you can make a disk "macro" to clean out the bank
and reload the file for you automatically at power on. There's a good
section about disk macros in the Disk chapter in the manual. It's well
worth digging into.