Ableton Forum

In Live options I have multiple instances OFF.

Yet when I have Live running, if I click on an ALS file, Live opens
another instance and reports 'Live has detected another active ReWire master application....'

Hi,

I just tried on my machine and with 'multiple instances' turned OFF, Live behaves as expected. So I'm wondering what we would do differently. Can you try again?

Regards,
Amaury

Yes, it still happens

Hi,

Can you try renaming your preferences.cfg file, and restart Live? That will create a new preferences.cfg file.

C:\Documents and Settings\your user name\Application Data\Ableton\Live x.xx\Preferences

Regards,
Amaury

I deleted the preferences folder.

Same thing still happens

Hello,

If you delete the whole preferences folder, Live copies preferences from an older version of Live, if present. Delete only the preferences.cfg, inside the preferences folder. Then Live will create a fresh new preferences.cfg file from scratch.

Regards,
Amaury

OK, I deleted just preferences.cfg.

Nothing changed.

Hi,

Try re-downloading and installing the application then.

Regards,
Amaury

I just re-installed 6.0.5 and this problem occurs in that release.

I'd rather not re-install 6.0.7 again. This is a minor problem,
if it is unique to me, let's just forget about it.

It seems to me it is related to Windows DDE messaging.

arachnaut wrote:I just re-installed 6.0.5 and this problem occurs in that release.

I'd rather not re-install 6.0.7 again. This is a minor problem,
if it is unique to me, let's just forget about it.

It seems to me it is related to Windows DDE messaging.

Hi,

Well, it's a bit sad not to be able to access the lessons and the File manager.

You're saying that it also happens on 6.0.5 now?

Regards,
Amaury

I don't have any trouble accessing these features.

I just have two instances of Live running, not one.

It seems to me that documents should be sent to an open
instance of the program, not create a new one, especially
when the specific option is there.

As far as I remember, this happened in Live 5 and
earlier versions of Live 6 as well. I just reported it now.

arachnaut wrote:I don't have any trouble accessing these features.

I just have two instances of Live running, not one.

It seems to me that documents should be sent to an open
instance of the program, not create a new one, especially
when the specific option is there.

As far as I remember, this happened in Live 5 and
earlier versions of Live 6 as well. I just reported it now.

Hi,

Sorry, I guess I crossed issues and replied the wrong anser to the topic, in my previous message.

One thing: Live files on your hard drive are associated to the latest Live version opened, and closed. It means that you have to open Live 6.0.7 once, and then close it, so the als files will be associated with 6.0.7.

When you say multiple instance, are they the exact same version, or another version?

Regards,
Amaury

A picture helps, see below.

I opened Live 6.0.7 and waited for it to come up.

Then I opened a project on my Desktop called
'Squeaky Clean Project' and clicked
'Squeaky Clean.als' in the project folder from the
Windows Explorer (not the Live Browser).

This opens a completely new Live session as you can see.

Both sessions work fine on playback and both
receive MIDI notes at the same time from my keyboard device.

I resized the windows side-by-side and opened the options
window in each. Both versions are 6.0.7.

Below is a screen dump of the running processes in my system
showing 4 instances of Live running.

1) Live 6.0.7 launched from Program menu
2) Live 6.0.7 launched by clicking on .als file
3) Live 6.0.5 launched from Program menu
4) Live 6.0.5 launched from .als file using 'Open with..." and
selecting Live 6.0.5 from the list.

They were launched in that order.

Isn't Windows one of the most frustrating operating systems
of all time?

I wrote my first program in 1968, been a professional since 1972,
and ran more than a dozen OS's on mainframes, mini's, micro's,
as well as bit-sliced microcoded machines.

I've never seen anything with the whimsical, fickle behavior of
Windows.

This bug has now gone away for some reason, but darned if
I know what it was that I did, or how I would ever fix
it if it happened again.

Do we really have to install, uninstall, and re-install our applications
constantly just to satisfy the 'Are you sure?' nature of this OS?

For what it is worth, I ran a disk check on all my drives - that took
a bunch of hours; re-downloaded and installed 6.0.7 again,
did a few mumbo-jumbos to the Library and some paths,
erased the preferences file, reset all the options first 'off' then 'on',
and now it looks like things are OK.

Perhaps I should restart before I pronounce it fixed for good.