[Cs-dev] Doppler Opcode - Excessive Messages
Date | 2014-04-21 17:33 |
From | Steven Yi |
Subject | [Cs-dev] Doppler Opcode - Excessive Messages |
Hi All, I'm diagnosing an issue with a Blue user's project that uses the doppler opcode. It looks like doppler gives a message like this every k-period: 31 Doppler::kontrol: sizeof(MYFLT): 8 Doppler::kontrol: PI: 3.142 Doppler::kontrol: this: 0x13da7cb70 Doppler::kontrol: sampleRate: 48000.000 Doppler::kontrol: blockSize: 48000.000 Doppler::kontrol: blockRate: 480.000 Doppler::kontrol: speedOfSound: 345.000 Doppler::kontrol: samplesPerDistance: 139.130 Doppler::kontrol: smoothingFilterCutoff: 6.000 Doppler::kontrol: kMicPosition: 0.000 Doppler::kontrol: kSourcePosition: 25.194 Is there a way to turn this off by default and turn on only when necessary? steven ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2014-04-21 18:08 |
From | Michael Gogins |
Subject | Re: [Cs-dev] Doppler Opcode - Excessive Messages |
Attachments | None None |
These messages should only appear when warnings are turned on. I will check that. I think this and some other cases indicate a need for a level of printing in between warning and debug, say, info.
Best, Mike -----------------------------------------------------
Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Apr 21, 2014 at 12:33 PM, Steven Yi <stevenyi@gmail.com> wrote: Hi All, |
Date | 2014-04-22 17:23 |
From | Steven Yi |
Subject | Re: [Cs-dev] Doppler Opcode - Excessive Messages |
Hi Michael, Thanks for looking into this. I think having WARN, INFO, and ERROR message formats would be good. This seems common among logging frameworks. Perhaps too we might make some opcodes, something like: log_warn "message" log_info "message" log_error "error" log_set_level iVal that would match up with logging in the C/C++ side. steven On Mon, Apr 21, 2014 at 1:08 PM, Michael Gogins |
Date | 2014-04-22 17:45 |
From | Michael Gogins |
Subject | Re: [Cs-dev] Doppler Opcode - Excessive Messages |
Attachments | None None |
I think your opcode idea is great. Best, Mike -----------------------------------------------------
Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Tue, Apr 22, 2014 at 12:23 PM, Steven Yi <stevenyi@gmail.com> wrote: Hi Michael, |