User:Tash/Prototyping 01: Difference between revisions

From XPUB & Lens-Based wiki
 
(10 intermediate revisions by the same user not shown)
Line 2: Line 2:
==Command lines & Raspberry Pis==
==Command lines & Raspberry Pis==
* First time ever working with command lines, shell scripts and the Raspberry Pi.
* First time ever working with command lines, shell scripts and the Raspberry Pi.
* First bash script (using python scripts, ffmpeg, melt, spell and speak)
* Made first bash script (using python scripts, ffmpeg, melt, spell and speak)
* Experiment with interaction in scripts {{#Widget:Video|webm=https://pzwiki.wdka.nl/mediadesign/File:Echo_convo.webm}}
* Experiment with interaction in scripts
<source lang="bash">
espeak -w audio.wav -p 70 "I am dead inside"


* Better understanding of networks, servers & programming languages, setting up public websites on the Pi.
sox audio.wav audio2.wav speed 0.7
* How to use Git repositories.
 
sox audio2.wav -b 8 -e unsigned-integer -c 1 -r 4000 -t raw rawfile
 
rm frame*.jpg
 
python lip-sync.py
 
ffmpeg -r 10 -i frame%09d.jpg -i audio2.wav -y mymovie1.mp4
 
</source>
 
<source lang="bash">
espeak "Hi, What is your name?"
echo "What is your name?"
read content
 
espeak -z "Nice to meet you"
echo $content | espeak
 
espeak  "What’s your favorite color?"
echo "What’s your favorite color"
read content
 
espeak -z "Oh my god. I love the color"
echo $content | espeak
</source>
 
{{#Widget:Video|webm=https://pzwiki.wdka.nl/mw-mediadesign/images/8/82/Echoscript.webm}}
 
* Better understanding of networks, servers & programming languages, setting up public websites on the Pi, like we did for the documentation of our Special Issue 04 project
* First time using Git repositories


==Wiki-wiki==
==Wiki-wiki==
* Learnt how to use media-wiki as a writing and reading platform
* Learnt how to use media-wiki as a writing and reading platform
* Opportunities & challenges in using Semantic Media wiki: how the use of metadata, properties, values and forms can be useful in creating meaning, but also limiting in other ways
* Opportunities & challenges in using Semantic Media wiki: how the use of metadata, properties, values and forms can be useful in creating meaning, but also limiting in other ways. Very interesting to note that an archive's system can determine what it produces
* Wiki skinning with Manetta, my background in web design was helpful in this
* Wiki skinning with Manetta (my experience in web design and html was helpful in this)
* Pipelines that use wikis as a source / step / destination
* Using templates in the media-wiki environment
 
<source lang="html4strict">
 
{{#ask: [[Title::A chair in the Poortgebouw]]
|?Title
|?Document Type
|?Last editor is
|?Modification date
|format=template
|template=image overview
|sort=Modification date
|order=descending
}}
 
</source>
 
* Experimented with algorithms and scripts that used the Autonomous Archive wiki as a source of files, and generated a PDF output via command line
<br>
[[File:OutputPDFalgorithm3.jpg|700px|thumb|center| PDF output of query: Document_Type=Newspaper]]


==Going forward==
==Going forward==
[[File:PostDigitalPrint1.jpg|thumb|Image via Post-Digital Print: Illustration, Everyday Science and Mechanics magazine, 1935]]
[[File:Google_translate.jpg|thumb|Google translate: Indonesian pronouns to gendered English pronouns]]
* Would love to push my technical skills in the next trimester. This means more coding, python, publishing on different servers, research on networks, but also experiments with hardware. These are all practices I don't have much experience with.
* Would love to push my technical skills in the next trimester. This means more coding, python, publishing on different servers, research on networks, but also experiments with hardware.  
* Algorithmic curation & generative content is a growing interest for me. How can I experiment more with the relationship between content - design - system?
* Algorithmic curation & generative content is a growing interest for me
* Also: In a publication, where is the border between reader & writer? Wikis are all about collaborative content; they are also 'platforms with attitudes'. How does software influence behaviour? Politics of 'seamlessness'?
* Also: In a publication, where is the border between reader & writer? Wikis are all about collaborative content; they are also 'platforms with attitudes'. How does software influence behaviour? Politics of 'seamlessness'?
* For later: editorial design for the future > what's next for print, what's next for e-books and digital magazines?
* To explore further: language, value systems in software, designing the rules and not the output
* References:  
* References:  
**''Post Digital Print'' by Alessandro Ludovico http://postdigitalprint.org
**''Eleven Orderings: Guttorm Guttormsgaard'' http://guttormsgaard.activearchives.org
**''Eleven Orderings: Guttorm Guttormsgaard'' http://guttormsgaard.activearchives.org
**''1984 by @realdonaldtrump'' http://emmaking.net/index.php?/projects/1984-by-realdonaldtrump/
** ''Editor'' by NYT Labs
<br>
{{#widget:Vimeo|id=133766552|width=700}}

Latest revision as of 12:48, 11 December 2017

Image from lip-sync animate project

Command lines & Raspberry Pis

  • First time ever working with command lines, shell scripts and the Raspberry Pi.
  • Made first bash script (using python scripts, ffmpeg, melt, spell and speak)
  • Experiment with interaction in scripts
espeak -w audio.wav -p 70 "I am dead inside"

sox audio.wav audio2.wav speed 0.7

sox audio2.wav -b 8 -e unsigned-integer -c 1 -r 4000 -t raw rawfile

rm frame*.jpg

python lip-sync.py

ffmpeg -r 10 -i frame%09d.jpg -i audio2.wav -y mymovie1.mp4
espeak "Hi, What is your name?"
echo "What is your name?"
read content

espeak -z "Nice to meet you"
echo $content | espeak 

espeak  "What’s your favorite color?"
echo "What’s your favorite color"
read content

espeak -z "Oh my god. I love the color"
echo $content | espeak

  • Better understanding of networks, servers & programming languages, setting up public websites on the Pi, like we did for the documentation of our Special Issue 04 project
  • First time using Git repositories

Wiki-wiki

  • Learnt how to use media-wiki as a writing and reading platform
  • Opportunities & challenges in using Semantic Media wiki: how the use of metadata, properties, values and forms can be useful in creating meaning, but also limiting in other ways. Very interesting to note that an archive's system can determine what it produces
  • Wiki skinning with Manetta (my experience in web design and html was helpful in this)
  • Using templates in the media-wiki environment
{{#ask: [[Title::A chair in the Poortgebouw]]
 |?Title
 |?Document Type
 |?Last editor is
 |?Modification date
 |format=template
 |template=image overview
 |sort=Modification date
 |order=descending
}}
  • Experimented with algorithms and scripts that used the Autonomous Archive wiki as a source of files, and generated a PDF output via command line


PDF output of query: Document_Type=Newspaper

Going forward

Google translate: Indonesian pronouns to gendered English pronouns
  • Would love to push my technical skills in the next trimester. This means more coding, python, publishing on different servers, research on networks, but also experiments with hardware.
  • Algorithmic curation & generative content is a growing interest for me
  • Also: In a publication, where is the border between reader & writer? Wikis are all about collaborative content; they are also 'platforms with attitudes'. How does software influence behaviour? Politics of 'seamlessness'?
  • To explore further: language, value systems in software, designing the rules and not the output
  • References: