(2013-03-12, 16:28)deh2k7 Wrote: (2013-03-12, 14:39)orbtwin Wrote: i think i'm missing something.
i have several mini-series and tv-movies multipart.
Named like this:
in ember setting i have checked <movie>.nfo (stack) but i get new files named like:
*Children of Dune.dvd (2000).avi
*Children of Dune (CD 2).avi
*Children of Dune (CD 3).avi
*Children of Dune.dvd (2000)-fanart.jpg
*Children of Dune.dvd (2000)-poster.jpg
*Children of Dune.dvd (2000).nfo
*Children of Dune.dvd (2000)-trailer.mp4
Is this correct?...will XBMC play in order?...should not be "Children of Dune (CD 1).avi" ??
What are the correct "stack" final names for the video files?...
I recommend putting children of dune, and other TV mini series, in your TV library vs. your movie library. They'll generally scrape better, IMO.
For example, I have it like this in my TV Library:
Children of Dune S01E01
Children of Dune S01E02
Children of Dune S01E03
I agree, your naming convention and structure can mess up a lot of stuff
CD 1 etc... are used for multipart movies (= 1 movie divided on multiple disks)
if you have a mini series this is a group of different movies so you should use S01E01 etc... or equivalent (I prefer this to the 01.x01 or others as is more explicit and avoid confusion).
Please note that you can combine them
movie1 S01E01 part1
movie1 S01E01 part2
is a multipart episode of a series
(2013-03-12, 03:22)deh2k7 Wrote: (2013-03-06, 05:45)deh2k7 Wrote: I noticed that Ember seems to be stripping two fields (these came from another media editor).
The first is the <set> tag. I would like to see Ember be able to scrape this field from TMDB.
The second is the <TMDBID> tag. Might also be a good thing to populate in the nfo, as a backup for the <ID> tag (IMDB ID).
Can anyone else confirm this behavior?
This part of an earlier post got lost in the shuffle when we were discussing naming conventions for artwork. Dan or M., can you confirm this behavior on your end?
Also, are you thinking about adding support for tags?
I already replied in the past: YES
I want to use them but we have discovered a major issue: we need to fix all the scraping procedures first
then we can change the DB and NFO structure
changing them now will only require double patching .(
(2013-03-12, 03:47)pfp_az Wrote: I'm using Ember to scrape for YAMJ so I'm not sure if this affects XBMC too.
I've noticed an issue when scraping writers.
Using 1.3.10 writers are saved to the NFO like this:
Code:
<credits>Chris Marker</credits>
<credits>David Webb Peoples</credits>
YAMJ is expecting it to look like this:
Code:
<credits>
<writer>Chris Marker</writer>
<writer>David Webb Peoples</writer>
</credits>
If this only affects YAMJ would it be possible to get a switch on the YAMJ compatibility module to save writers in the YAMJ format.
Thank you
It appears to me to be Yamj related, have you checked with Ometron? usually he tries to keep the NFO compatible with XBMC
ù