Wirrunna,
Thanks for that.
This is going to sound like nit-picking of the highest order - and I
apologise for that.
A few words of caution though.
We are in a situation where many people using Inguz have probably
updated their Plugin.pm and custom-convert.conf (which is re-generated
by Plugin.pm) for their own particular requirements. (For example the
"alc" section in your Plugin.pm is broken.) If your new Plugin.pm is
used "as is" it might well knock out something else that has been
previously tweaked.
The zip file contains:
install.xml
custom-types.conf
Plugin.pm
They all have CRLF line endings which might possibly cause problems with
non-Windows sytems such as Ubuntu, etc. The original files had LF line
endings and I think it is best to maintain that for compatibility.
install.xml
The only change in this is to the version number. While it is obviously
a good idea to have version numbers, in the current situation where no
one person is responsible for Inguz and where various people are making
their own amendments to Plugin.pm, etc changing version numbers might
get confusing - just a thought.
custom-types.conf
You have changed the "aap" entry to "aac". In my experience there is no
need for an "aac" entry in the Inguz custom-types.conf as it already
specified in the LMS "types.conf". The "aap" entry becomes redundant but
does no harm.
Plugin.pm
See my earlier comments.
It might be a good idea for someone to try to pull together a Plugin.pm
which contains the necessary corrections and additional entries that
people have made over the years and to have that as a reference.
However, that is much easier said than done but I will try to do a bit
of research over the coming week (unless someone else would like to do
it).
In the mean time I think it is probably best to give people the choice
of replacing the Plugin.pm (the other files are not really necessary) or
editing the entries in their existing files.
Edit with Wordpad or an editor that supports "LF" line endings.
_Plugin.pm_
In the last section headed "# transcode for 24-bit FLAC output (sb2,
sb3, transporter)"
(This is at the end of the file.)
Replace the aap entry with:
Code:
--------------------
aac flc * $CLIENTID$
# IFT
[faad] -q -w -f 1 $FILE$ | [InguzDSP] -id "$CLIENTID$" -wav -wavo -d 24
| [flac] -cs -0 --totally-silent -
--------------------
_custom-convert.conf:
_
The aap entry would be replaced by:
Code:
--------------------
aac flc * XX:XX:XX:XX:XX:XX
# IFT
[faad] -q -w -f 1 $FILE$ | [InguzDSP] -id "XX:XX:XX:XX:XX:XX" -wav
-wavo -d 24 | [flac] -cs -0 --totally-silent -
--------------------
(Where "XX:XX:XX:XX:XX:XX" represents the player's MAC address)
Of course, edits to the Inguz custom-convert.conf file will take
immediate effect once LMS is restarted. BUT the Inguz
custom-convert.conf file will eventually be overwritten with a
re-generated custom-convert.conf file from the entries in Plugin.pm,
e.g. if Inguz is de-enabled and then re-enabled in the LMS Plugins, etc,
etc.
Touch, Meridian G92, Bryston B4 SST2, PMC OB1i speakers, HP Proliant
Microserver/Ubuntu, PC/Windows 7, iPad 4, iPeng, Squeezepad.
------------------------------------------------------------------------
JohnB's Profile: http://forums.slimdevices.com/member.php?userid=31553
View this thread: http://forums.slimdevices.com/showthread.php?t=77084
_______________________________________________
audiophiles mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/audiophiles
