[ sox-Feature Requests-2037990 ] soxrc

[ sox-Feature Requests-2037990 ] soxrc

[SourceForge.net]

Feature Requests item #2037990, was opened at 2008-08-04 13:20
Message generated for change (Comment added) made by janstary
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360706&aid=2037990&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: robs (robs)
Assigned to: Nobody/Anonymous (nobody)
Summary: soxrc

Initial Comment:
See attached.

----------------------------------------------------------------------

Comment By: Jan Starý (janstary)
Date: 2013-02-02 14:26

Message:
Has this ever been implemetned?
The manpage doesn't mention a ~/.soxrc file



----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2009-03-23 01:42

Message:
Note that we now have SOX_OPTS (which doesn't necessarily supersede
soxrc/sox.conf but may reduce its priority).

----------------------------------------------------------------------

Comment By: Chris Bagwell (cbagwell)
Date: 2008-10-26 10:54

Message:
A note about a related feature.  SoX 14.2.0 will have a new --effects-file
option.  It reads a file and uses its contents just like user specified it
on the command line.  Adding a --files-file that works in the vein but for
filenames and related options wouldn't be to hard to add.  The main problem
with current code though is that they are used in place of and not a
complement of command line options.

Reviewing the sample config file and requests for url/format specific
default, I think the real requests seems to be limited to auto-setting
--options and not so much short hands for filenames or effect names.  Since
we have the --effects-file now, who ever adds this can concentrate on just
fixed and conditional option setting.

I looked at libpopt a little bit and seems like it would be about the same
amount of work to write custom alias support in a custom config file then
it would to reorganize our internals to support it.  The custom version
would be much more flexible as well.  libpopt is a nice concept though over
all.

----------------------------------------------------------------------

Comment By: Reuben Thomas (rrt)
Date: 2008-09-22 17:15

Message:
A comment on the sample rc file: sometimes you say "similar to" a given
command line option. The rc options should be *identical to* command line
options, and the parsers automatically generated from the same source. I
suggest that lines should look like this:

[EFFECT|FORMAT =]OPTION...

which means: for the given effect or format, use the relevant options (or
if none is specified, always use them).

You could add some pseudo-effect or format options. For example, for my
use, I'd like to specify a large input buffer, but only when reading from
the internet, so a "url" pseudo-format could be used:

url = input-buffer=1000000

I suggest you look into using libpopt, as it already provides support for
configuration files using command-line arguments.

----------------------------------------------------------------------

Comment By: Reuben Thomas (rrt)
Date: 2008-09-22 17:10

Message:
I want this too: I want to be able to specify a large input buffer when
playing URLs.

As far as the name goes, ".conf" is more logical, even if "rc" has
historical currency. But it's not very important.

----------------------------------------------------------------------

Comment By: Pascal Giard (evilynux)
Date: 2008-08-04 13:50

Message:
Logged In: YES 
user_id=36773
Originator: NO

I'm not arguing the feature itself but wondering why not use a sox.conf
filename instead of the less frequently used *rc filename?


----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2008-08-04 13:21

Message:
Logged In: YES 
user_id=27473
Originator: YES

See attached file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360706&aid=2037990&group_id=10706

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

[ sox-Feature Requests-2037990 ] soxrc

[SourceForge.net]

Feature Requests item #2037990, was opened at 2008-08-04 13:20
Message generated for change (Comment added) made by robs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360706&aid=2037990&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: robs (robs)
Assigned to: Nobody/Anonymous (nobody)
Summary: soxrc

Initial Comment:
See attached.

----------------------------------------------------------------------

>Comment By: robs (robs)
Date: 2013-02-03 02:03

Message:
No, it's not been implemented; still looks that, to some extent, it's
useful to do so.

----------------------------------------------------------------------

Comment By: Jan Starý (janstary)
Date: 2013-02-02 14:26

Message:
Has this ever been implemetned?
The manpage doesn't mention a ~/.soxrc file



----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2009-03-23 01:42

Message:
Note that we now have SOX_OPTS (which doesn't necessarily supersede
soxrc/sox.conf but may reduce its priority).

----------------------------------------------------------------------

Comment By: Chris Bagwell (cbagwell)
Date: 2008-10-26 10:54

Message:
A note about a related feature.  SoX 14.2.0 will have a new --effects-file
option.  It reads a file and uses its contents just like user specified it
on the command line.  Adding a --files-file that works in the vein but for
filenames and related options wouldn't be to hard to add.  The main problem
with current code though is that they are used in place of and not a
complement of command line options.

Reviewing the sample config file and requests for url/format specific
default, I think the real requests seems to be limited to auto-setting
--options and not so much short hands for filenames or effect names.  Since
we have the --effects-file now, who ever adds this can concentrate on just
fixed and conditional option setting.

I looked at libpopt a little bit and seems like it would be about the same
amount of work to write custom alias support in a custom config file then
it would to reorganize our internals to support it.  The custom version
would be much more flexible as well.  libpopt is a nice concept though over
all.

----------------------------------------------------------------------

Comment By: Reuben Thomas (rrt)
Date: 2008-09-22 17:15

Message:
A comment on the sample rc file: sometimes you say "similar to" a given
command line option. The rc options should be *identical to* command line
options, and the parsers automatically generated from the same source. I
suggest that lines should look like this:

[EFFECT|FORMAT =]OPTION...

which means: for the given effect or format, use the relevant options (or
if none is specified, always use them).

You could add some pseudo-effect or format options. For example, for my
use, I'd like to specify a large input buffer, but only when reading from
the internet, so a "url" pseudo-format could be used:

url = input-buffer=1000000

I suggest you look into using libpopt, as it already provides support for
configuration files using command-line arguments.

----------------------------------------------------------------------

Comment By: Reuben Thomas (rrt)
Date: 2008-09-22 17:10

Message:
I want this too: I want to be able to specify a large input buffer when
playing URLs.

As far as the name goes, ".conf" is more logical, even if "rc" has
historical currency. But it's not very important.

----------------------------------------------------------------------

Comment By: Pascal Giard (evilynux)
Date: 2008-08-04 13:50

Message:
Logged In: YES 
user_id=36773
Originator: NO

I'm not arguing the feature itself but wondering why not use a sox.conf
filename instead of the less frequently used *rc filename?


----------------------------------------------------------------------

Comment By: robs (robs)
Date: 2008-08-04 13:21

Message:
Logged In: YES 
user_id=27473
Originator: YES

See attached file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=360706&aid=2037990&group_id=10706

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel