(Topic ID: 179619)

Rebuilding sound for DataEast & WPC using a pi

By steve45

7 years ago


Topic Heartbeat

Topic Stats

  • 2,042 posts
  • 124 Pinsiders participating
  • Latest reply 32 days ago by Ashram56
  • Topic is favorited by 144 Pinsiders

You

Linked Games

Topic Gallery

View topic image gallery

20230816_111929 (resized).jpg
20230816_111238 (resized).jpg
20230816_111216 (resized).jpg
20230816_111301 (resized).jpg
IMG_6421 (resized).jpg
IMG_6420 (resized).jpg
2023-03-27_18-06-16 (resized).png
IMG_8790 (resized).JPG
rev-3.8-board (resized).jpg
C7BECF85-6A35-49A4-9C0C-611A6E059682 (resized).png
49C01E99-89EB-40E0-8790-5284A9D5CE12 (resized).jpeg
8B5C3740-485C-4518-B3F8-75DECB3FE0F2 (resized).jpeg
F484B39F-E731-4EA6-AF15-EDA85E40774D (resized).jpeg
6A8ECF6B-5C7C-4DB0-9B57-78787F299920 (resized).jpeg
224F7226-27C1-4E5B-8240-13940876411D (resized).jpeg
IMG_9634 (resized).JPG
There are 2,042 posts in this topic. You are on page 26 of 41.
#1251 3 years ago

Demo for UIDemo for UIIn case you never saw it before: https://demo.tiltaudio.com/ also updated to the latest firmware build 1.31 just now

#1252 3 years ago

1) Interested in buying the Tilt board for STTNG since I read about raspy sound few years ago. , is it just the WPC kit then? 3.0 now right.

2) nervous at soldering the smd chips, is there any way to buy a preassembled board kit ( minus raspberry pi) , Or anyone willing to sell me an assembled one on here?

Also planning on buying a pin2dmd excited how that product has grown also.

#1253 3 years ago
Quoted from JBBOPT:

nervous at soldering the smd chips, is there any way to buy a preassembled board kit ( minus raspberry pi) , Or anyone willing to sell me an assembled one on here?

I can do the smd soldering for you, but you still need to solder the rest. so some soldering skill are required.

I saw boards solder so bad that these only work by accident. so if you are not sure that you can make it better buy a ready to use product. or find someone who can help you.

schematic and pcb are public anyway. if someone in the US is willing to build and sell I'm fine with it.

br Steve

#1254 3 years ago

Wanna see a nice new feature ...


Will be integrated in the next firmware release

#1255 3 years ago
Quoted from steve45:

schematic and pcb are public anyway. if someone in the US is willing to build and sell I'm fine with it.
br Steve

Can you give a link to where these live? I spent some time on the website and couldn't find them.

EDIT: Found it here; https://easyeda.com/steve45/tiltaudio

#1256 3 years ago

Does the image for the device work on raspberry pi 4 or just 3? Thanks!

#1257 3 years ago
Quoted from RobF:

Can you give a link to where these live? I spent some time on the website and couldn't find them

here is the latest https://oshwlab.com/steve45/tiltaudio

#1258 3 years ago
Quoted from JBBOPT:

Does the image for the device work on raspberry pi 4 or just 3? Thanks

unfortunately the latest "official" image does not boot on the pi4, which is a bug. given the new features a new image is required anyway which will also again run on pi3 and 4

#1259 3 years ago

Cool I would guess a pi4 is overkill for this so I’ll just order a pi3 for it. I know it’s unrelated but is Germangamingsupplies still best place to buy a full Pin2dmd EVO setup?

#1260 3 years ago
Quoted from JBBOPT:

Cool I would guess a pi4 is overkill for this so I’ll just order a pi3 for it. I know it’s unrelated but is Germangamingsupplies still best place to buy a full Pin2dmd EVO setup?

We don´t give any recommendations about suppliers, because we don´t have personal experience with any of them. From our side the pin2dmd project is strictly DIY. There should be a pretty good chance that you get one from within the united states, if you ask around in one of the active pin2dmd threads or on vpuniverse.com

Now back to the topic

#1261 3 years ago

Thanks I’ll check there!

#1262 3 years ago
Quoted from JBBOPT:

