kdf Wrote: > On 1-Jan-06, at 9:52 AM, Michaelwagner wrote: > if it is a perl interpreter failure, I expect that any method > slimserver could use to test (thus relying on perl) might still cause > perl to see the 261 characters. > > Lets not forget issue #3: bad setup of EAC. The CUE and the audio file > > should be appearing in the same folder. Even if perl can stop crashing > > over it, you'll want the music to index properly. > > -kdf Although I am not a Perl developer, I expect the Perl failure is occuring when the script attempts to look for a file whose path exceeds the OS maximum. I would expect a string in Perl could contain well in excess of 261 characters, so it should be feasible to validate the length of the path before attempting to test for the presence of the file.
I agree regarding the EAC config... -- veloearl ------------------------------------------------------------------------ veloearl's Profile: http://forums.slimdevices.com/member.php?userid=3045 View this thread: http://forums.slimdevices.com/showthread.php?t=19555 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
