Jump to content
Antrad

CD audio tracks

Recommended Posts

On 5/9/2020 at 1:07 PM, Garrett said:

There was a previous discussion about removing "settings" from the headings. Some of the templates already have information which is a feature rather than an actual setting (e.g. input settings has "Steam Input API support"), so a row for CD audio would not be the first case like that.

I wasn't saying that it clashes with the title, but actually with the mood of all others option. They are all of a somewhat "artistic choice" kind. You can rename it as you want, but it shouldn't be a bin where you throw everything and the kitchen sink.

And indeed, Steam input API should absolutely go in the API table. 

Then I guess like you might be right, that just using winmm is not enough for CD-DA support (even though I wonder why just about all the fixes I have seen relied on a patched _inmm.dll). Wait. But that's actually what you care for?

That's what's broken in new windows. What else is there? If you were directly reading yourself the CD like a music player, then nothing should change on your side.

Share this post


Link to post
Share on other sites
On 5/7/2020 at 9:41 PM, Andytizer said:

However as a 'normal user' I think I'd be confused by the term Red Book, it would be better IMO to use a generic term CD audio with Red Book in the tooltip or in brackets. 

Games referred to this as "Red Book" quite a lot back in the day, often using both terms interchangeably (some like Descent II actually call it Red Book most of the time). The template text has both terms, so even if a reader has never heard of Red Book its meaning can be easily inferred (and is then confirmed by the tooltip).

Putting this term in the template will hopefully also reduce situations where this is set incorrectly (e.g. for games that stream audio files from the CD rather than playing actual tracks).

Based on a few test searches, internet search engines do not appear to know that Red Book is another term for CD audio in the context of gaming (search results are completely different unless pages happen to mention both terms), so search keyword accessibility is another strong reason for putting both terms in the displayed text.

11 hours ago, Mirh said:

Then I guess like you might be right, that just using winmm is not enough for CD-DA support (even though I wonder why just about all the fixes I have seen relied on a patched _inmm.dll). Wait. But that's actually what you care for?

That's what's broken in new windows. What else is there? If you were directly reading yourself the CD like a music player, then nothing should change on your side.

As I said there are implementations that don't use APIs at all, so handling this with an API focus would inevitably involve ambiguity (which can already occur with some parts of the API table, e.g. being able to set "OpenGL versions" to unknown) and therefore should be avoided when less ambiguous options are also available.

Share this post


Link to post
Share on other sites
35 minutes ago, Garrett said:

search keyword accessibility is another strong reason for putting both terms in the displayed text

I think that sounds good as both words are there. I think it belongs in the Audio section.

Share this post


Link to post
Share on other sites
19 hours ago, Mirh said:

And indeed, Steam input API should absolutely go in the API table. 

Ah yes, so should our "XInput-compatible controllers" rows (pertains to the XInput API for controllers), and the DualShock 4 rows (pertains to DirectInput / DS4 HID APIs), as well as the "Generic/other controllers" rows as well (pertains to, well DirectInput as well, I guess).

After all, you can't interface with a controller without using some form of API...

 

The "Steam Input API Support" row should definitely not solely go in the API section since it pertains to Steam Input support as a whole, which is covered by it as well as the rest of the rows under the Input header. I ain't going to ask our readers to scroll up and down all over the place just to properly get an understanding of how the game interfaces with Steam Input.

 

Also sorry if my tone of voice was a bit aggressive -- just got done after an hour and more editing extravaganza that involved five browser windows, over 30 different tabs, countless edit previews, 10+ actual committed changes, and god knows what other random changes and searches while performing those. I'm friggin' exhausted.

Share this post


Link to post
Share on other sites

I think the troubleshooting note should be set to automatically append after the human-written note, with a line break separating them, so that we don't need to manually put in the troubleshooting note when there is something to note about it even though it is set to true. For example:

https://www.pcgamingwiki.com/wiki/Star_Wars:_Galactic_Battlegrounds#Audio_settings

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

  • Found PCGamingWiki useful? Please consider making a Donation or visiting our Patreon.
  • Who's Online   1 Member, 0 Anonymous, 260 Guests (See full list)

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Forum Statistics

    1,409
    Total Topics
    7,621
    Total Posts
×
×
  • Create New...