RetroFE forums
General Category => Feature Requests / Suggestions => Topic started by: dustind900 on June 07, 2017, 11:00:20 PM
-
As mentioned here (http://retrofe.nl/SMF/index.php?topic=144.msg1852#msg1852). I'm really hoping to see this as a feature. And if it does become a feature, you can bet I will write code to convert the hyperlist files I have made. Which leads me to ask, what should a standard Info.conf for a game look like?
10-Yard Fight (Japan).conf
lb_description = Description
lb_cloneof = CloneOf
lb_manufacturer = Manufacturer
lb_developer = Developer
lb_year = Year
lb_genre = Genre
lb_rating = Rating
lb_score = Score
lb_players = Players
Description = 10-Yard Fight (Japan)
CloneOf = 10-Yard Fight (USA, Europe)
Manufacturer = Nintendo
Developer = Nintendo
Year = 1985
Genre = Sports
Rating = ESRB - E (Everyone)
Score = 2.3
Players = 2
-
Sounds like a great feature, should we not add the system the game belongs to as well so that we can query the whole list of consoles/plateforms it has been developped on and choose which version we prefer to play with ?
-
Not sure I see the benefits of this other than accommodating my fixation on organizatio, in that I don't like having it all on a loooong list, plus it's similar to how Kodi/Plex handle .nfo files - but that's enough for me if I'm understanding this right ;D
Regarding the standard - if it's gonna be metadata, wouldn't .nfo be better suited?
Regarding the fields, I think "Date" is more appropriate than "Year" as it encapsulates more info and is the standard used on ID3 tags, that "Distributor" is more contemporary (as in digital) than "Manufacturer", that "Players" implies plurality (so "Players = 1" would be weird), and that I believe "Rating" is much more often associated with what's been here labelled as "Score".
-
If I were to set this up, it would be no different than the info.conf support for collections. Any tag in there is automatically supported, and it's up to the theme designer which fields (s)he wants to use.
Sent from my SM-G920F using Tapatalk
-
Per game info should only contain info that is not already present in the xml (already supported) and will negate the need for custom xml
Currently, a standard xml has description (actually full game name), cloneof, crc, manufacturer, year, genre and rating
So, the per game info would have tags for things like score, players and developer (using the example in the first post)
You could use all in the info conf but why when you already have and can already pull the info from the xml.
-
Question remains: if certain information is present in both xml and info file, which should have preference?
Sent from my SM-G920F using Tapatalk
-
Question remains: if certain information is present in both xml and info file, which should have preference?
Sent from my SM-G920F using Tapatalk
XML as that (should) always be present.
Also, just to note:
lb_description = Description
lb_cloneof = CloneOf
lb_manufacturer = Manufacturer
lb_developer = Developer
lb_year = Year
lb_genre = Genre
lb_rating = Rating
lb_score = Score
lb_players = Players
These are not needed, they are Aeon Nox specific
-
If anything I think If info is present for both the info file should override the xml since it would be user specified. However, I don't really see the point in someone doing that since it would make more sense to just edit the xml instead of having dupe fields. It is a use case that would need to be considered though. The purpose of the proposed info.conf was to allow people to specify information on a per game basis for fields not included in the xml from what I gathered.
These are not needed, they are Aeon Nox specific
They're optional, yeah. but aren't really specific to the Nox theme. They're just labels to accompany the other fields that any layout could use although Nox may or may not be the only one using them currently.
-
The purpose of the proposed info.conf was to allow people to specify information on a per game basis for fields not included in the xml from what I gathered.
That's what I thought as well, stuff not in the xml goes in the info
These are not needed, they are Aeon Nox specific
They're optional, yeah. but aren't really specific to the Nox theme. They're just labels to accompany the other fields that any layout could use although Nox may or may not be the only one using them currently.
The lb_ prefix is not needed in order to be used/displayed by a theme, that is what I meant. Nox is the only theme that I know of that uses the prefix.
-
Question remains: if certain information is present in both xml and info file, which should have preference?
Sent from my SM-G920F using Tapatalk
The info file for sure. I'm tired of having to base everything around XML databases that don't even contain enough data to do a legitimate rom scan. Once the TruRip scene catches on this won't be such an issue. But as it is right now the the Hyperlist files (unless you are using the set Pieter uploaded) don't even have all the fields available to work with RetroFE. What happens if a user chooses to use a GoodRom set? There is no Hyperlist or TruRip dat for that...
Info.conf files IMO will be much easier to work with and users don't all have to have the same databases, roms, art, etc.. The data i proposed in the first post would be basic information included with all game info.conf files, then users could add extra data to the existing default. The files could then be shared among the community and full sets could be made. Plus once Pieter gets time to add media searching without tags the info.conf files will become even more universal.
-
I'm gonna be polite here and just say good luck with the project Pieter, I'm done.
-
My preference would be to have the XML be leading; any value not entered in the XML file can then be added via the the info conf file. That way, if you don't wish to use the XML files, simply delete them so RetroFE cannot find a value in the meta database, and use the info.conf informaiton in stead. This also preserves the current RetroFE behaviour, and just adds functionality to it.
-
I'm gonna be polite here and just say good luck with the project Pieter, I'm done.
The point of this thread was to discuss the possibilities behind this purposed new feature. I'm sorry I don't want a clone of every other arcade machine being built.
Even if we are only going to use the conf files for extra info shouldn't we think about standardizing some of the label names that could be utilized by theme makers? That way users wouldn't need different sets of conf files to use different themes. igarikoitz mentioned some useful ones here (http://retrofe.nl/SMF/index.php?topic=144.msg1851#msg1851).
Sent from my LG-H950 using Tapatalk
-
I'm gonna be polite here and just say good luck with the project Pieter, I'm done.
The point of this thread was to discuss the possibilities behind this purposed new feature. I'm sorry I don't want a clone of every other arcade machine being built.
Even if we are only going to use the conf files for extra info shouldn't we think about standardizing some of the label names that could be utilized by theme makers? That way users wouldn't need different sets of conf files to use different themes. igarikoitz mentioned some useful ones here (http://retrofe.nl/SMF/index.php?topic=144.msg1851#msg1851).
Sent from my LG-H950 using Tapatalk
How about we just ignore each other?
There was/is no need to quote me as going forward I won't respond/reply to you.
-
How about we just ignore each other?
There was/is no need to quote me as going forward I won't respond/reply to you.
Grow up ::). Either way I don't care. It's obvious this community is going nowhere and it's easy to see why. I have never seen a user go out of his way to be a dick just because someone had a suggestion. Pieter I wish you luck, your front-end is awesome unfortunately your forum community isn't.
-
Everyone chill out and keep on topic please. I don't see why anyone is getting worked up over a feature request that would only add completely optional functionality and not affect how things are currently. That's exactly what this section is for and community input is key in making the frontend better for all. But, if anyone isn't interested in or capable of discussing these things without getting bent out of shape, don't participate in the discussion.
-
My preference would be to have the XML be leading; any value not entered in the XML file can then be added via the the info conf file. That way, if you don't wish to use the XML files, simply delete them so RetroFE cannot find a value in the meta database, and use the info.conf informaiton in stead. This also preserves the current RetroFE behaviour, and just adds functionality to it.
This is the best option, certainly.
This community is growing little by little and we can make retrofe a beautiful and easy to use frontend. I'm using almost all of my free time in designing and programming the Aura layout and I would not want to be disillusioned because of some nonsense. Peace Please :)
-
Question remains: if certain information is present in both xml and info file, which should have preference?
Sent from my SM-G920F using Tapatalk
The info file for sure. I'm tired of having to base everything around XML databases that don't even contain enough data to do a legitimate rom scan. Once the TruRip scene catches on this won't be such an issue. But as it is right now the the Hyperlist files (unless you are using the set Pieter uploaded) don't even have all the fields available to work with RetroFE. What happens if a user chooses to use a GoodRom set? There is no Hyperlist or TruRip dat for that...
Info.conf files IMO will be much easier to work with and users don't all have to have the same databases, roms, art, etc.. The data i proposed in the first post would be basic information included with all game info.conf files, then users could add extra data to the existing default. The files could then be shared among the community and full sets could be made. Plus once Pieter gets time to add media searching without tags the info.conf files will become even more universal.
Retrofe supports trurip SUPERdats files, which holds all meta data info there, which is read out by retrofe theme also.
We didnt do this for the fun of it. Its already working. And can easily add all needed info for the seperate titles in the meta data part of the SUPERdat files
At this moment it holds (example):
<game name="Games\Cocktail Pack (Japan) (Disc 2)">
<description>Cocktail Pack (Japan) (Disc 2) - カクテルパック(テレカ付初回版)</description>
<trurip>
<titleid>10-81</titleid>
<publisher>NEC Home Electronics Ltd.</publisher>
<developer>Cocktail Soft</developer>
<year>1997</year>
<genre>Simulation</genre>
<subgenre></subgenre>
<ratings>18+</ratings>
<score></score>
<players>1</players>
<enabled>Yes</enabled>
<crc>b72eb2fd</crc>
<source>trurip</source>
<cloneof>Can Can Bunny Extra DX (Japan)</cloneof>
<relatedto>Cocktail Pack (Japan) (Disc 1)</relatedto>
</trurip>
<rom name="Cocktail Pack (Japan) (Disc 2).cue" size="2989" crc="c6fb7225" md5="90e5a9b2be04ac46aeb4c78b3cac7fd9" sha1="8edc17010797c062c7663e74274fad1ec50f43e0" />
<rom name="Cocktail Pack (Japan) (Disc 2).ccd" size="1697" crc="bc81d476" md5="3d0970e2e681f0dcb7c962b1a70a6606" sha1="e4072fe5c7a5ca6dee897f732095b0210f4d5600" />
<rom name="Cocktail Pack (Japan) (Disc 2).img" size="744283344" crc="b72eb2fd" md5="67d6ca40254fd09a965c11ab3bcd2675" sha1="1c7da12f7a20095853df26060cf661f8c97bde1f" />
<rom name="Cocktail Pack (Japan) (Disc 2).sub" size="30378912" crc="843bcca8" md5="93b2966dd427753aea452b6a5839a265" sha1="dcd6cb4e758cbf804a5ee3f6ae26880754aa70b4" />
</game>
As you can see it also has fields related to and clone of
-
Question remains: if certain information is present in both xml and info file, which should have preference?
Sent from my SM-G920F using Tapatalk
The info file for sure. I'm tired of having to base everything around XML databases that don't even contain enough data to do a legitimate rom scan. Once the TruRip scene catches on this won't be such an issue. But as it is right now the the Hyperlist files (unless you are using the set Pieter uploaded) don't even have all the fields available to work with RetroFE. What happens if a user chooses to use a GoodRom set? There is no Hyperlist or TruRip dat for that...
Info.conf files IMO will be much easier to work with and users don't all have to have the same databases, roms, art, etc.. The data i proposed in the first post would be basic information included with all game info.conf files, then users could add extra data to the existing default. The files could then be shared among the community and full sets could be made. Plus once Pieter gets time to add media searching without tags the info.conf files will become even more universal.
Retrofe supports trurip SUPERdats files, which holds all meta data info there, which is read out by retrofe theme also.
We didnt do this for the fun of it. Its already working. And can easily add all needed info for the seperate titles in the meta data part of the SUPERdat files
At this moment it holds (example):
<game name="Games\Cocktail Pack (Japan) (Disc 2)">
<description>Cocktail Pack (Japan) (Disc 2) - カクテルパック(テレカ付初回版)</description>
<trurip>
<titleid>10-81</titleid>
<publisher>NEC Home Electronics Ltd.</publisher>
<developer>Cocktail Soft</developer>
<year>1997</year>
<genre>Simulation</genre>
<subgenre></subgenre>
<ratings>18+</ratings>
<score></score>
<players>1</players>
<enabled>Yes</enabled>
<crc>b72eb2fd</crc>
<source>trurip</source>
<cloneof>Can Can Bunny Extra DX (Japan)</cloneof>
<relatedto>Cocktail Pack (Japan) (Disc 1)</relatedto>
</trurip>
<rom name="Cocktail Pack (Japan) (Disc 2).cue" size="2989" crc="c6fb7225" md5="90e5a9b2be04ac46aeb4c78b3cac7fd9" sha1="8edc17010797c062c7663e74274fad1ec50f43e0" />
<rom name="Cocktail Pack (Japan) (Disc 2).ccd" size="1697" crc="bc81d476" md5="3d0970e2e681f0dcb7c962b1a70a6606" sha1="e4072fe5c7a5ca6dee897f732095b0210f4d5600" />
<rom name="Cocktail Pack (Japan) (Disc 2).img" size="744283344" crc="b72eb2fd" md5="67d6ca40254fd09a965c11ab3bcd2675" sha1="1c7da12f7a20095853df26060cf661f8c97bde1f" />
<rom name="Cocktail Pack (Japan) (Disc 2).sub" size="30378912" crc="843bcca8" md5="93b2966dd427753aea452b6a5839a265" sha1="dcd6cb4e758cbf804a5ee3f6ae26880754aa70b4" />
</game>
As you can see it also has fields related to and clone of
I was talking more about you guys not having a lot of systems done yet. Which, I understand, takes time. If you guys had some more of the bigger systems I would start using your databases for sure.
Sent from my LG-H950 using Tapatalk
-
Not done many systems? (so far 143 Systems / regions in the database)
We have a lot of systems done , except our focus was on optical media systems.
Bigger systems like? (as in number of titles? since optical media are by a mile the largest sets - sizewise)
Atm the sets are 20TB large and soon over 30TB. (and thats without the roms sets).
-
Not done many systems? (so far 143 Systems / regions in the database)
We have a lot of systems done , except our focus was on optical media systems.
Bigger systems like? (as in number of titles? since optical media are by a mile the largest sets - sizewise)
Atm the sets are 20TB large and soon over 30TB. (and thats without the roms sets).
I was talking about Systems like NES or SNES. If you have databases for them thats good, but I can't find them. I wasn't trying to offend you or anything.
-
Yeah sure np.
Havent added the roms yet since those are easy to grasp and add into db.
But yeah we will do that.
Will first spit out cd-i + dreamcast sets