1622 replies to this topic

[jthompson]

 

 

Strange... I'm not sure where the window could be disappearing to.  You don't see a resized version of the window lurking in a corner somewhere?  Maybe a 1/4 size version or something odd like that?  It would be entirely black content while a game is running - all videos/graphics are shut down to minimize performance impact.  If you can't find it anywhere, what happens if you right-click on the playfield window during this condition and select "Show Backglass"?

 

I'll test it again when I get a chance and let you know.

 

Not to bombard you with stuff but I did find another issue. I was able to get Future Pinball tables to load after searching this post to see what was working for others. I use BAM so I had to change some stuff up to get it to work. My tables launch and close properly now. The problem I'm having is I'm trying to launch futureDMD using the launch before field in the setup window. When I launch the table, futureDMD launches but the table loading seems to hang. Not sure if it's a timing issue or a focus issue, but I figured you'd like to know.

[mjr]

 The problem I'm having is I'm trying to launch futureDMD using the launch before field in the setup window. When I launch the table, futureDMD launches but the table loading seems to hang. Not sure if it's a timing issue or a focus issue, but I figured you'd like to know.

 

At what point in the process does it get stuck?  

 

You're using [NOWAIT TERMINATE] with the Run Before command, right?  I don't know what a futureDMD is, but I'm assuming it's another one of these DMD helper programs you need to launch and leave running in the background while the game runs.  Is that a fair guess?  If so, and you're *not* using [NOWAIT TERMINATE], that would explain the apparent hang - it's not actually hanging, it's just that PinballY is happily waiting for futureDMD to exit before proceeding to the game launch, because that's just what Run Before normally does.  [NOWAIT TERMINATE] says "run the program, don't wait for it (leave it running in the background), kill it when the game ends".

(See the help for more on how to use the flags like [NOWAIT] and [NOWAIT TERMINATE].  Quick summary: just stick them at the very start of the Run Before box:  [NOWAIT TERMINATE] c:\path_to\futureDMD.exe args...)

[jthompson]

 

 

You're using [NOWAIT TERMINATE] with the Run Before command, right?  I don't know what a futureDMD is, but I'm assuming it's another one of these DMD helper programs you need to launch and leave running in the background while the game runs.  Is that a fair guess?  If so, and you're *not* using [NOWAIT TERMINATE], that would explain the apparent hang - it's not actually hanging, it's just that PinballY is happily waiting for futureDMD to exit before proceeding to the game launch, because that's just what Run Before normally does.  [NOWAIT TERMINATE] says "run the program, don't wait for it (leave it running in the background), kill it when the game ends".

(See the help for more on how to use the flags like [NOWAIT] and [NOWAIT TERMINATE].  Quick summary: just stick them at the very start of the Run Before box:  [NOWAIT TERMINATE] c:\path_to\futureDMD.exe args...)

 

Ahh! I didn't know this. I'll try it tonight when I get home. I guess I need to become acquainted with the help as well. I assume this is built into PBY or a separate txt file that came with the install. I'll find it. I was doing the plug-n-pray method, LOL.

 

Future DMD is a virtual DMD for Future Pinball. It creates and lets you move a virtual DMD and put it anywhere you like such as a third monitor. It is designed to run all the time, but it covers other stuff that I don't want it to so I only run it when I start FP. I also have an autohotkey file to kill it when I close the table. I'll put the path to that file in the run after dialog.

[mjr]

 I guess I need to become acquainted with the help as well. I assume this is built into PBY or a separate txt file that came with the install. 

 

It's pretty easy to find - right click on any window -> Help, or hit Escape to call up the Exit menu and select Help, or click the "?" icon at the top of the settings dialog.

 

 

I also have an autohotkey file to kill it [futureDMD] when I close the table. I'll put the path to that file in the run after dialog.

 

In that case you can just use [NOWAIT] to leave the process running until you explicitly kill it.  But I'd actually ditch your autohotkey script instead and use [NOWAIT TERMINATE] - it would be a bit more reliable in that it doesn't require launching anything separate, and it would be a bit faster in that it doesn't require launching anything separate.

[hlr53]

 

