Good morning.
I purchased (a year ago) an Artisan interface to convert my pedal board to MIDI. I got the pieces then the project got tabled. I'm now putting everything together and this is the last piece I'm waiting on. Mark is spread way too thin and I'm sure he has more important things to do than help someone with their home setup! When I loaded the program supplied by Artisan to pull down the config from the board, there's nothing there to pull down.
What I received is the a micro-midi controller and a matrix256 keyboard interface (2 16-pin connectors). I think I have the pedal board mapped out. I hooked up everything and I see midi messages flying, but a single note is sending three notes. I attempted to download the program from the board and when I do that, I get nothing, so I'm thinking maybe I need to load a program. Does someone have one I could try? I'm willing to attempt some tweaks against a file/config, I'm just unsure how to start from scratch. I think I'm really close.
oh... because of the three notes firing, I thought maybe I had the two parts of the matrix reversed. I swapped all that around and got no midi messages, so I put it back to what I originally had.
Artisan config file
-
- Member
- Posts: 34
- Joined: Thu Jun 21, 2012 7:35 pm
Re: Artisan config file
Unfortunately, this seems to be becoming a problem for several of us on this forum.
I purchased the hardware for a full drawstop console conversion. This all arrived promptly and has been installed. Unfortunately, the config file has not been forthcoming, as promised. I'm currently trying to grasp the language in the document to write it from scratch, but it is almost impossible.
My advice to any potential purchasers would be to negotiate a deliverable timeframe for the config file prior to purchase.
I purchased the hardware for a full drawstop console conversion. This all arrived promptly and has been installed. Unfortunately, the config file has not been forthcoming, as promised. I'm currently trying to grasp the language in the document to write it from scratch, but it is almost impossible.
My advice to any potential purchasers would be to negotiate a deliverable timeframe for the config file prior to purchase.
Re: Artisan config file
lol. My biggest problem is I’m close to having this thing playable (after not having it for two years). I’m getting antsy!
I was hoping someone might just have a config file handy as a push in the right direction. I fear I too may have to start from scratch, or order from elsewhere. … time vs money.
I was hoping someone might just have a config file handy as a push in the right direction. I fear I too may have to start from scratch, or order from elsewhere. … time vs money.
-
- Member
- Posts: 34
- Joined: Thu Jun 21, 2012 7:35 pm
Re: Artisan config file
Are there diodes installed in your wiring? If not, that would explain the sending of three notes at once.
AFAIK, configs are not pulled from the boards, but loaded from the configuration program on the PC vi MIDI.
This should be a fairly simple encoder...there is a document on their website that details the syntax needed.
Assuming you are using a uMidi Module and HV64 input board, this may work to send Pedal on channel 3. It would need to be copied as plain text, and saved with the .ucf file extension before loading into the configuration program.
*UMIDI_MODULE
*HV64
*DIVISION=pedal *BITS= 1,32 *MIDI_CHANNEL = 3 *MIDI_NOTE =36
*END
I'm only just getting my head around it, so if it doesn't load, try deleting the "*DIVISION=pedal" term, as you are only encoding one standalone division. Hope this makes sense.
AFAIK, configs are not pulled from the boards, but loaded from the configuration program on the PC vi MIDI.
This should be a fairly simple encoder...there is a document on their website that details the syntax needed.
Assuming you are using a uMidi Module and HV64 input board, this may work to send Pedal on channel 3. It would need to be copied as plain text, and saved with the .ucf file extension before loading into the configuration program.
*UMIDI_MODULE
*HV64
*DIVISION=pedal *BITS= 1,32 *MIDI_CHANNEL = 3 *MIDI_NOTE =36
*END
I'm only just getting my head around it, so if it doesn't load, try deleting the "*DIVISION=pedal" term, as you are only encoding one standalone division. Hope this makes sense.