Some VCs are not stored as single video files, but are instead stored as separate video files (one for the screen share, one for the webcams, etc.) and what I assume is a bunch of non-video extra data (for students' comments, etc); on the web portal, these are presented as an iframe that acts as a custom video player and presents the data through a mix of <video> tags and other HTML elements.
The video files are stored at a different subdomain, but the API erroneously reports them as being in video.polito.it.
The API also erroneously reports the video as a single file called .mp4 (which would be the case for the "usual" VCs), while in reality the split video files are stored in subdirectories of (which is thus a folder and not an mp4 file).
This makes these VCs inaccessible through the APIs, which is also manifested in the official app, which fails to load them and leaves an empty video player.
Some VCs are not stored as single video files, but are instead stored as separate video files (one for the screen share, one for the webcams, etc.) and what I assume is a bunch of non-video extra data (for students' comments, etc); on the web portal, these are presented as an iframe that acts as a custom video player and presents the data through a mix of <video> tags and other HTML elements.
The video files are stored at a different subdomain, but the API erroneously reports them as being in video.polito.it.
The API also erroneously reports the video as a single file called .mp4 (which would be the case for the "usual" VCs), while in reality the split video files are stored in subdirectories of (which is thus a folder and not an mp4 file).
This makes these VCs inaccessible through the APIs, which is also manifested in the official app, which fails to load them and leaves an empty video player.