- Home ›
- Apps ›
- Entertainment ›
- Digital Lighter Server APK
Digital Lighter Server
What's Digital Lighter Server APK?
Digital Lighter Server is a app for Android, It's developed by Milos Jovac author.
First released on google play in 10 years ago and latest version released in 8 years ago.
This app has 0 download times on Google play and rated as 5.00 stars with 2 rated times.
This product is an app in Entertainment category. More infomartion of Digital Lighter Server on google play
git: https://github.com/dohnto/CDP
Group: #5 (Silent Ducks) - Agnethe Søraa, Tomáš Dohnálek, Jan Bednařík, Miloš Jovac
Customer: Netlight AS
Title: Rock Concert Audience as a Screen
Assignment text:
The cell phone screens of the rock concert audience become the pixels of a giant screen.
Audience members at a concert have downloaded a simple app to their cell phone, and registered this
through a simple GUI. There is a screen on the stage behond the artists. On top of the screen there is
a simple camera, taking pictures 5 times a second.
The audience are at occasions instructed to hold up their cell phones with their screens toward the
stage, similar to holding up a lighter.
The server-side of the apps deliver control-signals, instructing the app when to show something.
Usually filling the entire screen with a single colour, at full light intensity. The apps are synced with
the control signals, which is a simple list of instructions (e.g. all pixels white, max strength) at a
certain time intervall (1583 - 1802 seconds), and is specific to each app/phone.
At startup, each app is alone in lighting up in a time intervall, and the server-side kan map where a
mobile is in the image/grid from the camera.
Goals:
Handle timing and syncing issues between multiple independent units.
Division and simplification of the problem.
Generating test-data.
Implementing image processing, and mapping of mocked apps/units to locations in the crowd as a
function of time.
Discuss issues related to the goals.
Discuss generalisation of solution and possible uses of framework outside of rock concert domain.
Proof of concept should include client side implementation, server-side control, mapping of return
image from apps to grid, playback of video.
Integration of all submodules for proof of concept demonstration is desirable, but comes second in
favour of making sure to implement all submodules. In which case, mocking must be used.
The goals/requirements of the project may be tweaked/moulded by customer to accomodate/utilize
the skill set of the specific group members.
Group: #5 (Silent Ducks) - Agnethe Søraa, Tomáš Dohnálek, Jan Bednařík, Miloš Jovac
Customer: Netlight AS
Title: Rock Concert Audience as a Screen
Assignment text:
The cell phone screens of the rock concert audience become the pixels of a giant screen.
Audience members at a concert have downloaded a simple app to their cell phone, and registered this
through a simple GUI. There is a screen on the stage behond the artists. On top of the screen there is
a simple camera, taking pictures 5 times a second.
The audience are at occasions instructed to hold up their cell phones with their screens toward the
stage, similar to holding up a lighter.
The server-side of the apps deliver control-signals, instructing the app when to show something.
Usually filling the entire screen with a single colour, at full light intensity. The apps are synced with
the control signals, which is a simple list of instructions (e.g. all pixels white, max strength) at a
certain time intervall (1583 - 1802 seconds), and is specific to each app/phone.
At startup, each app is alone in lighting up in a time intervall, and the server-side kan map where a
mobile is in the image/grid from the camera.
Goals:
Handle timing and syncing issues between multiple independent units.
Division and simplification of the problem.
Generating test-data.
Implementing image processing, and mapping of mocked apps/units to locations in the crowd as a
function of time.
Discuss issues related to the goals.
Discuss generalisation of solution and possible uses of framework outside of rock concert domain.
Proof of concept should include client side implementation, server-side control, mapping of return
image from apps to grid, playback of video.
Integration of all submodules for proof of concept demonstration is desirable, but comes second in
favour of making sure to implement all submodules. In which case, mocking must be used.
The goals/requirements of the project may be tweaked/moulded by customer to accomodate/utilize
the skill set of the specific group members.
