Previous Page | Next Page

by Knurek at 5:56 AM EDT on May 14, 2014
You're better off recording them separately and mixing afterwards in Audacity.
by Nisto at 7:44 AM EDT on May 14, 2014
Ah, sorry kode54! I tend to mix all the different VGM components up. XD Anyway, guess I'll settle for infinite loops then.

EDIT: ... well, I just tried enabling "force all songs to play indefinitely", but, the issue remains.

edited 8:20 AM EDT May 14, 2014
by kode54 at 9:21 PM EDT on May 14, 2014
You should also disable tagging your files with play counts, if possible. Unless you really want all of your files rewritten every time you play them.
by Nisto at 3:22 AM EDT on May 15, 2014
Unless you really want all of your files rewritten every time you play them.

I'm afraid I do.. I used to use customdb for such tags, but the problem became that, if a file was moved (matching by filepath) or the file's tags or whatever (matching by track info) changed, then the keys for the entry in the customdb database no longer matched, so the tags would basically be "lost". Yeah, I know, they're still there, and I could use an SQLite manager to edit and update the keys in its database manually, but, mass updating filepaths, not to mention tags, is such a chore and not at all convenient. I'm sorry for being off-topic here, but if you have a better solution for storing playback counts, then please do tell. (The Playback Statistics component also matches by filepaths - at least last I checked.)

But at the same time I wonder why it has suddenly started doing this? I mean, I've used the same fb2k setup for months and this issue only appeared after my latest component update, I'm quite sure. Did you add something to PSF Decoder lately that may cause this? Did it not stop/write/restart (like you mention) before?

edited 4:14 AM EDT May 15, 2014
by kode54 at 6:33 AM EDT on May 15, 2014
It should work just fine, as long as you only have foo_psf, and not foo_input_upse. The former is guaranteed to seek and replay properly, the latter is unknown, and has been removed from download anyway.
by Nisto at 9:10 AM EDT on May 15, 2014
@kode54: don't have (and never did have) foo_input_upse installed. Here is a components report of what I do have installed, FWIW: http://pastie.org/pastes/9178461/text?key=nl5dbnzqqokjngm3f00tg

I know it's a lot to ask, but could you try testing out the Playback Statistics Custom component? Personally, I use the "Update when a track is ended" setting, but it does happen with all other possible settings, too (except "disable" of course).

And as I said, it never happened before my latest update batch (via the components page). I can't remember which version of foo_psf I was on before the current (2.0.38), but Playback Statistics Custom was not updated (it's kind of abandonware since 2009, and it's also impossible since it isn't in the components repository), so it's not something new in Playback Statistics Custom component that causes this.
by kode54 at 9:08 PM EDT on May 18, 2014
It only causes a discontinuity here. Blank spot. Because when it hits the minute mark, it takes it longer than my sound output buffer to restart playback and seek up to the minute mark.

Try increasing your playback buffer size to between 5 and 10 seconds.
by Nisto at 6:32 AM EDT on May 19, 2014
Yes, "discontinuity" is what I mean pretty much. Increasing the buffer size only pushes the discontinuity to a later point in the track.

But I'm afraid I have to admit I've been a fool. The thing is, I actually haven't had a single PSF in my music library before I last updated my components (I had some, but they were not in the library; PSFs I had in the past I converted due to slow, and sometimes inaccurate seeking, and.. now it looks like I may have another reason to :p). Therefore, since I have Playback Statistics Custom set to only update on library music, it has never actually updated the tags of any PSF file before... I guess I just thought I had played some PSFs I had in my library once and that it did work fine...

Anyway, thanks for putting up with me. I'm just relieved knowing the problem isn't just on my side.
by xenphor at 12:56 AM EDT on May 23, 2014
Do some tracks not have looping information? For example, I'm trying to encode X-men vs SF for psx using:

./test -l 1 -f 10 -g -o "$a.wav" "$a"

but tracks like the character select sreen music loop for 5 minutes.
by vajuvaju at 4:30 AM EDT on July 8, 2014
vgmstream cannot decode .hwas files correctly.

This file is from the Nintendo DS game Guitar Hero On Tour - Decades. foobar2000 with vgmstream only decodes the first half of the song, and there are glitches throughout.

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 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270

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