I've recently wanted to start getting into bld, I've watch a few of Eric's video's but have now started learning from badmephisto's 30min video.
I've watch the whole thing once but plan to again soon, I know the algs already (Except R, which I'll learn soon.) But I'm finding it really hard to memo everything. I'm planning on first using letter pairs according to colours for edges and possibly making stories for them (If anyone has words for the letter pairs that'd be great) then maybe just using numbers 1-8 for corners. How does this sound?
Letters will probably be easier to memorise than numbers, how are you planning on memorising the orientation of the corners with 8 numbers?
You may of already looked at the Summary and Explanation of Memory Methods thread, it's good.
 
I've recently wanted to start getting into bld, I've watch a few of Eric's video's but have now started learning from badmephisto's 30min video.
I've watch the whole thing once but plan to again soon, I know the algs already (Except R, which I'll learn soon.) But I'm finding it really hard to memo everything. I'm planning on first using letter pairs according to colours for edges and possibly making stories for them (If anyone has words for the letter pairs that'd be great) then maybe just using numbers 1-8 for corners. How does this sound?

Here is a list of letter pairs
 
Why do most people normally do corners first in BLD execution instead of edges?

Probably because they use audio loop for conrners. The "audio memory" is similar to a computer's cache memory in that it lasts for around 15 seconds and then it is gone. That's why they execute corners before the audio is forgoten.
I think it is more popular with corners because it is less info to memorize than edges.
 
Oh well thats what I thought thanks............I'm thinking of using audio for edges cause my letter edges suck...or maybe I'll make a letter pair list but I don't know if i'm that into BLD
 
I memo corners with letter pairs then edges with audio loop, exec corners, parity and edges, parity I memo it visually, it works great :D but my audio loop has something different: two As Es Is Os and Us, it makes it easier and is not too confusing if I give a hit voice in one of each vowel, It might be stupid but Im really proud of the idea and works great :D
 
I'm sure this has been asked and answered a bunch of time before.


Can someone/sometwo/three please link me to what they consider to be the best resource for learning BH corners? I'm been using byu's thread already and I like it, but I think I'd like to see the problem from a different angle.

Written or filmed, I don't have a preference for the medium. I'd rather not be linked to just a page of algs, though. (Unless you truly believe that to be the best resource.)

Cheers.
 
Hi, I'm learning Classic Pochmann for edges and I have a question about breaking cycles. In Badmephisto's video he says that you must memorize another piece instead of the one that goes in the buffer but in Joël van Noort's website he says you must shoot that piece somewhere else (when it's in the buffer position). Sorry about the lame question but I'm confused. BTW, does anyone know if Joël's webstie will be up again? I'm reading a Google caché version of it.
Thanks.
 
Hi, I'm learning Classic Pochmann for edges and I have a question about breaking cycles. In Badmephisto's video he says that you must memorize another piece instead of the one that goes in the buffer but in Joël van Noort's website he says you must shoot that piece somewhere else (when it's in the buffer position). Sorry about the lame question but I'm confused. BTW, does anyone know if Joël's webstie will be up again? I'm reading a Google caché version of it.
Thanks.

They are both right. When you break a new cycle, you memo a position that does not have a solved edge, then the edges that is in that position and do the rest normally.

Hope that helps.
 
Well I decided to do corners first and then edges, and I've already found out the parity for that by watching a random tutorial.
 
I dont know what's that way but if you had parity you could do M2 L' U' L U M2 U' L' U L M2- first edge
 
What's a good success rate to shoot for?

Also, whenever I go slower to make sure I get the memo perfect, I end up with a slower time (obviously). But if I rush, then I would get a great time in the off-chance that I actually do finish the solve. So in practice, do you guys recommend going slowly, rushing, or some type of mixture? So far, I've just been practicing different components of the solve/memo at a time.
 
I have improved a lot by risking like crazy, I think is good to risk to get a goal and then dont risk anymore to look for a bigger succes rate, if you have a comp or something
 
Last edited by a moderator:
Back
Top