For those that have installed the custom audio plus video, are you still experiencing bugs like the trex multiball one mentioned earlier in this thread? I really want this, but kinda want to wait until the bugs have been ironed out.

I have been using the latest audio/video code for several days. I haven't had any bugs or the T-Rex multi-ball glitch. I'd say I've played about 30 games or so.

I have been using the code for a few days and have had the T-Rex multi ball crash once out of 20+ games. I am using the SD card mentioned a few posts ago. The game does slow for me during start of t-Rex multiball most times. The other T-Rex encounters are fine. The video is great! Really is what the game should have been from the start. I have had just the one bug. I am using a new SD for just audio and video+audio so I can always go back.

Same experience for me. Happened once in about 15 games. Other encounters are fine.

If on Mac, what did you use to flash and verify if not Balena Etcher?

Hello everyone, Timlah sent me the update this weekend and I can only congratulate him. He did a great job. In my case, I didn't have any voice lag when starting the game when John was speaking. It's great work and it totally changes the game play. Thanks Timlah

I've been running the new code (Audio+Video) and must say it's perhaps the single most game changing mod I've seen on any pinball. It's fantastic. I've also just had the machine hang at the point in the T-Rex multiball where the kids are pressing against the glass roof of the car. As this is the only place where there is a bug it would seem a real shame to view this as a reason to abandon the video + audio version as they both work fantastically in all other respects. Has anyone any idea what is causing this isolated bug in the T-Rex multiball so a fix can be created?

For the T-Rex MB issues: I have not had any restarts or anything like that on my LE. However, while playing last night I noticed something I thought was different from a previous iteration delt31 sent me OR it's always been this way and I'm trippin': The "chomp chomp" the t-rex head lines up with the movie scene but then the "roar" comes a couple seconds after the actual t-rex head roars/opens his mouth (consistently). I'm wondering if that's related. i.e. perhaps the clip in there is too long tripping the game up sometimes as it tries to transition to another video. Just a suspicion and I pinged delt about that. Does anyone else notice the off-timing I described?

Just checking code mod status at this point... Tim's original V29 audio-only upgrade code is solid. No bugs detected by anyone on this thread. The combined V31 audio+video update has a few bugs, some minor and rarely seen, but none the less, still there.

Is this accurate?

Yes; I have noticed this every time. That said, I feel like this might have been an issue since before the video was added to the mix, but I can't recall now. Either way, yes! The T-Rex chomping occurs in sync (or within nanoseconds of synced, which is just fine!), but then the pinball Rex makes its roaring motion w/ no audio to back it up, and a few seconds afterward, the audio (+ video now) does the roar and the shaker motor goes.

Awesome work Tim! Loving all the new callouts! vids from delt is icing on the cake! what an incredible mod you guys have created. The only callout that does not seem to fit IMO is the "didnt...say the...magic word" for the countdown. I know that is a bummer because you have said previously that you really like it and was kinda hard to implement. Thanks again for the countless hours you have devoted to this!

Accurate AFAIK. I had never heard of a random re-start or a restart loop prior to the V31 audio+video version (or I'm forgetting but I feel like I'd remember that).

It does take some getting used to and I know not everyone is going to like it. But it's grown on me, maybe it will grow on you!? In the future (after we surpass these current issues) I'll make a separate version with the stock countdown instead if enough people want that.

** UPDATE ** I just had a system crash a few seconds after feeding T-REX. The machine just went black and restarted.... first issue since installing V31. It seemed like it happened right after the TREX "chomp" video sequence if that helps any. I'll setup my camera and see if I can get video of it happening for troubleshooting purposes.

1. Could you also share your sd card info and the program you used to burn the sd card?
2. If you have another sd card handy, could you burn it and give that one a shot?

The more I hear about the circumstances of these crashes, the more it feels like a PB problem. It feels like PB is not respecting the code/data boundries, and allowing data to be written on top of code. (I think this comes with the territory of working with binary files, rather than source code and re-compiles...)

Just happened a 2nd time for me in the same Trex spot. I might have to roll back to the audio only version unfortunately.

Another piece of info that may help for those getting reboots / restarts at T-Rex MB. Please note:

a) Do you have a PREM or an LE?
b) What method/app did you use to flash to SD (Mac or PC + Balena Etcher or Win32DiskImager)?
c) What is the model and size of your SD card?
d) Did you get any errors during the flashing process? If so, what were they?

My game is a Premium manufactured June 2020
I used Win32DiskImager on Win 10 PC
Its a PNY 16GB card (pic below]
No errors during flash process