Spent an hour yesterday checking folder and file permissions and nothing jumps out at me. 

 
That fits what I'm seeing; I spent a while going over the relevant code, and I can't see anything where Admin mode should make a difference either.  I'm now thinking that what you're seeing is a run-of-the-mill crash and that running in Admin mode is just accidentally masking it.  Admin mode can do that with certain types of crashes.
 
 

Do you want me to compile A21 with debugging enabled and run it?

 
That would be perfect - that would definitely the easiest way to get to the bottom of it.  I can add instrumentation instead but that will probably take many iterations, whereas if you can run it under the debugger, it will instantly pinpoint the crash location.
 
 

The irony here is it doesn't work on the PBY Adm version but does on the regular PBY running as admin.

 
Right, that's because they're completely different things, despite the name.  "PinballY Admin Mode" doesn't mean "PinballY running in Admin Mode".  It means "PinballY running in normal user mode, with the ability to launch Admin Mode child processes when needed".  
 

 
Question: I cloned the latest A21 repository and built a 64 debug in VS. Is the PinballY.sln supposed to create the associated PBY directories also? It just created a bunch of LIB, PDB, EXP and ILK files along with the executable's in a single directory. Sure I am missing something on the settings. I copied those and the entire repository over to the pincab to get it to run. 
 
Anyway, the PinballY debug build and the PinballY Admin Mode debug both work! I also want to build a Release version (tomorrow unfortunately) but I want all the directories to go with it.
 
Thanks!

Edited by hlr53, 26 September 2018 - 09:26 AM.

[mjr]

Question: I cloned the latest A21 repository and built a 64 debug in VS. Is the PinballY.sln supposed to create the associated PBY directories also? It just created a bunch of LIB, PDB, EXP and ILK files along with the executable's in a single directory. Sure I am missing something on the settings. I copied those and the entire repository over to the pincab to get it to run. 

 

Anyway, the PinballY debug build and the PinballY Admin Mode debug both work! I also want to build a non Release version (tomorrow unfortunately) but I want all the directories to go with it.

 

Great - glad you got it building.  That should be a big step towards figuring out the crash.

 

There's no extra "create the directories" step in the VS build, if that's what you're asking.  The full build process is simply Build -> Build Project.  That will leave things in a state that's ready to run, by pressing F5 in Visual Studio.  The build environment is a bit different from the deployment environment, but that will be transparent if you just leave everything exactly where it is; the build leaves things in a state that's ready to run.  You'll want to do your building on the same machine where you're going to run the test because of this.

To run under the debugger, just go into Visual Studio and press F5 or Debug -> Start Debugging.

[jthompson]

 

In that case you can just use [NOWAIT] to leave the process running until you explicitly kill it.  But I'd actually ditch your autohotkey script instead and use [NOWAIT TERMINATE] - it would be a bit more reliable in that it doesn't require launching anything separate, and it would be a bit faster in that it doesn't require launching anything separate.

 

 

Wow, that worked great. I'll read the directions from now on when I run into an issue before reporting it as a bug. 

 

About the backglass not retaining it's fullscreen properties... I can't explain why, but it worked the way it is supposed to last night. Open vpx table, play, close table. PBY returned with fullscreen backglass. Open future pinball table, play, close. PBY returned with fullscreen backglass. I looked at the settings.txt to see if I somehow was using my edited version where I manually entered the backglass coordinates. I wasn't. The coordinates in there were smaller and located in a different area than the fullscreen size I had previously entered, so I guess PBY was ignoring those this time and was going with whatever fullscreen flag the program uses. Sorry I couldn't get it to repeat to help you troubleshoot it more. I will keep testing and if the issue comes up again, I'll try doing the alt-tab thing to see if I can see the PBY backglass.

 

I have a full set of FX3 tables and that will be the next thing I attempt to set up. Maybe this coming weekend.

[mjr]

About the backglass not retaining it's fullscreen properties... I can't explain why, but it worked the way it is supposed to last night. Open vpx table, play, close table. PBY returned with fullscreen backglass. Open future pinball table, play, close. PBY returned with fullscreen backglass. I looked at the settings.txt to see if I somehow was using my edited version where I manually entered the backglass coordinates. I wasn't. The coordinates in there were smaller and located in a different area than the fullscreen size I had previously entered, so I guess PBY was ignoring those this time and was going with whatever fullscreen flag the program uses. Sorry I couldn't get it to repeat to help you troubleshoot it more. I will keep testing and if the issue comes up again, I'll try doing the alt-tab thing to see if I can see the PBY backglass.

 