Cool I would guess a pi4 is overkill for this so I’ll just order a pi3 for it. I know it’s unrelated but is Germangamingsupplies still best place to buy a full Pin2dmd EVO setup?

There is quite some threads around in the German forum about people complaining about that supplier.
Seems they hardly get their paid orders delivered.....

#1263 3 years ago
Quoted from JBBOPT:

Cool I would guess a pi4 is overkill for this so I’ll just order a pi3 for it. I know it’s unrelated but is Germangamingsupplies still best place to buy a full Pin2dmd EVO setup?

There is a user selling 3 of them in the UK forums £165.00 each.

https://www.pinballinfo.com/community/classifieds/pin2dmd.73/

#1264 3 years ago

I was wondering if anyone had images of a TiltAudio board in a DataEast machine? I'm curious how people have run their speakers and how people are running their power. I'm still getting mine setup and would love to see what others have done.

#1265 3 years ago

I've just installed my tilt!audio board in my DE Batman. Unfortunately I only get sound on boot up or if I play a sound from the webUI. Has anyone run into this in the past?

Here is what I've configured after prepping the board.

1. I imaged a class 10 32gb microSD card with latest firmware using Win32 Image Writer.

2. I placed my license key in the data folder.

3. I placed 2 different sound sets in the sound folder. One is the original and the other is a custom mix.

4. I set vendor=0 in the configuration file in the sound folder.

5. After installing the tilt!audio board in my machine i made sure all of the cables were reconnected. The ribbon cable has the red stripe to pin 1.

6. On starting my machine I get the start chime and boot notifications from the pi. After that the only way I can get any sound is to use the webUI. I have my audio device set to equal-dac.

I should note the original sound board is working perfectly.

Any help or suggestions would be greatly appreciated.

Edit: problem has been solved. The jumper pins weren't installed on the board. Big miss on my part. Seems to be working great! Just need to mess with some of the sounds a bit.

#1266 3 years ago
Quoted from gern:

Seems to be working great! Just need to mess with some of the sounds a bit.

Great to hear. I would appreciate if you share a video, batman de is missing my collection of "TILT!Audio works with ..."
Br Steve

#1267 3 years ago

There is a new firmware version out. Check it out https://tiltaudio.com/changelog. Feature highlights:
pasted_image (resized).pngpasted_image (resized).png

Please be sure to reflash the sd card with the new image, if you like to use the new bluetooth sound feature. The new image also has updated base image (TILT!Audio uses DietPi as base linux). Also for bluetooth I would recommend to use a Pi4 with BT 5.0, that works much more stable on the Pi and also offers bigger range.
Br Steve

#1268 3 years ago

Here is a video of Tilt!Audio in action on my DE Batman. There are some adjustments needed. At times I can hear older sounds playing and the difference in volume levels at times is a bit too much. The logs say I'm missing some sounds. I'll have to do some investigating there. But it's working!!!

#1269 3 years ago

I was wondering if anyone has made their own custom sound set for a Tilt!Audio board? If so, how did you go about it? Did you just use the webUI or some other way?

1 week later
#1270 3 years ago

Is it normal for the running program on the Pi to restart/crash when changing sound cards and/or trying to play a test sound ?
Board v 3.0, software 1.32, just assembled.
Display works, ssh works, web interface works, no error messages - but also no sound.
WPC, Pi3 b+ new out of the box.

#1271 3 years ago

Well ... got sound running, it was the sound card itself probably.

Testing on Getaway and Addams.
Same card (different Pis) triggers extra sound #186 where it shouldn't.
Same ID for both games.

Altsound sample set for both games.

This time, I have had the three 74LVC* SMD chips presoldered from JLPCB.
Card is version 3.0, software 1.32 (full install, stock, just downloaded and put on SD card).

What can be the problem here ?

Here's an extract from the log (sfx 'space_17', id 186 should not be playing here) :

