I could have also added in this post that I see no way in colorsync to specify the CMM, either, but in trying to diagnose my problem I did run PS set to the Apple CMM in order to check whether that was causing the difference between "adobe manages color" and the "printer manages color" output. The difference is so big that I doubted it could be due to choice of CMM, and printing from PS with relCol rather than perceptual rendering made the match between the two printing pathways, so that seems to be the underlying issue. I just can't figure out how to wrench control of the rendering intent option away from the "printer manages color" colorsync workflow.
Again ColorThink has provisions to edit the profile for a preferred CMM so in theory, you could select ACE and in theory get BPC but I have no idea if that would work. But the bigger issue here is probably
Printer Manages Color in your case (and in many other cases) ain’t working. I’m under the impression that the app, driver and OS all have to behave correctly for this to work. Even when its “right” I have no idea if you’d get identical results as
Application Manages Color. It would not surprise me in the least if that were not the case. I suspect that is why so many make the suggestion not to use
Printer Manages Color except in the rare case where
App Manages Color doesn’t work. Odd is it seems, I’ve seen a few isolated cases where
App Manages Color simply will not work no matter how much trouble shooting one attempts and at that point,
Printer Manages Color works or is at least the only viable fix. Yes, its a huge stinky pile of dog doo.