Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: aybe aybe <aybe.one-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/4] avcodec/mdec: DC reading for STRv1 is like STRv2
Date: Sat, 13 Jan 2024 02:28:52 +0000
Message-ID: <PAVPR08MB979517A49DBA7E2AC6E5D94B9A6E2@PAVPR08MB9795.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20240110024602.GQ6420@pb2>

Here are the two STR files I have used when writing this patch: https://github.com/aybe/FFmpeg-PSX-STR-tests
Fanatics would probably say that 30 FPS for NTSC is wrong (i.e. should be 29.97)...
However, as the reversed-engineered docs in jpsxdec mentions, it is sort of impossible to figure out which value to snap to from how frames spans across CD-ROM sectors.
The sector count per video frame always seem to juggle between two values, e.g. 6 sectors, then 7 sectors, rinse/repeat. i.e. it's never constant.

Also, as one can see in the various code samples online on writing a PSX program that plays MDEC videos, it is the responsibility of the coder to present the frames on screen.
i.e. there is not definitive way on how to do so, and even if there was, you can be sure some folks did not play by the rules back then.
The only way to figure out how a movie was intended to be played is to reverse engineer a game to see what values they did cram in.
In short, the computed frame rate is 99% good, not 100%. But for mere mortals, they are unlikely to notice it at all.

As for the movies in the samples repository, they are corrupt and FFmpeg fails at them, obviously.
I figured these ones were by checking them in a hex-editor but also by loading them in https://github.com/m35/jpsxdec<https://> which has great logging.
Not sure why these samples were corrupt in first instance, maybe it was intentional for testing? I can't tell.

------ Original Message ------
From "Michael Niedermayer" <michael@niedermayer.cc<mailto:michael@niedermayer.cc>>
To "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org<mailto:ffmpeg-devel@ffmpeg.org>>
Date 1/10/2024 3:46:02 AM
Subject Re: [FFmpeg-devel] [PATCH 1/4] avcodec/mdec: DC reading for STRv1 is like STRv2

On Tue, Jan 02, 2024 at 02:49:26AM +0000, aybe aybe wrote:
Hi,

As I understand, support for .STR files is broken for almost 10 years now (since 161442ff2c4b0dd8a5072c6bbe6bf55303fffccf it seems).

Currently, ffmpeg fails with tons of errors like this on version 1 STRs, e.g. Wipeout 1:
[mdec @ 00000000027c72c0] ac-tex damaged at 1 9

where can i find a psxstr file to test this ?
the psxstr files i find on https://samples.ffmpeg.org/ seem not affected by this

thx

[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are best at talking, realize last or never when they are wrong.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-01-13  2:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  2:49 aybe aybe
2024-01-05 20:53 ` Michael Niedermayer
2024-01-06 12:31   ` aybe aybe
2024-01-10  2:37 ` Michael Niedermayer
2024-01-13  2:32   ` aybe aybe
2024-01-10  2:46 ` Michael Niedermayer
2024-01-13  2:28   ` aybe aybe [this message]
2024-01-14 20:38     ` Michael Niedermayer via ffmpeg-devel
2024-01-15 16:14       ` aybe aybe
2024-01-15 23:42         ` Michael Niedermayer
2024-01-16 14:27           ` aybe aybe
2024-01-16 14:32             ` aybe aybe
     [not found]             ` <emd5d779f2-9283-4be7-82e5-afaf16ca635e@a51bcb19.com>
2024-01-16 14:39               ` aybe aybe
2024-01-16 14:56                 ` aybe aybe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PAVPR08MB979517A49DBA7E2AC6E5D94B9A6E2@PAVPR08MB9795.eurprd08.prod.outlook.com \
    --to=aybe.one-at-hotmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git