videosnap non stop

[yoxxxoy]

When I start a game the VideoSnap played in AM does not stop, and sound in the background. Is it normal?

This is my set: Xubuntu 14.04 - Attract Mode 1.6 compiled to x86

[yoxxxoy]

I have solved this problem changing *Configure/General/WindowsMode to "Fill Screen (Default)" and *Configure/Emulators/mame/MinimumRunTime to 1   

 Sorry my bad english. 

[attrekt]

For some reason, this has just become a problem for me as well - had been playing with GLSL, then mame.ini, then my attract-mode config, but didn't change anything I don't normally change (I think). Now the snaps audio keeps playing in the background after the game has launched.

Tried switching between Fullscreen and Fill Screen, and tried setting Minimum Run Time to 1 like the OP, but no effect.

Edit: have reverted my mame.ini completely to a backup, no change (which makes sense). but at least it rules out GLSL and my mame.ini as the problem.

[attrekt]

More investigation suggests that starting a game is successfully killing the video snap threads, but then starting new ones at the same time as running the game.

Have attached some (novice) gdb output with my own markup showing what I did between activities.

Code: [Select]

attrekt@Cabinet:~$ gdb attract
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
[...]
(gdb) run
Starting program: /usr/local/bin/attract
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Starting Attract-Mode 1.6.0 (Linux)
Config: /home/attrekt/.attract/attract.cfg

*** Initializing display: 'mame'
 - Loaded master romlist 'mame' in 0 ms (66 entries kept, 0 discarded)
 - Constructed 2 filters in 0 ms (132 comparisons)
[New Thread 0x7fffe4017700 (LWP 11443)]
[Thread 0x7fffe4017700 (LWP 11443) exited]
[New Thread 0x7fffe4017700 (LWP 11444)]
[New Thread 0x7fffe3816700 (LWP 11445)]
[New Thread 0x7fffe1d15700 (LWP 11446)]
[Thread 0x7fffe1d15700 (LWP 11446) exited]
[New Thread 0x7fffe1d15700 (LWP 11447)]
[Thread 0x7fffe1d15700 (LWP 11447) exited]
 - Loaded layout: /home/attrekt/.attract/layouts/robospin/ (layout.nut)
[New Thread 0x7fffe1d15700 (LWP 11448)]
[New Thread 0x7fffe0d14700 (LWP 11449)]
// Selecting a new game in navigation
// You can see two threads start, and two threads unload, every time I do this
// I'm assuming these threads are for playing the snap video
[New Thread 0x7fffd7ffe700 (LWP 11450)]
[New Thread 0x7fffd77fd700 (LWP 11451)]
[Thread 0x7fffe0d14700 (LWP 11449) exited]
[Thread 0x7fffe1d15700 (LWP 11448) exited]
// Selecting a new game in navigation
[New Thread 0x7fffe1d15700 (LWP 11453)]
[New Thread 0x7fffe0d14700 (LWP 11454)]
[Thread 0x7fffd77fd700 (LWP 11451) exited]
[Thread 0x7fffd7ffe700 (LWP 11450) exited]
// Launching game
// Video threads unload
[Thread 0x7fffe0d14700 (LWP 11454) exited]
[Thread 0x7fffe1d15700 (LWP 11453) exited]
*** Running: /home/attrekt/src/mame/mame/mame64 polepos2
// Wat. Why are these threads starting? These aren't MAME, they're attract.
// Y u do dis.
[New Thread 0x7fffe1d15700 (LWP 11459)]
[New Thread 0x7fffe0d14700 (LWP 11460)]
// Quitting game
// Notice the threads above don't unload, because the video has been
// playing the whole time, and just keeps goin
Average speed: 98.92% (16 seconds)
>>> Snap video reaches end and loops <
[Thread 0x7fffe1d15700 (LWP 11459) exited]
[Thread 0x7fffe0d14700 (LWP 11460) exited]
[New Thread 0x7fffe1d15700 (LWP 11466)]
[New Thread 0x7fffe0d14700 (LWP 11467)]
// Selecting a new game in navigation
[New Thread 0x7fffd7ffe700 (LWP 11468)]
[New Thread 0x7fffd77fd700 (LWP 11469)]
[Thread 0x7fffe0d14700 (LWP 11467) exited]
[Thread 0x7fffe1d15700 (LWP 11466) exited]
// Quitting attract-mode
[Thread 0x7fffd77fd700 (LWP 11469) exited]
[Thread 0x7fffd7ffe700 (LWP 11468) exited]
[Thread 0x7fffe3816700 (LWP 11445) exited]
[Thread 0x7fffe4017700 (LWP 11444) exited]
[Inferior 1 (process 11439) exited normally]

[attrekt]

So I just set up a brand new cabinet today, new OS (but Ubuntu 15.10, just like current build) and new hardware. I copied my .mame and my .attract folders from my current build, but I built new binaries.

With that setup, I'm not seeing this bug. I've already built a new attract binary on my current setup and that made no difference. I'll try a new mame binary, but otherwise it's something in my OS that's causing the problem, I guess - I just have no idea what.

[ziviani]

Hi friend,
I have the same problem with my AM in Raspberry Pi
Have you ever found a solution to this problem?
I would not like to reinstall my arcade

So I just set up a brand new cabinet today, new OS (but Ubuntu 15.10, just like current build) and new hardware. I copied my .mame and my .attract folders from my current build, but I built new binaries.

With that setup, I'm not seeing this bug. I've already built a new attract binary on my current setup and that made no difference. I'll try a new mame binary, but otherwise it's something in my OS that's causing the problem, I guess - I just have no idea what.

[yoxxxoy]

in AM 2.10 this bug has been fixed. 

Full screen work great.