Tips & Tricks For LokSound Programming (292)

LokSound decoders seem to be popping up almost everywhere today so it seems like a good opportunity to pass on some tips and tricks that will serve you well when it comes time to program yours. So sit back and get ready to see how to access all those indexed CVs and sound slots buried deep in that LokSound decoder.
Chapters
0:00 Intro
0:50 Programming options
1:40 The secret about new LokSound decoders
3:00 UK & EU approach
3:45 LokSound USA approach
4:30 Programming the CVs
6:48 LokProgrammer software
10:30 Dealing with sound slots
11:50 Creating the CV file
13:00 Saving the bulletin
15:15 DecoderPro-loading the CVs
18:17 Wrapup

[@What_If_We_Tried]

I am planning my first layout, and plan to go DCC, so this video is fantastic. Please consider activating your KZbin "Thanks" button so I can give you some coffee money.

[@peteengard9966]

A shout out to ESU. I bought a programmer way back when Loksound hit the shores of North America. ESU keeps it up to date with periodic updates. Most companies would have forced us to buy new equipment. Love my Loksound.

[@paparoysworkshop]

Tons of information. Thank you.

[@eXtremeFX2010]

I have used this technique you shared in a previous step by step video exporting the .txt file from the software then importing into that .txt into Decoder Pro. I did this for years and it worked successfully just took longer. But today I have a Programmer and goes so much smoother for my ESU installs.... But if you don't have the programmer this is an excellent tip and video I will share with many. Thank You Dcc Guy. Also... Matt from ESU and his sound collection Is absolutely FANTASTIC!

[@TJRohyans]

Clear as mud! 😂 Seriously though, I bought a new Atlas Alco S-2 about 4 years ago with the intention then of building a small switching layout, then never did. Now I've actually begun work on the layout but I haven't yet purchased my DCC system. So without a running system I can't really do anything with it yet. But I'll be saving this video to my "Favorites" for future reference.👍

[@TheDCCGuy]

Yes, it can be a bit challenging to wrap your brain around LokSound decoders until you have worked your way into them. Helps to start with a simpler decoder like SoundTraxx, familiarize yourself with the process then move up to LokSound. There are still things that I have to review again when I get into the deep end.

[@jcjackson726]

Wow, great video Larry. I didn't know you could import that file into Decoder Pro and it would work. Thank you for the "new" information! Keep the helpful videos coming! I look forward to your videos each week, they're a great end to my week and a great start to the weekend!

[@TheDCCGuy]

Remember, you’re just importing the CV settings not the sound file itself. Only the LokProgrammer hardware device can upload the actual sound project.

[@waynes3606]

Great timing, just getting into esu decoders, thanks, keep up the good work.

[@EdKuligowski]

Larry what a great video! Especially coupled with the videos on the basics of Decoder Pro. You have made it sooo easy for a newbie. My 1st time using Decoder Pro and also loading an ESU sound profile without a Lok Programmer. Keep up the great work and I always look forward to your latest vids.

[@ToccoaFallssRR]

Great information!

[@stuartaaron613]

I purchased my Lok Programmer and Decoder Tester back in 2015. I also had the hobby shop I worked at get them as well. I've done over 100 projects for myself and customers. One of the best investments I made. When ESU came out with "Full Throttle" I updated the decoders that I previously programmed with the new files. It also makes it easy to change the function mapping of the decoders. For example, I feel the Function 3 (F3) "coupler clank" is useless for me. So instead I change F3 to "Run 8." Now when I click on F3 the prime mover revs up to full throttle. On my diesels which do not have dynamic brakes I change F4 from "Dynamic Bakes" to "Drop to Idle" (or something like it). This way instead of dynamic brakes these engines will simply drop to idle when F4 is clicked.

[@TheDCCGuy]

Yes, for serious LokSound owners the LokProgrammer is the best option. As you point out ESU does offer sound project upgrades that require a LokProgrammer device. Glad to hear it is working out so well for you.

[@enriqueaguilar4892]

Great idea i like that loksound technology for ho locomotive's steam n diesel n g scale locomotives with sound technology it's worth the investment

[@epacm50]

This reminds me of loading new sound files via FTP. It's pretty simple to download.

[@jhoodfysh]

Excellent information Larry. I really would not be able to afford $150 for the sound decoder. Having to purchase it would mean I would have to trade off for something else (another locomotive for example). thank you.

[@Arch007]

What conection is used if you don’t use the loksound programer?

[@PLPLPLPPP]

Do you have any advice for programming decoders that are fitted to rolling stock rather than locos, such as for coach lighting, rear lights etc. many thanks

[@gsigs]

Yankee Dabbler also applies sound files to decoders you buy from them at no cost. Excellent service as well. For some reason, though, JMRI can read CVs from my Loksound decoders, but can't write them. Still working on that.

[@TheDCCGuy]

