Okay, with problem 1, I know so far that the PSG noise works like the hi-hat I'm trying to use. But only if you open the tracker, and then open the song I made first. Whenever you load a different song before you upload mine, the PSG sounds different.
Also, unrelated, your example song has all three PSG tone channels playing, along with the PSG noise channel. I thought that you couldn't do this on the real hardware(either two tone channels and a noise channel, or three tone/no noise)? Though I might be mistaken, after all...
It is not a bug, you just need to learn SN76489 features. It can't produce high frequency noise in low resolution mode, it is only possible in high resolution mode, which indeed takes one of tone channels. It is documented in Instruments editor section of the help. If the help does not open, try a CHM decompiler or online viewer.
Demick12 wrote:
What's next? SEGA CD PCM channels? ;)
There is no point to make a special tracker for PCM channels of any device. Just make a MOD player or something and use existing software.
Regarding GEMS and SMPS, who should use it? If me, why I should do that? It is old, very limited, and copyrighted software.
I will make a question not directly related to VGM MM. Why GensKMod dumps doesn't store the FMS/AMS values?, the same for MVS Tracker MD.
This is intentional, right?, maybe those values are managed with effects?.
And why LFO enable/disable flag @ register 22 and his frequency is not included on VGM MM?, is written by the effects automatically?.
Thanks.
Edit: hrm. The PSG channels also sound very soft in AudioOverload (and the newest version of the in_vgm plugin for WinAMP). :/ I wonder WHY, though. o_O
Your best bet would be to ask ValleyBell. It may have been done deliberately as it may be more accurate, who knows.
I will make a question not directly related to VGM MM. Why GensKMod dumps doesn't store the FMS/AMS values?, the same for MVS Tracker MD.
This is intentional, right?, maybe those values are managed with effects?.
Import code is taken from TFM MM. YM2203 has no LFO. Also, the instruments format weren't documented mostly, so it was a guess work, done long ago. If some instrument formats do store the values, but the values are not loaded by VGM MM you can report about it.
Delek wrote:
And why LFO enable/disable flag @ register 22 and his frequency is not included on VGM MM?, is written by the effects automatically?.
The docs wrote:
Lxy - Set LFO
Enables or disables the LFO and sets its frequency if enabled. Zero xy disables LFO, with non-zero x you can set frequency of the LFO using y 0..7 (0 is slowest, 7 is fastest).
Kizul wrote:
Any chance you could make the PSG channels a little louder in the editor? D:
Previous page:
Shiru wrote:
Volume balance is the most asked question. To save typing:
Shiru wrote:
I have no idea what the proper FM/PSG balance is, as I don't have the hardware, and it is different across the emulators. I'm still waiting for help from some people who know this. Will be changed later.
There are other problems with VGM export as well. Wait for updates.
Okay, with problem 1, I know so far that the PSG noise works like the hi-hat I'm trying to use. But only if you open the tracker, and then open the song I made first. Whenever you load a different song before you upload mine, the PSG sounds different....
It is not a bug, you just need to learn SN76489 features. It can't produce high frequency noise in low resolution mode, it is only possible in high resolution mode, which indeed takes one of tone channels. It is documented in Instruments editor section of the help. If the help does not open, try a CHM decompiler or online viewer.
OK. That explains it, about the PSG. Thanks for the quick response, Shiru. I've almost figured out this chip. Haven't really used it all that much, other than using Mod2PSG, so I guess I've got some documents to review about it. Shouldn't be too hard to find.
The help file I'm still having trouble opening. I've tried moving the file, decompiling it, opening it online, re-downloading it, still nothing. I don't want to keep bothering you, or anyone else with this, though. Is there another method I could try? Or would anyone be willing to send a help file that works? Maybe I'll figure all of this out on my own by then, and no one will have to go out of their way.
Thanks again, and sorry for the intrusion.
_______________________
Thanks for listening!
-Linker2A03
How it could be nothing with decompiling? CHM is just a compressed set of HTML files. You can get them back with a decompiler.
Also, if you try to google about the problem, you find it is common, and there are articles on this, like that one. As I don't have any problems, I can't check if it can help, so check it by yourself.
Hey, that link actually helped me out. After unchecking a few things(read-only and the "always ask" option), it now works, with no problem. Sorry for taking up valuable time.
Anyways, once again, great tracker! The best one I've used so far. If I could, I would donate to help the cause. Trying to save money for a car, so every bit counts. Probably afterwards, though. Thanks for your help!
_______________________
Thanks for listening!
-Linker2A03
* Help item disappeared from the About menu after a module or an instrument has been opened
* VGM output is improved and optimized, also fixed bugs with exporting modules with large amount of sample data
+ Built-in VGM optimization code from VGMTools by Valley Bell
* Saved VGE files were too big, had 32K of empty data added by a mistake
* PSG envelope now is reset on every new note, previous FM-like behaviour didn't allowed to use instruments with slow attack in a predictable way
* Effects above F were displayed incorrectly in previous/next patterns
* Resampling had problems with large samples with 32000 Hz samplerate
* DAC and FM desync by a frame in the VGM exporter is fixed
* Detune parameter of a wrong PSG instrument has been used
* Unsupported WAV files were blocked until the editor closed
* Some clicks in the end of samples are removed
* Default volume is lowered a bit to prevent clipping
* SMPS instruments import is fixed
+ Automatic horizontal scroll in the pattern editor for cursor movements
+ Now detune for PSG is audible in the instrument editor
* Periodic noise was detuned because of wrong emulated PSG settings
+ Adjustable pitch for samples
+ Testing samples with Space key