2021-01-23 17:32:33.006 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-01-23 17:32:33.006 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:33.006 DEBUG SndServi [setMusicVolume] [sdl_sound.c:517] setMusicVolume to 32 (musicVol=32, ducking=100)
2021-01-23 17:32:35.442 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 186 0xba 10111010 len: 1
2021-01-23 17:32:35.442 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0xba 0x00 0x00 0x00, id: 186
2021-01-23 17:32:35.442 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:35.442 DEBUG SndServi [playSample] [sdl_sound.c:1585] playing sample 186:0 vol: 50->32 'sfx' 'space_17' on channel 0
2021-01-23 17:32:35.442 DEBUG SndServi [doCheckDucking] [sdl_sound.c:529] sample starts playing on channel -1
2021-01-23 17:32:35.442 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:35.442 DEBUG SndServi [setMusicVolume] [sdl_sound.c:517] setMusicVolume to 25 (musicVol=32, ducking=80)
2021-01-23 17:32:36.815 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-01-23 17:32:36.815 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:36.815 DEBUG SndServi [setMusicVolume] [sdl_sound.c:517] setMusicVolume to 32 (musicVol=32, ducking=100)
2021-01-23 17:32:36.952 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 177 0xb1 10110001 len: 1
2021-01-23 17:32:36.952 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0xb1 0x00 0x00 0x00, id: 177
2021-01-23 17:32:36.952 DEBUG SndServi [loadSample] [sdl_sound.c:1519] sample not in RAM, loading 1 samples
2021-01-23 17:32:36.952 DEBUG SndServi [loadSample] [sdl_sound.c:1521] sample not in RAM, loading from /boot/data/sound/taf_l7/0x00b1-paf_1.ogg
2021-01-23 17:32:36.968 DEBUG SndServi [loadSample] [sdl_sound.c:1528] Loaded sample 177:0: len: 70 kB, used: 02 MB
2021-01-23 17:32:36.969 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:36.969 DEBUG SndServi [playSample] [sdl_sound.c:1585] playing sample 177:0 vol: 50->32 'sfx' 'paf_1' on channel 0
2021-01-23 17:32:36.969 DEBUG SndServi [doCheckDucking] [sdl_sound.c:529] sample starts playing on channel -1
2021-01-23 17:32:36.969 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:36.969 DEBUG SndServi [setMusicVolume] [sdl_sound.c:517] setMusicVolume to 25 (musicVol=32, ducking=80)
2021-01-23 17:32:37.371 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-01-23 17:32:37.372 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 32
2021-01-23 17:32:37.372 DEBUG SndServi [setMusicVolume] [sdl_sound.c:517] setMusicVolume to 32 (musicVol=32, ducking=100)
2021-01-23 17:32:40.552 DEBUG MHD-sing [requestHandler] [httpservice.c:1774] url: /log, method: GET, version: HTTP/1.1, connCtx: 0x0000
2021-01-23 17:32:40.552 INFO MHD-sing [handleLogFileRequest] [httpservice.c:1574] request for logfile

#1272 3 years ago

So just to be clear, you get sound and music and call outs, but there is a specific sound which is played at some point where it should not?

#1273 3 years ago
Quoted from Ashram56:

So just to be clear, you get sound and music and call outs, but there is a specific sound which is played at some point where it should not?

Exactly. Sound #186 is triggered at random, frequent points when other sounds are playing.

#1274 3 years ago
Quoted from Zigzagzag:

2021-01-23 17:32:35.442 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 186 0xba 10111010 len: 1

This line is directly coming from the communication handler that receives sound commands from the game. And you really get this 186 sound command as the only "wrong" or "unexpected" sound command and everything else works. And it is the same in two different games? Sounds really weird ...

#1275 3 years ago

steve45 So I built card #2 out of 5 and got the same result.

Yes, sample #186 is wrong/unexpected.
The same sample plays in both games.

Sample #186 plays repeatedly on top of other sounds.
Other sounds seem correct, but #186 is so loud and comes so often the cards are unusable.

Card #1 is the same, I tried changing Pis and got the exact same result.

So I have now tried :

Card #1 game #1 Pi #1 : sample 186 pops up
Card #1 game #1 Pi #2 : sample 186 pops up
Card #1 game #2 Pi #1 : sample 186 pops up
Card #2 game #1 Pi #2 : sample 186 pops up

I can of course try more combinations, but this seems consistent across games, Pis and cards.

Any tips ?

#1276 3 years ago

steve45 Tried changing soundsets from altsound to another on Getaway, same result.

#1277 3 years ago

So here's a trace from Getaway with altsound during attract mode using trace level.
There should be no sound AFAIK, but sample #186 is played occasionally and the log tells about other missing samples.

Is this something with the SMD chips again ?
I see the old 2.6a board used LCX chips while the BOM for 3.0 calls for LVC chips.

