maybe a half dozen different horns, different engines, etc.Ī set of "triggers" that map the "sound events" to the "sounds" in various ways. These become the buttons on the "sounds" tab of the GUI and get mapped directly to Throttle events.Ī set of "sound options" that can be mapped (indirectly) to the "sound events". It contains:Ī set of "sound events" ("horn", "bell1", "bell2", "engine", "air hose".) that loosely correspond to throttle button presses or other "triggering events". For example, the VSD file with the Nathan horn has a duplicate copy of the same EMD567 engine as the Leslie-horned loco. This version provides a nice, "clean" 1:1 relation between a locomotive and a VSD file, but you could end up with a lot of VSD files with a lot of duplication. If you want to have your loco with a Nathan horn instead of a Leslie, that's a different VSD file (or you edit the one you have and *replace* the horn sound). The VSD file also contains exactly one set of sound files that exactly corresponds to that one profile.
![jmri sample sound files jmri sample sound files](https://www.frontiersin.org/files/Articles/557680/fnins-14-00911-HTML/image_m/fnins-14-00911-g001.jpg)
Unless of course the prototype has two or three. I have a "tight" version and a "loose" version, would like to know which you prefer.Įach VSD file contains a profile the describes the sounds that go with exactly one locomotive. Have a question about the construction of the "VSD File", though. OK, so I've made a bunch of progress, will hope to have it added to JMRI (debug builds) in a few weeks. Would you prefer having a separate "simple panel" (above) floating around for each decoder, or would you prefer a single "VSD Manager" window, with all of the active decoders managed within that big window? Would like to know what folks preferences would be here.īIG QUESTION: I assume folks would like to have multiple sound decoders tied to multiple locomotives running. Now, I'm not sure how you'll access it, whether it'll be yet another button on the simple panel, or a button on the expanded panel, or a menu item, but there'll be another panel with sliders (an audio mixer, basically) to allow you to tweak the relative volume settings of the different sounds. Or if you just prefer to click the buttons directly on the decoder. This is for optional sounds that might not be mapped to throttle function keys. When you click that, the window grows to include another set of buttons below, to allow you to directly trigger sounds in the window.
![jmri sample sound files jmri sample sound files](https://www.jmri.org/help/en/package/jmri/jmrit/beantable/images/BlocksEditBasicTab.png)
Now, pretend the button marked "Sounds" is really one of those little "drop down" buttons. Once you've done that, the VSD will listen for any throttle attached to that loco, and will provide the sounds from the sound profile when you do things to the throttle. Otherwise, you can choose a different profile. If you have a sound profile assigned to the rostered loco, it will be set in the "Sound Pofile" box. Now, you either choose a loco from the roster, or you enter a loco address in the Address box (and click "Set"). OK, so you start JMRI and somewhere in the menus is "Virtual Sound Decoder". Where better to start than among my friends.
![jmri sample sound files jmri sample sound files](https://www.jmri.org/help/en/package/jmri/jmrix/loconet/sdfeditor/SdfInitSound.gif)
OK, so I'm working on this Virtual Sound Decoder thing, and I'm getting far enough along I need to bounce some ideas on a user interface off some actual users.