Thanks! I can confirm it works. Interesting to see this in action, in any case. I'll have to play more with it to see how I'll use it in practise. No time right now but winter is coming...
Edit: Just as I was writing the above, I thought of something. I recently composed a somewhat longer track directly in asm. As I went along, I found myself relying more and more on macros, up to a point where almost the entire track was completely macro-ized. Now, I could definitely imagine using reference blocks in a similar fashion, ie. create a "fake" kick or whatever, give that a name, then improve it later on and use Ctrl-Shift-P to update all the occurances.
However, there are two problems with this. First of all, I've been using a lot of parametric macros as well, eg. for a variable starting pitch on a kick. This could work with the block ref system if a ref update would (optionally) ignore all data in the child blocks that do not match the parent.
The second problem is more serious. Basically, I wouldn't want to create a seperate block for each kick in the track - that would completely defeat the main purpose that blocks currently serve, which is quick navigation and easy copy/pasting of song sections. So basically this would require ref blocks to be a separate thing from the current block sections.
Well, just throwing out some ideas here, obviously nothing really thought out.