What DCC system are you using? Timing and programming track voltage can be an issue with some older systems but the new ones have compensated for that. Indexed CVS take longer to read/write. I had some initial issues like that several years ago but not with my newer DCC systems and newer versions of DecoderPro.

[@TheDCCGuy]

Yes, I imagine that most LokSound dealers offer that service, you just have to make sure to ask up front. A friend ordered several for his narrow gage steamers then called me asking how to select the steam sounds. He had actually purchased the default decoders with the clunky German diesel sounds so I had to explain the situation. Fortunately the dealer took them back and loaded the correct sound files for him.

[@gsigs]

@@TheDCCGuy I use a DCS 52 and I'm pretty sure my JMRI is up to date. I have no problems with Soundtraxx decoders, just Loksound. I'm currently reading all the CVs (takes forever) then I will try a reset.

[@TheDCCGuy]

Those are a relatively new system introduced in 2019 so I wouldn’t expect problems. Do you have the most recent firmware installed? If your unit is from early production they might have tweaked the programming capability. There was a firmware upgrade released in 2021.

[@luismencosguzman994]

Hello Larry, I would like to say thank you very much for your videos I have already reviewed almost all your tutorials. I am new using LokProgrammer and I am facing a situation that I cannot solve. I want to configure the braking sound on a decoder so that the wheels grind can be heard automatically when the loco gets stop. I have placed in the slot of “Break Sound” the sound I want, but without success, no breaking sound at all. I also configured in a separate slot the “Break Squeal” sound I want, I configured the transition from “Mute” to “Init” with an acceleration < -4 and I achieved the result I want for the sound but I have to press the function key every time the locomotive breaks for getting it. I want the loco does it automatically. Could you please advise or give me guidance? I have no found any info related. Thanks in advance for your support,

[@TheDCCGuy]

I’ve run into this issue before-drove me nuts at first. You have to increase the brake rate and keep moving it up until you get the sound you want. The longer it takes for the loco to stop the more brake sound you get. I’ll crank mine up tomorrow and check the value I use on my locos, can’t remember off the top of my head.

[@TheDCCGuy]

Ok, I got DecoderPro cranked up and I have CV3 and 4 set to 50 and 20 respectively. I have the automatic brake sound volume (CV 16.1.459) set to 80. I found these settings draw out the brake sounds long enough to produce good sounds. You may want to experiment with values of your own to find your sweet spot. I use DecoderPro for programming LokSound decoders once I get a project loaded and the initial CV settings transferred from LokProgrammer to DecoderPro. It is a lot easier to use.

[@luismencosguzman994]

@@TheDCCGuy Thanks a lot Larry. I will try it next weekend. My best regards.

[@luismencosguzman994]

​@@TheDCCGuy Hello Larry, I just want to say thank you very much. You have solved my sound issue. My loco break sound is working perfectly now. My best regards.

[@renezwart3201]

So how do you get the altered file (if you made changes in DecoderPro) back onto the decoder? That's what really important I think, but is not covered? Am I missing something? Cheers.

[@TheDCCGuy]

You send the changes to the decoder it the same as with any decoder using DecoderPro. You just can’t load a sound project with DecoderPro.

[@renezwart3201]

Great, so using a PR3 and DecoderPro for example you could program the ESU decoders except for the sound files? That is great news, thanks!@@TheDCCGuy

[@TheDCCGuy]

I do it all the time with my DCS240 which has a PR3/4 usb port built in to it. The main issue is as I said in the video is getting the default CV settings for the decoder from LokProgrammer in to DecoderPro. Once those are imported you can easily modify these and write to the decoder.

[@renezwart3201]

Larry, thanks, appreciate the expanded answer. I just didnt pick up on how to program the decoder after changing the settings. Knowing how to get the data from the decoder is now clear and helpful. Great, cheers!!@@TheDCCGuy

[@mikejames8192]

Have to wonder how ethical this is. Cant believe Mr ESU will be ecstatic that you are promoting the stealing of their sound files, manipulating settings on its software for use on a competitors programming software?

[@donaldshroyer8633]

Oh come on. The software is specifically designed to provide this functionality. Dah.

[@TheDCCGuy]

If they did not want you to do it they would not have included the ability to save a CV text file that you can then load into DecoderPro. Also no one is “stealing” the sound file, you are just transferring the CV settings to DecoderPro. If it helps sell decoders that’s what they are in business to do.

[@mikejames8192]

@@TheDCCGuy I fully understand what you are saying. I guess I'm wrong just doesn't seem right to me.

[@LaurenzEdelman]

The ability to use hardware and software from different manufacturers is a core feature of DCC. It is the whole reason DCC was created, instead of having many proprietary systems from different companies. Because of DCC you can buy decoders from any manufacturer and program CV's with your system of choice.

[@jamesbrown9761]

@@LaurenzEdelman Very good point. I also model in O Gauge and the proprietary nightmare that is Lionel really holds back that scale and is an almost insurmountable barrier to entry for new manufacturers IMHO.