Okay... let me know if it comes back.  You're right that there's a separate full screen flag in the settings, in this case BackglassWindow.FullScreen. The stored size value only reflects size of the window just before it was made full screen, since the program always figures the full screen location based on the actual monitor layout at run time; it's not a good idea to store that in a file because monitor layouts can change, hence it's safer to determine it anew on each run.

[hlr53]

[snip] never mind

Edited by hlr53, 28 September 2018 - 06:08 PM.

[mjr]

Alpha 22 released.  No major changes, just some bug fixes and other minor tweaks.  If you've been having problems with the backglass window switching out of full-screen mode when playing a game and switching back to PinballY, hopefully this will fix it.

[hlr53]

I reinstalled Windows and PBY sets up VPX tables OK and doesn't crash.

 

On A21 & just now A22, media capture only displays Playfield Image, Playfield Video and Table Audio options. Back glass option in not showing up? When I start a capture it creates the image and then nothing else happens? Seems to be frozen? I have set for 2 monitors.

Edited by hlr53, 28 September 2018 - 07:32 PM.

[mjr]

On A21 & just now A22, media capture only displays Playfield Image, Playfield Video and Table Audio options. 

 

Do you have a backglass window open?  It offers capture for the open windows.

 When I start a capture it creates the image and then nothing else happens? Seems to be frozen? I have set for 2 monitors.

 

Don't know... I just ran through a quick playfield image + video capture and it's working fine for me.  What's on the screen when it freezes?  What's in the log?

Does pressing Escape (or your "Exit Game" key if you remapped it) do anything when it's stuck?

[hlr53]

 

On A21 & just now A22, media capture only displays Playfield Image, Playfield Video and Table Audio options. 

 

Do you have a backglass window open?  It offers capture for the open windows.

 When I start a capture it creates the image and then nothing else happens? Seems to be frozen? I have set for 2 monitors.

 

Don't know... I just ran through a quick playfield image + video capture and it's working fine for me.  What's on the screen when it freezes?  What's in the log?

Does pressing Escape (or your "Exit Game" key if you remapped it) do anything when it's stuck?

 

Edited by hlr53, 28 September 2018 - 08:04 PM.

[hlr53]

 

 

On A21 & just now A22, media capture only displays Playfield Image, Playfield Video and Table Audio options. 

 

Do you have a backglass window open?  It offers capture for the open windows.

 When I start a capture it creates the image and then nothing else happens? Seems to be frozen? I have set for 2 monitors.

 

Don't know... I just ran through a quick playfield image + video capture and it's working fine for me.  What's on the screen when it freezes?  What's in the log?

Does pressing Escape (or your "Exit Game" key if you remapped it) do anything when it's stuck?

 

 

 

A22 On my other system when trying to record media I am getting the enable Stereo Mix error. From previous testing ffmpeg requires this, correct? I am running a Sound Blaster Recon3Di and it is set to 2 speakers stereo. So, I don't know how to fix this?

 

Debug Output

 

