Photoaster
Metricks is a diverse artist with a broad body of work, all of which displa… Read Full Bio ↴Metricks is a diverse artist with a broad body of work, all of which displays a high degree of originality and quality music production. His aproach to music is diverse and expansive, nevertheless there is always a blueprint of unique personal expression and emotion present.

Metricks is native to Lisboa (Lisbon, Portugal), a city of multi racial crossovers of cultures and people, and of course of different music, and musical sensibilities.

Metricks works with great artists like Daniel Iorio, Stuart Elliott, Phrulex, Renato Ventura, Mario Raposo, JDVoid, SoundFreak, Lisa T, Rakur, Pio Pio, GaiaBeat, Pixieguts and Dead Men Talking

The work of Metricks was nominee in four editions of the Internet Online Music Awards (IOMA). In 2004 he reached the final five in Best Electronic Artist, Best Producer and Best Composer.

In the 2005 Edition Metricks won the "Best Electronic Artist". In 2006, the track "Memoire des Temps Perdu" received the IOMA award for "Best Instrumental Soundtrack". See the Ioma hall of Fame.

The work of Metricks was also used in two films, "High Octane - OverBoost" and "High Octane - Detonate" from New Zealand Production Company, High Octane.
TRACKS
Genre not found
Artist not found
Album not found
Search results not found
Song not found

Photoaster
Metricks Lyrics


No lyrics text found for this track.

The lyrics are frequently found in the comments by searching or by filtering for lyric videos
Comments from YouTube:

@ryoonio

Appreciate the more frequent uploads lately! This series and the space invaders game have been great to watch. And great progress in a short period of time.

@namr2000

Thanks for putting these streams up, they''re giving me motivation to do my own weekend projects.

@Guyflyer12

Has Jon talked about the whole `codex` and memory profiler thing? Besides just the visualization but the under the hood stuff?

@Paul-to1nb

This was an extremely fun stream. Thank you for uploading!

@Adamarla

The algorithm in the original paper picks packing to rows or columns based on aspect ratio rather than toggling. That reduces the thin rectangles as it allows them to be packed in the other direction. I waited until finishing watching everything before pointing this out in case it was already fixed on stream.

@Pangeli70

I followed the entire series, really cool. Enjoyed all the development cycle, from the beginning to the end. With all the decisions and bug hunting and testing and experimenting in a real project. I have so many ideas to improve the tool. On the UI part, there are so many things that could be done. If it could be integrated with a text viewer or text editor, you could maybe control-click on a function and jump directly into the file and look at it for immediate investigation. Or maybe you can shift-click and list all the modules where the function is used or where all the polymorphs are declared. Right-click could open a context menu for quick contextualized operations. I'd try to remove entirely the bottom area of the UI to expand the treemap and I'd show a tooltip under the cursor while you move it so you don't have to read in a different position where the cursor is. Clicking on the file cursor could pop up a window that shows the function's metrics in detail.
Another cool thing to add would be an AST per metric visualizer of the function to display how these are collected.
Adding this tool to a profiler can allow us to watch how the behaviour of the program evolves at runtime. And combing codex data with profiler data could help join code complexity metrics with real usage metrics to visually identify bottlenecks and areas where to push hard till reaching the metal to squeeze out the performance.
AST patterns and Codex metrics could be used to identify and visualize antipatterns, or obsolete syntax and aim at the areas that need refactoring. So many ideas. Maybe someone useful. :)

@Protoex

There is a very easy to fix bug to improve squareness.

Instead of alternating between horizontal/vertical layout, decide it based on the aspect ratio of the remaining free rectangle.
At some point in part one, it seems like you got the idea, but as complexity spiraled out, you make it alternating and never fixed back

@jblow888

Have you actually tried this and compared to see if it is better?

@JeffHanke

@@jblow888 I haven't, but it should reduce the number of rects that get squashed in the upper-right corner of parent rects that start out with an aspect far away from 1. When packing squarish rects into columns/rows and always alternating between them, the remaining space's aspect ratio will trend away from 1.

Imagine starting with 200x100 (aspect ratio 2), you pack a column of 10x10, and a row of 10x10, you're left with 190x90 (aspect ratio 2.11), if you pack another column & row of 9x9s, you end up with 181x81 (aspect 2.23), etc. Subtracting approximately equal values from both the width and height will push the aspect ratio father and farther from 1.

With the proposed change, you'd pack a column of 10x10s, end up with 190x100 (aspect ratio 1.9), see it's above 1 still, pack another column of 10x10s, end up with 180, etc, until you get down around 100x100 (aspect ratio 1) and then (most likely) start switching back and forth.

Without trying it myself, I can't be sure that the packed rects will be more square, but the remaining space will certainly be more square, and I think that will end up giving you more rects that are close to square.

@Protoex

@jblow888  sorry I haven't. Do I get beta access to the compiler if it get improved?

More Comments

More Versions