2021-02-06 14:26:34.145 INFO RasPiSnd [updateSound] [sdl_sound.c:1855] 201828 - 141827 > 60000 -> fading background music id=0
2021-02-06 14:26:35.115 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 186 0xba 10111010 len: 1
2021-02-06 14:26:35.115 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0xba 0x00 0x00 0x00, id: 186
2021-02-06 14:26:35.116 DEBUG SndServi [loadSample] [sdl_sound.c:1519] sample not in RAM, loading 1 samples
2021-02-06 14:26:35.116 DEBUG SndServi [loadSample] [sdl_sound.c:1521] sample not in RAM, loading from /boot/data/sound/altsound_gw_l5/0x00ba-electric_touch_5.ogg
2021-02-06 14:26:35.116 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 032 0x20 00100000 len: 1
2021-02-06 14:26:35.116 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x20 0x00 0x00 0x00, id: 32
2021-02-06 14:26:35.143 DEBUG SndServi [loadSample] [sdl_sound.c:1528] Loaded sample 186:0: len: 208 kB, used: 472 kB
2021-02-06 14:26:35.143 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 52
2021-02-06 14:26:35.143 DEBUG SndServi [playSample] [sdl_sound.c:1585] playing sample 186:0 vol: 50->52 'sfx' 'electric_touch_5' on channel 0
2021-02-06 14:26:35.143 DEBUG SndServi [doCheckDucking] [sdl_sound.c:529] sample starts playing on channel -1
2021-02-06 14:26:35.143 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '32' not found
2021-02-06 14:26:36.160 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 097 0x61 01100001 len: 2
2021-02-06 14:26:36.161 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 033 0x21 00100001 len: 2
2021-02-06 14:26:36.161 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x61 0x21 0x00 0x00, id: 24865
2021-02-06 14:26:36.161 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6121
2021-02-06 14:26:36.368 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-02-06 14:26:37.208 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 098 0x62 01100010 len: 2
2021-02-06 14:26:37.209 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 034 0x22 00100010 len: 2
2021-02-06 14:26:37.209 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x62 0x22 0x00 0x00, id: 25122
2021-02-06 14:26:37.210 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6222
2021-02-06 14:26:38.256 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 099 0x63 01100011 len: 2
2021-02-06 14:26:38.258 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 035 0x23 00100011 len: 2
2021-02-06 14:26:38.258 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x63 0x23 0x00 0x00, id: 25379
2021-02-06 14:26:38.258 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6323
2021-02-06 14:26:39.305 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 100 0x64 01100100 len: 2
2021-02-06 14:26:39.306 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 036 0x24 00100100 len: 2
2021-02-06 14:26:39.306 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x64 0x24 0x00 0x00, id: 25636
2021-02-06 14:26:39.306 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6424
2021-02-06 14:26:40.387 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 186 0xba 10111010 len: 1
2021-02-06 14:26:40.387 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0xba 0x00 0x00 0x00, id: 186
2021-02-06 14:26:40.387 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 52
2021-02-06 14:26:40.387 DEBUG SndServi [playSample] [sdl_sound.c:1585] playing sample 186:0 vol: 50->52 'sfx' 'electric_touch_5' on channel 0
2021-02-06 14:26:40.387 DEBUG SndServi [doCheckDucking] [sdl_sound.c:529] sample starts playing on channel -1
2021-02-06 14:26:40.387 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 037 0x25 00100101 len: 1
2021-02-06 14:26:40.388 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x25 0x00 0x00 0x00, id: 37
2021-02-06 14:26:40.388 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '37' not found
2021-02-06 14:26:41.441 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 186 0xba 10111010 len: 1
2021-02-06 14:26:41.441 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0xba 0x00 0x00 0x00, id: 186
2021-02-06 14:26:41.441 DEBUG SndServi [getVolumeForSample] [sdl_sound.c:1035] getVolumeForSample: sample->gain: 50, gainByType: 50, res: 52
2021-02-06 14:26:41.441 DEBUG SndServi [playSample] [sdl_sound.c:1585] playing sample 186:0 vol: 50->52 'sfx' 'electric_touch_5' on channel 0
2021-02-06 14:26:41.441 DEBUG SndServi [doCheckDucking] [sdl_sound.c:529] sample starts playing on channel -1
2021-02-06 14:26:41.441 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-02-06 14:26:41.442 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 038 0x26 00100110 len: 1
2021-02-06 14:26:41.442 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x26 0x00 0x00 0x00, id: 38
2021-02-06 14:26:41.442 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '38' not found
2021-02-06 14:26:42.482 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 103 0x67 01100111 len: 2
2021-02-06 14:26:42.483 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 167 0xa7 10100111 len: 2
2021-02-06 14:26:42.483 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x67 0xa7 0x00 0x00, id: 26535
2021-02-06 14:26:42.483 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x67a7
2021-02-06 14:26:42.660 DEBUG SndServi [doCheckDucking] [sdl_sound.c:531] channel 0 has finished
2021-02-06 14:26:43.530 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 104 0x68 01101000 len: 2
2021-02-06 14:26:43.531 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 040 0x28 00101000 len: 2
2021-02-06 14:26:43.531 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x68 0x28 0x00 0x00, id: 26664
2021-02-06 14:26:43.531 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6828
2021-02-06 14:26:44.578 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 105 0x69 01101001 len: 2
2021-02-06 14:26:44.579 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 041 0x29 00101001 len: 2
2021-02-06 14:26:44.579 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x69 0x29 0x00 0x00, id: 26921
2021-02-06 14:26:44.579 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6929
2021-02-06 14:26:45.626 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 106 0x6a 01101010 len: 2
2021-02-06 14:26:45.627 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 042 0x2a 00101010 len: 2
2021-02-06 14:26:45.627 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6a 0x2a 0x00 0x00, id: 27178
2021-02-06 14:26:45.628 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6a2a
2021-02-06 14:26:46.674 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 107 0x6b 01101011 len: 2
2021-02-06 14:26:46.676 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 043 0x2b 00101011 len: 2
2021-02-06 14:26:46.676 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6b 0x2b 0x00 0x00, id: 27435
2021-02-06 14:26:46.676 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6b2b
2021-02-06 14:26:47.723 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 108 0x6c 01101100 len: 2
2021-02-06 14:26:47.724 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 044 0x2c 00101100 len: 2
2021-02-06 14:26:47.724 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6c 0x2c 0x00 0x00, id: 27692
2021-02-06 14:26:47.724 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6c2c
2021-02-06 14:26:48.771 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 109 0x6d 01101101 len: 2
2021-02-06 14:26:48.772 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 045 0x2d 00101101 len: 2
2021-02-06 14:26:48.772 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6d 0x2d 0x00 0x00, id: 27949
2021-02-06 14:26:48.772 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6d2d
2021-02-06 14:26:49.819 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 110 0x6e 01101110 len: 2
2021-02-06 14:26:49.820 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 046 0x2e 00101110 len: 2
2021-02-06 14:26:49.820 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6e 0x2e 0x00 0x00, id: 28206
2021-02-06 14:26:49.820 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6e2e
2021-02-06 14:26:50.867 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 111 0x6f 01101111 len: 2
2021-02-06 14:26:50.868 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00001 047 0x2f 00101111 len: 2
2021-02-06 14:26:50.868 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x6f 0x2f 0x00 0x00, id: 28463
2021-02-06 14:26:50.868 DEBUG SndServi [idsToIgnoreForWpc] [sdl_sound.c:1640] ignore wpc / dcs command 0x6f2f
2021-02-06 14:26:51.915 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 126 0x7e 01111110 len: 1
2021-02-06 14:26:51.915 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x7e 0x00 0x00 0x00, id: 126
2021-02-06 14:26:51.915 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '126' not found
2021-02-06 14:26:51.916 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 096 0x60 01100000 len: 1
2021-02-06 14:26:51.916 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x60 0x00 0x00 0x00, id: 96
2021-02-06 14:26:51.917 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '96' not found
2021-02-06 14:26:51.917 DEBUG isr wpc [wdenInterrupt] [pincom.c:346] wpc cmd 00000 032 0x20 00100000 len: 1
2021-02-06 14:26:51.917 DEBUG isr wpc [soundWpcHandler] [sdl_sound.c:1900] wpcSoundHandler cmd: 0x20 0x00 0x00 0x00, id: 32
2021-02-06 14:26:51.917 WARN SndServi [handleSoundByTypeWithIdx] [sdl_sound.c:1682] sample for id '32' not found

