MAJOR reponse time issues with Firefly remote and Meedio

[durex]

So i just replaced my ati remote wonder 1 with a brand new snapstream firefly remote.

I installed the software as suggested, upgraded it to 1.2, chose meedio as the application to launch and connected the usb transmitter.

The problem is, Im experiencing MAJOR lag issues between the remote and meedio. When I press the firefly button (which is set to launch meedio) it takes a good 45 seconds to a minute. When its finally launched theres roughly a 5-8 second delay between using any of the navigation buttons and when they actually respond.

At first I figured it was a bunk remote or issues with the drivers or usb transmitter, but I can navigate through the snapstream 'beyond media' program without any response issue...

Anyone have any thoughts on this as Im very anxious to get this remote working....

Thanks!

[aaronmielke]

Is your CPU maxed out when you are waiting for Firefly to respond? Or is your computer just doing nothing?

[durex]

Just sits there doing nothing...

[aaronmielke]

Are you up to editting your profile? Cause I have some things you could try to diagnose the problem.

[durex]

Im up for doing anything that will make this work.

Fire away!!

[aaronmielke]

All right. Here's what you do:

Here is where your profiles are located:
C:\Documents and Settings\All Users\Application Data\SnapStream\Firefly\Profiles

The profile that describes global actions (ff button, music-video button) is global.xml
The profile that describes what to do when Meedio is in focus is Meedio Essentials-Meedio-1.15.22.xml

So you will be editing those two profiles depending on what you want to test you’ll want to edit those profiles. Looking at the Meedio profile, I’d have to say I’m suspicious about what you are saying about the navigation keys not responding. Are you sure Meedio is responsive. For instance, if you hit up/down on the keyboard are you sure that Meedio just doesn’t take a long time to respond?

As for taking 45 seconds to launch. Try replacing the switch-app action that is in your global.xml with a simple launch action and let me know if it launches faster. Here’s a short tutorial on profile editing:
Firefly profile tutorial

Let me know if you have any questions,
Aaron

[durex]

Originally Posted by aaronmielke

All right. Here's what you do:

Here is where your profiles are located:
C:\Documents and Settings\All Users\Application Data\SnapStream\Firefly\Profiles

The profile that describes global actions (ff button, music-video button) is global.xml
The profile that describes what to do when Meedio is in focus is Meedio Essentials-Meedio-1.15.22.xml

So you will be editing those two profiles depending on what you want to test you’ll want to edit those profiles.

So what exactly should I be editing?

Originally Posted by aaronmielke

Looking at the Meedio profile, I’d have to say I’m suspicious about what you are saying about the navigation keys not responding. Are you sure Meedio is responsive. For instance, if you hit up/down on the keyboard are you sure that Meedio just doesn’t take a long time to respond?

You may have read my original post incorrectly as I never stated the navigation within Meedio doesnt respond at all. It does, exactly as you stated- it takes about 3-5 seconds for them to respond. So for example... I press down and 3 seconds later it actually moves down. I ONLY have this problem in Meedio.. the other programs (SnapStream at least) respond as soon as I hit the button...

Originally Posted by aaronmielke

As for taking 45 seconds to launch. Try replacing the switch-app action that is in your global.xml with a simple launch action and let me know if it launches faster. Here’s a short tutorial on profile editing:
http://forums.snapstream.com/vb/showthread.php?t=15113

Ill give this a shot and post back the results.

Thanks for the quick response!

[aaronmielke]

You may have read my original post incorrectly as I never stated the navigation within Meedio doesnt respond at all. It does, exactly as you stated- it takes about 3-5 seconds for them to respond.

So does this mean that navigation within meedio with the keyboard also takes 3-5 seconds to respond?

[durex]

Originally Posted by aaronmielke

So does this mean that navigation within meedio with the keyboard also takes 3-5 seconds to respond?

No, if I use the keyboard it responds immediately as it should. Its only when I use the remote that it takes this long.

Also, another thing I should add is that Ive installed meedio and the firefly software on another PC and it has the exact same results, so I would assume its not the hardware... (Which I have never really thought anyway, because again, it works without issue with SnapStream)

[durex]

Ok... Ive been playing around with this and have a bit more info that I HOPE will help things along.

I found the Firefly logs folder and noticed that it is getting written to on two different occasions.

The 1st is when I press the Firefly button. Now let me say that when I press this Firefly stops responding. I cant right click on the sys tray icon and nothing happens for perhaps a good 2 minutes, then it finally starts responding again, but meedio still doesnt load.

I kept an eye on the log file from the moment I pressed the Firefly button and realized the log file is written to as soon as Firefly starts responding again. It adds the following to the log:

 01/06/2005 09:44:48 ************************************
 Thursday, January 06, 2005 9:44:48 PM
  System.InvalidOperationException: Process performance counter is disabled, so the requested operation cannot be performed.
     at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
     at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine)
     at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
     at System.Diagnostics.Process.GetProcessesByName(String processName, String machineName)
     at System.Diagnostics.Process.GetProcessesByName(String processName)
     at SnapStream.Firefly.App.ContainerForm.InitForm()

The only other time Ive noticed the log file being written to is when I open Firefly. Heres the entry it makes every time I start it:

01/06/2005 09:35:53 ************************************
  Thursday, January 06, 2005 9:35:53 PM
  System.InvalidOperationException: Process performance counter is disabled, so the requested operation cannot be performed.
     at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
     at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine)
     at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
     at System.Diagnostics.Process.EnsureState(State state)
     at System.Diagnostics.Process.get_MainWindowHandle()
     at SnapStream.Common.Util.LaunchWithState.Launch()

It doesnt seem to write to the file when I use the remote to navigate through meedio.

I have no idea what these errors mean, but I hope it helps get to the bottom of this problem!

[durex]

I figured it out!

Somehow I dont have Windows 'Performance Tools' installed on my XP machine (Administrative Tools > Performance).

I googled this error and found a bunch of references to a particular registry key... which sure enough I didnt even have. I then looked on my roomates pc, who had the reg key. I installed meedio and firefly on hers and volia! It works like a damn charm.

So now I need to figure out how the hell that piece didnt get installed and how to install it... first comes to worst Ill need to reload WinXP.

Thanks a ton for the help Aaron!

[aaronmielke]

As to perfromance monitors, there may be a registry entry you need to remove:

http://support.microsoft.com/default...;en-us;Q248993

Especially the steps at the bottom:

1. Start Regedit.exe. (You cannot use Regedt32.exe because it does not allow searching for registry values.)
2. Click to select the following key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es
3. Select Find from the Edit menu.
4. In the Find What field, type Disable Performance Counters.
5. Click Find Next. This will locate a Performance key that may have this Registry value set to 1.
6. If the Registry value is set to 1, set the value to 0 or delete the Registry value.
7. Press F3 to find the next occurrence of this Registry value.
8. Repeat the previous two steps until there are no Performance keys that have the Disable Performance Counters value set to 1.