So i still have to download some files? So im just going to google "Instrument Definition file dgx-650" or something? Do i still need the dgx-650 data list for the patch library? This will probably still take one or two days until i figure out where to write what number from the data list...

Well apparantly there are instrument definition files for dgx-200 to dgx 630 and anything between them.
But not for dgx-650.
Oh my.

So if anyone is still watching this thread, could that person tell me if i am doing this right? Because the way i did it in the screenshots doesnt give me results.

Here's the sequence I did.
Cancel that (why can't I delete it?) I made a mistake.

Here goes, again.

Insert a Bank select (MSB) to be the first of the three events. From the table the MSB is 0.
Then insert a bank select LSB to be the second event slightly after the MSB. You'll see I have it one tick later. From the table the LSB is 113.
Then alter the existing Program Change command by double clicking on it. Change the timing so that it occurs one tick after the LSB.
Now, as the list of program changes goes from 1 to 128 but the editing command goes from 0 to 127, one must subtract 1 from the listed number.
The instrument you want is 65, minus 1 is 64, so the entry is as shown in MIDIevent3.jpg.
The result in the event list is the last picture.

Another option would be to import the patch library for the dgx 630, assuming there is some overlap, and then edit the patch library. If you have trouble, rename the dgx630.ins file to dgx630.txt (Windows doesn't like to send .ins files - thinks they are system files). I can create import the patch library and send it back to you.

There is indeed a lot overlap.
DGX-650 data list (Link to the pdf is in the list): http://download.yamaha.com/search/product/?language=de&site=de.yamaha.com&category_id=16084&product_id=1789577
DGX-630 voice list (starts at page 128 of the manual): http://download.yamaha.com/api/asset/file/?language=pt&site=pt.yamaha.com&asset_id=9042

So i downloaded an instrument definition file for the 630 from here ( http://www.jososoft.dk/yamaha/ins_files.htm), but it gave me an error:
File format error in line 714: "57Hand Cymbal"

well what exactly do you mean by

I can create import the patch library and send it back to you.

what sort of effort are you talking about here

either way, i cant send the file as an attachment in here, it doesnt let me (also doenst work as a txt file)
So what? E-mail?

I can create import the patch library and send it back to you.

I dont quite understand that, in which exact case would this be an option?
Because there seems to be something wrong with the file itself. I cant send it as an attachmend though, not even in txt-form.

Ah dang it
i didnt notice that there are already 2 pages and so i thought my post was gone.

I love Anvil Studio, but I've never heard of "Anvil Studio Works". Is it possible you were gypped by a fake company that has nothing to do with Anvil Studio? Check whether or not it's made by Willow Software.

Good Luck
Chris Seddio

I've read this thread with interest, and I hope my tagging on to it will not be taken as discourteous.

John
I've read your more detailed posts with care. I'm a log-time midi user with ,as it were, user-software - programmes like Band in a Box, One Man Band, Notation Composer, Ludwig, Tonica etc which actually do most of the detailed technical stuff for you, and you rarely need to look under the bonnet.
I have now reached a stage where in order to do some things I want to do, I need to engage with the midi more directly. Obviously I can find directories of control codes etc, and I have been begun looking at the event lists of some midi-files to hand.

Is there a primer/spec document which sets out simply and comprehensively the semantics of a midi file - codifies the knowledge you obviously have ?

(E.g. I can see that some parts of a line have no spaces, and other parts of a line have single spaces, others again have triple spaces. Are these distinctions significant, and if so, what is the lexicon or hierarchy? Can the various controls be entered in any order, or is there a sequence or hierarchy ? Some controls seem to appear as abbreviations - is there an 'official' list of what will be recognised?)

It seems to me that working out these things inductively or by trial and error could be a long and wearying process. With the required info to hand, I would hope to get somewhere at a reasonable rate !

Any pointers much appreciated.

Sincerely

Ian Graham
amateur musician
Wales UK

Enzo

I don't know if you've come across this - ?

http://openmidiproject.osdn.jp/MIDIInstrumentLibrary_en.html

It seems to be a dll file, so how you run it, I,m not clear, but that's another story ! 🙂

Ian G

Supports non-destructive editing of each track's sound effects controls over time. For example, you could use it to gradually decrease the volume of a track at the end of a song, creating the effect of a moving fader.
It also lets you:
Use soundcards with low-latency ASIO drivers and load third-party VST effects.
Manage a graphical view of your MIDI setup.
Import Instrument Definition (.INS) files, and load and save Patch Libraries for a variety of synthesizers, sound modules, and effects processors. These allow you to use your synthesizer's patch names, controller names, and drum names, instead of the General Midi names.
connect each Instrument track to a different VST-Instrument,
connect each Instrument track to a different MIDI Out port, so a single song can be played on several synthesizers,
edit the values of any MIDI controllers such as Modulation, Tempo, Pan position, Sustain, and Volume over time.
edit an audio track's Pan position and Volume over time.
edit values of VST parameters over time,
use Automation to capture the position of faders and VST dials as you play / mix the song, and then use those changes every time the song is played.
use the ReWire standard for transferring audio data between Anvil Studio and other programs in real time. ReWire acts like a cable that streams audio from one program into another.
see a graphical view of your MIDI setup,
create your own Patch Libraries that describe your synthesizer's patch names, controller names, and drum names.
load Instrument Definition (.INS) files that describe your synthesizer's patch names, controller names, and drum names.
Add any number of routing commands that cause MIDI events received from any MIDI In port to get routed to any MIDI Out port or VST-Instrument port. This can be useful during either a recording session or live performance.

I've read this thread with interest, and I hope my tagging on to it will not be taken as discourteous.

John
I've read your more detailed posts with care. I'm a log-time midi user with ,as it were, user-software - programmes like Band in a Box, One Man Band, Notation Composer, Ludwig, Tonica etc which actually do most of the detailed technical stuff for you, and you rarely need to look under the bonnet.
I have now reached a stage where in order to do some things I want to do, I need to engage with the midi more directly. Obviously I can find directories of control codes etc, and I have been begun looking at the event lists of some midi-files to hand.

Is there a primer/spec document which sets out simply and comprehensively the semantics of a midi file - codifies the knowledge you obviously have ?

(E.g. I can see that some parts of a line have no spaces, and other parts of a line have single spaces, others again have triple spaces. Are these distinctions significant, and if so, what is the lexicon or hierarchy? Can the various controls be entered in any order, or is there a sequence or hierarchy ? Some controls seem to appear as abbreviations - is there an 'official' list of what will be recognised?)

It seems to me that working out these things inductively or by trial and error could be a long and wearying process. With the required info to hand, I would hope to get somewhere at a reasonable rate !

Any pointers much appreciated.

Sincerely

Sorry for the delay, Ian.

I've been so busy writing various articles for another forum and deleting the huge amount of SPAM that has recently hit this forum that I've had my eye off the ball for a while.
Look for a personal message from me.

Regards,
John.