The Patch['*'] line is just for unnamed banks, as you said, and even then it still outputs patch numbers 0-127

Mike, sorry it's not working. Yes, to confirm, I just inserted a dummy bank for the PC2X into my master.ins with the first patch set as 1= and the last as 128=. Sure enough, the patch select dialog begins with an inserted patch "0", and ends with 127. I gave it a Bank 8 assignment (Patch[8]=Dummy Bankj. But 128th patch simply doesn't show in the dialog. (Using S7P.) It's not an issue with the PC2X, since its numbering follows the 0-127 protocol. (I wonder why Kurz changed that on the PC3 series.) BTW, my bank select parameter in the instrument definition is "normal." MIDIOX shows that changing the patch in the track pane issues 3 events. CC0=0, CC32=the bank number, and PC=patch number from the Sonar generated dialog.

Other midi software allows for "zero-based" or "one-based" patch numbering. Don't understand why CW would not have a comparable feature. (Or what the significance of those Patch['*']=1..128 in some of the .ins files is.) Please post if you learn more.

-Ron

ORIGINAL: rkl122

Other midi software allows for "zero-based" or "one-based" patch numbering. Don't understand why CW would not have a comparable feature. (Or what the significance of those Patch['*']=1..128 in some of the .ins files is.) Please post if you learn more.

Well, Cakewalk really do allow 1 based numbering. This goes back to the early days of MIDI. Most synths would number their patches on the front panel starting at patch number 1 and going up from there. Behind the scenes, however, the first patch was selected by PC=0. All that happens in Sonar is that the name of the patch is called "1" even though the actual PC transmitted is 0. This all makes sense since it is not possible to send a PC greater than 127. The problem is that Kurzweil have decided to make the PC3 ignore PC=0 in the first bank. This has the advantage that MIDI PC now matches actual patch number. However, this is only of benefit for the first bank Other MIDI programs allow CC0, CC32, and PC all to be defined for every patch name, but Sonar does not have this flexibility.

As I said earlier, it doesn't stop me using the PC3 and Sonar together, but it offends my sense of aesthetics to see the banks in Sonar not match the banks in the PC3.

I was searching for someone that had completed the PC3X banks.  I found this forum, question and problem. 
 
I made two banks for my PC3X and they work perfectly.  Use the template starting with 1, start filling it out, cursor up to the top entry and hit delete.  cursor back down and finish the entries to 128 (the old Kurzweil standard stopped at 99 remember?)  When you get to 128 stop.  Start a new bank named bank01 & voice #129 is the first voicde, again use the template starting with 1, and fill it it. 
 
It works.  I can't post it yet because I have a lot of entries to make before it's ready to ship. 
 
I have every Kurzweil ever made and the PC3X is a little different.  I prefer the K1000-K2600 bank change method myself. 
 
 

DavidBrown99


I was searching for someone that had completed the PC3X banks.  I found this forum, question and problem. 
 
I made two banks for my PC3X and they work perfectly.  Use the template starting with 1, start filling it out, cursor up to the top entry and hit delete.  cursor back down and finish the entries to 128 (the old Kurzweil standard stopped at 99 remember?)  When you get to 128 stop.  Start a new bank named bank01 & voice #129 is the first voicde, again use the template starting with 1, and fill it it. 
 
It works.  I can't post it yet because I have a lot of entries to make before it's ready to ship. 
 
I have every Kurzweil ever made and the PC3X is a little different.  I prefer the K1000-K2600 bank change method myself. 
 
 

This sounds promising. I'm not really following what you are doing at the moment, but I'll have a go at it tonight.

BTW, if you can export even what you have, I should be able to easily merge all the rest of the program names. Might save you some typing.

Hi David,

I'm not having any luck following your instructions.

DavidBrown99
Use the template starting with 1, start filling it out, cursor up to the top entry and hit delete. 

First problem, and maybe why it all falls down. I don't understand how to use a template. I can only create a new note names list. I can add patches from 1 to 128, but when used in a song, Sonar inserts a patch called "0" into the list and truncates the list at 127.

I finally got around to almost finishing a template.  I have an 18K INI file named "PC3x.ini"  ready for anyone who wants it.  email me at:
dbrown12
AT
nc.rr.com

The next to the last bank is only partially complete.  this is version 3 of the software and voices. 

Hello David,
I am brand new to the Cakewalk forum having just installed Sonar 8.5 earlier this year and am learning to use it. I have been viewing the forums for the last couple of months and they have been very helpful on a lot of different topics. Until now, I really didn't have a reason to register since I am new and have nothing to add to the posts.
 
I also have the Kurzweil PC3 keyboard (76-key version and LOVING IT!) and would like to get a copy of your INS file so I can use the sounds in my PC3 with MIDI tracks in Sonar. I will send a separate email like you requested in your post. I'm still new to the whole "instrument definition" side of things, but I would love to be able to select and see the names of PC3 program selections in my Track View.
 
Thanks. I know it's probably a lot of work to put an INS file together and I appreciate you offering it up to forum users.
 
'Startngo'
Dana Hester

Hi David - the above post could almost be read word for word and apply to me. 

I've sent an email per your instructions.

TIA
JB

I created an .ins file for the PC3 Kore 64 expansion  I uploaded it on Sonikmatter if you want it, it took a while to compile and test, there are gaps between some of the sounds that took some testing and debugging. It is my 1st attempt at a definition file and after I figured out what I was doing it wasn't so hard. The trick was finding where the gaps were between the sounds.

http://forum.sonikmatter....le/353-pc3-kore-64ins/

Enjoy!