'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\msvcrt.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\msvcrt.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\msvcrt.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\combase.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\gdi32full.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\winmmbase.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\ResourcePolicyClient.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Program Files\NVIDIA Corporation\Ansel\Tools\NvCameraWhitelisting64.dll'
The thread 0x360c has exited with code 0 (0x0).
INFO: XAudio 2.7 debugging enabled
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\CoreMessaging.dll'
INFO: mastering voice has 2 channels, 44100 sample rate, 00000003 channel mask
The thread 0x3e58 has exited with code 0 (0x0).
The thread 0x2a58 has exited with code 0 (0x0).
The thread 0x680 has exited with code 0 (0x0).
The thread 0x4344 has exited with code 0 (0x0).
The thread 0x3cac has exited with code 0 (0x0).
The thread 0x3dec has exited with code 0 (0x0).
The thread 0x4728 has exited with code 0 (0x0).
The thread 0x472c has exited with code 0 (0x0).
The thread 0x297c has exited with code 0 (0x0).
The thread 0x3b30 has exited with code 0 (0x0).
The thread 0x1ff0 has exited with code 0 (0x0).
The thread 0x4474 has exited with code 0 (0x0).
The thread 0xbb4 has exited with code 0 (0x0).
The thread 0xed0 has exited with code 0 (0x0).
The thread 0x994 has exited with code 0 (0x0).
The thread 0xa58 has exited with code 0 (0x0).
The thread 0x4650 has exited with code 0 (0x0).
The thread 0x2964 has exited with code 0 (0x0).
The thread 0x3df4 has exited with code 0 (0x0).
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\dcomp.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\rmclient.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\twinapi.appcore.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\DataExchange.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\XAudioD2_7.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\devenum.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\InputHost.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\Windows.UI.dll'
The thread 0xe8 has exited with code 0 (0x0).
The thread 0x4444 has exited with code 0 (0x0).
The thread 0x39c8 has exited with code 0 (0x0).
The thread 0x2c64 has exited with code 0 (0x0).
The thread 0x32c8 has exited with code 0 (0x0).
The thread 0x38c0 has exited with code 0 (0x0).
The thread 0x3024 has exited with code 0 (0x0).
The thread 0x27d0 has exited with code 0 (0x0).
The thread 0x4524 has exited with code 0 (0x0).
The thread 0x1608 has exited with code 0 (0x0).
The thread 0x3f50 has exited with code 0 (0x0).
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_945f3411f285793e\nvwgf2umx.dll'
'PinballY.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_945f3411f285793e\nvldumdx.dll'
The thread 0x462c has exited with code 1 (0x1).
The thread 0x376c has exited with code 0 (0x0).
The thread 0x3794 has exited with code 0 (0x0).
The program '[6484] PinballY.exe' has exited with code 0 (0x0).

--------------------------------------------------------------------------------------------------

On my Pincab I think what is happening is when PBY gets to the ffmpeg start portion it hangs. It records the image ok. No errors and nothing shows in the log files.  The table stays running and I can actually play it. Even if I don't play it when I press Esc it brings up the Quit to VPX editor dialog box. Esc does not go back to PBY. My Realtek audio is set to stereo.

 

If you can think of something else to try, short of installing VS17 on the cab and doing a debug build.

Edited by hlr53, 29 September 2018 - 03:00 PM.

[mjr]

A22 On my other system when trying to record media I am getting the enable Stereo Mix error. From previous testing ffmpeg requires this, correct? I am running a Sound Blaster Recon3Di and it is set to 2 speakers stereo. So, I don't know how to fix this?

 

If you want audio, you need a Stereo Mix device.  It's what ffmpeg uses as the source for sound.  So to fix "you need stereo mix to do this", either:

 

- Install/enable Stereo Mix (search the web for "how to install stereo mix")

 

- OR -

 

- Record without audio, by selecting "Capture Silent" instead of "Capture w/Audio" for the playfield

 

 

No errors and nothing shows in the log files.

 

Does "nothing shows in the log files" mean

 

(a) "The log files are complete empty"

 

or (b) "The log files look perfectly normal to me, I don't see anything explaining why it's freezing"?

 

If it's the latter, you might post them anyway as they might suggest something to me.

 

 

On my Pincab I think what is happening is when PBY gets to the ffmpeg start portion it hangs. It records the image ok. No errors and nothing shows in the log files.  The table stays running and I can actually play it. Even if I don't play it when I press Esc it brings up the Quit to VPX editor dialog box. Esc does not go back to PBY.

 

What happens if you just PLAY the game, forgetting media capture entirely for the moment?

 

1.  main menu -> Play Game

 

2.  let it start up

 

3.  press Escape

 

Does it return to PBY then?

 

If not, could you perhaps have something set up wrong with the launch parameters?  If Escape doesn't work and FFMPEG isn't starting up, it suggests to me that PinballY doesn't think the game has started, which usually means that it's one of those Steam/BAM things where the initial Program EXE and the actual game process are different programs, and the PROCESS parameter isn't set up to reflect that, so PinballY is waiting for the wrong thing to finish.

