freezy
CRZ colorization files not in sync/plays slow on real PinDMDv3
It may be related to issue #406 , which was reported for alphanumeric colorizations only. When using a CRZ file for colorization on a real PinDMDv3, the playback is slow. In attract mode al plays fine and seems to be synchronized, but when starting to play a game, the real DMD lags behind with scenes and scores. Once the game ends and the attract mode begins again, everything is synchronized.
To demonstrate the issue, I recorded three different games, showing my real DMD, the virtual DMD, and the PinMAME virtual DMD. Since I was holding the phone to record, I couldn't play the game, but it's evident that the score and scenes lag behind compared to the virtual DMD, which matches the PinMAME DMD. As all video's are just short ones, the issues is best to see in ATM. And when game is over and the Matching starts, you will see that it skipps all the rest of the scores and scenes and start attract mode.
Additionally, I've attached three dmddevice.log files created during the games, although I didn't notice anything unusual.
I find it hard to believe I'm the only one experiencing this problem. Perhaps others haven't noticed it. I'm hopeful for a quick fix so I can enjoy the CRZ colorizations as well.
AFM : https://youtu.be/oEzdvOD3jJg DmdDevice_AFM.log
CFTBL: https://youtu.be/qlifYAlBRBo DmdDevice_CFTBL.log
Twenty4: https://youtu.be/IBItdIcMKE8 DmdDevicetwenty4.log
I observed a brief detail. When the ball is drained and bonuses are counted, as the ball enters the shooter lane, the DMD are in sync again. Scores went fast and other scenes where skipped
I wasn't aware, but I noted the following error multiple times ; Error writing to serial port: The semaphore timeout period has expired.
not sure what is causing this . same tables with PAC files are working fine. I can't imagine that I'm the only one with this issue
IMO this is a problem with 64-color frames being converted to rgb24 because pindmd3 doesn't understand the 64-color format. We'll see what we can do with the firmware..
In the meantime, I ordered an esp32 and put zeDmD firmware on it. Connected it to de Pindmdv3 and all is working now. If it is just me, this issue can be closed
A firmware update sounds easier than adding hardware but I'm happy to go either way. There has to be a lot of pindmd3 users out here that would appreciate the above with instructions. Thx
If you want the route I took :, I ordered an esp32 (for 6 euro's including shipmemt), and due to my fine motor skills no longer working well, I couldn't do the soldering myself, so I bought a shield that fits the ESP32 and allows the cable to plug into the LED panels. The shoeld was more expensive (17 euros and 10 euro shipment, but if you are handy you can make this cable your self). Zedmd has a nice tool for installing firmware and that was flashed in a minute. All can be found here: https://github.com/PPUC/ZeDMD.
Thanks Mike, but I'll try to be patient even though I am pretty handy with a soldering iron; and thanks Freezy for your continued support.
Kraken, made a serum v2 of AFM for me. That is playing like a charm. What I understand is that serum V1 is RGB888 and Setum V2 is RGB565. If authors of the Crz files update their colorization files to version 2, al should be f8ne, right ? Or am I missing something?