Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom image always picking season 1 for the "BOX set" image for escaped series names. #880

Closed
Omertron opened this issue Mar 15, 2015 · 2 comments

Comments

@Omertron
Copy link
Member

Original issue 881 created by Omertron on 2009-06-29T19:04:07.000Z:

For the TV series CSI: Miami I would like to add a custom "SET" image...

My episodes are all in one folder
CSI.Miami.S01E01.Golden.Parachute.avi
.
All episodes from 7 seasons.
.
.
CSI.Miami.S07E25.Seeing.Red.avi

I have no problems with the individual Set xml / html being created with
the seven season covers. Nor do I have a problem with thetvdb lookups for
individual season covers or episode names. ( the problem lies in
thetvdb.com naming the series "CSI: Miami".

However I cannot seem to name a "SET" image that YAMJ will pick up.
Even if I create an image named:
Set_CSI$3A Miami_1.jpg
and place it in the same folder (notice the unescape sequence)
this image will not be used as the "SET" image...rather I get the image
from Season 1 with the "set" overlay.
Also an image named:
Set_CSI Miami_1.jpg
also will not be used...

How to name a file or use NFO for YAMJ to use my .jpg to create the custom
.png with the overlay. Wiki doesn't give any more clues than what I've tried.

create a single command line that will do the .png creation with overlay
given a particular .jpg?

@Omertron
Copy link
Member Author

Comment #1 originally posted by Omertron on 2009-10-13T09:59:33.000Z:

<empty>

@Omertron
Copy link
Member Author

Comment #2 originally posted by Omertron on 2009-10-13T10:19:51.000Z:

Fixed in r1143

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant