DanyPPC wrote:Super Street Fighter has not correct sound, tested with 0.51 and 0.52
Yes, I hear the PSG sound a bit too long. I wonder if that gets fixed with the same fix as Alien 3. I'll try it with the newest FPGAgen core.
Moderators: Mug UK, Zorro 2, Greenious, spiny, Moderator Team
DanyPPC wrote:Super Street Fighter has not correct sound, tested with 0.51 and 0.52
jotego wrote:slingshot wrote:Did you try it with "Fast VRAM speed?
I don't know what that is.
slingshot wrote:Alien 3 already fixed in git, I think connecting the FM reset to the Z80 reset fixed it.
Which one is your GIT repository? I was pulling from harbaum's one and the bug is still there.
Yes, I hear the PSG sound a bit too long. I wonder if that gets fixed with the same fix as Alien 3. I'll try it with the newest FPGAgen core.
jotego wrote:DanyPPC wrote:Super Street Fighter has not correct sound, tested with 0.51 and 0.52
Yes, I hear the PSG sound a bit too long. I wonder if that gets fixed with the same fix as Alien 3. I'll try it with the newest FPGAgen core.
slingshot wrote:I think I found the problem with Alien 3, I wonder how can it work on the hardware without freezing it.
New release uploaded!
- Has the new cycle-perfect FX68k CPU from ijor. Worth to watch the Titan demos again.
- Has jt12 0.52 for exciting music from jotego.
- Lot of small bug fixes, probably some new bugs.
Feel free to try it, and report any new and old issues.
https://github.com/mist-devel/mist-bina ... -fx68k.rbf
Xtro wrote:Tried Titan 2 Demo and graphically it is perfect, but there is no music and loses sound very quickly.
slingshot wrote:Xtro wrote:Tried Titan 2 Demo and graphically it is perfect, but there is no music and loses sound very quickly.
I've only have silence after the plasma scene, near end. Anybody else has full silence?
slingshot wrote:I think I found the problem with Alien 3, I wonder how can it work on the hardware without freezing it.
New release uploaded!
- Has the new cycle-perfect FX68k CPU from ijor. Worth to watch the Titan demos again.
- Has jt12 0.52 for exciting music from jotego.
- Lot of small bug fixes, probably some new bugs.
Feel free to try it, and report any new and old issues.
https://github.com/mist-devel/mist-bina ... -fx68k.rbf
Xtro wrote:Tested again and I don't have music (FM Sound?) on Titan Overdrive 2 demo. Sound effect work (PSG Sound?) and very shortly no audio at all. I am running the core on 15khz if that matters.
jotego wrote:I think I have explained it in other post. Titan Overdrive 2 Demo tries to push too much the maximum write speed
phoboz wrote:jotego wrote:I think I have explained it in other post. Titan Overdrive 2 Demo tries to push too much the maximum write speed
I don’t know it this is related to the problem above, but now when you have a cycle accurate CPU – shouldn’t the clock speed be reduced to 7.67 MHz instead of 54 MHz? Maybe that will slow down the Titan Overdrive 2 Demo enough?
jotego wrote:
So no fixing needed for Titan Overdrive 2 Demo from my point of view. It is just out of spec.
slingshot wrote:jotego wrote:
So no fixing needed for Titan Overdrive 2 Demo from my point of view. It is just out of spec.
Yepp, Z80 must be slowed down with 68000 memory access wait states.
jotego wrote:
Regular games work with a fast Z80 because they check the BUSY bit and get synchronized there. Or they just use a slow writing approach. But that demo tries to go at full speed to show maximum sample rate on the PCM channel so it is too dependent on bus/system/FM timing.
slingshot wrote:I experienced another strange thing, if Titan 2 has no music, then I start a game, like Super Skidmarks or Sonic 3, then reload Titan 2, it'll have music. Maybe it's just a co-incidence, or the duration of the T80 reset is not consistent, and not resetting the FM correctly, I don't know.
How many cycles required for a correct FM reset? Maybe the reset control port write must have a wait state, too.
jotego wrote:You need at least 32 FM clock cycles (6*32 effective input clock cycles) to have a full reset of JT12. Maybe I should generate an internal reset signal to guarantee this...
jotego wrote:I didn't know that document. Busy flag is not useless, it is actually very useful. The hardware works like this:
The different operator information for each channel keeps moving in a cyclic shift register. There is only one point where you can write. So when you have data to write, you have to wait until you see the operator you want passing through. That wait is 24 FM clock cycles in my (and some Yamaha) implementation(s). The busy bit is held for 32 FM clock cycles with a blind counter. It is blind because it will always count for 32 cycles even if not so many are needed. Busy bit does not gate writes. You can issue a new write while busy is high and it will get processed. But, a new write before the old one is done will delete the previous one and that data will get lost.
So without checking for the busy bit, you can still get things right as long as you wait for a good amount of time between writes and you're lucky.
jotego wrote:I think I have explained it in other post. Titan Overdrive 2 Demo tries to push too much the maximum write speed to the FM chip and ignores the BUSY signal that the chip produces indicating that there should be no writes. It is true that sometimes you can ignore BUSY and still get a correct write. But it is a lottery. Writes are already as fast as can be in JT12: one M68k clock cycles for adress writes and 24 FM clock cycles for data writes. BUSY is held up for 32 FM clock cycles, like real hardware. If that demo doesn't work for those conditions, that's their software fault. I don't think it can work for a large collection of real hardware either as it is now.
So no fixing needed for Titan Overdrive 2 Demo from my point of view. It is just out of spec.
You need at least 32 FM clock cycles (6*32 effective input clock cycles) to have a full reset of JT12. Maybe I should generate an internal reset signal to guarantee this...
Users browsing this forum: Thenesis and 5 guests