Bedwyr

Jason Carr said Thanks @Justified and @kmoney2315, great to hear. @Bedwyr, what game's video is causing the issue? I can just download it from EmuMovies and test it myself. After thinking about it, even if the video is corrupt, I should probably figure out how to make it so that corrupted videos don't crash things. So it'll be a good test/way to fix that scenario. Ultima VI: False Prophet.

Bedwyr said Jason Carr said Ugh, sounds like a nasty bug to fix. Or actually more sounds like a bug with VLC itself. I always blame my code first, but you're right, if it's only that video that's causing the issue, then it probably isn't the relative path issue. All I can figure is it must be a bug with VLC. I assume you're still getting the error with beta 14? Downloading now. Will let you know if it crops up again. Ok, I just reproduced the error. Sequence is: - Enter SNES list (using the list view) - Scroll up and down across the video (no problem; it loads every time) - Load a game (I did Link to the Past) - Exit the emulator and return back to the list - Scroll across the video - Get error; BB crashes You want my copy of the video or something? I still have some suspicion that it's an encoding issue and that the player/BB is just choking on it. Something about the video and the state of BB after having left emulation.

Jason Carr said Ugh, sounds like a nasty bug to fix. Or actually more sounds like a bug with VLC itself. I always blame my code first, but you're right, if it's only that video that's causing the issue, then it probably isn't the relative path issue. All I can figure is it must be a bug with VLC. I assume you're still getting the error with beta 14? Downloading now. Will let you know if it crops up again.

Jason Carr said Bedwyr said Just got a new error in the latest beta (13). System.IO.FileNotFoundException: Not found: Videos\Super Nintendo (SNES)\Ultima VI - The False Prophet (USA).mp4 The video in question does exist and I grabbed it from EmuMovies. And it does play in BB, but has occasionally not consistently played. Perhaps there's some encoding shenanigans going on in the file that VLC choked on? For reference the file I'm using is located on the server at /Official/Video Snap Packs (480p)(HQ)/Nintendo SNES (Video Snaps)(HQ-480p)(EM 20160209). Toss this in the bugtracker? Hmm, I wonder if it's because we're not using an absolute path. I should look into that. Added that to my list. :) That would be very very weird. The video file is in the same folder as the others and it's always that particular clip that causes issues. Before the current beta what I noticed is that it simply wouldn't load. That is: - It would play if I just started up BB. - But after entering and exiting an emulator it would not load the video. - It would continue playing the previous video (the one either above or below). So navigating up from UN Squadron it would still play the UN preview, and then the following clip one place up from U6. - LaunchBox *always* would play all videos correctly (as far as I can tell; results may vary). Now, however, it's just that error message.

No problem at all. Though if I could ask a teensy favor: could you explain the changes you made in the script when you get it complete? We may as well learn something new while we're at it.

ashramrak said Syriacn said Bigbox launches perfectly while Kodi minimizes what we are pointing out is that when the "quit kodi" setting is set to "yes" kodi should close completely and not minimize itself Yup, that's the issue. What I believe the Steam version does is use the AHK script to stay memory resident and wait until Steam is shut down so that it can re-start Kodi. So the primary issue probably? is in that script rather than the main Python script. Probably.

Also in beta 13, getting continued audio from videos after navigating away from that entry.

Just got a new error in the latest beta (13). System.IO.FileNotFoundException: Not found: Videos\Super Nintendo (SNES)\Ultima VI - The False Prophet (USA).mp4 File name: 'Videos\Super Nintendo (SNES)\Ultima VI - The False Prophet (USA).mp4' at Meta.Vlc.Wpf.VlcPlayer.LoadMedia(String path) at (<>c__DisplayClass4_0 ) at BigBox.Views.ImageVideoView.<>c__DisplayClass4_0.<PlayVlcVideo>b__0() at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore() at System.Windows.Threading.DispatcherOperation.InvokeImpl() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout) at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout) at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout) at System.Windows.Threading.Dispatcher.Invoke(Action callback) at BigBox.Views.ImageVideoView.PlayVlcVideo(String filePath, ChildViewModelBase parentViewModel) at (ImageVideoViewModel , Object ) at BigBox.ViewModels.ImageVideoViewModel.set_VideoPath(Object value) at (ImageVideoViewModel , String , String , Transition , ChildViewModelBase ) at BigBox.ViewModels.ImageVideoViewModel.Init(String imagePath, String videoPath, Transition transition, ChildViewModelBase parentViewModel) at (GamesViewModelBase ) at BigBox.ViewModels.GamesViewModelBase.<selectionChangedTimer_Elapsed>b__99_0() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() The video in question does exist and I grabbed it from EmuMovies. And it does play in BB, but has occasionally not consistently played. Perhaps there's some encoding shenanigans going on in the file that VLC choked on? For reference the file I'm using is located on the server at /Official/Video Snap Packs (480p)(HQ)/Nintendo SNES (Video Snaps)(HQ-480p)(EM 20160209). Toss this in the bugtracker?

