I have the same with my Indy. When I disconnect the ribbon cable from the display controller board, the error is gone. I have a friend with the same problem and same behavior. I mean, this is of course not a solution but I think it's a way into troubleshooting the problem.

does this problem occur with PIN2DMD or ColorDMD displays, has anyone tested this ??

Perhaps I should test it on my Funhouse after all, I will after a board rebuild.

I use a LCD with a Pi Zero as a DMD so no high voltage, I believe colorDMD and PIN2DMD would use the display board as I am so the issue would probably remain.

I have wondered because I use a Pi to produce the DMD image that there may be a way to use the data straight from the bus to the pi and do without the controller.

There are multiple ways to power a Pin2DMD, you can power from HV off the board, or a separate power supply. My STTNG (where this Tilt board is going) has a Pin2DMD with an external power supply.

I’m also using a Pi-based display in my TZ so I can test a couple different configurations once I build my board this weekend

But don't forget, it's about the data cables, not the power.

are there any progress ?? did the project collapse?

Steve still posts updates, he just Gets busy from his regular job! I am behind on my install too, just have not had time to finish soldering the kit

I have a 2.6g board to re-build a kit its half finished then got Flu for the last 2 weeks have not been in the mood to finish it yet. I also had the random sounds on my Getaway, I will post an update next week.

I'd love to do this for a CFTBL mod, but I have little faith in my soldering abilities.

ok all rebuilt, just testing on the bench first, all is working ok from the GUI, will be putting back into Getaway this PM.
photo_8301142032747779218 (resized).jpg

Thanks for the update. I'll hold off purchasing until the next revision comes out.

Ok, not good news same old random sound being played unless I disconnect the DMD Board, all sounds in the wrong places. My Getaway is obviously just feeding the Pi garbage .

If this is indeed noise I am not sure how steve45 is going to overcome this as his Williams machines do not seem to have this error making testing a problem ?

I am going to buy a pin2dmd but I cannot see this making any difference as I run a Pi with an LCD screen from Dr Pinball for my DMD so just the low voltage side of the DMD driver board being used on Getaway. I am running L-5 Rom modified for LED bulbs to stop flickering. steve45 can you please quote a link for working Funhouse Sounds I will test it in mine.

I am going to do some more testing

1. Replace the ribbons in my Getaway as they are the originals.
2. Run on a dedicated 12v PSU

Can anyone please provide a link to a working Funhouse soundset ?

Hi guys ,

I've received my kit for my Tales from the Crypt this noon... I ordered the PortExtender too but I don't have the IC

Then, I tried to install 1.25 on my raspberry Pi 3A (the one which doesnt have RJ45)... and it's very tricky to configure WIFI.
There is no "dietpi-wifi.txt" so I can't activate it at the first launch.
Of course, I tried to configure it by connecting me with SSH with the wifi as Hotspot but it seems that changing parameters in dietpi-config doesn't work too.
I can't find any exemple of this file on the web.

Any help will be welcome

Best regards

After booting the Pi, you should see a Tilt!Audio network/hotspot on your laptop / desktop if you have wifi enabled (It can take a little while for it to appear). Connect to this hotspot (the passphrase is "tiltaudio"). You can now access the WebUI via the following URL:

http://192.168.42.1/:31008

In the WebUI you should be able to configure the Wifi, save it and then reboot. You can now connect via http://tiltaudio:31008/

If http://tiltaudio:31008/ doesn't work, figure out the Pi's IP address and use that instead: http://xxx.xxx.xxx.xxx:31008/

https://tiltaudio.com/2019/05/11/whats-new-with-firmware-1-25/

This took me a while to figure out too. But what I discovered was that I just needed to wait longer for the hotspot. Don’t bother with the dietpi changes

It takes a few minutes for the whole thing to boot up and display the hotspot.

I was getting no sound using the built in amps so I ended up using a separate amp running from the pi's headphone jack. It is working fairly well on my HSII now, still have a bit of an issue with the background music fading out when an SFX plays but otherwise the SFXs play at the right times. I'm using the original display too.

Reading a few pages back I wonder if fixing the ground issue might fix the internal amp issue too? It would be nice to use those instead of an external amp.

Well, I tried this several times before.... but I've just tried it another time now and WHouuhouuu that works : thanks a lot !

Now, I have to assembly the PCB.

When you say it's basically the same hardware, do you mean that the pinout to get sound adress is the same, so we can use the last PCB, the actual software version and a sounds pack to make it work ?

I'm aware that we need to create the sounds pack ...

ok so I am basically stuck on the same old issues with my Getaway, this is my second board. Random playing sounds not all sounds in the correct place or triggering incorrectly.

I know this is diy but I have built other mods no issue, and looking through the forum I cannot see anyone claiming 100% success.

I have rebuild the board, changed ribbon cables, run from a dedicated PSU, run 1.25, 1.27, 1.28, 1.29.

I am going to try a different make faster sdcard and a different Pi3 and try and find my old L-2 rom chip to put back in if that does not work I am done with it.

Then off to Pinsound.

Doesn’t Steve have a working Getaway ? How could it possibly be so different I wonder

