Previous Page | Next Page
- by Vague Rant at 2:55 AM EDT on July 5, 2005
- I don't claim to know--well, anything--but, I would assume that the sound data from PAL games would be identical to that of NTSC games, since by the N64 era, audio was corrected (heck, even most NES games had their audio corrected). If anything, I'd guess that it would run faster, since the audio would try to play 16.6...% faster than it was already running, and one assumes that 64th Note plays at NTSC speed.
But yeah. It's not as if they included code in the systems to make the audio play slower. It's just that the whole system runs slower, so that's how it goes.
Again, chances are all this is wrong, I don't know anything.
- by hcs at 3:49 AM EDT on July 5, 2005
- It would be great to be able to adjust global USF volume.
Yeah, it would be nice, that's probably why the feature is already there.
- by Anonymous at 7:36 AM EDT on July 5, 2005
- oops.
- by hcs at 10:54 AM EDT on July 14, 2005
- OK, I'm going through and making some changes, so far I've added the Tagger field and fixed the fade-up which was really bothering me.
What I've been unable to figure out is the bug CaitSith2 reported wherein sometimes you wind up editing the wrong track. I can't see how that can happen in the current code.
- by hcs at 11:31 AM EDT on July 14, 2005
- current version:
http://halleyscometsoftware.com/usf/in_usf010_beta1.zip
- by CaitSith2 at 9:58 AM EDT on July 15, 2005
- Open the tag editor, of the current song. Somehow change the song playing, (let the timer run out, or just change it yourself. (You can still change it yourself, through the playlist winamp controls, even if the dialog is modal.), then change the tags.
- by hcs at 10:30 PM EDT on July 15, 2005
- Found it.
Winamp calls the info window with a pointer to the name of the file, but apparently it also changes the string when the currently playing file changes. So I make a local copy within my info window function now. Really careless on their part, I guess this is part of what foobar advocates are complaining about.
I'm now working on the default tag value, and I'm adding a feature to optionally round the frequency to a more reasonable value. Currently I'm using a lousy rounding technique. I've gone through all the USF sets and found what frequency the game is actually requesting from the OS and I've made a table of values to change to. With the "round AI frequency" option off I'll use the literal calculated value, direct from the AI dacrate register for accuracy's sake. This option will be disabled by default.
- by hcs at 10:34 PM EDT on July 15, 2005
- Also the use of %file% as a tag in the title format will be supported, it'll be replaced by the name of the file.
Also, if anyone can point me at instructions for accessing winamp.ini I'd like to pull the configuration out of the registry at this time but I don't know how.
- by hcs at 11:12 PM EDT on July 15, 2005
- Alright, beta 2 is now up:
http://www.halleyscometsoftware.com/usf/in_usf010_beta2.zip
I've got all the bits I mentioned out of the way, except for the single-dll.
I've also found a new bug:
When the recompiler is enabled and a USF is played wherein the AI DAC rate has not yet been specified at the time of the save state it will use the sample rate of the previously playing USF. This does not occur when the interpreter is enabled. It appears that the DAC rate is simply never set by the game.
You can see this in action by playing, say, Body Harvest after Blast Corps (Body Harvest uses my driver, which doesn't initalize the audio hardware until after the save state was made). The Dynamix intro is actually a better example because you can run it in interpreter mode and see that this problem doesn't exist then.
Something from the recompiler apparently isn't being reset. Drat.
The good news is that this is only a problem on a small number of sets, namely my "generic driver rips" and the Dynamix rip, at the moment. I've really no idea what I can do about it.
- by hcs at 10:29 AM EDT on July 22, 2005
- I'm very strongly considering rewriting 64th Note. I'm currently shopping around for a CPU core. I'd love to use PJ64 1.6 but the source isn't available, so I'll probably stick with 1.4 unless my examination of Daedalus or 1964 (also only an old source version) show promise.
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
Search this thread
Show all threads
Reply to this thread:
HCS Forum Index
Halley's Comet Software
forum source