OS X 10.8.2 update - all working ok so far

[andynormancx]

Originally Posted by Wim

It's good that it looks like Apple have addressed some of the issues we have been working on. A summary of our plans for releasing a new driver are summarised here:

Your plans to fix the problem involve us all not using the products we bought for yet another 3 months, at least.

It really seems like there is little urgency from DL to get this problem fixed. Unless you are just waiting on Apple to fix something, why exactly is there a three month delay between now and when you think the problem will be fixed ?

Is there still development effort involved in fixing the problem or is the three months some sort of extended QA period ?

As a software developer myself I don't understand how you can be sure that you already know how to fix the problem AND you know it is going to take AT LEAST 3 months to fix.

[Wim]

We are working on a Mac 2.0 software release which uses our latest core code and to write a new interface to the Mac Operating system. This involves writing new Mac virtual graphics drivers, device detection, USB video driver, audio driver and Ethernet driver. And making sure that our latest video encoder works efficiently on a Mac. That's quite a lot of work.

Once we have the new architecture, the core code gives us much more flexibility to workaround bugs found in the Apple OSX, if Apple does not address them.

With V1.8 release and older, it is getting harder to try and address a problem without breaking something else in the code. This is why V1.8 is on "life support" and you're not seeing a lot of updates.

We're trying to address the most critical bugs to make sure you can still use USB 2.0 devices. But rather than sinking more of the engineering team's time into this code stream, we want to get v2.0 out as soon as possible, as it will give the best long term solution.

Wim

[cmwade77]

Originally Posted by Wim

We are working on a Mac 2.0 software release which uses our latest core code and to write a new interface to the Mac Operating system. This involves writing new Mac virtual graphics drivers, device detection, USB video driver, audio driver and Ethernet driver. And making sure that our latest video encoder works efficiently on a Mac. That's quite a lot of work.

Once we have the new architecture, the core code gives us much more flexibility to workaround bugs found in the Apple OSX, if Apple does not address them.

With V1.8 release and older, it is getting harder to try and address a problem without breaking something else in the code. This is why V1.8 is on "life support" and you're not seeing a lot of updates.

We're trying to address the most critical bugs to make sure you can still use USB 2.0 devices. But rather than sinking more of the engineering team's time into this code stream, we want to get v2.0 out as soon as possible, as it will give the best long term solution.

Wim

Sounds like all work needs to stop on 2.0 until you can get 1.8.1 out, get it out the door, get everyone back up and running, then resume work on 2.0, leaving one or 2 people to work on problems in 1.8.1 for a week or two and the completely ignore it, focusing solely on 2.0.

[andynormancx]

That's great, I guess. But in the meantime I and many others are sat staring at useless blank screens for another 3 months or more.

If it really is going to be another 3+ months I'll have to go and find another solution, I can't work without my second external monitor for much longer. It won't unfortunately be a DL based product of course

It isn't as if we are talking about a discontinued product here, the non functioning adapter I own is still on sale to unsuspecting customers who are going to get a shock when it doesn't work with the latest version of OSX. I note that the driver download page makes no mention of the Mountain Lion problems.

[GodwinC]

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

[andynormancx]

Originally Posted by GodwinC

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

When my DisplayLink driver is causing problems there is no screen saver or power save involved. It can sometimes be in its broken state immediately after booting for the first time after installing it.

[GodwinC]

In that case, make sure DMProxy is loading correctly when you plug it in.. it should say something like, I also find some microUSB cables are junk:

2012-10-04 10:06:20.214 AM WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
2012-10-04 10:06:20.270 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.271 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.272 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.272 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.273 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.274 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.275 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.276 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.276 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.334 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.334 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.335 AM WindowServer[80]: Display 0x04273740: MappedDisplay Unit 0; ColorProfile { 2, "iMac"}; TransferTable (256, 3)
2012-10-04 10:06:20.335 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.336 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.336 AM WindowServer[80]: Display 0x2b34488d: MappedDisplay Unit 1; ColorProfile { 3, "DELL U2212HM"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.337 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.337 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)
2012-10-04 10:06:20.338 AM WindowServer[80]: Display 0x2b38400f: MappedDisplay Unit 3; ColorProfile { 4, "DELL 2005FPW"}; TransferFormula (1.000000, 1.000000, 1.000000)

Originally Posted by andynormancx

When my DisplayLink driver is causing problems there is no screen saver or power save involved. It can sometimes be in its broken state immediately after booting for the first time after installing it.

[cmwade77]

Originally Posted by GodwinC

I think the key is if using Displaylink.. don't ever let the machine goes to screen saver / power save..

Mine had gone to power save just fine all the time using the work around I posted earlier, but did not always work on boot, which is why we have gone over to the J5 Create devices with Mountain Lion systems for now, we have two other systems that we want to upgrade, but are trying to wait for the DisplayLink drivers.

3 Months will not work for our time frame that we want to upgrade within, ideally we would like to have this done by the end of next week, which means we need time to test the drivers on one system today or Monday, at the latest.