Jason Carr

Thanks Jade. Glad to hear it's working for you when you say "computer" at least. The exiting game bug probably has to do with the specific emulator. What emulator are you using? We still have some fixes to put in place for problematic emulators.

I did put out another new beta guys, but still focusing on fixing the issues with voice recognition. We can keep discussion on the voice recognition stuff in this thread: If you're testing voice recognition, please go hit that thread up and check out the latest comments to help us test. Thanks all!

Welcome back Martin! Don't have an ETA yet @AeronNL. We have a lot to wrap up yet. @jking3 My bartop arcade should be arriving tomorrow, so I can figure some things out then. At this point I'm still pretty much a noob to LEDBlinky, unfortunately. I'm sure once I get the cabinet I'll be able to focus on getting everything perfected.

Alright, new beta is out that should help to troubleshoot things further. First things first, after updating to beta 13, go into the voice recognition options and check the box to enable Debug Mode in the bottom right-hand corner. Then press OK out of both dialogs and restart LaunchBox. You will now need this "Debug mode" enabled in order to receive debugging information for the voice recognition. After restarting, LaunchBox should show you what it thinks it heard you say in the dialog at the top, in addition to the audio level. It should also prompt you with an error if it can't connect to the default microphone on the system. Thanks guys, let me know what LaunchBox is hearing when you say "LaunchBox", "Big Box", or "Computer", or what other issues you guys are still seeing. @DOS76, what do you have your accuracy slider set to?

Sorry about the microphone tab guys; I had added it and then never put anything in it, as of yet. So that is blank on purpose. I'm going to be doing my best to get these issues fixed today; it's my top priority. We shall see how it goes. For folks that are not seeing the audio level, that is baffling me a little. I'm wondering if LaunchBox is even seeing your mic at all in that case. I'll put in some more debugging for that to see what might be going on there. Do make sure voice recognition is enabled though, and restart. The box won't show up until voice recognition is enabled and a microphone is found. If you are seeing the audio level (and it changes as you speak), here's a few things you can try: - Go to Control Panel > Speech Recognition in Windows and click "Set up microphone" and run through the wizard. I'm curious if that helps make things better for anyone. - Instead of saying "LaunchBox", try saying "Big Box" or "Computer" to wake it up. LaunchBox is supposed to recognize any of those three. However, if the speech recognition is having trouble recognizing LaunchBox, one of the other two might help. - Try adjusting your audio level for your microphone to various places. Believe it or not, my microphones seem to work best when the audio levels are fairly low, because they pick up less background noise and tend to pick up only my voice. My "audio level" readings only ever reach about 20 as I speak, so having your microphone be too loud could be part of the issue, even if it seems you're having to shout. Thanks all; I'm hoping we can come up with a solution today. I'll have a new debug beta version out shortly.

Hi Jade, we're currently working to resolve the issues here: Gonna do my best to focus on this and get it fixed today.

HI Lenny, we are currently working to troubleshoot these issues; you are not alone. Please check out this thread here: Hoping to resolve these issues today, but not quite sure what all will be involved.

Unfortunately the issues are with the VLC integration engine, and not with VLC itself. We are working on resolving the issues.

Hi @timekills, I could add a setting for that. Can you use Issues/Requests in the header to add a ticket for it? Thanks!

Hi @Kishio, currently there is not but I believe we do have a ticket for that on Bitbucket (issues/requests in the header). Hopefully I can add that soon.

Hi Aurel, no problem. That is actually a good idea for a start. I may get back to this stuff at some point, but in general it seems people are more excited about some other features rather than uploading media from LaunchBox being the most desired. That originally surprised me, but for now there are plenty of other things to focus on I think. But thanks, that does sound like a smart approach for when we get back to it.

Thank you Hubz! Very nice! Unfortunately we need to leave off the adult games currently anyways until I get some sort of an age-gate feature built.

Hi impact, make sure the folder you're using for your ROMs is properly configured in the MAME configuration. It should be listed as rompath in mame.ini. Are you using MAMEUI too by chance?

One really odd thing that I've noticed with my laptop is that it seems to want to automatically "fix" volume levels, and completely disregards any changes I make. I'm wondering if that has something to do with the issue as well.

Alright, new beta is out. This should at least tell us what volume levels (if any) are coming into LaunchBox. There should be a new box that shows up at the top of the screen that will give you an "audio level" of the microphone as you speak. This will at least confirm that LaunchBox is receiving microphone input and at what level. Please let me know what the numbers max out at as you speak. Also test with the accuracy slider back in the center. I also fixed the Options dialog to stop trying to reset everything when you save the options. So after enabling or disabling voice recognition, a restart will be required before the changes take effect. There shouldn't be any more performance issues when closing the Options dialog. Hopefully this version will at least help us troubleshoot; let me know what you guys see. Thanks!

Thanks @smallsbig. That helps. Gonna force a restart after changing the settings.

Just out of curiosity, @shinra358, try turning your volume down on your microphone. I'm curious if we're having volume leveling issues. Try and see if you can get the green bars to fill half way up as you speak. It may be that I just need to add some controls for auto-leveling the volume of the microphone.

Thanks guys. Make sure you have the right microphone selected as your default microphone in your audio settings. I'm going to have to add some settings to let you choose and test your microphone because this seems to be a common problem so we'll at least need a way to figure out what's going on. Also, @donarumo, that is very helpful information. I'm going to make it so you have to restart LaunchBox in order to enable voice recogntion since it seems to be problematic time-wise in initializing it all post-startup.

What microphone are you using @shinra358?

Awesome, sounds good @smallsbig.

@Mute64 That error was happening because of the machine not having a microphone attached. However, it should be fixed in beta 11. @polymorph77 Most likely the 30% thing is just because it's only using one CPU core for the voice recognition initialization. 14 minutes obviously still isn't acceptable so sounds like it's back to the drawing board. Thanks though.

Yes, sorry guys, working on some critical bugs with the voice recognition. Apparently it is extremely CPU intensive and is also taking forever to load on some systems. Any performance or microphone testing you guys can do with the latest beta (beta 11) would be appreciated. Please see this thread: Also, keep in mind that microphone quality apparently matters a whole lot. For example, the built-in microphone on my Dell XPS 13 is absolutely useless and won't work at all for the recognition. However, of course my recording microphones work perfectly. I'm going to test with some more mics to see how it fares.

Ah, sure. Probably because the laptop microphone quality varies as well. That makes sense.

FYI, even though this message suggests that it's writing to the folder, it's not. It's just trying to read the folder only in order to detect the applications that you have installed for the voice recognition. Still working on a resolution though.

Alright, it might be 5 minutes or so for the new update to register, but I just put out another beta guys. Let me know if this does anything to resolve the performance issues if you would. I am noticing some huge performance differences between different CPUs, which is somewhat surprising. This beta loads the voice recognition in less than 2 seconds on my i7-4770K but it takes around 8 seconds on my laptop's i5-5200U. So apparently it's very CPU intensive and requires some monster hardware. Let me know though if this latest beta makes a significant difference for you guys.