I could give this another try and overwrite the stock Stern card and see if it makes a difference. Thanks!

41ZOOE4m9VL._AC_SY400_ (resized).jpg

Tim, in all honesty I seriously doubt it's the card or the flashing program at this point. We are all crashing at exactly the same spot. The evidence points to a problem with the code itself. delt31 needs to double check his video entries for that spot to ensure he respected the parameters of the original videos...

Or.. just to make sure it's the videos, do you have an audio version that is EXACTLY the same as the one with the added videos? Some of us could play that lots to see if we can trigger the crash.

I think you're right as far as there being general issues with this code version. However, there could be a PREM vs. LE handling of it that I'd like to find out as I have not had this issue on my LE. No, unfortunately I don't have any other video versions beyond what delt sent me. I am unable to import video due to a likely related but different PB problem on my PC. I only have my stable audio only versions which have never had this problem.

guys - I'm going to replace the trex MB screaming video (where it says TREXMB) with the original and see if that fixes it. I need to make a few more updates based on some other feedback (for better placement).

I have never seen this issue but in version 2, it will be adjusted. Hopefully that resolves it.

Thanks Delt! Can't wait to try out version 2.

I have an LE and have had it happen. The first time we got to TREX MB with the new code. It rebooted by itself and it hasn't happened since. There has to be some random thing that happens occasionally with a different callout or video being triggered.

Hey guys, thought I’d give another data point. Premium owner here and have not had the restart happen.

Win32diskimager Using Windows 10
Sandisk 32 Gig card class 10

It seems slow to skip the video when t-Rex multiball is achieved using a double flip, which I usually do to get on with playing, not sure if that is an actual clue or a red herring.

Anyway, love this project, wife does too except she plays worse because she drains while watching the videos, haha.

Brilliant. I think a version with a modification just at the T-Rex multiball is the way to go. Not sure what other feedback you are incorporating but I have one that may or may not be on your list. When the gear changing chase event happens and Jeff Goldbloom is sitting in the back of the car, his audio and the video seem totally out of sync, and because the audio and the video are the same clip, its very noticeable. Other than that, the video+audio project is sensational

thanks. I have the same sandisk except 16gb. Never had an issue.

Has anyone had this issue using the Sandisk XGB class 10? I still think this has to do with the SD card itself but I will inject the original file to play it safe.

Sandisk 16 here and no issues thus far!

I have a Premium JP. My SD Card is a Lexar Pro 633x. 32GB. I used Win32diskimager with Windows 10. Verified with no errors.

Only issue I’ve seen is some slight artifacts on the brown door of Jurassic Park that I don’t remember previously. I’ll try to get it in pics. White dots on the door.

33F367E2-96A5-4C11-9A6A-4C7206848E0C (resized).jpeg

D8A16F6B-8345-4FAD-ABF8-8D34D689F64C (resized).jpeg

I see this too. Also have experienced the crash same spot as everyone else.

Sandisk 16GB card. Flashed on Mac using VMware and WinDisk32 and also tried on Mac side using Balena. Same results.

That’s stock video - didn’t touch that.

Yeah, I believe that is normal.

I just ordered the SANDisk card you recommended with 1 day shipping so I can try it tomorrow to see if it solves the issue.-provided version 2 isn't released by then.

LE owner here, on SanDisk ultra 16gb card, used Windows with win32diskimager. No issues with the install, direct ok, no node board updates etc. Only settings are gone, played 2 games both trex multiball. No issues. Looks great. Such a huge improvement. Thanks for all the work! Will be testing more this weekend.

Tried v31 of audio+video on a prem and it goes into a boot loop. First time the display said LE, then on reboot it said PRE. Subsequent boots all say PRE.

Using a PHY 16gb class 10. Tried Bella on Mac first, then Bella on Windows with the same result. Both verified. I may try one more time using good old DD.

Edit: DD on a Mac worked.

Does anyone know for sure if the STERN CPU board reads the entire SDCARD into memory at boot-up, or does it R/W to the SDCARD throughout gameplay and normal operation? If the former, then the type of SDCARD card has MUCH LESS effect on this situation. If the latter, then the card performance will make a difference.

Based on the boot times I see, the system seems to be R/W directly to the card during normal operations, which means the card R/W specs matter.

I'm wondering if the SD cards simply need to be zero'd out before imaging. Seems like some kind of alignment issue.

The imaging tools essentially ZERO the card since they write the entire block on top of anything that is already there. What they do is drop the entire image down to the card, starting at the first byte. Think of the imaging tool as a bucket of paint that gets thrown on the floor. Doesn't matter what was on the floor previously, its all going to be covered with a coat of paint. (The software V29 or V31 is the 'paint')

