dash-3d-tmp/phd
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
Thomas Forgione
2019-10-01 11:59:47 +02:00
parent e9a564f07e
commit 9536bf1c25
7 changed files with 34 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/dash-3d/conclusion.tex
View File

@@ -6,7 +6,7 @@ The answer is \emph{yes}.
In answering this question, we contributed by showing how to organize a polygon soup and its textures into a DASH-compliant format that (i) includes a minimal amount of metadata that is useful for the client, (ii) organizes the data to allow the client to get the most useful content first.
We further show that these metadata that is precomputed offline is sufficient to design and build a DASH client that is adaptive --- it can selectively download segments within its view, make intelligent decisions about what to download, balancing between geometry and texture while being adaptive to network bandwidth.
\fresh{}
This way, our system answers, at least partially, all the open problems we mentionned in~\ref{i:challenges}.
This way, our system answers, at least partially, all the open problems we mentioned in~\ref{i:challenges}.
\begin{itemize}
\item \textbf{It prepares and structures the content in a way that enables streaming}: all this preparation is precomputed, and all the content is structured, even materials and textures. Furthermore, textures are prepared in a multi-resolution manner, and even though multi-resolution geometry is not discussed here, the difficulty of integrating it in this system seem moderated: we could encode levels of detail in different representations and define a utility metric for each representation and the system should adapt naturally.

2
src/dash-3d/introduction.tex
View File

@@ -1,7 +1,7 @@
\fresh{}
\section{Introduction}
In this chapter, we take a little step back from interaction and propose a system with very basic interaction but that answers most of the open problems mentionned in Section~\ref{i:challenges}.
In this chapter, we take a little step back from interaction and propose a system with very basic interaction but that answers most of the open problems mentioned in Section~\ref{i:challenges}.
We take massive inspiration from video streaming, since we have seen in Section~\ref{i:video-vs-3d} how related video streaming and 3D streaming are and how DASH, the standard for video streaming, is so efficient in Section~\ref{sote:dash}.
DASH is based on content preparation and structuring which helps not only the streaming policies that rely on it but also the performance of the system since it removes completely the load on the server side.
A DASH client is simply a client that downloads the structure of the content, and then, depending on its needs, decide what to download by itself.