Phuang3 wrote:
> Issue reported. Thank you all!
Just found this thread by search. I think i am having a similar issue
(running on Win10-64). I have a 192/24 flac album that measures 1.99Gb.
LMS chokes on it and won't play (all other flac are Ok). I tried
downloading the latest nightly (7.9.1
Issue reported. Thank you all!
Phuang3's Profile: http://forums.slimdevices.com/member.php?userid=66974
View this thread: http://forums.slimdevices.com/showthread.php?t=108131
Phuang3 wrote:
Thank you. I guess we have to wait for the fix. I'm surprised I'm the
only one having this problem here. How can I report this problem?
Send a PM to mherger but as you are the only person with this problem,
it may not be top priority.
You better get a bug report to the
Phuang3 wrote:
> Thank you. I guess we have to wait for the fix. I'm surprised I'm the
> only one having this problem here. How can I report this problem?
Send a PM to mherger but as you are the only person with this problem,
it may not be top priority.
Thank you. I guess we have to wait for the fix. I'm surprised I'm the
only one having this problem here. How can I report this problem?
Poting
Phuang3's Profile: http://forums.slimdevices.com/member.php?userid=66974
View
I have pinned down the problem to the Audio::scan module. This module is
OK on Linux but on Windows for the large 192Khz Flac file - the module
returned no data so getTag returns undef and so no track details.
I suspect the root problem is the file size (>2Gb) and this only shows
with high
This is only on Windows.
The problem can be clearly checked - if using Web UI - drill down Track
Info in a track of the 192kHz CUE album - the track do not have
samplerate or sample size info. Whereas the same large single flac file
resampled to a 48Khz with exact same CUE sheet - the tracks
The issues is a Windows specific problem and it has nothing to do with
file size or path. It occurs when resampling is required for the player
of a cue sheet file.
bpa's Profile:
Phuang3 wrote:
> Original content was individual flac per track. I merged them into
> single flac with Xrecode or Foobar2000 (tried both). After some
> googling, I found people complaining about windows flac.exe not being
> able to handle 2GB+ size correctly. I'm not sure if this is the cause.
>
bpa wrote:
> I don't use Windows normally - I'll have to look around to see if I can
> find a system.
>
> You still have not answered my question - how did you create the 192/24
> Flac file ? What utliity was used - some 3rd party application have
> produced "incorrect" flac file ? It is
Mnyb wrote:
> Daphile on windows 10 ? As you changed the version of flac used by LMS
> you have not Oslo changed SoX or use custom convert settings or files ?
> Or the 3CPO plugin ?
The issues is not related to Flac.exe or sox.exe as LMS is not
calculating offset and size correctly - this seems
Phuang3 wrote:
> It was not on Daphile. It was on Windows 10 + LMS 7.9.1. The "Daphile"
> you saw on my log is the player (LMS client) only. (Daphile= Linux + LMS
> client + LMS server) I already turned off LMS service on the player and
> sourced from another LMS instance on a windows PC.
Mnyb wrote:
> Daphile on windows 10 ? As you changed the version of flac used by LMS
> you have not Oslo changed SoX or use custom convert settings or files ?
> Or the 3CPO plugin ?
Hi Mnyb,
I did not change anything until this problem show up. Both stock
flac.exe and latest version were
bpa wrote:
> I created a test file of 2,310,172,573 bytes by resampling to
> 192Khz/24bit from a single flac file of a CD scan with external cue
> sheet. My Ubuntu based LMS 7.9.1 handled the file/tracks correctly -
> jumping to any track. So I'm guessing the problem is something to do
> with
Daphile on windows 10 ? As you changed the version of flac used by LMS
you have not Oslo changed SoX or use custom convert settings or files ?
Or the 3CPO plugin ?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621
I created a test file of 2,310,172,573 bytes by resampling to
192Khz/24bit from a single flac file of a CD scan with external cue
sheet. My LMS 7.9.1 handled the file/tracks correctly - jumping to any
track. So I'm guessing the problem is something to do with daphile or
something subtle with
Phuang3 wrote:
> Hi bpa,
>
> I generate the CUE sheet through Xrecode or Foobar2000. I don't think
> the CUE sheet is the cause, because I resampled (down sized) the flac
> and the problem was gone. Here are my CUE sheet & logs.
How was the flac file created ? IIRC Some 3rd party Flac
Hi bpa,
I generate the CUE sheet through Xrecode or Foobar2000. I don't think
the CUE sheet is the cause, because I resampled (down sized) the flac
and the problem was gone. Here are my CUE sheet & logs.
Poting
Code:
REM GENRE "Pop"
REM DATE 2001
TITLE "A BEST
How was the file and cue sheet created ?
Flac files are normally played natively by the player - I assume that is
your setup - in which case "Transcoding" is not an issue. I don't know
cue sheet specific but in general Flac files and playlist are analysed
and then "seeks" are performed by LMS
Hi Guys,
The LMS was installed on a Windows 10 X64 machine and the music folder
is on a local NTFS disk. It can seek tracks on 2GB+ wavpack without
problem, but not the FLAC. I replaced the stock flac 1.2.0 with 1.3.2,
but it didn't help. So, I revert it back to stock version. I suspect the
How do you check that you have Flac version 1.3.2 ?
The Flac version shipped with LMS is 1.2.1 (with LMS specfici pathes)
and it is the version of Flac in the Bin directory that will be first
used - not the verson in some other directory. If you are not using the
version of Flac suplied with
It does sound lke an OS/File system/32bitvs64 bit issue issue - for
example Fat16 has 2Gb file size limit.
Alternatively there may be a bug/mismatch in the file creator - how was
the file created ? Was it created using Flac or another application ?
You don't need to use the correct title as filename even if you use tags
, you can use some English title but still have Chinese tags .
Browse album and browse artist etc only cares for tags or cue sheet
content .
That said 2GB sound almost like a file system disk format or OS issue ?
What is
Julf wrote:
> Just curious as to why? It makes things more complicated, and I can't
> see any benefit.
Just want to reduce the file count, and most importantly I have lots
albums from Asia. Using the title as file name could be a problem for
for some players.
External cue sheet can be easily
Phuang3 wrote:
> Yes, I prefer single FLAC with external cue sheet.
Just curious as to why? It makes things more complicated, and I can't
see any benefit.
"To try to judge the real from the false will always be hard. In this
fast-growing art of 'high fidelity' the quackery will bear a solid
Julf wrote:
> 2Gb+ single file? Ouch!
Yes, I prefer single FLAC with external cue sheet. Unfortunately, most
192k music albums are larger than 2GB.
Phuang3's Profile:
Phuang3 wrote:
> It turns out the LMS has problem analyzing 2GB+ FLACs. I played another
> smaller FLAC (1.3GB) and the track seeking is functional.
2Gb+ single file? Ouch!
"To try to judge the real from the false will always be hard. In this
fast-growing art of 'high fidelity' the quackery
It turns out the LMS has problem analyzing 2GB+ FLACs. I played another
smaller FLAC (1.3GB) and the track seeking is functional. (My flac.exe
is 1.3.2 64bit version) Strangely, 2GB+ wavpack can be analyzed and
played.
Poting
mherger wrote:
> > [17-10-14 19:42:04.7867] Slim::Player::Protocols::File::open
> (193) Error: could not seek to -1 for E:\MyMusic\ÃñT¨B\2001 - A
> BEST\CDImage.flac: Invalid argument
>
> Looks like yet another path encoding issue... the cue sheet is referring
>
> to a file it can't
[17-10-14 19:42:04.7867] Slim::Player::Protocols::File::open (193) Error:
could not seek to -1 for E:\MyMusic\ÀرT¨B\2001 - A BEST\CDImage.flac: Invalid
argument
Looks like yet another path encoding issue... the cue sheet is referring
to a file it can't find because the encoding is
30 matches
Mail list logo