I am pretty sure it is the IMAGE itself that is corrupted, and I suspect that either a bug in PB is causing this, or the person specifying where to put a piece of data (audio or video) is mistaken on the starting point or the size of the data block. If a data block is too big, it could easily overwrite code.

Guys - while I work towards v2, for now I've injected the original mb intro video back into the updated code for those who have had resets to check out.

Tim has the new link to the code so please reach out if interested.

Thanks

An idea just popped in my mind while reading these last few posts: there is a setting for "allow fast boot" in the menu. Is it possible that the changes between code are causing the system to be looking for components in slightly different locations? If this were the case, I'd imagine that you would need to change this menu item before upgrading, so that SPIKE does a full clean boot from the start with the new code.

I'm anxiously awaiting a fix for this reboot issue as I'm super excited to get this loaded up!

Thanks to Delts and thanks again to Timlah for your efforts in pushing this already killer game through the f'ing roof!

Played JP with the code for 2 hours. No issues. Plays perfect. Only sometimes movie and speech is not completely in sync but only minor things. The whole looks great. Now if i only could play better.

Correct. PM me if you are someone having T-Rex MB game restarts or other odd issues with the video edited version and I'll link you to this version. Alternatively, I do still have the latest audio edits only versions available.

delt31 I did want to point out that this version still requires use of Win32DiskImager if using Windows. I tried with Balena and got the initializing game restart loop. But perhaps for Mac users with Balena this one will be more successful. Flashing afterwards to that same SD with Win32 worked. I'm using the SanDisk Ultra 16GB Class 10 SDHC UHS-I Memory Card up to 80MB/s (SDSDUNC-016G-GN6IN) here: https://www.amazon.com/gp/product/B0143RTB1E

I did a full format (not quick) on my stock SDCard that came with the game and so far after 20+ games I haven't had any Feed Trex resets. I'll keep on playing but its an encouraging sign vs the other card I tried that had 2 resets in 20 games.

Thank you both for this enhancement- simply fantastic. Puts this title over the TOP!!

Followed instructions to the letter - no issues using new Sandisk SD 32gb

I’m curious what folks are finding as the sweet spot in music/speech settings so far to balance hearing the callouts.

Tim really need you and Delt to do the new Avengers IQ pin!!!!

That would be awesome. No hurry I don’t pic it up for a couple weeks.....kidding....I know how much time you’ve invested.

Great to hear (pun intended!)! It definitely depends on your setup. For me I have a PinSUB board outputting to 2 powered speakers and a subwoofer. The most important thing to do (which I imagine you have already) is to make sure both Volume/Speaker settings for Ohms are both set to 8 Ohms, not 4 Ohms. I have bumped (compressed) the heck out of the movie callouts and music .WAV files beforehand since the stock callouts in particular are recorded incredibly loud and I need to align with what the machine expects. But with that said, not all custom callouts or music are created equal per se. For custom callouts specifically, those where I had less background noise to filter are going to sound "louder". Remember we're battling b/t 1993 audio from boom mics and 2019 vocal booth recorded actors. For music we're talking live orchestra recordings that may not be mastered at the same level/quality as the music they pulled from the movie. There's of course the bass and treble aspect. For example the raptor MB ready music is hecka loud. That's b/c a) it has less bass and b) the game "decided" to play that music loud. On the other hand the T-Rex modes play the music quieter for some reason, but I also feel like the game "limits" volume on sounds/music that have bass heavy drums/basslines (which those do IIRC).

In any case, the game chooses the end all volume to play sounds at any given time. It also depends on what else is going on at the time of a callout/music. If there are music and FX going on when a callout is played, you're not gonna hear it as well (the game is "mixing" in real time). And note that if you change the attenuation for either music or speech you're going to be affecting stock and custom sounds.

I feel that in general the game favors loud callouts and quieter music. So for me, I've set the EQ to NONE, simply changed the MUSIC attenuation to -10 (negative means make it louder), and have left the SPEECH at 0. But again, I'm speaking to an outboard audio set up, not the pin speakers. I have those playing as well and I try to balance the volume of my external speakers and sub to match the output of the stock speakers. If you're saying you're not hearing the callouts loud enough, do the opposite or find a happy medium.

I wouldn't go too crazy in either attenuation direction. You could also play with the 10-band EQ but I EQ things via my powered speakers' EQ settings.

Have Stern ship me one and I'll get right on it.