And in any case, what happens if you Alt-Tab back to PinballY while you're in this "stuck" state where PinballY isn't responding to Escape keys?

Edited by mjr, 29 September 2018 - 05:19 PM.

[hlr53]

 

A22 On my other system when trying to record media I am getting the enable Stereo Mix error. From previous testing ffmpeg requires this, correct? I am running a Sound Blaster Recon3Di and it is set to 2 speakers stereo. So, I don't know how to fix this?

 

If you want audio, you need a Stereo Mix device.  It's what ffmpeg uses as the source for sound.  So to fix "you need stereo mix to do this", either:

 

- Install/enable Stereo Mix (search the web for "how to install stereo mix")

 

- OR -

 

- Record without audio, by selecting "Capture Silent" instead of "Capture w/Audio" for the playfield

 

 

No errors and nothing shows in the log files.

 

Does "nothing shows in the log files" mean

 

(a) "The log files are complete empty"

 

or (b) "The log files look perfectly normal to me, I don't see anything explaining why it's freezing"?

 

If it's the latter, you might post them anyway as they might suggest something to me.

 

 

On my Pincab I think what is happening is when PBY gets to the ffmpeg start portion it hangs. It records the image ok. No errors and nothing shows in the log files.  The table stays running and I can actually play it. Even if I don't play it when I press Esc it brings up the Quit to VPX editor dialog box. Esc does not go back to PBY.

 

What happens if you just PLAY the game, forgetting media capture entirely for the moment?

 

1.  main menu -> Play Game

 

2.  let it start up

 

3.  press Escape

 

Does it return to PBY then?

 

If not, could you perhaps have something set up wrong with the launch parameters?  If Escape doesn't work and FFMPEG isn't starting up, it suggests to me that PinballY doesn't think the game has started, which usually means that it's one of those Steam/BAM things where the initial Program EXE and the actual game process are different programs, and the PROCESS parameter isn't set up to reflect that, so PinballY is waiting for the wrong thing to finish.

And in any case, what happens if you Alt-Tab back to PinballY while you're in this "stuck" state where PinballY isn't responding to Escape keys?

 

 

1. On Alienware Win 10 Home. OK, will check out audio stereo mix or I'll capture silently. Video captured correctly with audio silent.

 

2. On Pincab Win 10 Pro everything in log checked except DOF:

 

 

Saturday, September 29, 2018, 2:15:29 PM: Session started
PinballY 1.0.0 (Alpha 22), build 6750 (x64, 20180928-1854)

Starting pinball player system setup
The main table database folder is C:\PinballX\Databases

