[remix-api] Issue 52 in echo-nest-remix: Verbosity should be changed to cut down on amount of output.

3 views
Skip to first unread message

echo-ne...@googlecode.com

unread,
May 24, 2010, 8:22:05 PM5/24/10
to remi...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 52 by knifacat: Verbosity should be changed to cut down on amount
of output.
http://code.google.com/p/echo-nest-remix/issues/detail?id=52

There is /far/ too much output by default. Perhaps a global setting for
verbosity could be created?

Specifically, you cannot change the verbosity of the output from
echonest.action.render() since it doesn't have an argument for it, so the
command line parameters for en-ffmpeg is always shown until you edit the
module itself.

This is r444.


--
You received this message because you are subscribed to the Google Groups "The Echo Nest Remix API" group.
To post to this group, send email to remi...@googlegroups.com.
To unsubscribe from this group, send email to remix-api+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/remix-api?hl=en.

echo-ne...@googlecode.com

unread,
May 29, 2010, 10:01:01 AM5/29/10
to remi...@googlegroups.com
Updates:
Status: Accepted

Comment #1 on issue 52 by brianawhitman: Verbosity should be changed to cut

(No comment was entered for this change.)

echo-ne...@googlecode.com

unread,
Mar 28, 2011, 5:05:29 PM3/28/11
to remi...@googlegroups.com

Comment #2 on issue 52 by blac...@echonest.com: Verbosity should be changed

With r502, echonest.action.render() takes a "verbose" argument. The example
scripts that use this function have been changed for more thorough control
of verbosity; if they are called without the --verbose option, there will
be no printed output at all.

echo-ne...@googlecode.com

unread,
Mar 28, 2011, 5:09:33 PM3/28/11
to remi...@googlegroups.com
Updates:
Status: Fixed

Comment #3 on issue 52 by blac...@echonest.com: Verbosity should be changed

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages