Differences

This shows you the differences between two versions of the page.

--- recording_table_media [2024/01/23 11:40] – pinupadmin
+++ recording_table_media [2025/01/16 14:11] (current) – pinupadmin
@@ Line 1: / Line 1: @@
 ====== Video Recording ======
-Because vpx 10.8 uses more low-level gpu drivers it cannot record via the older default methods past (v1.4.6 popper). To support vpx 10.8 +and other emulators like FP we now need to use FFMPEG with GPU(lower level) recording methods.
+Because vpx 10.8 uses more low-level gpu drivers it cannot record via the past older default methods (v1.4.6 Popper). To support vpx 10.8 +and other emulators like FP we now need to use FFMPEG with GPU(lower level) recording methods.
 Technical Note: Popper's uses 3rd party tools for all of its recording features, which means all Popper does when you ask it to record is run 'recordstart.bat' and 'recordstop.bat' in the recordings subfolder. Paramaters are passed to the bat files for them to process the recordings.
 ==== New for Popper v1.5 watch this video to get familiar with how best to do your recordings today: ====
+//note in this video you can skip the part where he modifes the operatoredit menu for extra bat files as that is optional.//
 [[https://www.youtube.com/watch?v=yN0xNbid-GY|https://www.youtube.com/watch?v=yN0xNbid-GY]]
@@ Line 12: / Line 14: @@
 Awesome utility that can scan/find missing media and batch all recordings for you while you sit back on the couch… Fully automated with launch each game, recode each/any display as needed and close game and more onto next game.
+//Watch youtube video in above section to see an example of how to record all missing media!//
 You should ONLY run this after you have tested and recorded each display manually in Popper to make sure your recording is setup correctly.
@@ Line 48: / Line 52: @@
 FFMPEG recording of playfield uses GPU recording which can only happen on the PRIMARY display in windows. You must have your playfield set as PRIMARY.
+**"I can record my playfield in 10.8 DX version but cannot record my playfiled with 10.8 GL"**
+Some windows and/or nvidia update may make recording OpenGL vpx impossible. You can setup your VPX emulator launch script to alternate launch 10.8 DX when Popper is in recording mode (prior to launching table).
+{{:dec8cb24924f25045e4f36498ccdc094.png}}
+above is the default VPX launch script, you can just copy this one line that sets VPXEXE when recmode=1 into your script right before START line.
+<code>
+if "[RECMODE]"=="1" (SET VPXEXE=VPinballX64.exe)
+</code>
 **"My playfield 4K videos won't play in Popper, it only shows a few frames and freezes videos"**
@@ Line 55: / Line 72: @@
 **"my playfield is 'flipper' or mirrored'… worked fine in v1.4.6"**
-If you have your TV/monitor physically reversed in your cabinet and used your windows OS to flip your screen, then GPU recording will bypass that do your GPU recording before the OS 'flips' the display. You will need to modify your recordstop.bat file to have ffmpeg rotate your vidoes to your OS flipping method. See google /ffmpeg command line parameters to rotate based on your windows settings.
+If you have your TV/monitor physically reversed in your cabinet and use windows OS to flip your screen. This will cause GPU recording to bypass that, and GPU recording will happen before the OS 'flips' the display. You will need to modify your recordstop.bat file to have ffmpeg rotate your vidoes to your OS flipping method. See google /ffmpeg command line parameters to rotate based on your windows OS settings.
 **"something is not working".**
 after a manual recording, look at the many LOG files in the recordings sub-folder to see if they report any errors. Sometimes having older nvidia drivers can make GPU recording fail. If you have NVIDIA you can try setting recordstart.bat to NOT use nvidia in the top settings of file.
+**"i see a bunch of repeating balls appear when i start recording"**
+If you use the operator menu to record playfield you may see some repeating ball appear. This is because in vpx 10.8 they added a new feature called "debug balls" and made the default 'O' key. So simple to fix, go to vpx keys and change the debug balls key to something else not being used.
 **"it use to work fine in v1.4.6 but nothing works in v.1.5"**