Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 576

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 593

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 687

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/18/d69630753/htdocs/home/wp/wp-includes/classes.php on line 710

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/18/d69630753/htdocs/home/wp/wp-includes/wp-db.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/18/d69630753/htdocs/home/wp/wp-includes/cache.php on line 99

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/18/d69630753/htdocs/home/wp/wp-includes/cache.php on line 404

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/18/d69630753/htdocs/home/wp/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/18/d69630753/htdocs/home/wp/wp-includes/theme.php on line 576

Warning: Creating default object from empty value in /homepages/18/d69630753/htdocs/home/wp/wp-includes/update.php on line 39

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 932

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 933
roglok.net → Text
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 932

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 933

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 932

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 933

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 932

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/kses.php on line 933

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Best Before – A Dsico Fanzine


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-content/plugins/wp-lightbox2/wp-lightbox2.php on line 40

Manuel Bürger, Tracky Birthday, Konrad Kuhn and I teamed up to create “Best before - A Dsico Fanzine”.

The fanzine is a playful hommage but also a critical examination of Disco culture. It boasts of 52-pages, screenprinted by hand, limited to 250 copies, plus a poster inlay. The title “Best before” indicates that even if the validity of Disco music is long expired, it’s still around. Many people consider it dead - while there’s all kinds of ghosts that prove it’s stayin alive! Who will finally kill it?

To order your copy or download some fresh mixes visit the fanzine’s oldskool website (made by me): http://www.dsico-fanzine.com

dsico fanzine

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Interview for “Yomu Ongaku”


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-content/plugins/wp-lightbox2/wp-lightbox2.php on line 40

Masayuki who is running the music forest blog interviewed me about Upitup Records and the future of the music industry. The interview was published in the book Yomu Ongaku (Reading Music) made by J-Core producer DJ Technorch. “Yomu Ongaku” is written in japanese and limited to 300 copies - unfortunately I couldn’t get a printed specimen. Below you can download the english version.

Read

Yomu Ongaku interview (1,5 MB, japanese)
Yomu Ongaku interview (4 KB, english)

Scans

Yomu Ongaku CoverYomu Ongaku Cover

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

700|_71|\/|3


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-content/plugins/wp-lightbox2/wp-lightbox2.php on line 40

I wrote a little essay about authenticity in contemporary creative production which was published in the great book Shake Your Tree #3 by cool guys Manuel Bürger, Sebastian Haslauer and Florian Bayer.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 19

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 28

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 32

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/18/d69630753/htdocs/home/wp/wp-includes/functions.php on line 33

Final Project (Thesis)


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/18/d69630753/htdocs/home/wp/wp-content/plugins/wp-lightbox2/wp-lightbox2.php on line 40

In the design of contemporary music software, a strategy of simulation has been established: Functionality and appearance of analog instruments are imitated by means of complex algorithms and photorealistic graphics. Instead of recognizing the specific qualities of the computer as a musical instrument, one recurses to approved aesthetics and traditional methods of operation when designing digital sound tools.

My thesis elaborates on the intrinsic differences between traditional and digital instruments in order to explore the aesthetic qualities of the computer as a musical instrument. As with any software, music software exactly defines the possibilities of what can be expressed with it.

The aesthetical and functional decisions made in the design process undoubtedly exert an influence on the user‘s mode of working. The interface can therefore be considered as a musical ideology. To address the question, how the creative work is impacted by the tools being used in the production process, critical positions of contemporary electronic musicians are gathered and evaluated.

The text pages of my thesis were printed with a Riso RC 4000 while the pictures pages were printed with a Xerox digital printer. I chose these techniques to create an aesthetic correlation with the topic.

Read

Download Abstract (56 KB, english)
Download Thesis (1,5 MB, german)

Pictures

Digital Vintage ThesisDigital Vintage ThesisDigital Vintage Thesis