Bedwyr Posted August 5, 2018 Share Posted August 5, 2018 On a whim I decided to drop a startup video into the launchbox\videos folder and got BB to start up once with it. After that I get nothing. No exe in Task Manager taking up memory or anything for about two minutes. I removed the video and BB starts up perfectly fine again. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted August 5, 2018 Share Posted August 5, 2018 Not sure why that happened, but if you are using a LB version that is recent startup videos now go in their own folder. So you should have a /Launchbox/Video/Startup folder and then you can drop multiple videos in it (file names do not matter) and LB will use them at random on startup. Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 5, 2018 Author Share Posted August 5, 2018 (edited) Which version? I'm on beta 15 right now; no folder. I did make one and it seems to be working so far with one caveat: don't restart BB too quickly. It may be that if the video player is running a demo on closing BB, it'll stop the startup video from playing. Edited August 5, 2018 by Bedwyr formatting Quote Link to comment Share on other sites More sharing options...
Retro808 Posted August 5, 2018 Share Posted August 5, 2018 Yes, you have to make the folder. It is not generated by Launchbox. Are you talking about if you are running a shutdown video when you close BigBox if you restart BigBox too fast the the start-up video does not play? Are you using that outro/shutdown video plug-in from the 3rd party downloads? Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 5, 2018 Author Share Posted August 5, 2018 Nope. Just a pure shutdown. I heard the Super Mario 64 audio playing a few seconds after I quit so I theorize that it's preventing the startup video from playing; all I got was a black background. It's nothing worth calling a problem unless Jason's interested in it, but I think that's the cause. Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 6, 2018 Author Share Posted August 6, 2018 Nope, my theory is wrong. I came back after doing errands and discovered that starting BB would result in a long load time, a blank screen while the audio of the startup video played, and then the BB interface would load. Shut that down and it worked correctly the second time. Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 6, 2018 Author Share Posted August 6, 2018 (edited) Huh. And now the background video playback on the NES platform view is black. Ok, I'm switching from VLC to WMP temporarily to see if that fixes the issue. Edit: no it doesn't. Black screen on start is still there. Edited August 6, 2018 by Bedwyr new information. Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 6, 2018 Author Share Posted August 6, 2018 (edited) Only external factor I can think of is that I'm running a Handbrake ripping process right now. Maybe the decoding process is interrupting playback somehow??? Edited August 6, 2018 by Bedwyr clearer Quote Link to comment Share on other sites More sharing options...
neil9000 Posted August 6, 2018 Share Posted August 6, 2018 6 hours ago, Bedwyr said: Only external factor I can think of is that I'm running a Handbrake ripping process right now. Maybe the decoding process is interrupting playback somehow??? Yes handbrake could certainly be interfering there, its a heavy user of cpu especially if you are converting the format it will often use 100% of your cpu. So anything you try to open will be very slow if there is no spare cpu power to use there. Also as that is a video program it very well could be that it is using the same codecs and such that any other video program uses at the same time. I personally would never attempt to play games or load cpu intensive programs while running handbrake, thats just asking for issues, i run handbrake overnight when the PC isnt being used for anything else as it just kills performance. Quote Link to comment Share on other sites More sharing options...
Bedwyr Posted August 6, 2018 Author Share Posted August 6, 2018 (edited) It'd have to be the codecs then. CPU utilization when I do this is rarely above 30-50%. Edited August 6, 2018 by Bedwyr correction Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.