It's not a critical use issue for me as I've reverted to XB360 controllers for the time being. The problem has been twofold. First, Kodi 17 implemented initial support for the XBOne controller under xinput, I believe. This was needed as Microsoft mucked around with the input assignments again in March, screwing up 16.x Jarvis use (Kodi reads the controller trigger at rest as "right-input-as-fast-as-possible"). Unfortunately right now the beta incorrectly reads controller input *even while Kodi does not have focus*. I put in a bug report but have yet to see activity or a single response from whoever on the team is responsible for developing the XB1 support. That makes the BB launcher problematical. It's more of a workaround to do this, but the XB1 controller could still be usable if the launcher correctly shut down Kodi just as the Steam launcher does; that's what had me uncover how much work went into it. Again, it's not a big functional deal for me as the launcher still works ok with Kodi in the background on the XB 360, but for the sake of others and unwelcome surprises, the advertised feature should work. I'd like to dig further into the AHK script and see if I can suss out what to change to correct this, but I'm mostly a C++ engineer and have to throw most of my time at work and a couple of related self-study project. Learning AHK and hacking the launcher has to take a back seat in favor of placating bosses, advisors, and colleagues. So I do appreciate the offer of your setup. But the objective really is to correct the launcher. If you're curious enough to dig into it, please have at it. Just report back so that, when I do have a bit more spare time, I don't duplicate your work. ps- can you clarify what you meant by teedub's repo? I didn't know this launcher was ever part of it; just the Steam Launcher.

The null error does appears to be fixed.

emko said testing out VLC so far "System.NullReferenceException: Object reference not set to an instance of an object. at Meta.Vlc.Wpf.VlcPlayer.VideoDisplayCallback(IntPtr opaque, IntPtr picture)" happened while i was going up and down a games list VLC is looking very good now :) you went from thinking to get rid of it to making it work just as good as WMP Thanks spektor56 Just got the -12 update and made the report before I checked the beta thread: https://bitbucket.org/jasondavidcarr/launchbox/issues/886/null-exception It's the same message. Certainly the same issue. Sorry if I duped. Good old null pointer exception. How I missed thee. I haven't programmed in Java in forever; for me mostly segfaults and self-inflicted memory idiocy when mucking around with multi dimensional pointer arrays (to pointer arrays of pointer arrays....).

I haven't gotten to try anything else in the last week on this issue, but hopefully I'll get to spend maybe a little bit of time. Could I get someone to at least chime in? I feel like I'm broadcasting in the blind and hearing static back. I can understand Syriacn being to busy to log in, but it would be nice to see some interest from someone else that this is worth investigating and understanding.

Also the .sh scripts are exactly the same.

