can't locate local ip and startup delay

[msaleem]

Hello,

I'm using windows 7, media lab 2008.1 and direct rt2010. Media lab seems to be working fine until it has to transfer to direct rt and then all I see is a blank purple screen (no continue button). Direct rt never shows up. This is happening with several of my experiments which use direct rt within media lab questionnaires.

[uod]

I am having a very similar problem with an experiment that one of our labs is trying to run.

Windows 7 running Medialab 2008 w/ DirectRT 2010. When MediaLab starts up executeDRT.exe ... the system hangs at the white/purple-ish screen for about 50 seconds before executeDRT.exe seems to finally pull up the experiment. We can then run the experiment without any problem. Is there anything that can be done to prevent this delay? I can't figure out what is causing it.

[msaleem]

that's interesting that it moves forward after a few seconds. Mine doesn't seem to be moving forward at all. I waited for 2 minutes. The strange thing is we were running this experiment fine on Windows XP but we got new computers with Windows 7 and now it keeps getting stuck when it's supposed to transition to direct rt.

Does anyone have a suggestion as to what is happening?

[jarvis24]

What version(s) of DirectRT v2010 are we talking about here? If its a beta version, I would suggest uninstalling it and installing the current version from the main download webpage (www.empirisoft.com/download.aspx).

[msaleem]

How can I find out which version it is? I clicked on the about direct rt tab and it said "Version 2010: 38.824.9F".

[jarvis24]

That's a beta version. It should (at this date, Dec 2, 2010) read 2010.2.x.x in order to indicate that it's a final "official" release of v2010. I would suggest uninstalling and downloading the current non-beta version from www.empirisoft.com/download.aspx.

[jarvis24]

If you run the "Voice Response" setup utility from the DirectRT v2010's Tools menu--do you see a microphone input listed there? We've discovered on the machines here that if a valid sound input device is not listed then it creates a lengthy delay when DirectRT starts to run an input file. Try to use the utility to see if it can capture your test voice response times. When I selected a valid microphone input and saved the settings, DirectRT started up very quickly once again. Would be curious to know if anyone else finds this as we look for a better solution. This assumes that the delay in DirectRT happens regardless of whether it's run from within MediaLab or on its own.