Re: [Jmri-developers] Debugging help on VSD?

[<tw...@pe...>]

Oh, I forgot to say, also enable log4j.category.jmri.jmrit.audio=DEBUG
when you run the test.

And DO NOT actually PLAY any sounds.  Just move the volume slider.

If the sounds are playing while audio=DEBUG, the stuff I want to see will
be buried in a mountain of debug data.



> Can I ask one of you with access to a Windows box to capture some debug
> for me?
>
> Try this, and capture the output from log.debug() wherever it comes out on
> your system.
>
> 1) in default.lcf set log4j.category.jmri.jmrit.vsdecoder=DEBUG
> 2) Launch DecoderPro
> 3) Choose Debug->Virtual Sound Decoder
> 4) Choose File->Load VSD File and load example.vsd
> 5) In the window, select the GE 7FDL Profile
> 6) Move the volume slider at the bottom of the VSD window its full range.
>
> I have some people reporting that if you slide the volume all the way to
> the 100% limit, the sound cuts out, then returns if you pull it back.  I
> cannot reproduce this on my Mac, and from what I can see in the debug
> output on my Mac, I am doing the gain calculations correctly in response
> to the slider.  So I want to see what the Windows box is doing in the VSD
> code to help track this down.
>
> Thanks in advance for your help.
>
> - Mark
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>