Configuring pinball player system "Visual Pinball X"
+ database folder = C:\PinballX\Databases\Visual Pinball X
+ full executable path to player program is C:\Visual Pinball\VPinballX.exe
+ working path when launching player program is C:\Visual Pinball\
+ full table path (folder containing this system's table files) is C:\Visual Pinball\Tables
+ scanning for table files: C:\Visual Pinball\Tables\*.vpx
++ found file:  Big Game.vpx
++ found file:  Black Pyramid VPX v1.0.3.vpx
++ found file:  Nudge Test and Calibration.vpx
+ media folder base name is Visual Pinball X, full path is C:\PinballX\Media\Visual Pinball X; this folder name is defaulted from the system name
+ searching folder C:\PinballX\Databases\Visual Pinball X for table database .XML files

+ System "Visual Pinball X": loading table database file C:\PinballX\Databases\Visual Pinball X\Visual Pinball X.xml
++ This is the main file for this system (it doesn't define a category)
++ adding game Black Pyramid, table file Black Pyramid VPX v1.0.3, media file base name Black Pyramid (Bally 1984)
Pinball player system "Future Pinball" is disabled; skipping
Pinball player system "Pinball Arcade" is disabled; skipping
Pinball player system "Pinball FX3" is disabled; skipping

Media file lookup for Black Pyramid: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Table launch: Black Pyramid, table file Black Pyramid VPX v1.0.3, system Visual Pinball X

Media file lookup for Black Pyramid, for capture: Playfield Video, path C:\PinballX\Media\Visual Pinball X\Table Videos, found C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v

Media file lookup for Black Pyramid, for capture: Table Audio, path C:\PinballX\Media\Visual Pinball X\Table Audio, found C:\PinballX\Media\Visual Pinball X\Table Audio\Black Pyramid (Bally 1984).mp3

Media file lookup for Black Pyramid, for capture: Backglass Image, path C:\PinballX\Media\Visual Pinball X\Backglass Images, found C:\PinballX\Media\Visual Pinball X\Backglass Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid, for capture: Backglass Video, path C:\PinballX\Media\Visual Pinball X\Backglass Videos, found C:\PinballX\Media\Visual Pinball X\Backglass Videos\Black Pyramid (Bally 1984).f4v
+ launch: full table path C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3
+ table launch: table file C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3 doesn't exist; try adding extension -> C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx
+ table launch: file + extension (C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx) exists, using it
+ table launch: executable: C:\Visual Pinball\VPinballX.exe
+ table launch: applying command line variable substitutions:
+ Original> /play -"[TABLEPATH]\[TABLEFILE]"
+ Final   > /play -"C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx"
+ table launch: process launch succeeded

 

3.A  I can launch and play tables fine. ESC brings it back.

 

3.B Alt-Tab shows PBY quit running. Only VPX is running.

[hlr53]

Hold the phone, going silent on the other system told me to try it on the pincab. - testing without audio on pincab. I thought at first it didn't create a media folder but I was pointing to PBX folders. It worked OK.

 

Have to research the audio as it worked on the pincab in the past before a fresh Win 10 install.

 

My Alienware has the fancy SoundBlaster audio and my pincab has Realtek drivers.

---------------------------------------------------------------------------------------------------------------------

Media file lookup for Black Pyramid: Backglass Video, path C:\PinballX\Media\Visual Pinball X\Backglass Videos, found C:\PinballX\Media\Visual Pinball X\Backglass Videos\Black Pyramid (Bally 1984).f4v

Media file lookup for Black Pyramid: Playfield Video, path C:\PinballX\Media\Visual Pinball X\Table Videos, found C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v

Media file lookup for Black Pyramid: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Playfield Video, path C:\PinballX\Media\Visual Pinball X\Table Videos, found C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v

Media file lookup for Black Pyramid: Backglass Image, path C:\PinballX\Media\Visual Pinball X\Backglass Images, found C:\PinballX\Media\Visual Pinball X\Backglass Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Backglass Video, path C:\PinballX\Media\Visual Pinball X\Backglass Videos, found C:\PinballX\Media\Visual Pinball X\Backglass Videos\Black Pyramid (Bally 1984).f4v

Table launch: Black Pyramid, table file Black Pyramid VPX v1.0.3, system Visual Pinball X

Media file lookup for Black Pyramid, for capture: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid, for capture: Playfield Video, path C:\PinballX\Media\Visual Pinball X\Table Videos, found C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v
+ launch: full table path C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3
+ table launch: table file C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3 doesn't exist; try adding extension -> C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx
+ table launch: file + extension (C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx) exists, using it
+ table launch: executable: C:\Visual Pinball\VPinballX.exe
+ table launch: applying command line variable substitutions:
+ Original> /play -"[TABLEPATH]\[TABLEFILE]"
+ Final   > /play -"C:\Visual Pinball\Tables\Black Pyramid VPX v1.0.3.vpx"
+ table launch: process launch succeeded

Media capture: Capturing Playfield Image: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 0 -offset_y 23 -video_size 1080x1857 -i desktop   -vf "transpose=1" -vframes 1 -rtbufsize 2000M "C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png"

+ FFMPEG completed: process exit code 0

Media capture: Capturing Playfield Video: launching FFMPEG
> "C:\PinballY\ffmpeg\ffmpeg.exe" -y -loglevel warning -probesize 30M -thread_queue_size 32  -f gdigrab -framerate 30 -offset_x 0 -offset_y 23 -video_size 1080x1857 -i desktop -c:a none  -vf "transpose=1" -t 10 -rtbufsize 2000M "C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v"

+ FFMPEG completed: process exit code 0

Re-scanning for all systems' table files due to application activation
+ scanning for table files: C:\Visual Pinball\Tables\*.vpx
+ table launch: Close Game command received
+ table launch: game exited normally
+ table launch finished successfully

Media file lookup for Black Pyramid: Playfield Video, path C:\PinballX\Media\Visual Pinball X\Table Videos, found C:\PinballX\Media\Visual Pinball X\Table Videos\Black Pyramid (Bally 1984).f4v

Media file lookup for Black Pyramid: Playfield Image, path C:\PinballX\Media\Visual Pinball X\Table Images, found C:\PinballX\Media\Visual Pinball X\Table Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Backglass Image, path C:\PinballX\Media\Visual Pinball X\Backglass Images, found C:\PinballX\Media\Visual Pinball X\Backglass Images\Black Pyramid (Bally 1984).png

Media file lookup for Black Pyramid: Backglass Video, path C:\PinballX\Media\Visual Pinball X\Backglass Videos, found C:\PinballX\Media\Visual Pinball X\Backglass Videos\Black Pyramid (Bally 1984).f4v

Saturday, September 29, 2018, 2:44:22 PM: PinballY session ending

Edited by hlr53, 29 September 2018 - 07:31 PM.

[mjr]

Hold the phone, going silent on the other system told me to try it on the pincab. - testing without audio on pincab. I thought at first it didn't create a media folder but I was pointing to PBX folders. It worked OK.

 

So everything is working now?  (With silent mode capture, at least?)

 

 

Have to research the audio as it worked on the pincab in the past before a fresh Win 10 install.

 

If audio capture is what's making the difference, it's a good bet that it was just a matter of resetting drivers to defaults when you reinstalled Windows.  You must have had the Stereo Mix device enabled before and it got disabled when you reset everything.

[hlr53]

Yep, everything works in silent mode on both systems. Whew!!! I don't have an independent recollection (watching too much legal stuff this week) of having to mess with the pincab audio before but who knows? 

 

I'll get both working now that I know the issue. Probably good info for others in the future.

 

Too bad ffmpeg is not more robust in the audio dept.

Edited by hlr53, 29 September 2018 - 09:05 PM.

[mjr]

Yep, everything works in silent mode on both systems. Whew!!! I don't have an independent recollection (watching too much legal stuff this week) of having to mess with the pincab audio before but who knows? 

 

I'll research this week and see if I can both working. Probably good info for others in the future.

 

Sounds good.  I can add any tips you come up with to the documentation.

 

So the weird freeze-up behavior seems to have been caused by the audio issue?  I'll have to see if I can reproduce that.  It should just display the error and send you back into the normal UI, not do anything untoward like freezing or crashing.

 

 

Too bad ffmpeg is not more robust in the audio dept.

 

Well, it's not really ffmpeg's fault, it's more a matter of the Windows media APIs being incredibly scattered and hard to use.  Media seems to be an area where they had fifteen groups at Microsoft all having turf wars over a couple of decades about what's the best way to do it, so there are something like six completely separate official Microsoft media APIs, with varying degrees of hardware and OS version compatibility.  And they're basically all obsolete anyway.  Every group's documentation says that the *other* groups' versions are all deprecated and obsolete, claiming that *theirs* is the one true media API.  So it's difficult to know what to do or whom to trust when developing media software. 

 

Anyway, ffmpeg actually has multiple ways of capturing audio, but the only one that's built in is the "Stereo Mix" scheme.  Everything else requires installing some other software or device drivers.  I didn't want to go down that road and create a big pyramid of dependencies on third-party software for different systems.  But I suppose it might come to that anyway, since Stereo Mix is apparently no longer standard in Windows 10.  I believe it's installed in pretty much every Windows 7 and 8 system by default, which is probably why it became the universal ffmpeg solution in the first place, but apparently with Win 10 there is no standard, universal, built-in solution any more.  I guess every Win 10 user needs to install something additional now.  So this might merit more consideration to see if we can come up with something that will work for everyone on Win 10.  Let me know if you have any ideas about that - so far I haven't come up with anything that's suitably one-size-fits-all.  It seems to be a function of your sound card now.

Edited by mjr, 29 September 2018 - 09:12 PM.