vgmrips

Can anyone please point me at an in-depth tutorial on how to use vgm2txt and vgmlpfind to get the right values for vgm_trim?

I do have some previous minor experience with vgm2txt, vim_trim, etc. but this was for "single shot" music tracks that don't loop (Fantasia on Genesis), so it was extremely easy to find the start and end points in the vgm2txt file.

I'm now trying to rip the music from "PGA Tour Golf" on Genesis, which are regular tracks that loop (although I don't think any have an intro section, which makes things easier).

I logged the main theme (when the game starts) over 3 repeats but I can't work out how to find the start and end points in the vgm2txt file (attached), and vgmlpfind produced the output below... which I don't understand.

If there isn't already an online in-depth guide... then I'd really appreciate help understanding this particular output.

im not good at explaining but based on my experience, vgmlpfnd's purpose is to find loop points and end points of an vgm file. i use this to trim my vgm files without to do manual looping, but sometimes vgmlpfnd can be useless at all. to find a proper loop, you must need to log musics and play it at least 3 to 4 loops which vgmlpfnd can find the exact commands and determine what sample values has the proper loop.

Example for this:



The values you need are Start from the Source Block and Start from the Block Copy. The first value (Source / Block) means "where the loop starts" and the second one (Block / Copy) "where the end sample starts", so actually where the original loop ended. You can use then use vgm_trim with the inputs 0, 477258 and 2374215 in this case.

vgmlpfnd may report f, ! and e in the results. "f" means a proper loop has been found, which is more probable to be the right one than others without an "f" or !. If a "!" is displayed, it means it's almost sure the the correct loop has been found.





When you don't get an "f" or a "!", don't worry about it; just check the actual loop time of the track and compare that with the results. Or try to relog it again with much more loops, around 5 to 7 loops if see if vgmlpfnd is gonna find the proper loop for that. If it doesn't work again, try to lower the "minimum of matching commands" to like odd or even numbers. Default of this command is 1024, so try lower, maybe 512 or like 128. after that, there's a bunch of loop points that you can find, it's a little bit tricky, but one thing that you've need to find in vgmlpfnd is the marking like "f" or "!", which proper loop has been found. if it does not working again, I'm sorry, but you have to do manual looping using audacity.


vgm2txt is somewhat edit your vgm files using hex edit, finding the same loop points of each offsets to compare and verify it. or to remove volume of an sample. but there's much more for that that i can't explain properly. But there's an accurate description I found on SMSPower.

VGM Text Writer (vgm2txt) This program converts a vgm to a txt file showing the list of commands in byte order. Although it does not encode the values to notes, it does provide helpful labels, and helps you verify loop points and proper sample values to enter in vgm_trim. If the loop finder has challenges, this tool will help you see why. It acts as a second set of eyes on the results of the loop finder. Although loopfinder is easier to use, the output, once understood, will be the superior authority on the proper loop point. It shows you exactly what is going on. This is also an important asset in the vgm processing toolkit.
-SMSPower

So, that's it. Hope it helps.

_________________
To-Do list:
Rip all Dooyong Games (90%).
Rip all Afega Games.

Tempo: 105.95%
Pitch: +1.00

suprise is surprise, ok?



Please, check my WIP list for more updates.

I've almost forgot!

You can use vgm_sptd to cut silence or delay at the start of the music. remember, not all vgm files were cutted properly so if the vgm doesnt cut properly on the start sample points, you have to do manually as i said.

_________________
To-Do list:
Rip all Dooyong Games (90%).
Rip all Afega Games.

Tempo: 105.95%
Pitch: +1.00

suprise is surprise, ok?



Please, check my WIP list for more updates.

Thanks - that's all extremely helpful. I guess a large part of this is also just trying out the values in vgm_trim and listening back to the result.

What particularly confused me about the vgmlpfind output were lines like this:



where the values seem too large for the columns. What's going on there?

Oh, we're the same as mine too. Right now, I'm using Ubuntu for VGM ripping, cuz my hard drive broke. Don't worry about that output. What I'm usually do when I encounter this is to match the loop value number and end value number counts.

example of this



so the loop value is 5446054 which is counted 7 digit numbers. after that, you have to match it on the end sample value. Start at the last digit of the number like this, 9897070. also if you encounter this thing, you need to look up another loop points as a reference, and also the time. which is important how the samples increased by 1 digit or not.

example of this


on the third line, you see a bunch of joined numbers that you have struggled with. now, I want you to look at the another line, like line 1 or line 5. use that to match the sample value between what digit numbers count.


sorry if i cant explain it to you properly, but it is what it is.

_________________
To-Do list:
Rip all Dooyong Games (90%).
Rip all Afega Games.

Tempo: 105.95%
Pitch: +1.00

suprise is surprise, ok?



Please, check my WIP list for more updates.

The broken columns are probably caused by me using "tabs" for indentation.
On Windows, printing a "tab" character erases all characters that are skipped. On Linux systems, it often doesn't erase stuff.
I guess that is something I need to fix in vgmlpfnd.

And HappySpaceInvader:
Please don't attach "vgm2txt" output. Just attach the raw VGM itself.
The .txt file is useless if we want to help and we can easily generate it by ourselves.