Steve45 does not know why my Getaway is different. All I know is that he uses an older rom and a Pin2DMD. I do not want to go to Pinsound I like the fact the board is going to control addressable LEDs etc but if I cannot solve the fact that it purely does not work on its main use as in sound other functions are irrelevant.

I know at least of 10 machines running without a problem. If I find some time I can test it in my Getaway.

I also do not have a HV DMD, the odd thing is with mine is about 3 of the sound FX are 100% the adding of the bonus after ball drain for example is spot on all the time, other sounds like the horn sound on the 2x freeway work about 20% of the time. Music is all over the place.

The main thing also I cannot get my head around which someone with good up to date electronics knowledge could answer is why does my card act exactly the same way as it did when it had the 0v pin not connected on 2 of the ICs.

Tilt Audio is a fantastic project I really want it to work but there seems to be too many variables to contend with.

I'm in the same boat - I get missing sounds and background sounds that don't stop. My main machine I'm trying to get this to work in is a ST:TNG which has a PIN2DMD fitted as well. I've also tried it in my TAF with the same problem.

For those who are experiencing this, could you try and go into the Service Menu, and see what sounds you get there when using the service buttons? On mine, I get the expected correct sounds, but sometimes I get no sound. For example, if I repeatedly press the + button, I'll get the correct sound around 7 out of 10 times, but the other 3 won't play any sound at all. Those 3 might be in a row, or randomly dispersed among the presses. The Tilt audio log shows the board as misinterpreting the sound command for those errors. That leads me to think it's a timing issue on the Tilt board. The original DCS board and a Pinsound board both work fine in the machine.

Ok so last night I test metered all connections from the WPC connector to the 3 ICs and through to the Pi, I found pin1 of the 74LCX374 (READ_OC) not making contact with pin24 of the Pi.
Its not the board I think i have a bad solder joint on the IC so I will fix that today and try again later.

That sounds like something, which can be reproduced to debug it.

That's good news, report back when you can!

Ok I have fixed the board connection I have now made sure the board is 100% no errors.

More of the sound FX now are triggered correct. On the Pinball Test menu about 50% are correct. The music is still triggered wrong but I believe it is now not random it is triggered from switches which are supposed to trigger sound FX in play, I still get the unwanted sound effect playing whenever it feels like it.

So its onto the soundsets they must be wrong in some way ??

I have not bought a licence yet so I get the interruption of the Pi serial number, I take it that all it is as in an interruption not totally miss timing the sounds ?

That would be my guess. Good news at least! The sound sets being scrambled/unscrambled is much easier than a hardware issue

Hoping to get time to finish my board today- I am missing one of the small capacitors so hopefully I have one in my workshop somewhere

In my soundsets I have a file called config.pinsound reading through this thread I should have a file to descramble the sounds called config.raspisnd ?

Also the file is scrambled

¹Wñ2½Â©û?,ˆ®UØÛXŽÉšÊ.ƒh

Not

ducking_voice=65
ducking_sfx=90
gain_music=13
gain_sfx=16
gain_voice=28
gain_jingle=11
gain_single=15
# generated from jp-ost-mapping.txt
# first 4 digits are sound id in hex, next number ... decimal
0000 3411162208
0001 1664737660
0002 1027117153
.....

steve45 can you answer please if you do not have a config.raspisnd in your soundset directory are the sounds supposed to work properly or do they need this file ?