#1278 3 years ago

steve45 Well, I changed the 74LVC00 and 74LVC138 for 74LX00 and 74LX138.
Still the same error, maybe even worse - it seems the #186 sound is played more often than before, but I haven't compared the logs.

So status is now 3 x 3.0 boards with the same error and 2 x 2.6 boards non-working .... :/
Maybe I should take up knitting instead ?

#1279 3 years ago

try to test on version 1.30, I also have strange things happening on 1.32, and the previous one is OK.

#1280 3 years ago

fly Thanks for your suggestion ! I tried a full, clean 1.30 install but got the exact same results.

I have now tried a couple of cards in IJ as well.
Here I get missing sounds, wrong music and other bugs.
For example the grail music starts playing instead of the standard music.
Music keeps playing when ball goes into through.
Etc. etc.

This I have tried with 2 different cards.

Can this be a Pi-issue ?

#1281 3 years ago

If someone has a 3.0 board working with WPC - could you take a picture of the 3 SMD chips so I can see which types work ?

#1282 3 years ago

Any update on kits? Ordered a couple months ago, not in a huge rush though. Thanks.

#1283 3 years ago
Quoted from Zigzagzag:

If someone has a 3.0 board working with WPC - could you take a picture of the 3 SMD chips so I can see which types work ?

