Hi! We recently released a new update for the Mapillary Uploader, you can download it at https://mapillary.com/desktop-uploader and your installed apps will auto-update the next time you start.
Here’s what’s in this update:
Improved startup speed: we updated how we load upload history to reduce waiting time. We have also simplified the data we store in the upload history to prevent this issue from occuring in the future.
We have also added a “Reset” button to the upload history.
Also includes the latest ExifTool for improved camera compatibility.
Some UI improvements like: the app will now ask you if you want to apply the update when it has been downloaded and the app will ask you to confirm if you want to close it while an upload is in progress.
Ah, this one was is the OSM map tile fix. We were in the process of releasing 5.1.0 just as this was reported so we wanted to include it (and also a couple ofther minor dependency updates) so 5.1.1 is the one we announce here in the forum. We’ll add more info on https://www.mapillary.com/release-notes
I’m currently experiencing massive upload problems with the Desktop Uploader on my Ubuntu quad-core machine. This forces me to manually initiate each upload sequence individually. Typically, the upload speed starts promisingly at the beginning of each sequence, but then continuously drops and stagnates at just a few megabits per second. This pattern repeats itself the next time I try to upload. My network speed is fine, and I just reinstalled Ubuntu on the machine, but there’s no improvement.
Could it be that the Mapillary Tools require a powerful graphics card? The system load on my Linux machine shows normal values for all parameters, such as CPU usage and memory consumption.
In principle, I would like the idea of providing Mapillary with a remotely controlled client on my computers – for data processing and upload preparation – if this would improve the upload process.
This is not a Desktop Uploader issue but a network infrastructure issue. See Increasing upload problems.
No.
No, Mapillary is already short on staff and they surely do not want to manage even more hardware or software on the edge. It would not improve upload speeds or network stability either.
Hi! Your system specs seem fine and should not be a problem for uploading to Mapillary.
In this kinds of situations the internet connection is the most common culprit (ISP/router) but it could be also bottlenecks like HDD speed or server-side throttling.
Do you notice a similar problem when uploading to a cloud storage service (like Dropbox etc.) from your system?
If not, we could also take a look at your uploader logs (Help → Logs) for more details.
Right! Do not run multiple Desktop Uploader or mapillary_tools upload sessions concurrently on a single internet connection. They or rather the upload protocol are not designed for this (yet). It does not improve your throughput either. If anything it rather hurts your throughput.
You misunderstood me; I only use a single desktop uploader installation. I select a single recording, start the upload process, and wait for a green success message. Once the indicator is green, I manually select the next file and start the next upload. With some uploads, I usually get an “Upload failed” message exactly one minute before the estimated upload time is due to end. I then confirm “Try again.” The desktop uploader then works on the upload for significantly longer and finally displays “Finishing,” sometimes generating twice the uploaded data volume of the file itself. After waiting a while, a success message usually appears. The entire process is no longer automatic; each recording has to be started manually. Ultimately, this process works. I already have a backlog of recordings. I’m not complaining; at least it works somehow.
There are now significant fluctuations in the upload speed. It usually hovers around 18 MB/s, but now the speed frequently drops to 0, only to suddenly recover. During these periods, the actual upload process is running.
My current workflow is pragmatic: I first upload all the recordings to GSV. Once that’s done, I run the Mappillary Desktop Uploader. However, However, GSV, which isn’t experiencing any connection drops, is already 60 records ahead, and this discrepancy is causing me to run out of memory.
I see. This sounds indeed really inefficient and laborious. @nikola Doesn’t Desktop Uploader move on to upload the next sequence when uploading a sequence (on the list) fails? Maybe we should have like a “retry all failed sequences” button or what the “Retry” button should generally do?
Thanks to the now working uploads, I’ve been able to almost completely clear my backlog. I have already sent my log file to the support address you provided.
We were in the process of releasing 5.1.0 just as this was reported so we wanted to include it (and also a couple ofther minor dependency updates) so 5.1.1 is the one we announce here in the forum. We’ll add more info on 
No, Mapillary is already short on staff and they surely do not want to manage even more hardware or software on the edge. It would not improve upload speeds or network stability either.