Why Boxee Box scrapping by Title when <id> is specified in .NFO?

[mbryanr]

This is the ticket where users became aware of the issue, and resulting comments...
http://jira.boxee.tv/browse/BOXEE-10550

[drunkwithpower]

As I found out by myself from my TV serial ID issue jira.

1. If <ID> tag is persent in nfo, boxee ignore ALL information in nfo,scrap everything from boxee ID server(Terrible for TV serial and privacy issue).

2. If <ID> is NOT present in nfo. Boxee will fill the information from NFO without access Boxee ID server(Which have far less trouble if you scrap TV/Movie with something like Ember then remove <ID> from NFO file)

So what is the easiest way to remove the ID tag from an Ember file when you have 1,000s of them?

[painkiller]

So what is the easiest way to remove the ID tag from an Ember file when you have 1,000s of them?

Luckly, I have much less nfo to deal with. But I still think Boxee is one doing wrong thing here.They should fix it(I have no faith on them at all) instead of Ember.

[Wizzzard]

As I found out by myself from my TV serial ID issue jira.

1. If <ID> tag is persent in nfo, boxee ignore ALL information in nfo,scrap everything from boxee ID server(Terrible for TV serial and privacy issue).

2. If <ID> is NOT present in nfo. Boxee will fill the information from NFO without access Boxee ID server(Which have far less trouble if you scrap TV/Movie with something like Ember then remove <ID> from NFO file)

I will give this a try when i'm home!! Thanks for the info!

[boxee44]

I will give this a try when i'm home!! Thanks for the info!

Me too, this actually sounds quite interesting.
Does omitting the ID element speed up the time it takes for Boxee to do resolving?

I can easily write a script to take that ID element out of all of my nfo XML files.
Is it really worth doing this?

[drunkwithpower]

Me too, this actually sounds quite interesting.
Does omitting the ID element speed up the time it takes for Boxee to do resolving?

I can easily write a script to take that ID element out of all of my nfo XML files.
Is it really worth doing this?

It would be to me...

[eug7]

This is the screwiest product I have ever used. I have 2 Boxee Boxes.

I used to be able to use a common ID to stack multi-part movies and extras under one cover like this:

MyMovie (1980) Part 1.mkv
MyMovie (1980) Part 1.nfo
MyMovie (1980) Part 1.tbn
MyMovie (1980) Part 2.mkv
MyMovie (1980) Part 2.nfo

They they updated the firmware at some point and most of the titles using this scheme started to duplicate the covers (no longer under one cover).

I had this idea that if I create a tbn for part 2 maybe that was the solution (didn't have to do that at first) and it worked. All movies stacked under one cover. Then the latest 1.5 and boom, back to duplicates.

As someone said, so much potential and yet it performs like a dud product. This is only one of a variety of problems that creep up when using the box. Such a pathetic user experience.

[yoos]

yea, stacking is messed up in a few different ways... It does what you are saying for me some times, but not all the time. It's inconsistent... There are other stacking problems with iso's too.

[eug7]

Really, how do they expect us customers to use their product. It's like trying to drive a car on the freeway with a flat tire. I don't think they feel our pain.

This is like the anti-Apple company. If Apple goes to great lengths to balance their product designs and provide a pleasant user experience it seems Boxee is going out of their way to annoy their customers to the max.

[yoos]

Me too, this actually sounds quite interesting.
Does omitting the ID element speed up the time it takes for Boxee to do resolving?

I can easily write a script to take that ID element out of all of my nfo XML files.
Is it really worth doing this?

I think someone recently wrote a script just for this.... Maybe it was for something else and I'm mistaken??? It's on the forum tho somewhere if you search for script nfo probably.