---
title: 'Between: 2015/10/01 en 2015/10/31 - 0110.be'
canonical: https://0110.be/date/2015/10
markdown_url: https://0110.be/date/2015/10.md
page: 0
posts_per_page: 30
total_posts: 3
filters:
year: 2015
month: 10
previous:
next:
---
# Between: 2015/10/01 en 2015/10/31 - 0110.be
## [Lecture on MIR - Tone Scale Extraction - Acoustic Fingerprinting](https://0110.be/posts/Lecture_on_MIR_-_Tone_Scale_Extraction_-_Acoustic_Fingerprinting.md)
- Published: 2015-10-30T00:00:00Z
- Updated: 2025-11-29T19:35:10Z
- Author: Joren
- ID: 444
- Canonical: https://0110.be/posts/Lecture_on_MIR_-_Tone_Scale_Extraction_-_Acoustic_Fingerprinting
- Tags: [Presentation](https://0110.be/tags/Presentation.md), [UGent](https://0110.be/tags/UGent.md)
This morning, the 30th of October 2015, I gave a lecture on Music Information Retrieval in general and two MIR-tasks in particular. The two more detailed tasks were tone scale analysis and acoustic fingerprinting.
During the lecture some live demonstrations were done with [Panako](http://panako.be) and [Tarsos](https://0110.be/Software). Also some examples from [TarsosDSP](https://0110.be/Software) were used. Excerpts of the music used is available [here](https://0110.be/files/attachments/444/Acoustica-MIR-Tarsos-Panako-examples.zip), this is especially interesting if you want to repeat the demos. [Sonic visualizer](http://www.sonicvisualiser.org/), [Music21](http://web.mit.edu/music21/) and [MuseScore](https://musescore.org/) were also mentioned during the lecture.
The [presentation about Music Information Retrieval](https://0110.be/files/attachments/444/2015.10.30.MIR-Acoustica.pdf) and the [handouts](https://0110.be/files/attachments/444/2015.10.30.MIR-Acoustica-handout.pdf) can be found here als well.
- [Acoustica-MIR-Tarsos-Panako-examples.zip](https://0110.be/files/attachments/444/Acoustica-MIR-Tarsos-Panako-examples.zip)
- [2015.10.30.MIR-Acoustica-handout.pdf](https://0110.be/files/attachments/444/2015.10.30.MIR-Acoustica-handout.pdf)
- [2015.10.30.MIR-Acoustica.pdf](https://0110.be/files/attachments/444/2015.10.30.MIR-Acoustica.pdf)
- [slide.jpg](https://0110.be/files/attachments/444/slide.jpg)
---
## [Opening Sport Science Laboratory - Jacques Rogge](https://0110.be/posts/Opening_Sport_Science_Laboratory_-_Jacques_Rogge.md)
- Published: 2015-10-02T00:00:00Z
- Updated: 2025-11-29T19:40:47Z
- Author: Joren
- ID: 443
- Canonical: https://0110.be/posts/Opening_Sport_Science_Laboratory_-_Jacques_Rogge
- Tags: [UGent](https://0110.be/tags/UGent.md)
For the opening of the [Sport Science Laboratory - Jacques Rogge](http://www.ugent.be/ge/bsw/en/sportlab) of University Ghent I have created a demo of a system to visualize running impact. The demo can be seen starting at 45s in the video below.
---
## [TgForce Sensor on Android](https://0110.be/posts/TgForce_Sensor_on_Android.md)
- Published: 2015-10-02T00:00:00Z
- Updated: 2025-11-29T22:10:14Z
- Author: Joren
- ID: 442
- Canonical: https://0110.be/posts/TgForce_Sensor_on_Android
- Tags: [UGent](https://0110.be/tags/UGent.md)
[Kelsec Systems](http://kelsec.com/) developed a nice sensor for measuring running impact, the [TgForce Running Impact Sensor](http://tgforce.com/). The sensor comes with an IOS application but has no available counterpart on Android. To interface with the sensor on Android I needed to create some glue code. The people of Kelsec Systems were kind enough to mail some documentation about the protocol and with that information I got to work.
The [TgForce Sensor Android code](https://github.com/JorenSix/TgForceSensor) is available on GitHub, together with some documentation which is available below as well:
# TgForce Impact Running Sensor Andoid API
The TgForceSensor repository contains Android code to interface with the [TgForce Impact Running Sensor](http://tgforce.com/). The TgForce sensor is a Bluetooth LE device that measures [tibial shock](http://tgforce.com/about-tibial-shock/). It follows the\
Bluetooth LE standards and is relatively easy to interface with.
This repository contains Android code to interface with the device. The protocol is encoded in the source code and is documented in the readme.
---
