I don't want the log file but the line you are interested in is
Code:
--------------------
[10-02-04 12:06:33.1265]
Slim::Player::TranscodingHelper::tokenizeConvertCommand2 (536) Using command
for conversion:
"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\WaveInput\Bin\wavin2cmd.exe"
-m 8192 -o "wavin:0" |
"C:\PROGRA~1\SQUEEZ~1\server\Bin\MSWin32-x86-multi-thread\flac.exe" -cs
--totally-silent --compression-level-0 --endian=little --sign=signed
--channels=2 --sample-rate=44100 --bps=16 -
[10-02-04 12:06:33.1311] Slim::Player::Pipeline::new (93) Launching process
with command:
"C:\PROGRA~1\SQUEEZ~1\server\Bin\MSWin32-x86-multi-thread\socketwrapper.exe"
-D -w -o 64217 -c
"\"C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\WaveInput\Bin\wavin2cmd.exe\"
-m 8192 -o \"wavin:0\" |
\"C:\PROGRA~1\SQUEEZ~1\server\Bin\MSWin32-x86-multi-thread\flac.exe\" -cs
--totally-silent --compression-level-0 --endian=little --sign=signed
--channels=2 --sample-rate=44100 --bps=16 -"
--------------------
You can see the "-m 8192 " is being used.
Security s/w can cause delays as they get paranoid about the
interprocess comms and try to examine the audio streams.
You may be able to see where the delay could be happening by enabling
logging of player.streaming to DEBUG and make sure you log at least 15
secs after you hear first sound. It is easiest to have music playing on
PC before you start the test so that you actually know the delay.
--
bpa
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=74848
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
