Recent Posts

So fallacy are you just posting stuff to intentionally piss people off?  Field of Dreams is one of the greatest movies ever made and for the record it has absolutely nothing to do with baseball.   Baseball is used as a metaphor for life, the connections and divisions of the different generations, the relationships of fathers and sons. The point of the film is sometimes we need connecting tissue in life to bring people together and to mend relationships and for many generations we've used baseball as an excuse for fathers to hang out with their sons and bridge social and economic divisions.  If what you got out of it was it's dumb because baseball is dumb.... well I'm sorry for whatever happened in your life to make you this way.   

In this release, we've focused mainly on the eye candy, with some nice improvements to visualisation, better feedback during media scanning, and a number of new screensaver options.

This includes a nice little progress bar that will (optionally) be displayed during the media scan.
To turn this on, set 'ScanProgressShow' to 'true'.
To change the color, use 'ScanProgressColor'.

Whether using the progress bar or not, we now quickly pre-scan the SongPaths and let you know how many (valid) media paths and items will be processed, and give you a percentage indicator. If the progress bar is disabled, info will display in the 'Up Next' (Display2) window.

The new ScreenSaver options (all using per-pixel GPU math for silky smoothness):
  Aurora: Reminiscent of the southern/northern lights.
  Lava: Resembling a classic lava lamp, blobs float around the screen.
  Mandelbrot: Display the Mandelbrot fractal set, zooming into a known interesting boundary point (you can configure the coordinates used). NB: Very computationally intensive, so you will need a reasonably powerful system to avoid stutter (eg. runs full speed on a 4K monitor with a GTX 1060).
  Plasma: A nice colorful 'Plasma' field.
  Smoke: Gives a lovely simulation of smoke.
  Snow: With Christmas just around the corner, this option provides a little snow storm.


Changes:

• Added: Option: jukebox.ini > settings > ScanProgressShow.
• Added: Option: jukebox.ini > settings > ScanProgressColor.
• Added: New ScreenSaver options: 'Lava', 'Mandelbrot', 'Plasma', 'Smoke', 'Snow'.
• Fixed: Off-by-one error while scanning - total number of SongPaths.
• Refactored: Audio Visualiser - updated wave and FFT calculation, and implemented a GPU shader for a nice uptick in performance. Visualisation is now more responsive while appearing smoother.
• Refactored: SongPath scan - now pre-scans all SongPaths for valid media and calculates total number of available media items (so we can display progress percentage during scan).
• Refactored: Screenshot. Now, if the screensaver is running when you take a screenshot, the file will be named to match the active screensaver.
• Refactored: Screensaver 'Digital Rain' to use a GPU pixel shader, and cleaned up the jukebox.ini options to suit.
• Refactored: Screensaver 'Life' to use a GPU pixel shader.

Link here:

VideoJuke - 0.971b

Holy smokes. The .286 release that introduced emusync is amazing!!

Studying the documentation here:
https://github.com/antonioginer/GroovyMAME/blob/groovymame0286/docs/groovymame/real-time.md#configuring-part-the-real-time-audio-backend

I am using Windows. To avail of the best low latency new features do I need to run groovymame with these parameters or are they set in the mame.ini file?
-sound part
-audio_latency 0
-video d3d11 *
-framedelay 0
-autoframedelay
-nosleep
-tearbar

e.g.
groovymame -sound part -audio_latency 0 -video d3d11 -framedelay 0 -autoframedelay -nosleep -tearbar


* On -video d3d11 the docs read:
"Unfortunately, it was later discovered that this backend adds a full frame of latency on older ATI GPUs —confirmed at least on the HD 5000 series, likely due to legacy drivers"
I'm on R9 380X. does that suffer the frame of latency with d3d11? (If so, what is the best recommendation instead of d3d11?)


Thank you!!

anyone know how best to contact Glen about his products, I have tried email, FB but no response on anything.

Any help appreciated.

thanks for response thats great to know

Bro, sorry to hear your cancer came back and left increased struggles, but glad you beat it again and are still with us.  I had chemo for lymphoma in 2020-2021 and it definitely aged me, getting run over by a dump truck 6 times will do that to you.  But you and I now know how to enjoy the good moments when they happen.  Stay strong!

Another possible source of information is 10yard and his DKAFE project. He has done lots of DK hacks including sprite swaps so he can probably point you toward which specific ROM(s) should have the missing sprites.
https://forum.arcadecontrols.com/index.php/topic,164960.0.html
https://github.com/10yard/dkafe#readme

Hey Scott,

The Donkey Kong Forum moved to a new site a couple years back,   folks there will definitely be able to help LTC better than I can with hardware issues.
https://donkeykongforum.net/

These eeproms on the PCB are responsible for graphics.  The ID of the chip and the related file in MAME below.

Fixed/background graphics

3N → v_5h_b.bin
3P → v_3pt.bin

Sprites / moving objects

7C → l_4m_b.bin
7D → l_4n_b.bin
7E → l_4r_b.bin
7F → l_4s_b.bin

I've never seen an actual board myself,  so head over to Donkey Kong Forums LTC,  and you'll get the help you need.
They also have a discord at https://discord.gg/2tjHUa6wM

Good luck

Cool-o   

Yeah essentially the 100nF (or 1uF for Y) gives AC coupling (blocks DC), the 100R gives current limiting, the 100R + 75R is a voltage divider, and the 75R sinks DC noise. What you said

For the zeners, I selected 12v as they are there to prevent voltage spikes (like ESD or momentary short) from damaging the jungle. 1.2v zeners seem an obvious choice, but can be very "leaky" and allow a fair bit of current through anyway (quantum tunneling) at lower levels, which would be bad for a video signal. So that choice isn't written in stone, you might be able to go as low as 6.8v or 5.6v and probably be OK, but if going that way probably want *another* diode (e.g. 1N4148) in addition to prevent quantum tunneling leakiness. Just using 12v zener is simpler while doing mostly that same thing. I looked far and wide on the matter, you can read more about my reasoning at the time on my TCL TV mod thread.

Otherwise, there is a lot of stuff in the service menu to optimise like tint and colour systems, RGB brightness levels etc. and honestly I've half-forgotten most of it already. There are like 20 pages of settings. I think I attached an English version of a complete service manual PDF earlier on this thread, with some notes.

Yeah those photos are pretty early in the process, I've cleaned things up since then. My board didn't appear to have those spots. I'll see if I have any applicable zener doides as well. Your schematics have been very helpful, so thanks for those. The unloaded voltage was probably just too high as well, so I'm otherwise not sure why the actual signal level was so dark before. Lack of current limiting is the only other thing I can think of, as others have done YUV mods to these boards without that issue. I do also recall the original capacitor I decided to re-use from one of the audio output lines early on was causing sync issues, I believe it was 10μF. Before I replaced it with a 1μF electrolytic the picture would lose vertical sync between bright and dark transitions and sometimes bounce a little vertically. That no longer happens but I'm still swapping those with the ceramic 104 caps as suggested.

I looked carefully and don't seem to have that I˛C header on my board. Those traces don't go anywhere else except between the EEPROM and main microcontroller.

My 100nF capacitors are on the way, still waiting on the resistor kit I ordered to ship.

I totally missed this thread.
Nice work work. Except for the driving part. Hehe.

I love to see some different games getting love.