PCM pack for testing (counting from 0 to 255)
Zeldix :: MSU-1 Hacking :: MSU-1 Useful Things :: Tools
Page 1 of 1
PCM pack for testing (counting from 0 to 255)
Hi, everyone.
I made a pack like this a couple years ago to work with the PCM's pack that I was involved and never occour to me to share this because, at the time, I thought that I would be the only one who ever need this. (I think I'm still the only one, but well... Who knows if it would help somebody...)
This pack contains 256 pcm files witch simply speaks the number of the file. It helped me to verify things like:
-If the file called is correct.
-If the file is called at the right time.
-If the file is looping or not.
-Verify what file is called at a specific level/event (when a PCM pack contains duplicates)
DOWNLOAD MSU-1 TESTER PCM PACK:
ENGLISH SPEAKING
https://mega.nz/file/BZJA3IYB#f6do68YX4Y-b9exBR8wBY_eJSxzJzYdvmYtQ0hkmy_M
GERMAN SPEAKING
https://mega.nz/file/UVA2VIKT#f_-xOvzYJZbeZZRS7yJagq_jah_jnxKfCc3ROupDfiw
BRAZILIAN PORTUGUESE SPEAKING
https://mega.nz/file/oMBmSIpS#alfJIMPfJnUO5-tskHeJ9kIRCKXkrVtKXWKfarB-JbY
EXAMPLE: https://www.youtube.com/watch?v=rRQUiVkjUMk
It is always necessary to rename the rom file to "tester" or batch rename the files to fit your work. I recommend this last one because if you plan to make save states for testing on a emulator, it would be better to get a exclusive rom filename. Bulk Rename Utility is a mandatory software for this kind of task.
Create and share spreadsheets to keep informations about files, song titles and looping points would be a great job for every MSU-1 and could help future jobs for those who wasn't involved with the first pack. Unfortunately, almost every high demanded game have your MSU-1 job done. So, I think that this kind of re-track probably will be necessary in some cases.
I made a pack like this a couple years ago to work with the PCM's pack that I was involved and never occour to me to share this because, at the time, I thought that I would be the only one who ever need this. (I think I'm still the only one, but well... Who knows if it would help somebody...)
This pack contains 256 pcm files witch simply speaks the number of the file. It helped me to verify things like:
-If the file called is correct.
-If the file is called at the right time.
-If the file is looping or not.
-Verify what file is called at a specific level/event (when a PCM pack contains duplicates)
DOWNLOAD MSU-1 TESTER PCM PACK:
ENGLISH SPEAKING
https://mega.nz/file/BZJA3IYB#f6do68YX4Y-b9exBR8wBY_eJSxzJzYdvmYtQ0hkmy_M
GERMAN SPEAKING
https://mega.nz/file/UVA2VIKT#f_-xOvzYJZbeZZRS7yJagq_jah_jnxKfCc3ROupDfiw
BRAZILIAN PORTUGUESE SPEAKING
https://mega.nz/file/oMBmSIpS#alfJIMPfJnUO5-tskHeJ9kIRCKXkrVtKXWKfarB-JbY
EXAMPLE: https://www.youtube.com/watch?v=rRQUiVkjUMk
It is always necessary to rename the rom file to "tester" or batch rename the files to fit your work. I recommend this last one because if you plan to make save states for testing on a emulator, it would be better to get a exclusive rom filename. Bulk Rename Utility is a mandatory software for this kind of task.
Create and share spreadsheets to keep informations about files, song titles and looping points would be a great job for every MSU-1 and could help future jobs for those who wasn't involved with the first pack. Unfortunately, almost every high demanded game have your MSU-1 job done. So, I think that this kind of re-track probably will be necessary in some cases.
Last edited by daniloroxette on Thu 4 Jun 2020 - 10:30; edited 2 times in total (Reason for editing : link updates, 0 adding, 255 limit)
daniloroxette- Since : 2017-09-25
Re: PCM pack for testing (counting from 0 to 255)
That is something cool and eases the pain for people having problems with the debugger.
@all: use https://www.zeldix.net/t2079-bulk-rename-utitlity
to rename the pcm set to your rom you want to test (or better: rename the rom (sfc/smc) and empty msu file to tester.smc/tester.msu.
Thanks for sharing
@all: use https://www.zeldix.net/t2079-bulk-rename-utitlity
to rename the pcm set to your rom you want to test (or better: rename the rom (sfc/smc) and empty msu file to tester.smc/tester.msu.
Thanks for sharing
Conn- Since : 2013-06-30
Re: PCM pack for testing (counting from 0 to 255)
This is really simple and pretty smart
JUD6MENT- Since : 2018-04-19
Re: PCM pack for testing (counting from 0 to 255)
Nice. It made me glad. Thank you.
I updated the links because I included the empty tester.msu file inside the pack and add a pack in português.
I updated the links because I included the empty tester.msu file inside the pack and add a pack in português.
daniloroxette- Since : 2017-09-25
Re: PCM pack for testing (counting from 0 to 255)
Just some small things I noticed when downloading your sets (sorry I didn't found before):
you definitely need a tester-0.pcm (zero). There are a lot of games that use the 0 as track (some only mute, but a lot also have it as an real track).
MSU cannot go beyond FF (track -255), so all tracks 256-399 can be removed. With track-0 you have 256 files.
you definitely need a tester-0.pcm (zero). There are a lot of games that use the 0 as track (some only mute, but a lot also have it as an real track).
MSU cannot go beyond FF (track -255), so all tracks 256-399 can be removed. With track-0 you have 256 files.
Conn- Since : 2013-06-30
Re: PCM pack for testing (counting from 0 to 255)
Mistakes of those who don't understand well of the "paranauê". Thank you so much for checking them out. I updated them and the infos.
daniloroxette- Since : 2017-09-25
Similar topics
» New playthroughs & testing
» Erock's Testing
» Erock's Beta Testing
» Conker 1.2 beta testing
» FMV's Mega Pack
» Erock's Testing
» Erock's Beta Testing
» Conker 1.2 beta testing
» FMV's Mega Pack
Zeldix :: MSU-1 Hacking :: MSU-1 Useful Things :: Tools
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum