Search options (Page 32 of 66)

Want an account or what does the "cuts" mean?

Wiki pages, satakore.com and most of other console-related resources usually use full-width ones and people usually copy-paste them as is.

Meh, it's hard to say whether the symbols are full or half width on the cover when there's no other text nearby to compare with Though, if you look at obis/spine cards, the spaces are usually quite wide (especially before the subtitles).

I see this option as the fastest to implement _right now_ due to hardcoded LBAs and no additional attributes.

This needs lots and lots of further discussions about how to handle the lead-in, lead-out, security ring and other portions of data (and whether to use the cue sheets at all for these, not some xml-based format instead), that additionally rises the question about how to handle the TOC and the first pregap in the -150 to -1 area. And it's going to be a very bad idea to implement these LBAs now and lead-in/lead-out/rings/whatever later. Because the next time devs may refuse to change the cue scheme once again. If they accept the simplier format above, we could try to discuss the further format expansions with them.

And don't forget the format is primarily meant for DC emus which, again, don't need those LBA commands, because the area LBAs are hardcoded to 0 and 45150, your commands can do the parsing routines more complicated and the format less attractive to support (and we want it to be supported by as many emus as possible, including MAME - good luck explaining them how to process your proposed LBA commands and do all the addressing properly).

The format _right now_ should be as easy as possble, the complicated parts need to be well discussed before adding.

And once again, just in case I wasn't clear enough: adding those LBA commands to GD cues only is absolutely pointless, because they are hardcoded and cannot be changed; adding them to all the cues for multisession (and maybe other) needs needs (lol) to be better discussed and documented.

Because that's the only existant case of a disc with isolated sessions, there's no other similar case. For Saturn rings you need to implement the REM LEAD-OUT command to describe the exact amount of sectors before the ring, for multisession discs you need REM LEAD-OUT for the first session with the amount of lead-out sectors and REM LEAD-IN for the amount of lead-in sectors of the 2nd session, you don't need any direct LBA addressing, that's way away from cuesheets paradigm. We need to develop a custom format for direct LBA addressing if you want it that much.

If there's no agreement on the single cue format, do the 2xcues with no additional tags. Easy.

SINGLE-DENSITY AREA always starts at 0, HIGH-DENSITY AREA always starts at 45150, additional commands aren't needed here. These are to be discussed later for the multisessional discs (though, even they should have REM LEAD-OUT and REM LEAD-IN generating commands, not that LBA thing).

You need more commands, like REM LEAD-IN and REM LEAD-OUT to properly generate or insert the needed amount of sectors between the sessions/areas. And for describing the full GD structure, you would also need a REM MIRROR AREA command.

Or, if those areas are more or less standard (I haven't investigated too far), something like REM SECURITY AREA TYPE 1/REM SECURITY AREA TYPE 2 could be enough (same for the Saturn rings).

I've already mentioned such a solution. The problem is that such a cue is only "correct" for isobuster, other tools will "see" this track 9+ minutes longer than it should be, so it's not a good solution at all. The only proper way without implementing new commands would be to put everything into a single image.

REM SESSION 01 and REM SESSION 02 are also wrong, these commands generate a multisessional disc TOC, while GDs aren't multisessional, those are 2 separate images written on the same media (or 3, if to count the security ring area).

The GD image should NOT be seen as a single image with all the tracks at a time, that's why I've offered to do separate cues, so you could load them independently, just like a real thing. You either load and work with the LD area with 2 tracks or with the HD area with the track 3 and beyond (if any), not both.

Someone should try to contact Daemon Tools guys for the possible support of such cues.

Earlier SEGA docs call them "Single-Density" and "Double-Density" areas, more recent revisions call them "Single-Density" and "High-Density". No "Low-Density" anywhere.

Japanese PSX games with Japanese internal serial numbers that were later released in Asia are (Japan, Asia).
Asian PSX games with Asian internal serial numbers that were later released in Japan are (Asia, Japan).

The pairs you've mentioned are probably for the similar cases.