I can't run Emagic Logic Platinum 5.5.1 or 5.3 on Windows 10 x64
In both cases starting logo freezes at:
"Initializing External Sample Editor communication"

 

Please Help​

 

On Windows 7 x86 working.

 

Last edited: Nov 3, 2020

It seems that Emagic Logic Platinum 5.5.1 wont run on Windows 10 x64.You may have better luck with 5.3.No idea why you are using such an old version.Latest versions are really good.If its possible ,try to buy a mac .I am still using an old mac system (early 2009 model) running Logic 10.3.No issues at all.A 2013 mac desktop model would be ideal for you(They're cheap where I come from),if finance is a crunch that is.Anyway you seem to know what you really want.This is just my view on the subject.Hope you find your solution with others on this forum.All the best.

 

I like old soft. I wanna try synths & effects from Logic. Yeah I would like to play with something fresher from Logic too, but this is the last version for Windows. After all synths & effects from Logic 5 are similar to the newer ones. This will be ok for the test to me but I can't run it : (
Maybe in the future I buy a mac for Logic 8 or 9
But right now I don't have money for this and I don't know if I will like using this DAW

 

Your images aren't visible on my screen, not sure why ..
Anyway, I used Logic Platinum 5.2.0 a lot in the past and remember many error messages through the years. Especially with newer Windows versions and PC's, although it did work on W7 eventually. 3rd party stuff caused more issues. But maybe this helps:
https://www.kvraudio.com/forum/viewtopic.php?t=51009
About testing, I'm not sure if using 5 will tell you a lot because we're already @ Logic X 10.5.1 which is different (better) in many ways. I whish I had made the switch earlier but I agree that it's a big step (financially and workflow wise). Started with L9 @ Mac btw. But if you make the switch at some point, my advice would be: always use the latest version. Besides liking old software, I can't think of any reasons to use 8 or 9, if that's even possible because the App store is always up-to-date.

 

I have same problem sometimes. I see something like broken icon instead of image.
I'm using Chrome. When I checked on Edge everything was fine.
What browser do You use?
Check this thread on other browsers like Microsoft Edge or Firefox or even Internet Explorer

 

try using windows compatibility mode

 

Firefox
I only see

 

I don't know why this happen but in Edge or Internet Explorer everything is fine.
Maybe it's a html5 problem

 

But the DVDs are still available second-hand on eBay.
L9 was the last of the DVD products before the online download came.
Logic user since '99.

 

Strange. If you haven't already succesfully opened Logic and set an external editor, I don't know what it thinks it is looking for!

 

Maybe You know where is Logic preference file? Or what is the name of it?

Few weeks ago I set external editor in Ableton. But this shouldn't affects other daws.

 

I wouldn't know where that .plist is on Windows, sorry.
I remember back around Logic 5 times we might have sometimes used Soundtrack as the external editor. But that was on Mac.
I wonder if Logic is somehow looking for it? But you have the Windows version, so...
But as I said, if you haven't already set it in Logic, I don't know why it would look for something that hasn't been set yet.

 

This is going to sound bizarre (it is) It will also sound like it's irrelevant (and it might be; sorry if that's true)
But it's worth a try (and worth knowing about anyway - so not a waste of time)

On the old Windows versions of Logic..
Logic registers its midi inputs and outputs in the win.ini file (find win.ini inside the main windows folder)
It's just a plain text file, edit it in notepad or similar.
This file is obviously about lots of other stuff - not just Logic, so edit it carefully! (make a backup first if you're nervous)

Somewhere in the win.ini file you will find a header like this
[Logic]

and under that header there will be lines for each of your midi devices
- separate items for midi inputs and midi outputs

One very troublesome device (sometimes) is Microsoft's GS Wavetable Synth
and sometimes it can help to just disable Logic's access to that device.

If you can see a line like this

[Logic]
MidiOut_Microsoft_GS_Wavetable_SW_Synth=7

then the '7' means Logic's output access to it is enabled

Change the '7' to a '0' and Logic's output access to it will be disabled

MidiOut_Microsoft_GS_Wavetable_Synth=0

You may ask "how on earth is this midi synth related to external sample editor?" I have no idea.
AND I make no promises that this will fix it
but I have sometimes (ages ago) seen this work and I really can't remember whether I convinced myself that this was the solution or not. IF it works for you please tell us - I would like to know.

Additional info...
You can of course take control of Logic's access to all your midi devices using this idea. (and sometime you will need to)

Midi inputs require '0' to be disabled and '1' to be enabled
Midi outputs require '0' to be disabled and '7' to be enabled

Good luck

 

Omg. I spent almost a month installing logic 5 on windows through bootcamp. What an adventure. I finally got it working on XP.

 

Yes. I have this file but there's no microsoft gs wavetable synth under Logic.

This is how it looks like:



I changed everything under Logic to = 0
But nothing happen.
I try to reset pc or add microsoft gs wavetable synth line

 

Interesting that Logic's failed launch has got as far as adding those midi lines for your midi devices
and not yet added the line for Microsoft's midi synth. I think that might be a hint about where the launch crashed.
You made a good choice to set all values to '0' while testing this.
Have you tried adding the following line manually to see what happens

MidiOut_Microsoft_GS_Wavetable_Synth=0

You don't need to reboot your pc after making changes to win.ini

 

I check win.ini file on Win 7 x64 where Logic is running
And there is no info about Logic.
I removed completly info about Logic from Windows 10 win.ini file but nothing happen.

 

But that might not solve it, because Logic will try again to rebuild that information
and will still bump into arguing with the Midi Synth.
Please try adding the line that I suggested so that Logic has an instruction telling it to explicitly ignore MSoft's Midi Synth.

Slightly more drastic might be....

- temporarily disabling that Midi Synth in Windows (just for testing).
something like...
Right click on Start and select Device Manager.
Click on View menu and click on Show hidden devices.
Expand Software devices.
Right click on Microsoft GS Wavetable Synth and select Disable device.

and
although probably not relevant, maybe physically disconnect all those other midi devices that showed up in your original version of win.ini

(gotta go, I'll catch up with your progress tomorrow; good luck)