Long uploads that survive a restart
A long upload from DCAST Desktop does not have to finish in one sitting: after a restart of the app it carries on from the part the server already has.
If an upload from DCAST Desktop is interrupted, for example because the app was closed, it continues from where it stopped instead of sending the whole file again.
A short fault on the server side while the upload resumes does not send the file back to the start.
Only when the server reports that the earlier upload no longer exists does the app start that file again from the beginning.
Once the file has arrived in full, the app clears its record of the interrupted upload.
The record the app keeps for resuming an upload does not store your sign-in token.
Large recordings, such as a full service or a conference day, are where resuming matters most, because a restart no longer costs you the hours already uploaded.
When you start DCAST Desktop again, it first asks the server how much of your file has arrived and then sends only the rest.
The second attempt does not create a second upload on the server; it continues your first one.
DCAST Desktop keeps a record of each of your unfinished uploads on your computer, so that it can find the upload again after a restart.
The app can tell whether your file has an interrupted upload waiting before it starts to send.
The record is matched to your file and to the server address it was sent to, so the same file sent to a different address is not mixed up with it.
The record holds the name and the size of your file and the address of the upload on the server, which is what resuming needs.
When the server says that your old upload is gone, the app starts one new upload for that file and sends it to the end.
Leave your file where it is until the upload has finished.
Keep the app running until the last part has arrived, and start it again if your computer restarts.
DCAST Desktop can watch one or more folders on your computer and queue every new video that appears in them for upload.
While an export is still writing to the file, the app waits, and it queues the video once the file has stopped growing.
The video is queued at its final size, so the upload carries the whole file and not only the part that existed when it first appeared.
A finished export is queued one time, not again for every piece the export wrote along the way.
Project files, images and notes saved in the same folder are left alone.
Hidden files in a watched folder are ignored as well.
dcast Team
Professional video streaming experts helping creators succeed.
Related Articles
Start Your Video Business Today
Join thousands of creators monetizing their content with DCAST.
Get Started Free