2019-10-27 01:17:37.248 INFO RasPiSnd [searchSoundSets] [sound_util.c:660] searching for soundsets at: /boot/data/sound
2019-10-27 01:17:37.258 INFO RasPiSnd [searchSoundSets] [sound_util.c:694] found soundset 1, type: 0 at: /boot/data/sound/3
2019-10-27 01:17:37.267 DEBUG MiniDSer [miniDisplayHandler] [minidisplay.c:85] processing message
2019-10-27 01:17:37.268 INFO RasPiSnd [searchSoundSets] [sound_util.c:694] found soundset 2, type: 0 at: /boot/data/sound/1
2019-10-27 01:17:37.277 INFO RasPiSnd [searchSoundSets] [sound_util.c:694] found soundset 3, type: 0 at: /boot/data/sound/2
2019-10-27 01:17:37.285 INFO RasPiSnd [searchSoundSets] [sound_util.c:694] found soundset 4, type: 0 at: /boot/data/sound/4
2019-10-27 01:17:37.285 INFO RasPiSnd [searchSoundSets] [sound_util.c:707] maxSoundSets: 4
2019-10-27 01:17:37.285 INFO RasPiSnd [minidisplay_setText] [minidisplay.c:68] print 0,24: SOUNDSETS: 4
2019-10-27 01:17:37.285 INFO RasPiSnd [main] [despi.c:855] max soundsets: 4
2019-10-27 01:17:37.286 INFO RasPiSnd [loadHashMappingByName] [sound_util.c:767] loading hashes from /boot/data/sound/1/config.raspisnd
2019-10-27 01:17:37.287 INFO RasPiSnd [loadHashMappingByName] [sound_util.c:773] loaded 0 hashes
2019-10-27 01:17:37.287 DEBUG RasPiSnd [readConfig] [fileutil.c:272] reading config from: /boot/data/sound/1/config.ini
2019-10-27 01:17:37.288 WARN RasPiSnd [readConfig] [fileutil.c:315] config config.ini not found in /boot/data/sound/1
2019-10-27 01:17:37.288 DEBUG RasPiSnd [readConfig] [fileutil.c:272] reading config from: /boot/data/sound/1/config.raspisnd
2019-10-27 01:17:37.288 DEBUG RasPiSnd [readConfig] [fileutil.c:276] read config.raspisnd from /boot/data/sound/1/config.raspisnd
2019-10-27 01:17:37.293 DEBUG RasPiSnd [scan] [sound_util.c:465] gain for /boot/data/sound/1/jingle is 15
2019-10-27 01:17:37.350 DEBUG RasPiSnd [scan] [sound_util.c:465] gain for /boot/data/sound/1/music is 15
2019-10-27 01:17:37.536 DEBUG RasPiSnd [scan] [sound_util.c:465] gain for /boot/data/sound/1/sfx is 15
2019-10-27 01:17:37.617 DEBUG MiniDSer [miniDisplayHandler] [minidisplay.c:85] processing message
2019-10-27 01:17:38.409 DEBUG RasPiSnd [scan] [sound_util.c:465] gain for /boot/data/sound/1/voice is 15
2019-10-27 01:17:38.731 DEBUG RasPiSnd [scanAll] [sound_util.c:819] scan done id hash is: 2223564575
2019-10-27 01:17:38.731 DEBUG RasPiSnd [initSamples] [sound_util.c:915] sample 0000000001 0x00000001 0x017ee6d8, type: music, gain: 15, name: ball_in_shooter_lane, path: /boot/data/sound/1/music/0025093848-ball_in_shooter_lane/000001-ball_in_shooter_lane - LaGrange.ogg
2019-10-27 01:17:38.731 DEBUG RasPiSnd [initSamples] [sound_util.c:915] sample 0000000002 0x00000002 0x6df47883, type: music, gain: 15, name: attract_sound, path: /boot/data/sound/1/music/1844738179-attract_sound/000002-attract_sound - LaGrange.ogg
2019-10-27 01:17:38.731 DEBUG RasPiSnd [initSamples] [sound_util.c:915] sample 0000000003 0x00000003 0x27e26c31, type: music, gain: 15, name: lock_lit, path: /boot/data/sound/1/music/0669150257-lock_lit/000003-lock_lit - Gimme Lovin.ogg
2019-10-27 01:17:38.731 DEBUG RasPiSnd [initSamples] [sound_util.c:915] sample 0000000004 0x00000004 0x3b7d1450, type: music, gain: 15, name: lock_2_lit, path: /boot/data/sound/1/music/0998052944-lock_2_lit/000004-lock_2_lit - Gimme Lovin.ogg
2019-10-27 01:17:38.731 DEBUG RasPiSnd [initSamples] [sound_util.c:915] sample 0000000005 0x00000005 0x0f08fa3b, type: music, gain: 15, name: enter_your_name, path: /boot/data/sound/1/music/0252246587-enter_your_name/000005-enter_your_name - Sharped Dressed Man.ogg
2019-10-27

Just an update, I have checked the hardware all working, new higher speed sdcard, I know my 1 soundset is ok and not scrambled.

Here is a log from the start of a game (Getaway)

'electric_touch_5' Still playing whenever it feels like

DEBUG SndServi [playSample] [sdl_sound.c:1393] playing sample 186:0 vol: 15->64 'sfx' 'electric_touch_5' on channel 0

Music is supposed to be playing id'1' but it is nowhere to be seen in the log.

Trying to play sound ids that don`t exist

WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1470] sample for id '32' not found
WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1470] sample for id '248' not found
WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1470] sample for id '126' not found
WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1470] sample for id '46' not found

This seems to very different to steve45 Getaway video so I am at a brick wall to go any further, some support on these logs would be good.

If it’s trying to play IDs which do not exist, this implies to me maybe your sound set is scrambled - or at least needs to be reviewed. How do we confirm the IDs?

You should try joining the tilt!audio slack channel and posing your question there. Steve has a day job too!

The sounds are not scrambled as the ids are in a normal format 000001 000002 the log suggests the pinabll cpu also is not even asking the Pi for some sounds that are there and there is the annoying constant sound being played. id186 in the log is sound 000186 for example in the sfx folder. I have asked steve for help but yes he does have a day job so cannot commit to replys. The only reason I looked at this as he had it working on his Getaway so I cannot see the difference. I have a Funhouse but lost total faith so I am not going to try it. There is a definite change with the DMD being unplugged getting everything to work at about 80% but that is it. I wish everyone good luck with this but im moving on.

Watching with great enthusiasm

A strange situation, when I put a key file in the DATA folder, there is silence, nothing starts, if I delete the key file, the program starts, the initial sound is heard, etc.

Is it the correct keyfile for the hardware ? Any logfile info ?

Yes the key file is correct, it was version 1.25, I updated it to version 1.29 and no sound is heard at all, whether there is a key file or not.