Rick, I havenât used Anvil Studio at all, only MidiGlass, which is the Midi Sequencer which shows ALL of the element contents of a jOrgan disposition on Track 6 of the .mid file. It shows the note-on/note-off messages for each of the other Tracks (equating to the divisions) of the jOrgan disposition, as tracks. Of course, all tracks, except the metadata track are assigned Midi Channel 1. Years ago, I purchased a program called Record Producer Deluxe which is a good Midi Sequencer Program with an Audio Recorder/Editor window, an application within an application, Wave and MP3 being recordable while MIDI is playing back a .mid file, one program doing everything. It is a very useful program, but unlike MidiGlass, it does not show ANY of the jOrgan-proprietary metadata. While it is only the actual stop changes, couplers and expression/volume changes which occur during a recorded performance which are essential to be known, and it seems superfluous for MidiGlass to show the entire, element contents of a disposition, that it is done in the one, and not done in the other Midi Sequencer program, indicates that metadata extraction is possible in a program the name of which is MIDI Glass and not MetaMidi Glass. While Sysex may be considered âmetadata,â it comports with MIDI to the extent that it can be modified in a text editor and used in my other Midi Sequencer program. Indeed, the CMOS Reuters Pipe Organ (www.graeber.com) gives its stop list and instructions on how to use an old version of Cakewalk to show the stops used in the Sysex-proprietary .mid files produced by the organ. Unlike the metadata of jOrgan dispositions, the fact that the Reuters organ uses MIDI Channel 5 to transmit both Stops and changes of them, and Swell Shade degrees of openness or fully closed by static, note-on messages on MIDI key numbers equating to the Preset Numbers of the Soundbank of Organ Stops used by the organ, this conceptual difference is important, since designated MIDI note numbers are used in MIDI to effectuate Program changes, Reverb levels, etc.
While MIDI is somewhat familiar to most of us, because of Soundfont Bank Manager in the old AWE-32 and AWE-64 soundcards of 20 and more years ago, used in conjunction with MIDI Sequencer programs to play .mid files, given the distinct differences in effectuating sound production, to understand that it is the demands of the Graphical User Interface which require the non-MIDI is not something that is readily perceptible. How the
Checkbox, used as a Switch to designate the assignment of a Program Change/Preset, differs from a Drawknob or stop tab, with respect to the pre-programmed instructions which are effectuated when, mechanically, drawing or retiring the Drawknob or stop tab has ramifications which are greater than mere connection. Yet, mere connection is all that we are actually concerned about. So, we tend to see it more simplistically than it really is, because it WAS simpler 20 years ago, despite the limitation of one voice per MIDI channel, this limitation could be overcome by âlayeringâ of presets. So, many organ soundfonts included Presets with Combinations and multiple combinations of instruments in Presets asstops because they could be effectuated by MIDI.
I guess I might ask whether functionality has actually increased or whether the âglitzâ of Graphics is what has actually become much more complex. Ironically, given the skins of jOrgan, we still do not have a tutorial or program which allows for ready skin production and I still do not know how to edit photos to sizes which are compatible with jOrgan or how to edit the skin XML file to make it functional. All these things are related to
âmetadata,â which is not necessary to MIDI function but give âlook and feelâ to virtual organs. I think we have exchanged one kind of layering in soundfonts, compatible with MIDI, for another kind of layering in Metadata which is not. Maybe I am reading more into the idea of âinterfaceâ than I have a right to, because I continue to see the .mid file from the perspective of General Midi, providing universal playability. The idea that I could take a .mid file produced by anybody and immediately have it play back exactly as it was originally played, does not apply to jOrgan. The incongruity is that a piece of music can be played on any organ, BUT you need a specific disposition with an exact stop complement having produced that exact rendition of that piece of music on a specific program with its proprietary recorder, as the ONLY way that playback of that file is possible, is a limitation on the concept of âinterface.â That said, if we perceive each jOrgan disposition as an individual organ, we have a replication of the pipe organ concept with respect to uniqueness. Also, once a soundfont and a disposition are created, the facility of use is much greater than the âold way,â loading a soundfont of layered organ presets into RAM by Soundfont Bank Manager and using a Midi Sequencer program of tracks with assigned channel numbers to allow play of those Presets by the manuals and pedalboard, preprogrammed to transmit note-on/note-off messages on those assigned channels.
I am wondering whether, one day, XML will make it possible to readily equate stop name for stop name, do the necessary translation/equation correlates, automatically, and allow for the playback of a .mid file using them, even though the Preset numbers of the one bank differ from the Preset numbers of the same-named stops of the other bank. This is the only limitation which is imposed by the specification of a digit. 0 does not equal 1.
What program can set two soundfonts side-by-side, by reading analysis, equate an exact Preset name to an exact Preset name, reconcile two numbers which identify them as Presets in different banks and conclude that they are the same for purposes of the playback of Midi Track note-on/note-off messages? The answer is âSoundfont Bank Manager.â Standardization proves its purpose. Why is it objectionable? The standard midi file requires a sequencer program (or Media Player) to play it. Stop selection is Program Change assignment.
The shortest distance between two points is NOT metadata.
I apologize for the length of this post, I donât know if or how I could have put it more succinctly.
John B.
From: John Beach
Sent: Monday, June 5, 2017 8:44 PM
To: jorgan-***@lists.sourceforge.net
Subject: Fw: [jOrgan-user] Fw: Fw: Fw: jOrgan Recorder Disposition-Proprietary Data channel?
Rick, Iâm sorry you spent time stating what you did below. I am aware of all of what you said. The only reason I have been pursuing this subject at all is because I wanted to know, originally, if the metadata of a jOrgan-Recorder-produced MIDI file was always stored on a dedicated track or MIDI Channel. I found out that it is stored in a track and that assigning a MIDI Channel number to that channel deletes all the proprietary metadata. Essentially, the jOrgan-proprietary metadata is GUI-element related and there is no way that MIDI messages, as Channel Messages (e.g., Program Change) could effectuate the stop changes, since jOrgan stops
are non-MIDI switches which are referenced to a Preset in a Soundbank which are MIDI. You can take any standard midi file, edit the channel numbers so that the note-on/note-off messages from those tracks can play
the stops of divisions in jOrgan, record the file in jOrgan and save it with all the proprietary jOrgan metadata related to stop changes, couplers, tremulant, expression changes, etc. that you make during playback.
I think it is beneficial to understand the âMetaMidiâ concept since they are, obviously, closed connected, however the one may be distinct from the other and any cooperation is due to human input.
John B.
From: ***@gmail.com
Sent: Monday, June 5, 2017 7:19 PM
To: jorgan-***@lists.sourceforge.net
Subject: Re: [jOrgan-user] Fw: Fw: Fw: jOrgan Recorder Disposition-Proprietary Data channel?
Hello John
A MIDI file created by the recorder in jOrgan is intended for playback by the MIDI player in jOrgan in that actual disposition. Even editing the original disposition between record and playback could cause problems with the accuracy of the replay.
Playing a MIDI file created by the recorder in a jOrgan disposition using some other MIDI sequencer will render all information other than recognized MIDI messages as useless. The text comments used by Sven for registration changes will not be recognized by any MIDI software. They will not even be recognized by a different jOrgan disposition.
Any use of this text information would need to be done by human interpenetration with a detailed understanding of the disposition in which it was created. I can't see how any code or MPL could assist with this.
Yes, the jOrgan recorder assigns each division to a track, each track showing CH1. This can be changed in a MIDI editor like Anvil Studio.
My suggestion for assigning registration changes to a MIDI file being played into a different disposition would be as follows:
Edit the MIDI file to have unique channel numbers for each division.
Edit the intended disposition to match these channels to divisions using the Customizer.
Edit the MIDI file to have Program Change messages at suitably timed places in the music.
Edit the intended disposition to match these Program Change messages to Pistons in the disposition
Edit the combination memory to have suitable registration changes stored in the Pistons
Play the edited MIDI file into jOrgan from an external MIDI sequencer
Record the performance using the MIDI recorder in the disposition.
You will now have a MIDI file ready for playback by the jOrgan MIDI player in this specific disposition.
Regards
Rick
On Mon, 5 Jun 2017 at 23:36 John Beach <***@fairpoint.net> wrote:
In outputting the playback of a jOrgan-disposition, recorder-produced .mid
file using MidiGlass for the playback via Loopbe virtual midi cable
inputting to the same disposition, while the note-on/note off messages are
transmitted to jOrgan, they are all transmitted on Channel 1 and, thus, they
are not played by the divisions having other Channel numbers. All
note-on/note-off messages to to the Swell Manual (channel 1). None of the
jOrgan-proprietary metadata, shown on Track 6 of MidiGlass, is, apparently,
transmitted back to jOrgan to inform it in the same manner in which the
Recorder function of jOrgan does. Would this be possible with some
kind of MPL in the Messages section of jOrgan to "Intercept" such metadata.
Given the capability of the jOrgan Recorder, while this is a totally
unnecessary thing to do, it is the specific need to understand how metadata
is handled by MIDI and why, when MIDI can list all the metadata in an
external MIDI sequencer program, it has the limitation of not being able to
transmit that same data back to the program from which it received it to
effectuate what MPL effectuates or what jOrgan-proprietary "comments"
effectuate with respect to the innerworkings of the console elements of a
jOrgan disposition. Perhaps, Lynn can inform us how or why this disparity
exists. I am surmising that it is the difference between .txt messages,
identifying elements and the power of Controller-type messages which
activate, deactivate, engage and disengage elements within the time frame of
the note-on/note-off messages which are the single, most important aspect of
a .mid file.
The MIDI Sequencer program which I use most often allows one to create
(following a specified format) proprietary Patch/Program Change/Preset Lists
and to create one's own .syx (SYSEX) files which can be both loaded and
edited in the Sequencer program. While I have used the former to create
lists of the Presets of Organ Soundbanks based on Soundfonts, I have never
actually created a .syx file which specified the proprietary data of the
disposition of a program such as jOrgan. I am content to be thankful for
all the work Sven did to make this possible, since it seems like a rather
awesome task.
Is the future of MIDI, especially proprietary metadata, in XML, and is this
the solution to the ready translation or equation of different, although not
incompatible, specifications with respect to switch-effectuated, sound
schemes based on unspecified, individual soundbanks or soundfonts, such as
jOrgan is capable of creating and dealing with?
I also discovered that if I, manually, add the midi channel number (6) to
the jOrgan-proprietary metadata track in the MIDI Sequencer program, it
apparently erases all the data because, after doing so, only the track
identification shows and no metadata (the entire element list of a
disposition) is shown. Not sure why this occurs, but it is so.
John B.
-----Original Message-----
From: John Reimer
Sent: Monday, June 5, 2017 7:36 AM
To: jorgan-***@lists.sourceforge.net
Subject: Re: [jOrgan-user] Fw: Fw: jOrgan Recorder Disposition-Proprietary
Data channel?
Post by John Beachthe same stops in the same disposition are assigned the same
identifying number in different recordings. So, apparently, they are
permanent, element identifiers in a disposition. Since these are
readable,
as text, by such programs as Anvil Studio and Midi Glass, they are helpful
to know what stops of a disposition were used to produce the file and when
those stops were activated or cancelled.
Yes, that is my conclusion also.
However, I have to report no success with Anvil Studio even with the
accessory installed. Nothing has changed. I did make another jOrgan MIDI
file which it read, but it would still not read the notes-on and notes-off
information of the others. The one difference that I can identify is that
the âsuccessfulâ files had only one note at a time rather than chords being
played. I am not prepared to spend more time on this issue at the moment, as
I want to finish work on what will be my last jOrgan VPO for the time being
- an extension of the KOGARAH one.
As far as I can see, Anvil Studio could be useful in identifying the tracks
of standard MIDI files which one wants to use with jOrgan by means of a
sequencer, and also the stops being used in jOrgan MIDI files, but editing
of the notes being played in the jOrgan MIDI files still seems to be eluding
us.
John Reimer
--
View this message in context:
http://jorgan.999862.n4.nabble.com/Fw-Fw-jOrgan-Recorder-Disposition-Proprietary-Data-channel-tp4665052p4665053.html
Sent from the jOrgan - User mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
jOrgan-user mailing list
jOrgan-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jorgan-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
jOrgan-user mailing list
jOrgan-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jorgan-user
--------------------------------------------------------------------------------