#JMRI DECODERPRO ZIP#

I plan on making my custom one available shortly, but until then, the sample one will make it possible to get used to them. JMRI comes with a sample VSD, which is enough to get used to it. You can then enter the number of the decoder you want the VSD to respond as (or choose one from your saved roster), and then choose the VSD file you want to use with the “Load VSD File” button and the dropdown that will be populated with sound profiles once you do. To use them, you fire up JMRI, open DecoderPro, choose Debug =>”VSDecoder Manager”, and then “Add Decoder”. VSDs work following the rather simple idea I had: pretending to be a sound decoder. It’s not perfect yet, and it’s not perfect for all situations, but I’m very excited about the promise of this technology. It’s coming from the speakers I had plugged into my laptop that was connected (via a Digitrax PR3) to my DCC system. Note, the sound in the videos is not overlaid. You can see some examples of it in action here.

A GP10 with a three chime Leslie RS-3L horn.

A GP7 with a single chime “honker” horn.

Playing with those files, and some sounds I got my hands on (I’m not revealing where yet, but hopefully more on a very useful resource shortly), I was able to relatively quickly put together a few of the decoder versions I could use: wav files) and a config XML file that maps decoder functions to the files.

#JMRI DECODERPRO ZIP#

Inside those zip files are the sound files (as plain old. A little more googling, and there was the answer: vsd files are just renamed zip files. Luckily, implementing technologies like VSD is exactly what I do for a living, so I figured I’d be able to make my own sound files soon enough. There’s a demo VSD file (the format that are used for the sound files), and it has some basics, but it wasn’t up to what I wanted. The only thing missing were good sounds for my fleet. I did some digging, and it turns out that Virtual Sound Decoders are exactly what I was looking to do. It turns out JMRI has it built in already, calling it Virtual Sound Decoders. Lo and behold, someone had already thought of it! It’d need a listener to listen for commands for specific addresses, it’d need a mapping utility to map sounds to commands, and it’d need some way to store and deal with the information. I figured I’d be able to build it into JMRI. Then I started thinking about how I would make something like that. I know a number of people have tried and done this, but it seemed like a waste of relatively expensive decoders on something that a computer should be able to do. That got me started thinking about using static sound decoders, installed under the layout, and powering larger speakers. When it comes to getting good sound out of N models, the limits of physics mean that you can only do so much. The other day I was thinking about sound on N scale model railroads. In this article, I’ll get started talking about my discoveries around them. Virtual Sound Decoders bring sound cheaply and easily to N scale models.

I am not a computer tech, but not a complete dummy.November 2021 update: I’ve added a link to my open sourced Conrail Engine VSD pack. Short of throwing all into Bass Strait, can anyone shed light on my issues. All of this after a complete clean of my compter (Lenovo laptop with WIN 11) and all that that entails.

I have tried an Uninstall, reboot x 4 and the same problem occurs. As soon as I attempt to ADD LOCO, the connection drops out. I have the first log on screen showing the connection stautus a connected.

I have just reinstalled JMRI onto Java 18. I doubt it has been tested against Java 18, and there’s a fair chance that it won’t currently work on Java18.įrom: JMRI DecoderPro problem. There’s a JMRI webpage pointing to the relevant installers. From: On Behalf Of Nigel Cliffe Sent: Sunday, 8:00 PM To: Subject: Re: JMRI DecoderPro problem.

Jmri decoderpro