Ok, I'm confused now. Looking at the differences between the Steam and BB AHK scripts, the only difference is what I have highlighted: ;KODI steam launcher autohotkey script by teeedubb ;See: https://github.com/teeedubb/teeedubb-xbmc-repo http://forum.xbmc.org/showthread.php?tid=157499 ;Manual script usage: <strong>Big-Box.exe</strong> "e:\path\to\steam.exe" "d:\path\to\kodi.exe" "0/1" "true/false" "scriptpath/false" "scriptpath/false" ;$3 = 0 Quit KODI, 1 Minimize KODI. $4 = KODI portable mode. $5 = pre script. $6 post script. ;Change the 'steam.launcher.script.revision =' number below to 999 to preserve changes through addon updates, otherwise it shall be overwritten. ;You will need to have AutoHotKey installed to recompile this .ahk file into a .exe to work with the addon. ; ;<strong>BigBox.launcher.script.revision=999</strong> These are in the comments though. There's no functional change in the script. I extracted the code from the AHK exe and it's exactly the same Steam script. Which means that all the references to Steam are non-functional? Why make a change to the comments but not the script itself?? I'm not really familiar with AHK, but I can try to look through and figure out what's likely happening. My guess at the moment is that BB is being loaded, Kodi is being dropped to the background, but Kodi isn't being correctly closed because a bad reference to a non-existent Steam Big Picture reference is preventing the Kodi->close part of the script for working properly. I could be wrong.

Ok, comparing the Kodi debug logs I noticed this in the BB launcher process: 18:43:44 T:6440 NOTICE: script.BigBox.launcher: attempting to launch: "C:\Users\HTPC\AppData\Roaming\Kodi\userdata\addon_data\script.BigBox.launcher\scripts\BigBoxLauncher-AHK.exe" "D:\Games\Emulators\LaunchBox\BigBox.exe" "C:\Program Files (x86)\Kodi\Kodi.exe" "0" "false" "false" "false" 18:43:44 T:6440 DEBUG: "C:\Users\HTPC\AppData\Roaming\Kodi\userdata\addon_data\script.BigBox.launcher\scripts\BigBoxLauncher-AHK.exe" "D:\Games\Emulators\LaunchBox\BigBox.exe" "C:\Program Files (x86)\Kodi\Kodi.exe" "0" "false" "false" "false" 18:43:44 T:6440 NOTICE: script.BigBox.launcher: busy dialog started 18:43:44 T:6148 DEBUG: Activating window ID: 10138 18:43:44 T:6148 DEBUG: ------ Window Init (DialogBusy.xml) ------ 18:43:45 T:6148 DEBUG: CWinEventsWin32::WndProcWindow is active 18:43:45 T:6148 DEBUG: CWinEventsWin32::WndProc: Focus switched to process D:\Games\Emulators\LaunchBox\BigBox.exe 18:43:54 T:6440 NOTICE: script.BigBox.launcher: busy dialog stopped after: 10 seconds The Steam launcher process shows this: 18:46:52 T:5764 NOTICE: script.steam.launcher: attempting to launch: "C:\Users\HTPC\AppData\Roaming\Kodi\userdata\addon_data\script.steam.launcher\scripts\SteamLauncher-AHK.exe" "D:\Games\Steam\Steam.exe" "C:\Program Files (x86)\Kodi\Kodi.exe" "0" "false" "false" "false" 18:46:52 T:5764 DEBUG: "C:\Users\HTPC\AppData\Roaming\Kodi\userdata\addon_data\script.steam.launcher\scripts\SteamLauncher-AHK.exe" "D:\Games\Steam\Steam.exe" "C:\Program Files (x86)\Kodi\Kodi.exe" "0" "false" "false" "false" 18:46:52 T:5764 NOTICE: script.steam.launcher: busy dialog started 18:46:52 T:8564 DEBUG: Activating window ID: 10138 18:46:52 T:8564 DEBUG: ------ Window Init (DialogBusy.xml) ------ 18:46:52 T:8564 DEBUG: CWinEventsWin32::WndProcWindow is active 18:46:52 T:8564 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc 18:46:52 T:8564 DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit 18:46:52 T:8564 NOTICE: Storing total System Uptime 18:46:52 T:8564 NOTICE: Saving settings 18:46:52 T:8564 NOTICE: stop all Why would focus be switched in the BB add-on but not in the Steam add-on? I'm going to switch to Kodi 17 and see if that changes anything. edit: no change in 17.0 Krypton (There's some interface issues with Mimic so I'll revert back to 16.1... Steam Launcher still shuts down correctly, BB Launcher does not).

