it's not Ableton's responsibility to keep up with every rinky dink driver that company X, Y, or Z release to control their device. a large portion of the time (such as with Logitech mouse drivers) no third party driver is needed. the OS happens to be "aware" enough of simple pointing devices.Machinesworking wrote:Well in the case that they know there's an incompatibility and do not make it known, or do not inform all their tech support people, then yeah, they get some blame for it.H20nly wrote:^ +1 certain Logitech webcam drivers have been known to wreak havoc with audio as well...
... which is obviously Ableton's fault.
i recently had a hard drive fail on one of my computers... this too, was clearly a result of poor planning by Ableton.
Not all incompatibility issues that affect only one manufacturer are that manufacturers fault.
I guess the best example I can think of is MOTU and DP, when DP adopted Audio Units over continuing to press developers to develop their own MAS plug in standard, they coded their host support for AU absolutely to spec, and because Apple had in the meantime tweaked the AU plug in developer code to get Logic to behave properly with AU, DP had issues with some AU plug ins. Not at all MOTU's fault.
so to be clear... YES, i was being sarcastic when i said:
but was dead serious when i said:H20nly wrote:... which is obviously Ableton's fault.
i recently had a hard drive fail on one of my computers... this too, was clearly a result of poor planning by Ableton.
how do i know this?? because i found out the hard way... when i went combing through the far corners of the internet i found some lines of text supporting the theory... when i tried this left field solution it solved my issue. i passed the info on to someone else and "ta dah!" it helped them too.H20nly wrote:certain Logitech webcam drivers have been known to wreak havoc with audio as well...
from a technical standpoint you have to draw a line in the sand and divide the data into known/good and unknown/bad... Ableton staff should be working on software features that have to do with their DAW application and not have to have an 'Other Devices Liaison' and a team to test every camera, printer, pointing device, cell phone, media player, scanner, card reader, usb stick, children's toy, doo, dad, and hunk of shit that happens to have a USB connector sucking juice from their customer's personal computers.
again, Ableton cannot possibly cover every thing someone can throw at their computer... at some point keeping a computer in order has to be the responsibility of its owner. people want to blame someone else though... so to top it off with a car analogy; they have to be forced to check the emissions on their vehicle, because if left up to them, that black smoke coming from the tail pipe is simply something they leave behind them while they chug on blindly, bare knuckled, gripping the wheel, and slamming the gas to get wherever it is they think they are taking themselves with no regard or sense of ownership as it pertains to the vehicle/means by which they travel.
check your own engine.