I just have an older version that i was going to put into a DE game. I plan on ordering a new 3.0 version to try in my Dr who.

I'm sure the root cause of the issue you've encountered will be resolved and that this project will continue. Great to see Steve getting time to focus on this project again!

#1284 3 years ago
Quoted from Zigzagzag:

I have now tried a couple of cards in IJ as well.
Here I get missing sounds, wrong music and other bugs.
For example the grail music starts playing instead of the standard music.
Music keeps playing when ball goes into through.
Etc. etc.

I have the same issue with a 3.0 board, latest firmware and 2 different PI's in my IJ. I posted about it earlier. Never found out why.

I was so happy when the new 3.0 boards was released, and Steve started posting in here again. I thought the progress sounded awesome. But the fact is that I have now bought 3 different board revisions, and none of them works without some form of glitches. One of them was actually assembled by Steve himself, but still had issues. I know there is a chance it is just me that isn't skilled enough to make it work, but i don't think so based on other peoples reports.

So i think i might as well just cut my losses, and stop trying. It just pains me, as i think this project is really awesome and promising. And compared to the french variant actually have a lot of nice extra features in the WebUI and so on.

#1285 3 years ago
Quoted from Phantasize:

I have the same issue with a 3.0 board, latest firmware and 2 different PI's in my IJ. I posted about it earlier. Never found out why.
I was so happy when the new 3.0 boards was released, and Steve started posting in here again. I thought the progress sounded awesome. But the fact is that I have now bought 3 different board revisions, and none of them works without some form of glitches. One of them was actually assembled by Steve himself, but still had issues. I know there is a chance it is just me that isn't skilled enough to make it work, but i don't think so based on other peoples reports.
So i think i might as well just cut my losses, and stop trying. It just pains me, as i think this project is really awesome and promising. And compared to the french variant actually have a lot of nice extra features in the WebUI and so on.

I would say don't give up. Even though the interface seems complex it isn't rocket science. There may be some kinks in the handshaking, etc to work out. Once these issues are identified we will all benefit. What data can we provide to Steve to help get this sorted out?

I'd really like to see this project succeed.

#1286 3 years ago

I have a 3.0 board I assembled myself, full kit acquired through Steve.

Installed in a CFTBL. I originally had a specific callout being played randomly, and music stopping, as if it was missing a command. But for some reason over the last few weeks it has been working flawlessly (can't remember the version though I'll check tomorrow).

The core of false detection is likely a bus detection issue, which could be cause by multiple reasons, such as signal integrity, code missing detection (RPI is not a real time system).

I'm using a RPI3 Model A+

So I don't know what made it work, but I'm glad it does

It's just kind of shame that Steve is not very active in supporting the project, although to his defense he's probably not making a lot of money to justify the engineering investment (unlike Pinsound who charges a fortune). Also Steve has been actively developping a new version of PIN2DMD Editor which brings 64 colors capability, and the capability to develop colorization for Stern SAM, so I assume he did not have much time to spend on TiltAudio. Maybe if his code was open source other contributors would start looking into it and debug it more actively. But I know of a few not happy individuals on the Facebook french group that tried the solution and could not make it work.

