Previous Page | Next Page

by Missingno_force at 12:45 PM EDT on May 6, 2018
Awesome, thanks a lot!
by Kirishima at 12:47 PM EDT on May 13, 2018
More viopsf feedback. Crash Team Racing appears to not be playable probably for similar reasons to Crash 2 and 3 (PAL rip). It sorta is playable if skip silence on start is disabled/set to 0, but apparently there is alot of silence in these files.

I was contemplating re-ripping the game with markgrass's generic psf driver, but the readme stated the game is using its original driver for features a generic driver can't provide.

Anybody know of other pal rips that could be problematic?
Metal Gear Solid PSF's by Enclave123 at 7:49 AM EDT on June 22, 2018
I wonder if there any recommended ways to play the PSF of MGS? it not really playing well in Winamp for some reason. It have no sound when playing them.

I am really happy to see a PSF of MGS since i really enjoy the soundtrack.

Is there going to be a MGS VR missions PSF in there future?
by Nisto at 9:04 AM EDT on June 22, 2018
@Enclave123: I recommend viopsf with the Mednafen SPU DLL. Most PSF players don't have (proper) support for SPU interrupts, so that's why they won't play it correctly (if at all).

I uploaded VR Missions (as part of MGS Integral) a few pages ago, but it has since disappeared from Sendspace (guess no one uploaded it to Josh W or elsewhere). It's a rather large set since it's not a minipsf set. But I have the "PSF kit" still up on my Dropbox if you want to build the PSFs yourself. You need to know what you are doing though; there are some pretty crucial values in the Python script you might want to configure before you run it:

https://www.dropbox.com/s/4joqco4kkih8zxx/mgs_psfkit.7z?dl=1

edited 9:17 AM EDT June 22, 2018
by Kirishima at 1:29 PM EDT on June 22, 2018
If only it could have the alternate reverb that's in the "Peopsound" plugin. That's one of the few that sounds similar to a real spu's reverb rather than most of the others which, to me, sound like an enhanced snes reverb.

Also since I'm here, viopsf was updated to fix Crash Team Racing some time ago: https://ux.getuploader.com/foobar2000/download/201
by Nisto at 12:55 PM EDT on July 25, 2018
@ viopsf developer

Can you please update to SDK v1.4? It's still listed as a legacy decoder in foobar2000 v1.4, which finally has a stable release.

edited 1:12 PM EDT July 25, 2018
by Nisto at 12:06 PM EDT on July 30, 2018
I caved in and decided to install VC++2017 in an attempt to build viopsf for foobar2000 v1.4 myself. After spending the whole evening with this yesterday, I think I finally managed to do it. But as I have zero past experience with the foobar2000 SDK, and not much experience with the extended features of C++ (templates, classes, and all that), I can't guarantee a proper build. I hope someone who perhaps does have better experience can point out any mistakes I may have made!

Here's what I did to build it for v1.4

1. Install VC++2017 (I got the free Community edition of Visual Studio 2017 personally)

2. Create a folder named viopsf

3. Download the foobar2000 SDK and unpack the contents directly into the "viopsf" folder

4. Download viopsf and unpack the contents of the src folder in src.7z directly into the "viopsf" folder. You should now have three folders in the "viopsf" folder created in step 2 -- "viopsf", "foobar2000" and "pfc"

5. In the viopsf\foobar2000 folder, create the directory tree test\components. Without this, Visual Studio fails to execute a copy command at the end of the build process, even when run as administrator.

6. Open viopsf\foobar2000\foo_input_viopsf\foo_input_xsf.cpp

7. Change line 368 to:

class input_xsf : public input_stubs

8. Add this code between line 997 and 998:

static const char *g_get_name() { return "PSF Decoder"; }
static const GUID g_get_guid() { return XSFDRIVER_GUID2; }
static const GUID g_get_preferences_guid() { return XSFDRIVER_GUID1; }

9. Open the viopsf\foobar2000\foo_input_viopsf\foo_input_viopsf.sln file (solution) in Visual Studio

10. Build foo_input_viopsf by right-clicking the item in the left-hand pane and clicking "build"

edited 1:57 PM EDT July 30, 2018
by Kirishima at 3:50 PM EDT on August 11, 2018
@Nisto

Viopsf has been updated to SDK 1.4.
Soma Bringer by RetroFanatic at 9:38 AM EST on December 22, 2018
No success in ripping this one yet?
by SmartOne at 11:38 PM EST on January 5, 2019
in_vgm 0.40.9 was released!

That's right; for the first time since October 19, 2017, we're able to used the "nuked," cycle-accurate YM2612 core to listen to VGMs!

https://vgmrips.net/forum/viewtopic.php?f=3&t=112
https://github.com/vgmrips/vgmplay

But if I were you, I'd skip that official Winamp plugin (for use in XMPlay, of course; you're not crazy, are you?) and get the unofficial foobar2000 port plugin, creatively named "VGM input" and maintained by mysterious Japanese:

https://ux.getuploader.com/foobar2000/download/213

"VGM input" is functionally superior because you can configure the core type in the GUI, unlike "in_vgm," which requires a secret INI setting change. Here are the completely intuitive GUI help tooltips:

https://github.com/vgmrips/vgmplay/commit/f712603913050feca455dcd547f981dc1f2ebc9a

Also, the foobar2000 plugin sounds less bad on manual track change. I believe the correct technical term is "less poopy."

It's a great time to be alive, folks. Accurate YM2612 (which has been available in Genesis Plus GX for over a year)! Much hype.

Previous Page | Next Page
Go to Page 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220

Search this thread

Show all threads

Reply to this thread:

User Name Tags:

bold: [b]bold[/b]
italics: [i]italics[/i]
emphasis: [em]emphasis[/em]
underline: [u]underline[/u]
small: [small]small[/small]
Link: [url=http://www.google.com]Link[/url]

[img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message

HCS Forum Index
Halley's Comet Software
forum source