Synth Forum

Notifications
Clear all

Reaper instrument definition file

7 Posts
2 Users
0 Reactions
484 Views
Posts: 263
Reputable Member
Topic starter
 

I try write ins definition file for MODX with Cockos REAPER but something went wrong. Is it ReaControlMIDI buggy?
Some names this is missing. I dont see here unicode like hardly symbols as is.

 
Posted : 20/05/2022 7:39 pm
Posts: 263
Reputable Member
Topic starter
 

In ReaControlMIDI list (Cockos Reaper)
after
PC=007 CFX & Pad
following
PC=010 CFX & Orch 2 (show as PC=8)
missed
PC=008 CFX & Pad 2

CFX & Pad 2 and CFX & Orch 1 is fully ignored in the program
Mayby app filtering some patches for some reason?

I try some version Reaper and all the same. it could doesn't look like a bug.

What is it you are trying to do and what trouble are you having doing it?

I need Program Change via MIDI. I whant to create Reaper - reabank file

 
Posted : 20/05/2022 8:10 pm
Posts: 263
Reputable Member
Topic starter
 

Interesting idea! Although that's probably not the point.
Some examples found here:
http://www.djemberecords.com/reaper.html

The second column numbers is not actual for this! It's just shown in user screen for look reason.
Only one column actual for work.

// Pianos, Clavinets, Pipe Organs and Guitars
Bank 63 0 Pre 1 Pianos, Pipe & More
0 [1 Ap: Full Grand]
1 [2 Ap: BriteGrand]
2 [3 Ap: Dark Grand]

second column of digits this is superfluous

 
Posted : 20/05/2022 8:36 pm
Posts: 263
Reputable Member
Topic starter
 

example: http://www.djemberecords.com/reaper_files/Yamaha_Motif_Rack_ES.reabank

reabank format is 0 - 127 for PC

Attached files

 
Posted : 20/05/2022 8:50 pm
Posts: 263
Reputable Member
Topic starter
 

From cockos forum

The explanation for the behavior is technical and maybe we can improve it, but the quick fix is, don't use leading zeros in the file.

We will wait for the update 🙁

to skip leading zero is not resolve problem

1 01 001 the same

--->8----

Yes! Resolved! I forgot to delete second leading 01
Now work!

001 or 01 not allowed only 1

 
Posted : 20/05/2022 10:22 pm
Posts: 263
Reputable Member
Topic starter
 

As I said three times now - you entered 8 for LSB instead of 10.

The field [8] is not LSB
It is PC mean field. This strange GUI look.
LSB all 0
MSB 63

Problem resolved.

Not allowed
008 CFX & Pad 2
009 CFX & Orch
010 CFX & Orch 2
011 CFX Shrine

Good
8 CFX & Pad 2
9 CFX & Orch
10 CFX & Orch 2
11 CFX Shrine

 
Posted : 20/05/2022 10:45 pm
Jason
Posts: 8238
Illustrious Member
 

I think AB has it.

For the rest, paraphrasing from "The Art of REAPER MIDI Patch Banks":

.reabank files start with a line like:

Bank BANK DESCRIPTION

Where "" is replaced by the decimal MSB (CC #0), "" is replaced by the decimal LSB (CC #32) and "BANK DESCRIPTION" is free-form text to describe the bank. MSB as 0 and LSB as 0 for MODX, for example, is the GM bank and you may replace "BANK DESCRIPTION" with "GM BANK" (no quotes) or similar.

Next lines define each Performance, in MODX speak, for that bank assuming using the bank associated with Multi-Part. The format of this line is:

PERFORMANCE DESCRIPTION

... I've elected to "MODXize" the documentation. The PC is zero-based (starts at 0, not 1) and is decimal. What follows is free-form text for each Performance. The suggestion is to start with the number that's in the data list for that Performance number. For = 0..127 these numbers would be 1 through 128 (one more than the PC). You'll need a new Bank line after 128 values because the LSB is going to increment for the next batch of Performances. And for the very next batch (first +1), the will start at 129. That's if you elect to have the handy number preceding the Performance name.

I haven't seen any 0-prefixed numbers in the example files (000, 001) and the link mentions issues with those. So don't do that. AB knows this, but I'm just restating.

Current Yamaha Synthesizers: Montage Classic 7, Motif XF6, S90XS, MO6, EX5R

 
Posted : 20/05/2022 11:24 pm
Share:

© 2024 Yamaha Corporation of America and Yamaha Corporation. All rights reserved.    Terms of Use | Privacy Policy | Contact Us