If any of you remember about 2 years ago, maybe a bit more, I was working on the ADX Encoder Frontend, which I ended leaving at v1.1 and quite unfinished. Well, I polished my skills quite a bit on the software development program I was using and FINALLY I can bring you the changes you asked for and a new interface that won't blind you or make you turn away screaming for some sort of salvation!
After a couple of years in "WIP status", it's now been given a violent shove into a stable (I think) status with better features. Here's what's different and new:
-Text is updated to reflect new program changes (ex., Source File: is now WAV File:)
-Fonts have been changed to Tahoma 10pt for better clarity
-Buttons are larger
-Old Output File: edit box is now gone (it is no longer needed)
-New Open function lets you open the WAV file you want without having to type it in anymore
-Saving and Loading of loop points in *.lp format (can be edited in any text editor)
Here's a screenshot of the new program:
As you can see, it's different from my old one, if it's still being used at all. If not, I can try to provide a screenshot of what the old one looks like for comparison.
Spoiler, click to toggle visibilty
EDIT: - information updated as of April 3rd, 2011
WOW! It's been a while, hasn't it? Now it's 2011 and people are still using my frontend. I'm proud people still find it useful. I came back on here to help others with some troubles I have seen posted on the YouTube video tutorial and perhaps some that think this is all done with completely. I plan on doing a re-write to add some "minor" functionality, but nothing promised. :p
Q: I press the encoding button but nothing happens/pop-up flashes and nothing happens!
A: This can be attributed to two things. You either don't have the adxencd.exe file in the same folder as the frontend or the music you're trying to convert is in or is being output to a folder that contains spaces. The encoder itself can't handle folders/directories with spaces in them due to the limitations of the DOS file system and functions. I know that in Windows XP - Windows 7 you can see full directories in the Command Prompt, but please remember that it's not real DOS anymore. DOS "Real Mode" died out in Windows 98. WinXP and above use a virtual system and thus they can make it do as they wish, except be fully compatible with older DOS programs and viewing habits.
In short: Make sure the WAV and ADX files are in folders and being saved to folders that have NO spaces. Underscores work just fine.
Q: *Anti-Virus* program has declared viruses in the program! This seems sketchy! ;
A: False positive. To be honest, this program was created in a program called Multimedia Fusion 2 Developer and I don't see why it'd be showing false positives. To get the program to run/to be extracted onto your PC, simply add an exception. If you think this is more trouble than it's worth, submit a report of a false positive or don't use it. The encoder can still be used without the frontend, it's just a pain to type out all those commands into the Command Prompt. If you submit a report for a false positive and they find there is a virus (an actual one), then I can try to add a virus-free version, which is the one I use, but it's the same one everyone else has been using. My developer version was lost quite some time ago after some major HDD failure.
Q: When I encode my WAV to ADX, the loop points sound horrible/are off!
A: Remember, you're encoding using samples for precision instead of decimal-based time. Also, conversion from 16-bit to 8-bit can cause loop point changing as well as down/upsampling your WAv files before saving and encoding. Make sure your loop points are just the way you want them. Another thing is to leave at least 32 samples after the end loop point. Some music (I don't know why) has clicking and popping noises at the end loop if the loop ends right at the cut off point. Happened to me a lot during initial testing of the frontend.
Q: My encoded ADX is really loud and just one big thing of static! What happened!?
A: You're probably trying to convert a 32bit or 24bit WAV file. That is a big no-no. The program was made to work with files at a range from 8khz - 48Khz and at either 16bit or 8bit quality. This is not an issue with the frontend, but rather an issue with the way ADX files are made. Blame CRI Middleware for that.
Q: My ADX files won't play at all in MUGEN!
A: I've just recently found out about 1.0 (I was gone from the MUGEN scene for a long time) and I don't know if Winamp plugins still work, but if they do, grab the latest version of vgmstream since in_cube is now obsolete. It should also fix issues with loop points sounding off if you did everything right. Seems the old in_cube plugin was rather buggy and although vgmstream is still not completely bug-free, it fixes a lot of bugs that were in in_cube.
I hope this helps others that are still using this. Thanks for your continued support by using the frontend!
- EDIT edit...lol? - Okay, so I've found out that there is no longer a need for ADX files in 1.0 due to in-engine BGM looping of WAV/MP3/OGG files without the need to convert to a WAV and then an ADX file. This has many advantages over ADX, such as:
- No need for conversion of MP3/OGG to WAV, then to ADX
- MUCH smaller filesizes (from 20+ MB to 1-5 MB instead)
- You choose the quality of music being used
It seems they are using the same method of looping, which is using samples, not decimal-based time. Instead of typing copy/pasting the samples into the converter, just put them into the stage defs in the music section.
Although it saddens me to know that this measure effectively puts my frontend out of business, it's great to see that this functionality is now integrated directly into the engine itself, which makes me happy. If anyone needs help with the frontend for the use of ADX files in other things (or perhaps for WinMUGEN, for those that have not upgraded), then I'll be glad to help out in any way I can until no one needs it anymore. Only at that time will I have this thread locked. Thanks again to everyone for their support during the creation of the program. I really appreciated it.