The Steam launcher correctly closes Kodi with the proper setting. The Big Box launcher does not even after I removed the add-on, reset the system, and removed the user data. This is perplexing. The only difference I can see so far is that I have LaunchBox installed to D:\Games\Emulators\Launchbox\ on a different partition. Maybe both AHK scripts make wrong assumptions about relative folder locations... although my Steam install is also on D:\Games\ so that probably can't be it. I'll try comparing the scripts again, but there's nothing obvious going on. Anyone who knows more than me about this is welcome to chime in with any ideas.

Ok, I'm trying to do a line-by-line comparison between the steam launcher and BB launcher. The Kodi shutdown code in the scripts appear to be exactly the same so I'll try to remove, reinstall both plugins, and test each between 16.1 and 17.0 alpha.

Reporting in some observations from the latest beta. - The database didn't correctly recognize Ultima VI from the SNES library. It's probably the filename causing the hitch: "Ultima - The False Prophet (USA)". - I downloaded a x480 movie clip from EmuMovies for this game and get some weird behavior. If I load BixBox and navigate down to the game, it will load the clip. However if I then go into a game and exit, the clip will no longer play. It will simply play the clip from the last game highlighted (for example the clip from UN Squadron will continue playing even though the rest of the Ultima VI assets have loaded once I highlighted the game). edit: all videos play correctly every time in LaunchBox desktop application. - Before this beta I was getting a lot of delay when first opening BigBox and loading the first clip (Actraiser). The delay appears to have been reduce a fair bit; still some choppiness for about 5-10 seconds of browsing but definitely better.

That rivals the AVGN's collection. Though James has finer taste in 80s chic basement wood paneling.

Sorry if I missed this thread when posting a new topic. Cross referencing: https://www.launchbox-app.com/forum/troubleshooting/possible-kodi-issue-heads-up Do any of you observe the same control issue in Kodi? And also are any of you having trouble with the addon not closing Kodi?

Correction, sorry. I forgot that the addon has a "close Kodi" setting. However the setting does not work. Kodi is still running in the background whether the setting is set to 'yes' or 'ask' and you select 'yes'. I'm running 17.0 with Mimic. For reference I started a bug ticket with Kodi here: http://trac.kodi.tv/ticket/16719. edit: Ok, belay that. I was going to start a ticket but saw this: https://bitbucket.org/jasondavidcarr/launchbox/issues/577/does-the-big-box-work-with-kodi-160-jarvis. So I guess consider this the report to whoever makes the launcher.

This is not super critical yet, but some renewed MS controller changes borked the XB1 controller for Kodi again. I upgraded to the 17.0 alpha as it has a joystick addon that explicitly supports xInput and correctly recognizes a 360 style controller. That appears to have worked. HOWEVER Currently their addon functionality still receives and processes controller inputs even while Kodi is in the background. So while running an external program, it is possible for Kodi to do weird things based on the input you're giving to the other program. I've had Kodi try to reboot the computer twice now and end up in a folder menu once. Unfortunately I couldn't log in to their bug tracker, so I reported it to hopefully relevant thread. Upshot: Be aware that Kodi users might come here once 17 gets closer to release and past release if they don't fix the problem. While not LaunchBox's problem, one possible preemptive solution would be to make it work like the Steam Addon which closes Kodi when launching Steam and opens Kodi when exiting Steam. Just a thought for consideration.

Jason Carr said Wow, well I do have to thank you and congratulate you, @Bedwyr for your troubleshooting skills! That's impressive. Thanks for that. I do have an Xbox One controller to test with so I'll take a look at that soon. :) It's an engineer thing. Try troubleshooting intermittent autopilot telemetry with 15 teammates around you doing nothing and the plane not flying till you figure it out. Ah flight test.

Oddly, this only applies to the Options menu. No other popup has the same problem; I just tested it. It's also super reliable. If I have the controller on and select Options no popup. If I hold down the guide button, the very second it shuts off the Options menu pops up.

Got it! It's the Xbox 1 controller. As long as it's active, Options won't pop up. I can normally select Options all day long to my hearts content but with the XB1 turned on it will not load. That's why I was making the BB connection. It's the only time I usually have the controller active and why I claimed the behavior happened only after loading BB. Possible things to test further: - This is with the wireless receiver. Does it also happen on a USB cable? - How about the 360 controller and wireless receiver? - I've disabled normal Win10 "game bar" functionality. Will the same behavior appear if I re-enabled it?