N
nikfrozty
Guest
So we'll wait for Aali to update his drivers?? Oh I wish he figures it out.
Well he tried to incorporate a faster decoder last time, and it kind of worked, but still not enough to run a HD FMV with more than 15 fps.So we'll wait for Aali to update his drivers?? Oh I wish he figures it out.
Ah, I assumed you had noticed when I posted earlier about the v0.92.0 update which fixed frame rate detection, and were using that latest version. That would explain why you thought there were "50 different frame rates" (which the older v0.35 inaccurately reported). I'm glad we got that cleared up...except for what I said earlier...that the FF7 PSX still does not use all 1 frame rate.OK....me and kranmer have been looking into this. First, an apology. Your program does seem to report exactly what I would expect on most of these video's, which is what I said earlier....that they are all 1 frame rate.
(the earlier version of your program was way off on pretty much all of them,
Yes, as you found, SMK.STR and LSLMV.STR both have the different frame rate of 18.75fps. jPSXdec is operating correctly, and is accurately detecting the exact rate on the PSX disc. The rate is very easy to calculate: 150/8 = 18.75. I trust this calculation makes since to you because you must have looked at my documentation by now (something I have twice suggested you do).I still cannot explain why there is just 1 vid out here... that is still reporting (as of latest release) an 'odd' framerate of 18.75 fps.
Thank you for accepting them as 'correct', because that is exactly what they are on the PSX. As I've said before, you are welcome to adjust all the videos to be exactly 15fps for the PC version since that's what it needs.All the others are perfect and reporting 14.985 or 15.000 which is correct.
(using 15 fps for that in PC would be what is expected)
You may notice the pattern that all videos with 15.000/1.001fps have audio, and all videos without audio are 15fps (except for the 18.75 cases, which I admit are odd, but still that is how they are). And no, just because there is audio in a PSX movie doesn't mean it will automatically have a fractional frame rate (please see my documentation for details). The PSX game designers deliberately chose those frame rates that you see. My assumption is they used 15.000/1.001fps to prevent the audio from getting out of sync with the video. Why they used 18.75fps for those two videos is a mystery to me.By Kranmer (marked in red are problems?):
CD1
BIKEGET[0].avi = 14.985 (has audio)
BISKDEAD[0].avi = 15.000 (no audio)
BOOGDEMO[0].avi = 15.000 (no audio)
BOOGDOWN[0].avi = 15.000 (no audio)
BOOGSTAR[0].avi = 15.000 (no audio)
BOOGUP[0].avi = 15.000 (no audio)
BRGNVL[0].avi = 14.985 (has audio)
CAR_1209[0].avi = 15.000 (no audio)
D_ROPEGO[0].avi = 14.985 (has audio)
D_ROPEIN[0].avi = 14.985 (has audio)
EARITHDD[0].avi = 14.985 (has audio)
FALLPL[0].avi = 14.985 (has audio)
FUNERAL[0].avi = 15.000 (no audio)
GOLD1[0].avi = 14.985 (has audio)
GOLD2[0].avi = 14.985 (has audio)
GOLD3[0].avi = 14.985 (has audio)
GOLD4[0].avi = 14.985 (has audio)
GOLD5[0].avi = 15.000 (no audio)
GOLD6[0].avi = 14.985 (has audio)
GOLD7[0].avi = 14.985 (has audio)
GOLD7_2[0].avi = 14.985 (has audio)
HIWIND0[0].avi = 14.985 (has audio)
JAIROFAL[0].avi = 14.985 (has audio)
JAIROFLY[0].avi = 14.985 (has audio)
JUNAIRD[0].avi = 15.000 (no audio)
JUNAIRU[0].avi = 15.000 (no audio)
JUNELEGO[0].avi = 15.000 (no audio)
JUNELEIN[0].avi = 15.000 (no audio)
JUNIN_GO[0].avi = 15.000 (no audio)
JUNIN_IN[0].avi = 15.000 (no audio)
JUNON[0].avi = 15.000 (no audio)
MAINPLR[0].avi = 14.985 (has audio)
MK8[0].avi = 15.000
MKUP[0].avi = 15.000
MONITOR[0].avi = 15.000 (no audio)
MTCRL[0].avi = 15.000 (no audio)
MTNVL2[0].avi = 15.000 (no audio)
MTNVL[0].avi = 15.000 (no audio)
NIVLJNV[0].avi = 14.985 (has audio)
NIVLSFS[0].avi = 14.985 (has audio)
NORTHMK[0].avi = 14.985 (has audio)
NVLMK[0].avi = 14.985 (has audio)
ONTRAIN[0].avi = 14.985 (has audio)
OPENING[0].avi = 14.985 (has audio)
PLREXP[0].avi = 14.985 (has audio)
RCKTFAIL[0].avi = 14.985 (has audio)
SETO[0].avi = 15.000 (no audio)
SMK[0].avi = 18.750 (no audio)
SOUTHMK[0].avi = 14.985 (has audio)
U_ROPEGO[0].avi = 14.985 (has audio)
U_ROPEIN[0].avi = 14.985 (has audio)
I will agree yet again that adjusting to 15fps for PC sounds like the best course of action. I hope since we agree on that point, you don't have to persist asserting your still unfounded idea that all the FF7 PSX videos should all be detected as 15fps. In the unfortunate case that you continue to insist that erroneous notion, let me address 3 reasons you have briefly mentioned why you might think that.I am not sure if aali's driver or FF7 PC will manage with 14.985, and hence, an option to round them all to 15 would definately be preferable imho. I will need to test it...
Not really important, but I may not have been perfectly clear about this. PSX games can actually use just about any frame rate you can imagine. PSX videos can even have variable frame rates (which took no small effort to include handling for in jPSXdec). FF7 videos just happen to use three particular rates.I never intended to say that all videos report 15 fps in different games (but I certainly didn't know that), although it is news to me that they can use different ones inside the same game.
Camtasia or Sony Vegas.Grimmy-I was googling a video editor and I don't know whats best and easier to use. What do you use to edit your vids?? :?
TheoreticallySo is it possible to get 720p or higher video resolution in the game?
Well 720P is widescreen aspect, and FF7 isn't, so it wouldn't look right.So is it possible to get 720p or higher video resolution in the game?
Flash?? I bet that's hard to use. But I'll try it. Thanks for the info.I used flash to edit my vids, but would suggest any new people to use adobe premiere. As far as freeware I use vdub but it's not all that good.
So that means you have actually done that?? Would you mind uploading or posting a video of what you've done so that we could see what you've done?? If what you say is possible then that'll be epic!! ;DThe FF7 field script sets a number of frames to count and soon after calls the movie. Once the frame count is up, the script resumes when the movie is expected to stop. If the frames exceed or fall short of this frame count as called on by the field script, then you experience oddities. Aali can possibly come up with some wizardry to bypass it, but one solution would be to bundle the FMVs with different frame rates alongside field files to insert that have been modified to accommodate them. This can be done in Meteor and fortunately is none too difficult, however the downside is that modifying the field files will make them incompatible with any other mods which alter them. On the other hand, you can always make compatibility patches down the road so it's not too big of a downside.
As an example of the potential for this, a project I was working on before I got tired of Meteor's slowness was to completely modify the beginning cutscene. I had a 30 fps video with the PS3 tech demo train rolling into the station, a prerecorded video of the guards being taken out and Barret waving to Cloud added onto the end of that, and finally the PS3 tech demo Cloud jumping off the train and landing. Field script was modified to start actual game events already on the ground with the prior events already wrapped up.
There are ways around everything.