Thanks a lot for replies and the video, it explains a lot. However, I'm not sure if you understood what I meant by "relative" fades: with this I mean that the cue should tell the picture to move 320 pixels to the left, regardless of what the original position is. so if the x-axis of the clip is currently at 1320, after the relative fade the clip will be at 1000. With the osc-cue in the previous post, the picture will first jump from 1320 to 0, then fade to -320.
Zoltans idea is good also, it could be simpler to keep as much possible inside Resolume. Sometimes though it seems that the "speed" settings is a bit tricky to work with, it would be easier if "speed" could be replaced with "fade time".
What I think I will do in my workflow, is to use the dashboard-controls, and remote-control that from Qlab using 1d fade.
Then I can tune the starting and end-point of the parameter using parameter controls in Resolume, use the OSC-command for the dashboard-controls, and always set the fade in Qlab with 0 starting value and 1 end value. This will also make programming in Qlab easier. For every automation there will only be the dashboard-cue, and I won't need to convert the values from a resolume-value to something between 0 and 1 (like was done in previous post) because the qlab-fade always goes from 0 to 1.