<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b9e69a4b8c324fc9a97bac7b5e27668e&quot; frameborder=&quot;0&quot; width=&quot;1784&quot; height=&quot;1338&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1338</height><width>1784</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1338</thumbnail_height><thumbnail_width>1784</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b9e69a4b8c324fc9a97bac7b5e27668e-a275bbd8e04413ca.gif</thumbnail_url><duration>42.165</duration><title>Cracking Wacky Dream Theater Coding Timing</title><description>This Loom discusses why a piece of music sounds like it is coming in on the upbeat or on the two, creating confusion about the timing. The speaker mentions using “wacky code” in Dream Theater, where you crack it and then modify it further later. They note that the issue is compounded by the other person playing a polyphonic chord. Overall, the Loom focuses on the difficulty of interpreting the rhythmic entry and harmony due to the chord texture.</description></oembed>