Yamaha Studio Manager & El Capitan No Workie!!

Re: Yamaha Studio Manager & El Capitan No Workie!!

I'm not a Mac guy - does OSX have any sort of "compatibility mode" that allows a program to think it's working in an older version of the OS? I just use my MacBook for testing stuff and don't have a timemachine backup of the previous OS. :-(
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Yea, I try to be the last kid on the block to upgrade the OS on my Macs unless some mission critical program demands it and even then I maintain another machine or even just a separate drive partition with the last "known to work " OS version. A hard lesson learned after 28 years of running Macs.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

The last time something like this happened (on Mavericks, I believe) it simply required re-installation of the most current SM version and re-installation of the necessary console modules. Apparently various necessary stuff in the OS had moved and a re-install was need to re-establish the links.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

The issue appears to be El Capitan's new System Integrity Protection which prevents writes to /usr/lib (as well as other directories) unless the installer is signed by Apple. I was able to get Studio Manager and the M7 and LS9 editors to install and run by disabling SIP and reinstalling. I then ran Studio Manager, then reenabled SIP.

I did NOT need to copy library files or rename them (as suggested here: Yamaha Studio Manager with El Captain | Apple Support Communities )
so it appears the Studio Manager does the necessary copies that are required (when SIP is disabled).

I no longer have an M7 or LS9 to see if it actually controls the console. Maybe someone else can test this.


Read about disabling/enabling SIP here: Configuring System Integrity Protection

Read more about SIP and why disabling it isn't the best idea here: How to turn off system integrity protection on OS X (but don't) | iMore
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

There has been a version of this as far back as OS10.8 that would refuse to run installers not signed by Apple but the system would throw up a dialog explaining why it wasn't willing to proceed with the install. There is the option in 10.8 to disable that check entirely and "trust" everything. Sounds like Apple has torqued that function down even further putting more onus on the developers to pony up the programming time, effort and fees required to do it the Apple way.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Riley Casey said:
There has been a version of this as far back as OS10.8 that would refuse to run installers not signed by Apple but the system would throw up a dialog explaining why it wasn't willing to proceed with the install. There is the option in 10.8 to disable that check entirely and "trust" everything. Sounds like Apple has torqued that function down even further putting more onus on the developers to pony up the programming time, effort and fees required to do it the Apple way.
Click to expand...

Could also be that at the core of SM is some of the worst and most poorly-designed code ever. It's always been a half-done port from Windows and frankly I'm glad to see Apple exerting some control over who can write where in the deeper reaches of the OS.

I'm so happy Yamaha put this (and MIDI-over-IP) behind them when they began designing the CL and QL series.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Kevin Windrem said:
The issue appears to be El Capitan's new System Integrity Protection which prevents writes to /usr/lib (as well as other directories) unless the installer is signed by Apple. I was able to get Studio Manager and the M7 and LS9 editors to install and run by disabling SIP and reinstalling. I then ran Studio Manager, then reenabled SIP.

I did NOT need to copy library files or rename them (as suggested here: Yamaha Studio Manager with El Captain | Apple Support Communities )
so it appears the Studio Manager does the necessary copies that are required (when SIP is disabled).

I no longer have an M7 or LS9 to see if it actually controls the console. Maybe someone else can test this.
Click to expand...

You're a genius!!

It seems to be working, at least SM is sending and receiving MIDI. I haven't tested it with a console but I'm certian it will work fine.
Thank you so much for finding the answer and posting here. Amazing that Yamaha still hasn't fixed this after all these months.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Yamaha telegraphs pretty clearly that writing software to interact with third party information devices is not a high priority. Just the bare minimum to look appealing in the advertising. How hard is to get a computer to spit out tab text files of text information ?

Andrew Broughton said:
You're a genius!!

... Amazing that Yamaha still hasn't fixed this after all these months.
Click to expand...
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Milt Hathaway said:
I'm so happy Yamaha put this (and MIDI-over-IP) behind them when they began designing the CL and QL series.
Click to expand...
Actually, they didn't. They just created their own MIDI-Over-IP protocol for the CL/QL. Took me over a year to figure it's internals, but it's definitely still MIDI information, just delivered in a proprietary way. IMHO, what they should have done was embrace RTP-MIDI which is native to OSX and available as a free driver for Windows. Following standards and all that...
Yamaha for a long time was only company that truly embraced remote control with documented messaging for pretty much every control on the surface. The X32/M32 have gone further, with more dedicated apps and OSC support, but other companies are still way behind on this.

