M4L 7 not loading editor. period. Not sure what to do?
Ok This just started today.
I have Max for live 7 for ableton live 9 version 2.1 32x bit.
I find it odd how out of no where. I'll hit the editor icon on any m4l device and it won't open the editor just leave me starting up M4L then the tab will turn off.
I fount only two related forums neither were any help, because I thought it was the permissions. Checked that out and it's all correct all are running as admin on my windows 10 now. Not sure if it's my OS update from windows 8.2 to 10 or it's that I had to uninstall live 64 bit and the editor worked fine there, but I had to reinstall the 32x bit, but including M4L 7 from uninstalling the 64 to 32 bit version. I know it was working a bit fine, like not even a month ago then all of a sudden now I can't open it.
I don't know I'm out of options.
I hope anyone has a clue what's going on. :( I was hoping to make devices, but I guess not until this is fixed.
Would a reinstall of Max 7 fix this?
Windows 10 user as well, having the same issue. Both Max 6 and 7 will not start up, period. Clean install of Windows 10, Max 6 and 7 clean installs, won't even go into demo mode on Max 6.
Max 6.x users please try and get things going by installing the ilok license manager software from ilok.com
This will update your Pace drivers.
Windows 10 Max 7 users please check firewalls and security settings.
If you 're not having any luck at all, please get in touch with support.
So far in our testing, everything is working fine with Max 6, 7, MFL and Windows 10.
Cheers
I'm not convinced that's the case. I have a theory this has to do with compatibility settings. Still working through some tests of my own, and I will check in once I have managed a solution.
I had the same issue - Win 8.1, 64-bit Live Suite and Max 7.
I uninstalled Max, Live and Pace iLoc, rebooted. Reinstalled Live 64, tested. Reinstalled Max 7. Could not open Max 4 Live.
Changed the compatibility settings for both Live and Max to run as Administrator, and Max 4 Live editing now works correctly.
Simon
I concur. For myself, there's been a development as I've been fiddling around. I have a M-Audio Delta 44 card, on which Windows has WDM drivers for the devices Line 1&2, Line 3&4 and Multichannel. The ASIO drivers, I can pretty much pick what I want. Previously, I had 1&2 assigned as the default playback, and the WDM drivers would get knocked out and not grab the devices again, even after a restart. I would have to reinstall the driver or hit the "reset" button on the Delta Control Panel, which I think just gives the hardware and drivers a kick in the pants. Well, after assigning Multichannel as the default playback, the WDM drivers seem to work somewhat better and would work along the ASIO drivers while Ableton was running. After doing this, Max for Live is now running without a problem for me. I think it was Andrew helping me (thanks again), so I thought I would provide an update here for others who may be experiencing the same.
Did a Win 10 clean install, installed both x32 and x64 Max7.0.5 and both editions didn't start.
Ran the compatibility troubleshooter and put both to run in Win8 compatibility. Both editions now run perfectly.
So as the result of a very quick-n-dirty analysis of some crash reports, it looks like the portaudio driver may be causing some problems under Windows 10. Here's the ticket on the portaudio Assembla site.
So maybe try removing C:\Program Files\Cycling '74\Max 7\resources\externals\ad\ad_portaudio.mxe[64] to see if Max starts properly. I'd like to reiterate that this is just a wild guess at this stage, but it's an informed wild guess, and we'd like to get you up and running ASAP. Thanks for getting back and letting us know.
So having it all working fine since Aug 21, I decided to update the NVidia video card drivers on my laptop (to allow the opportunity to play with CUDA bassed FFT).
After the update, my Max4Live editing no longer works. Unless I get some better ideas, it looks like I may be reinstalling again. I may as well upgrade to Windows 10 first.
Simon
And following an upgrade to Windows 10, I had to uninstall Max and Ableton, and completely reinstall them both. But it is now working.
How long for, I don't know.
Simon
According to support, these problems have, so far, been traceable to outdated hardware drivers. Obviously, portaudio/Max should not crash in this case (as the ticket above indicates, there is apparently a problem with portaudio under Win10), but carefully ensuring that all of your audio hardware is running the latest software available will probably eliminate the issue.
After updating to Windows 10 Max and M4l don't start. two messages appear about missing two DLL files: M:
Dependency MFPlat.DLL is missing
And
Dependency MFREADWRITE.DLL is missing.
I looked around the web and found some suggestions for fixing the problem: to install the Windows Media pack and DirectX latest update (I am on windows N version which doesn't come with media packs installed and it seems after the update to win10 they got uninstalled once again), I installed both but I still can't start M4L or Max standalone. I unistalled and reinstalled Max also, the problem persists.
i already went through Ableton Support and redirecto to Cycling, I already started a ticket but was wondering if anyone here knows about another fix.
I can't make a clean install of windows since I have a couple of elicenser products and I don't have the USB dongle, I would lsot my licenses if I made a clean install.
I ahve not tried to reinstall Live but I doubt it is the problem.
Thanks!
Just to clarify: did you install this Media Feature Pack? https://www.microsoft.com/en-US/download/details.aspx?id=49919
It appears that some features are disabled in the N versions, even with the Media Feature Pack installed (https://support.microsoft.com/en-us/kb/3099229). I am not sure if Max relies on them offhand (nothing pops out at me).
I see that we don't specify that a non-N version is required on Windows, although a media-feature-free version of Windows is likely not the best basis for a media manipulation environment. Please let us know if that above MFP (1511) helps with the problem -- if not, please contact support.