Closed GoogleCodeExporter closed 8 years ago
Thanks for the very detailed reports BTW. It's nice to have feedback and know
that
people want it to improve.
If the game was downloaded via nzbget then the best thing to do is make a copy
of
unpak.cfg and add more newsgroup categorisations. Eg.
unpak_auto_categorisation_from_newsgroups=1
unpak_subfolder_by_newsgroup_0="erotica:PIN:FOLDER"
unpak_subfolder_by_newsgroup_1="sounds:/share/Music"
unpak_subfolder_by_newsgroup_2="pictures:Pictures"
unpak_subfolder_by_newsgroup_3="games:/share/Games"
If an nzb file has a group listed in the unpack_subfolder_by_newsgroup options then
the download will be moved directly to the named folder after unpacking, and it
will
not be cataloged or added to oversight. I should probably make this a wiki page
:)
Other than that another longer term option would be to mount the iso and make
sure it
has no typical PS3/Xbox type files. (as I understand they may have video_ts)
Let me know if the unpak rules are not sufficient and I'll happily discuss
and/or
repoen the issue.
Original comment by lordylo...@gmail.com
on 19 Aug 2009 at 1:14
Thanks for the follow up. The additional newsgroup categorization was exactly
what I
was referring to under the Expected Output section of my initial comment. In my
situation, I should probably also remove the "Completed" folder from being
indexed
altogether. I consider the Completed folder the second level of staging my
content.
The content first gets put in the downloads folder while it is being
downloaded, then
gets moved to the completed folder when its done, and finally makes it's way to
the
destination folder in a cleaned up format (samples removed, files renamed,
content
indexed into catalog)
This is particularly the case with music. I typically comment out the Music
unpak_subfolder_by_newsgroup_1 item so that the content just gets moved to the
Completed folder. From there, I manually review the music to make sure the
filenames
fit my naming convention, there is proper album art, and the ID3 tags are
properly done.
Original comment by lyon.jos...@gmail.com
on 19 Aug 2009 at 2:02
Original issue reported on code.google.com by
lyon.jos...@gmail.com
on 17 Aug 2009 at 5:33Attachments: