File could not be parsed

[hervelemoal]

Hi all,

I'm using UMS on Debian 8,

some of my files aren't appearing on the http page (i.e http://localhost:9001)

all of them generates this kind of log trace :

TRACE 17:52:07.570 [pool-1-thread-3] Matched format FLAC to "/data/musique/Alt-J/ThisIsAllYours/01 - Intro.flac"
INFO 17:52:07.592 [pool-1-thread-3] The file /data/musique/Alt-J/ThisIsAllYours/01 - Intro.flac could not be parsed. It will be hidden

Do you have an idea where I should look for ?

P.S : I've read the "debug trace how to", but using headless version, I'm not very sure about generating "zip debug package", do you need others information?

Regards

[michaelt]

Do you have an idea where I should look for ?

First: the 'Parse' error just means the 'parse' function returned an error. This is one error which has nothing to do with parsing or data other than the bit stream bandwidth check failed.

You might want to try two things:

• 1 - General Configuration->Network Settings->[Uncheck]Use Automatic, Set Max BW higher
  2 - In your renderer .config file set MaxVideoBitrateMbps higher

The auto setting 'measures' your connection and sets your max bandwidth along with the value in the .conf file. The result is compared to the value found in the video. If not high enough, it rejects it and 'hides' it.

I set my Max BW to 200, the .conf value from 25 to 80 and noted the max video BitRate in my videos (all Blu-ray ) is 39.4. Any value lower than 80 drops some video titles. I stream fine with no issues other than Avatar (working on it).

[hervelemoal]

First, I would like to thank you about the time you've taken to make me an answer,

I'm on a linux UMS installation and the setting you mentioned is not activated by default, see /etc/UMS.conf (extract):

# Maximum bandwidth in Mb/s
# -------------------------
# Set the maximum bandwidth to be consumed by the server.
# Leaving the setting blank or zero switches off bandwidth throttling.
# Default: 90
maximum_bitrate =

# Use automatic maximum bandwidth
# -------------------------------
# When this setting is enabled, we estimate the speed of the connection to the
# renderer and limit the bandwidth accordingly.
# Default: false
automatic_maximum_bitrate =

anyway I've made a try reducing maximum_bitrate to 20 Mb/s and nothing's changed.

I don't know anything about UMS, but, from my understanding I don't see the relationship between parsing files error and bandwidth (but perhaps I'm wrong )

Can somebody gives me information about the way to provide a "zip debug package" like on linux ?? (just a tarball of the logs ? start UMS with others options ??, please tell me)

Regards

[hervelemoal]

I've done another test :

one of the non-parsed file was : "01 - Intro.flac"

I just renamed the file to "01_Intro.flac" (with no space)

in result the file is parsed now....

It shows that there something to set like a charset, but for the moment and don't know how ....

The search goes on .....

[michaelt]

one of the non-parsed file was : "01 - Intro.flac"

I just renamed the file to "01_Intro.flac" (with no space)

Oh yes - missed that point. In the "parse()' routine it does a bunch of tests which, if they fail, all report "parse error". Very misleading. The bandwidth issue was my main one, a secondary one was Title (file) name character issues:

• any illegal characters in a title will cause the "Open()" to fail and "parse error"

On Mac OSX 10.7.5 there are only two: '*' and '?'. I have not fired up my linux box yet but the first test will be to identify the illegal characters. The process is simple if you are not afraid of a few CLI (command line) commands.

Open a shell (terminal, CLI, …) window and copy this code, replacing "Pathname" with the pathname to your Titles and "AGoodTitle" with a Title that plays.

Code: Select all

cd  Pathname
ln -s AGoodTitle XXXX
ls -lLi AGoodTitle XXXX

The "ls" must show the same data for both except for the name like this:

Code: Select all

$ ls -lLi Skyfall.mkv XXXX
744 -rw-r--r--  1 umsmkv  staff  6910433637 Feb  8 15:23 Skyfall.flac
744 -rw-r--r--  1 umsmkv  staff  6910433637 Feb  8 15:23 XXXX

Now copy and paste all this into the same window:

Code: Select all

mkdir TestChars
cd TestChars
# Test the the single quote first:
ln -s ../XXXX "Test'Char.flac"
# Now all the rest
ln -s ../XXXX 'Test!Char.flac'
ln -s ../XXXX '[email protected]'
ln -s ../XXXX 'Test#Char.flac'
ln -s ../XXXX 'Test$Char.flac'
ln -s ../XXXX 'Test%Char.flac'
ln -s ../XXXX 'Test^Char.flac'
ln -s ../XXXX 'Test&Char.flac'
ln -s ../XXXX 'Test*Char.flac'
ln -s ../XXXX 'Test(Char.flac'
ln -s ../XXXX 'Test)Char.flac'
ln -s ../XXXX 'Test-Char.flac'
ln -s ../XXXX 'Test_Char.flac'
ln -s ../XXXX 'Test=Char.flac'
ln -s ../XXXX 'Test+Char.flac'
ln -s ../XXXX 'Test[Char.flac'
ln -s ../XXXX 'Test{Char.flac'
ln -s ../XXXX 'Test]Char.flac'
ln -s ../XXXX 'Test}Char.flac'
ln -s ../XXXX 'Test\Char.flac'
ln -s ../XXXX 'Test|Char.flac'
ln -s ../XXXX 'Test;Char.flac'
ln -s ../XXXX 'Test:Char.flac'
ln -s ../XXXX 'Test"Char.flac'
ln -s ../XXXX 'Test,Char.flac'
ln -s ../XXXX 'Test<Char.flac'
ln -s ../XXXX 'Test.Char.flac'
ln -s ../XXXX 'Test>Char.flac'
ln -s ../XXXX 'Test/Char.flac'
ln -s ../XXXX 'Test?Char.flac'
ln -s ../XXXX 'Test`Char.flac'
ln -s ../XXXX 'Test~Char.flac'
ln -s ../XXXX 'Test Char.flac'

If any of these commands fail, it is an illegal character (e.g. on OSX slash /, your ??nix space ' ').

Now run UMS and navigate into the TestChars folder. Your Log will list all the "parse errors" and "hiding" for the illegal characters.
You got the list - avoid them when naming.

When done, copy and paste this into the same window to clean up:

Code: Select all

cd ..
rm -rf TestChars XXXX

Note: in my system the ripping is done in a script where the title is derived from the UPC and the illegal characters are mapped to the underscore (_). Problem solved.

Sorry for the length of this but I am not sure of your *nix skills and the time to go back & forth but this was faster than me lighting up ubuntu, updating, installing UMS and testing.

Enjoy - hope it helped.

Please let me know what Linux system you are running and what illegal characters you found.
Might want to put system details in your signature so all will know for issues.

[hervelemoal]

Hi

thanks for your feedback !

I've just done the test and finally only space ' ' and star * is problematic,

I'm running a Debian Jessy on an Atom D510.

I am quite happy about your feedback thanks again, respect

P.S to be really precise if anybody reads that : Please note that this help, let me now see some files in UMS browser. It don't solve anything about playing flac files on my linux headless system. (other thread open elsewhere without any answer)

[michaelt]

Good - enjoy!