New Method: Pairing First 8 Edges

[legoanimate98]

I wonder if the ability to place the four cross edges on L would save a couple of seconds in the 3x3 stage.

I was thinking the same thing. It could become a new popular method because it could give an advantage similar to the one you get from yau. I think I am going to practice this for a while and see if I can do at least as well as I usually do with normal redux.

 

[Emily Wang]

This is a pretty interesting method. It does seem easy. I wonder if the ability to place the four cross edges on L would save a couple of seconds in the 3x3 stage.

Last four edges would mess it up, unless you make sure to preserve position and orientation of the white edges, which would probably(?) negate any time saved.

Edit: tried a solve (2:44). Someone better at m slice pairing should probably try this out for speed. Either way it seems to be a viable beginners edge pairing. (Have you tried this out on cube sim, Michael? That would probably give everyone a better idea of the upper limit speed wise of this; after trying it, I really don't think it's as fast as free slice, but I might be wrong)

 

[CarlBrannen]

I've been using this method for the last year, but I do all 12 edges this way. I set the world record for 7x7x7 for ages 54+ using it.

Here's my youtube on the technique from October:
https://www.youtube.com/watch?v=pVVvfKVgkqc

A difference is that I orient the edges the other way. I think the way you do it is better and I may try to switch.

As I solve the second set of 4 edges, I keep count of the orientation "parity" of the last 4 edges. Then I orient the last 4 edges using this information. This means that the "PL4E" algorithms are vastly reduced in number, I only know two algorithms.

 

[stoic]

Just got round to trying this since it was posted, and although I'm pretty noobish at 5x5 I think it's quite cool.
At first, I struggled a bit making tredges on the M slice, so I switched it around to the E slice and it seems to suit me better as that's what I'm used to.
I especially like that its easy to restore centres after the first 8 tredges.
Gonna give it a try on bigger cubes next...

 

[masterofthebass]

This is similar to how I go about solving edges. I've been doing white->yellow for at least 3 years now and what helps me lookahead is keeping the orientation of white stickers similar so that I'm always just looking for white stickers and insert them into the pairing layer in a way that there's always pieces to pair up. I don't go so far to restrict myself to specifics like you do, but the concept of looking for white stickers still applies.

http://www.speedsolving.com/forum/showthread.php?4624-5x5x5-Move-Count

shows typical averages even several years ago were well under 100 moves for all 12 edges; this method seems to be around 100 for just the first 8. (Last 4 probably runs somewhere in the 20-25 range?) So it seems this is pretty high on move count.

you didn't quite scroll down to Jon Choi's post did you

EFi 58 64 68 55 51

Those were his first 8 edges counts.

 

[Mike Hughey]

Wow, his last 4 edges were a lot more moves than I would have thought, but I guess it doesn't matter all that much since you tend to get good at those algs?

Anyway, I do remember watching your video for how you do white->yellow, and it got me to try freeslice for a while again. (I tried it for a while again, but still never got any good at it. ) It's true - it's kind of like this method in terms of searching for pieces, but move-optimized, unlike this method.

 

[Pyjam]

I don't now if it's "new".

If I understand the method correctly, this is what I do for two years.
I exposed the method here.

At this time, nobody cares.

I started by orienting the first 8 edges then I realized that it's better to only orient the first 4, and to orient the next 4 while pairing the last 4.