A few suggestions:
- Besides the SMD components, check that all resistors are soldered correctly, reflow all of the connections, including headers
- if you have a RPI4, just install it (hopefully Steve can transfer the licence without charging), it's higher speed might be beneficial for more reliable command detection (completely shooting in the dark here to be honest).

@steve45, if you're reading this thread, it would be good if you could comment and assist with some guidance based on the logs.

#1287 3 years ago

1. I read this thread.
2. I invested a lot of time (together with lucky) to get the new 3.0 board more stable by added bus termination, pullups and of course carefully select smd chips series.
3. the pi should be fast enough in any case, the fastest sequence you typically see is 3-byte commands (or 4 byte commands) that the game sends in at 1 byte per milli second which is volume commands. If that works reliably it is not about speed on the game to pi interface.
4. I always offer to do a full remote analysis by looking at a complete set of config / logfiles together with an error description. Not sure if I received that from the users that have problems at the moment.
5. At the moment there will no open source release of the firmware, but contributors are welcome, if they are really able to help (in the past unfortunately my experience - also with pin2dmd / goDMD - was, that all kind of people requested access to source code for different reasons and none of them were ever of much help or did contribute, some were not even able to compile it). So just convince me that you can and will help and you will get access.

And more specifically to that kind of problem: I never experienced such a special code 186 did occur unexpected and anything else running. If there is much noise on the data bus, okay could cause trouble, but not just one unexpected code?!?