Without Yamaha's MIDI support, I never would have been able to do all the crazy stuff that I can do with the Yamaha consoles. Thanks to Kevin I can now do this on OSX!!

[video=youtube_share;Hisyhjr6-mk]https://youtu.be/Hisyhjr6-mk[/video]
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Andy, I do use your Yammie Patch list program / utility / app / whatever on a regular basis now. If the thread on your forum weren't locked I would heap effusive praise on. This even despite the fact that it means starting up windows to run it ::/ . You are are an exemplary, upstanding, public spirited citizen for having written this software - all of it. None of which gets Yamaha off the hook for dropping the ball on making the software that supports their ever increasingly complex consoles more usable for their client base by including functions as simple as text list exports.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

I hear your frustration. I've ranted on and on about how Yamaha will add features on newer consoles but then they always take something away as well. There's no console that has all the best features of the Yamaha desks.

If the thread on your forum weren't locked I would heap effusive praise on.
Click to expand...
The threads with the software are typically locked so that I can just put release notes in the thread without getting it muddied up with lavish praise posts. ;-)
Nothing stopping you from starting a new thread, though. I'm just glad to hear you find it useful.

This even despite the fact that it means starting up windows to run it
Click to expand...
I have it working on OSX via Wine. It's ugly but it does work. I've been working with WineSkin to try and create a standalone app but I'm still struggling as I'm somewhat lost on the Mac.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

Kevin Windrem said:
The issue appears to be El Capitan's new System Integrity Protection which prevents writes to /usr/lib (as well as other directories) unless the installer is signed by Apple. I was able to get Studio Manager and the M7 and LS9 editors to install and run by disabling SIP and reinstalling. I then ran Studio Manager, then reenabled SIP.

I did NOT need to copy library files or rename them (as suggested here: Yamaha Studio Manager with El Captain | Apple Support Communities )
so it appears the Studio Manager does the necessary copies that are required (when SIP is disabled).

I no longer have an M7 or LS9 to see if it actually controls the console. Maybe someone else can test this.


Read about disabling/enabling SIP here: Configuring System Integrity Protection

Read more about SIP and why disabling it isn't the best idea here: How to turn off system integrity protection on OS X (but don't) | iMore
Click to expand...
I confirmed today that Studio Manager does work when installed using my procedure above, at least with the M7.

Remember to configure the DME-N control panel (System Prefs) first BEFORE launching Studio Manager.

Then in Studio Manager Preferences, select the MIDI ports you want to use in your workspace (you can run multiple editors even of the same model, but I've found you should only enable the ports you intend to use since Studio Manager takes over the ports and prevents other instances (including the iPad) from using those ports.

Finally, select the input and output ports under File/System Setup in the console's Editor.
 
Re: Yamaha Studio Manager & El Capitan No Workie!!

I confirmed that Studio Manager does work when installed using the procedure below, at least with the M7.

1) Download Studio Manager, DME-N and any console editors, but don't install at this time.

2) Restart in Recovery Mode (hold Cmd-R while restarting the computer)

3) Open Terminal

4) Disable SIP: csrutil disable

5) Restarat in normal mode

6) Run the installers

7) Run Studio Manager and all the editors once. You can configure later (or now if you prefer). At this point, the editors will probably NOT connect to the console. This step is essential since apparently, library files are copied to /usr/lib when SM and the editor(s) first run. Writes to /usr/lib can only be performed with SIP disabled.

8) Restart in Recovery Mode (hold Cmd-R while restarting the computer) again

9) Enable SIP: csrutil enable

10) Restarat in normal mode

11) Configure DME-N (in System Preferences) if you have not done so previously. Any DME-N configuration changes won't be seen by Studio Manager if it is running. Quit and restart Studio Manager AFTER configuring DME-N.

12) Launch Studio Manager, then In it's Preferences, select the MIDI ports you want to use in your workspace.

13) Finally, select the input and output ports under File/System Setup in the(each) console's Editor(s). Closing the setup dialog should connect to the console if configuration settings are all correct and the console network is configured correctly and the laptop and console are connected to the network.
 
Top Bottom