Ableton Forum

Hello,

I can start Live 2.03 in two ways. I can click on the Live 2.03 icon or I can double click on an .ALS file.

When I start live the second time other then the first time I get the following message:

"Live's ReWire engine has been installed. Live can now be used as a ReWire slave. Please restart any ReWire host applications that might be running."

English isn't my native language so let me explain. I start live with a click on its icon. Perfect. The next day I start live with a click on an icon. Perfect again. I close Live and now I start live with a double click on an .ALS file. Now I get the message box. The next time I start live with a double click on an .ALS file I don't get this message. When I start Live with a click on the Live icon I get this message again. The next time I get this message is when I start live with a double click on a .ALS file.

This is what I found out.

The Target in the icon properties is:

"C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe"

The command in the registry is (HKEY_CLASSES_ROOT\Live 2.0.3.Document\shell\open\command)

C:\PROGRA~1\Ableton\LIVE20~1.3\Program\Live 2.0.3.exe "%1"

Every time when you restart Live a different way it changes the registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Propellerhead Software\ReWire\Ableton Live Engine

in

C:\Program Files\Ableton\Live 2.0.3\Program\Ableton Live Engine.dll

or

C:\PROGRA~1\Ableton\LIVE20~1.3\Program\Ableton Live Engine.dll

When I set the command key (HKEY_CLASSES_ROOT\Live 2.0.3.Document\shell\open\command) in the registry the same way as the icon target properties, the "problem" is gone.

Regards,
Diederick F.M. Cools.

Hi DCools,

"Live's ReWire engine has been installed. Live can now be used as a ReWire slave. Please restart any ReWire host applications that might be running."

Normally this message indicates that the currently started version of Live is different from the one started at last (or if it's the first run of Live).

So I would assume that by double click on a .als file a different version than Live 2.0.3 was opened. Have you checked that everytime Live 2.0.3 was opened before you manually changed the registry?

And which windows version do you use?

regards,
Alex

So I would assume that by double click on a .als file a different version than Live 2.0.3 was opened. Have you checked that everytime Live 2.0.3 was opened before you manually changed the registry? And which windows version do you use?

I'm using Windows XP Pro SP 1 US.

I start the same version, “Live 2.0.3.exe”. As I describes in my previous message, the "problem" only occurs when the startup command of Live is different, sort name or long name.

For example start CMD.EXE or Start / Run and type the following command.

C:\PROGRA~1\Ableton\LIVE20~1.3\Program\LIVE20~1.EXE
"C:\PROGRA~1\Ableton\LIVE20~1.3\Program\Live 2.0.3.exe"
"C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe"

All three starts "Live 2.0.3.exe" but the path is in short name, long name or short and long name in one command. So when you start these three commands, each time you get the message. Do you start Live the second time with the same command, no message.

Example: I start CMD.EXE and type the following:

"C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe"
(No Message because the “ReWire\Ableton Live Engine” key is the same)

"C:\PROGRA~1\Ableton\LIVE20~1.3\Program\Live 2.0.3.exe"
(The message and “ReWire\Ableton Live Engine” key is set to "C:\PROGRA~1\Ableton\LIVE20~1.3\Program\Live 2.0.3.exe")

"C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe"
(The message and “ReWire\Ableton Live Engine” key is set to "C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe")

"C:\Program Files\Ableton\Live 2.0.3\Program\Live 2.0.3.exe"
(No message)

I think you should only check this path and set the “HKEY_LOCAL_MACHINE\SOFTWARE\Propellerhead Software\ReWire\Ableton Live Engine” key when you start live for the first time and don’t check and set this key every time you start live?

Regards,
Diederick F.M. Cools.

Hi Diederick,

thanks for your detailed posting. I understand now what you meant with short and long path.

I think it's needed every time when Live starts to check which version of Live was used at last. But the problem is that the comparing of the path coming from the registry and the one from the currently started Live doesn't tolerate this long vs. short problem. The main question for me is why sometimes we set the path in the long style and sometimes in the short style. Solving this problem would also solve the other one.

regards,
Alex