If you doubt it could be a firmware version specific problem (which I don't assume) just try another. You can still also download older version in the changelog page.

Quoted from Ashram56:

It's just kind of shame that Steve is not very active in supporting the project

Not sure what motivates you to that kind of statement, but beside the fact that a have a day to day job, house, wife and kids I invest a lot of time in this hobby.

I'm also not making any money with this project. The kits are sold more or less for the purchasing price, and every minute I spent on that project I could invest better otherwise if my goal would be make more money. Not to mention that I spent hundreds of dollars on lawyers to fight The French that were thinking I'm doing something illegal ... So please don't tell me about money.

/Steve

#1288 3 years ago

Maybe to add: I myself have it in MSF, FH, HS2, DrWho & JP. Lucky runs it in LOTR and we (Lucky and me) tested in a couple of games: STTNG, NBA Fastbreak, IJ, LW3 and a few more. There's demo video's online from various tests and also gamers that did install the board (also older rev) in their games: https://tiltaudio.com/2020/12/20/demo-videos/

#1289 3 years ago
Quoted from ViperJelly:

Any update on kits? Ordered a couple months ago, not in a huge rush though. Thanks.

Couple of months sounds really long? I'm not aware of such an old open order, but anyway the truth is that china parts are delivered very slowly these days, and I have 9 kits lying around just waiting for one or two essential parts.

If you want more specific info about your order, please include an order number in the request that will make my life easier. Thank you.

/Steve

#1290 3 years ago

@steve45, I believe you have slightly misread my comment.

I did state specifically that you were not making a lot of money on this project, if at all. And I stated a few reasons as to why you might have been slow in responding, time being the main issue.

So if you understood that I was stating that you should support because you were making money, this was not my intention, apologies for that. We all fully understand this is an diy project, and you have other obligations.

I even advertised tiltaudio on some French Facebook groups, starting it was clearly for the experienced individuals, but worth it if you had the skills.

However, the fact remains that some people fail to make it work (that's not my case, it does work), and raised questions that are currently pending. I don't know the ratio of success VS failure though, so this might be that success ratio is higher than what we see on pinside.

Let's hope these questions get answered with a root cause identified so that everyone benefits from the knowledge

Regards

#1291 3 years ago

Let's not start a flame war, we are all interested in finding a solution.
steve45 has been so kind as to get in touch with me in private, and we are going to try different solutions.

#1292 3 years ago
Quoted from Ashram56:

I don't know the ratio of success VS failure though, so this might be that success ratio is higher than what we see on pinside.

The problem is that if it works you will not read anything about it. Only issues or complaints are posted publicly.

#1293 3 years ago

lucky1 that's good to know about the Pi, it gives me another possible solution to test
I'll buy one today and try it out.

#1294 3 years ago
Quoted from lucky1:

The problem is that if it works you will not read anything about it. Only issues or complaints are posted publicly.

Very true. Although to my defense I did post publicly that is was working just fine for me (although I did have some unexplained behaviour at the beginning, which disappeared after I replaced my 12v regulator and I reflowed several solder points).

Anyway, as stated, apologize for the poor choice of words on my part.

Regards

#1295 3 years ago

a short video of how it works With BTTF, some fun with sound configuration and it will be OK, software version 1.30, because I have problems with 1.32, I don't know why

#1296 3 years ago

lucky1 I tried a brand new Pi out of the box, the problem remains.
I have tried different things (separate PSU, disconnect screen, 3 different cards in 3 different machines) and sent steve45 the logfiles.

#1297 3 years ago
Quoted from ViperJelly:

Any update on kits? Ordered a couple months ago, not in a huge rush though. Thanks.

Same here - I got excited for the software and hardware update and ordered one too. I followed up with Steve via email, but haven't heard anything yet.

#1298 3 years ago

Looks like there is a misunderstanding regarding board revisions that are on sale (or not on sale). Of course the latest board 3.x is on sale, even though the shop was saying "Rev. 2.8" I've updated the shop to 3.x

I always only sell the latest board revision (except some special sale actions, that are announced specially).

So shop system is updated and misunderstandings removed (hopefully).

Br Steve

#1299 3 years ago

I ordered the 2.8 board and a week later the new board came out. Steve sent the latest board

Took it to my local phone repair shop to solder the IC chips for us. Then soldered the rest of the components. Have it installed in my wwf royal rumble and works perfectly. Thanks Steve!

#1300 3 years ago
Quoted from Wharhed:

Same here - I got excited for the software and hardware update and ordered one too. I followed up with Steve via email, but haven't heard anything yet.

Mine is in the states somewhere. Shipped 2 months ago. Gotta love usps.

Promoted items from Pinside Marketplace and Pinside Shops!
$ 35.00
Cabinet - Other
Rocket City Pinball
 
7,800
Machine - For Sale
Anaheim, CA
$ 35.00
Cabinet - Other
Rocket City Pinball
 
$ 130.00
Gameroom - Decorations
Dijohn
 
$ 99.00
Playfield - Toys/Add-ons
Loop Combo Pinball
 
$ 39.99
Rubber/Silicone
NO GOUGE PINBALL™
 
$ 85.00
Cabinet - Other
Pinball Haus
 
$ 36.00
Playfield - Other
Rocket City Pinball
 
$ 35.00
Playfield - Toys/Add-ons
G-Money Mods
 
$ 9.95
7,000
Machine - For Sale
London, ON
$ 69.99
Playfield - Toys/Add-ons
Lighted Pinball Mods
 
$ 399.00
Cabinet - Decals
Mircoplayfields
 
$ 69.99
Playfield - Toys/Add-ons
Lighted Pinball Mods
 
$ 20.00
Cabinet - Decals
Pinball Haus
 
$ 6,999.00
Pinball Machine
Classic Game Rooms
 
$ 17.99
Eproms
Matt's Basement Arcade
 
$ 14.95
Playfield - Toys/Add-ons
ULEKstore
 
$ 79.99
Cabinet - Armor And Blades
PinGraffix Pinside Shop
 
$ 49.99
Cabinet - Toppers
Lighted Pinball Mods
 
$ 329.99
Lighting - Other
Lighted Pinball Mods
 
$ 30.00
Playfield - Other
YouBentMyWookie
 
$ 30.00
Playfield - Toys/Add-ons
G-Money Mods
 
4,999
Machine - For Sale
West Chicago, IL
Wanted
Machine - Wanted
West Chicago, IL
$ 45.00
Playfield - Toys/Add-ons
G-Money Mods
 
There are 2,042 posts in this topic. You are on page 26 of 41.

Reply

Wanna join the discussion? Please sign in to reply to this topic.

Hey there! Welcome to Pinside!

Donate to Pinside

Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!


This page was printed from https://pinside.com/pinball/forum/topic/rebuilding-sound-for-de-jurassic-park-using-a-pi/page/26?hl=phantasize and we tried optimising it for printing. Some page elements may have been deliberately hidden.

Scan the QR code on the left to jump to the URL this document was printed from.