From: Steven S. <ste...@co...> - 2005-03-05 00:54:23
|
Greetings - So far, I've found that if I take the time to compose an email to ask a question to the group, the process of formulating the question usually lets me find the answer myself. Not so with this one. I would think that a bank driver requests a dump of the entire bank to store as a patchlib, but the code looks like it looks for a single patch from the synth, not from the big dump. Then again, when requesting a patch from the bank driver, I can't select a specific patch. What exactly is the purpose and expected behavior of a bank driver? Also, my (Korg Triton) device and single driver are working. Should I check them in or wait till the editor is done? Gracias! |
From: Steven S. <ste...@co...> - 2005-03-05 04:04:11
|
Steven Schmidt wrote: > Also, my (Korg Triton) device and single driver are working. Should I > check them in or wait till the editor is done? Whoops - spoke to soon. I can request any patch from the synth and save it in a patchlib, but when I try to store a patch from a patchlib to the synth, it grabs the GM patch (bank G) at patchNum + 1 and saves it to the bank I specified. If I then try to play the patchlib patch, it plays the GM patch. What's up with that? I'm hoping this is familiar to someone with some experience at writing synth support who can show me the error of my ways. |
From: Hiroo H. <hir...@co...> - 2005-03-05 23:22:32
|
Well I might misunderstand you problem. Steven> Whoops - spoke to soon. I can request any patch from the synth and save Steven> it in a patchlib, but when I try to store a patch from a patchlib to the Steven> synth, it grabs the GM patch (bank G) at patchNum + 1 and saves it to Steven> the bank I specified. If I then try to play the patchlib patch, it Steven> plays the GM patch. What's up with that? I'm hoping this is familiar Steven> to someone with some experience at writing synth support who can show me Steven> the error of my ways. The only problem here is "when I try to store a patch from a patchlib to the synth, it grabs the GM patch (bank G) at patchNum + 1 and saves it to the bank I specified". In other words, store command sends a patch which is next to the patch specified. Am I correct? -- Hiroo Hayashi |
From: Steven S. <ste...@co...> - 2005-03-06 00:33:16
|
Hiroo Hayashi wrote: >Well I might misunderstand you problem. > >Steven> Whoops - spoke to soon. I can request any patch from the synth and save >Steven> it in a patchlib, but when I try to store a patch from a patchlib to the >Steven> synth, it grabs the GM patch (bank G) at patchNum + 1 and saves it to >Steven> the bank I specified. If I then try to play the patchlib patch, it >Steven> plays the GM patch. What's up with that? I'm hoping this is familiar >Steven> to someone with some experience at writing synth support who can show me >Steven> the error of my ways. > >The only problem here is "when I try to store a patch from a patchlib to the >synth, it grabs the GM patch (bank G) at patchNum + 1 and saves it to >the bank I specified". In other words, store command sends a patch >which is next to the patch specified. Am I correct? > > Correct-sort of. I am expecting it to load the patch that I have highlighted in the patchlib, but it is getting a GM patch from the synthesizer and storing it instead. Here is a more detailed example: From JSL, I select new library. From 'unsaved library', I select Patch->get. From that dialog, I choose Bank A, patch 27. Patch A-27 is retrieved. I highlight the patch and select 'store'. From the dialog I select Bank E, patch 9. Patch 10 from Bank G gets stored at Bank E, patch 9. Obviously, its only doing that because I must be telling it to do that, I just can't see where I'm telling it to do that. Any help would be appreciated. Do you think a different list for synth-driver development might be helpful? Issues like the very hard to decipher Midi Implementation documents could be dealt with there along with how to use them in driver deveopment. Just a thought, in case the core developers prefer not to deal with these issues. |
From: Bill Z. <wrz...@po...> - 2005-03-06 01:13:04
|
Steven Schmidt wrote: > From the dialog I select Bank E, patch 9. Patch 10 from Bank G gets > stored at Bank E, patch 9. Perhaps you've stumbled across the 'copy patch' command instead of the 'upload patch' command? Or maybe the synth mangled the sysex it sent you so that when you send it back, it doesn't work. Only suggestion I can think of is make sure you have the right command, and make sure the bytes are correct. -Bill |
From: Hiroo H. <hir...@co...> - 2005-03-05 17:54:33
|
Hi, Steven> lets me find the answer myself. Not so with this one. I would think Steven> that a bank driver requests a dump of the entire bank to store as a Steven> patchlib, but the code looks like it looks for a single patch from the Steven> synth, not from the big dump. If you request a big dump to your synth, the synth will return big dump. Steven> Then again, when requesting a patch from Steven> the bank driver, I can't select a specific patch. What exactly is the I may be misunderstanding your question, but let me try. The methods BankDriver (IBankPatch interface) do the job. You may have to override some of them. Steven> Also, my (Korg Triton) device and single driver are working. Should I Steven> check them in or wait till the editor is done? I can check-in your working driver. Editor is optional. For your single editor problem, I recommend you to use Windows->MIDI Monitor. Using debugger may be a good way. -- Hiroo Hayashi |
From: Steven S. <ste...@co...> - 2005-03-05 20:32:59
|
Hiroo Hayashi wrote: >For your single editor problem, I recommend you to use Windows->MIDI >Monitor. Using debugger may be a good way. > Would Windows-MIDI Monitor be a windows program? I'm working in Linux, not Windows. My question about the bank driver though, is it intended to process an entire bank? |
From: Steven S. <ste...@co...> - 2005-03-05 21:36:00
|
Steven Schmidt wrote: > Hiroo Hayashi wrote: > >> For your single editor problem, I recommend you to use Windows->MIDI >> Monitor. Using debugger may be a good way. >> > Would Windows-MIDI Monitor be a windows program? I'm working in > Linux, not Windows. Ok - I see what you mean - yes I've been using that. |