The Y/S driver is a peer to peer type only driver and therefore each hardware device even if chained together, the communication is still being treated separately by the computer to each device. If the Y/S driver became networkable - e.g. work under the same concept as mLAN does, then any devices chained together would be visable inside a mLAN network and no longer be working as peer to peer with the computer. This means that routing can then be shared across each device held within the mLAN network.
mLAN development has now unfortunetly ceased, so unless this concept is ressurected cannot ever see the monitoring issue on the MR units being resolved? It will probably be also expensive to back track the software to make it work using mLAN drivers.
I never understood Yamaha's decision to move off from mLAN especially when all of the initial mLAN driver problems finally got resolved on both Mac and PC /win XP.
If we did have current mLAN drivers on W7 x64 and Mac SL then confident the N12 and MR's could potentially work that way. (Remember that the N12 originally worked under a mLAN driver anyway and then you had to flash it to the Y/S driver with no going back to mLAN - so this proves it can theoretically be done.) There are no mlan drivers for W7 or Mac OSx SL which is why N12 users have to ditch mLAN and move to the Y/S drivers as peer to peer.
PC i7-930, 6GB ram, Gigabyte EX58 UD5, W7x64, Cubase 7, Wavelab 7, Yamaha n12, Yamaha KX-61, Steinberg MR816x, CC121, CMC-PD, CMC FD, Universal Audio UAD1x2 +UAD2Solo, Line 6 Pod XT 2.0 Yamaha HS80monitors, Rode K2, NT2A, NT1A
IK Multimedia Software Synths, Native Instruments Komplete, EastWest Play VOP, Gypsy and Fab Four.
(Yamaha AW2400+mlan16, Fostex X-26, Tascam 488mk2)