I have to say that I don't often feel the need for a blipless join; when working with two colours, it's easy to put the blip at the back. And in some patterns it can even look pretty as a design element. I can't say, therefore, that I have spent a lot of time avoiding the blip!
When working Jane's join though, it got me thinking and wondering whether it could be done differently. Basically, what happens in the blipless join is that there is an extra thread at the back which covers the small bit of thread of a different colour.
I actually came up with two different ways of doing the join and made a video for the one I preferred.
The other caveat is that whether with Jane's method or with mine, there is a bit of a tiny bump going on due to the extra thread which you don't have with a regular join. I don't see how this could be avoided completely - but I'm always prepared to be put right if someone knows another way!
Here are photos.
My way, blipless join from the front
My way, blipless join from the back
Jane's way, blipless from the front
Jane's way, blipless from the back
Examining carefully, there appears to be a bit of extra thickness from the thread showing on the inside curve of the ring when using Jane's method and also, the picot is twisting a little. A little line showing horizontally on the front is visible using both methods. I'm pulling hairs here but just trying to study the differences.
I've just uploaded a video that shows how I do the blipless join my way. And I will also make one that shows Jane's method. Then you can choose which you prefer!
How about you, do you find you use (or would use) a blipless join often? I also discovered a new join which I didn't know about: the smooth join - do you know it? And I played again with the Lark's Head join which is very nice indeed (though it does not avoid the colour blip) in that it looks like a double stitch so is practically invisible... apart from the fact that it adds a double stitch to your count and the whole of this stitch sits inside the picot join... but that's another story... for another day!