Comment 5 for bug 1101907

I am not sure if we can afford an other thread between GUI and Engine priority.
This will just introduce probably unnecessary tread switches and overhead for syncing.

Actually there is no difference between the Human DJ using the GUI and the AutoDJ.
This mean if AutoDJ is looked out, a human DJ will be looked out as well, which Is at least as worse.
AutoDj makes also use of the database, which is still running in the GUI thread.

It is best to solve the root bug and remove the SQlite access from the GUI

Of cuase we should make the transitions independent from deck transport.
Maybe we can move some of the Audto DJ transaction process to the engine thread.
Remember that we have planed to support different transaction effects.
Not sure what will be the right architecture for it, but maybe we can utilize the Quick Effect rack and have the transaction effects also available without AutoDJ.