Automatically Uploading Files Feature on A329S/T: Do You Need It?

lufa6977 said:
SFTP would probably be wiser.
Click to expand...
What is the advantage over using FTP?
And the disadvantages such as getting blocked by firewalls?
 
Vortex Radar said:
Thinking of Blackvue's implementation, what do you think of an option to upload at reduced resolution if we prefer,
Click to expand...
If you are uploading impact only, and they are probably in low bitrate parking mode at 1 minute duration, they are not going to be big files anyway, I think most people would want the full resolution, assuming that it is a genuine impact?

If they are not low bitrate, a lower bitrate version would be more useful than a lower resolution version, you can quite likely half the size and not be able to see much difference, but with lower resolution you definitely can see less detail.

Vortex Radar said:
as well as to choose which camera(s) to upload footage from?
Click to expand...
In that case, you want the camera that was facing the impact, not the one that you pre-selected!
 
lufa6977 said:
SFTP would probably be wiser.
Click to expand...

It depends ...
1) If the AP is in trusted closed (home/business) LAN encryption is not necessary
2) SFTP needs much more processing power from dashcam to encrypt the traffic and thus if the main goal in parking status is to save power encrypting the data is not the best way to operate
3) Normally transferring data wisely over WAN is used thru VPN tunnel. Why to encrypt the data twice? (VPN+SFTP)

I would go with FTP only.
 
iZak said:
3) Normally transferring data wisely over WAN is used thru VPN tunnel. Why to encrypt the data twice? (VPN+SFTP)
Click to expand...
People are going to be connected via WiFi, LTE, or 5G, all of which are encrypted (unless someone has deliberately turned the WiFi encryption off), so it is more a case of "Why to encrypt multiple times?"!

I think all of those are secure enough for a normal person, if you are really worried then 5G is the best, but they are all far more secure than the files sitting on your physical memory card/storage device in the vehicle. If people are really worried about security, then the video files themselves should be encrypted, not just the transmission, and then they would be secure on both the card and during transmission, whatever you use to transmit them.

Of course encrypted files are of no use in court, for most people there is little reason to encrypt them at all, and if a dashcam owner gets killed in a crash, their family might be very grateful to find that their video files are not encrypted and thus usable for compensation claims and prosecution of the culprit.
 
1) FTPS is generally considered to be deprecated and has been dropped by many server/cloud-centric organisations. If someone does not understand that, then they should excuse themselves from this discussion.

2) Anyone who is using a service to upload a 1-minute or so clip of an impact, after the car is turned off, should not be concerned about power usage for that brief period. If they are, they should install two additional battery packs. This will eliminate their fears. Power is not an issue.

3) Who said a VPN or any other encryption would be used? The average user is as dumb as a bag of bricks when it comes to protocols and security.

4) Viofo wants to maintain total control of the transmission, with total encryption and security. More is better.

5) Viofo will need to decide if they want the legal risk of transmission and housing the file on their servers in China or other countries where required by law. SFTP offers a more comprehensive set of tools than FTPS.

6) If Viofo wisely chooses to use AWS or other cloud services, AWS and those other clouds will be happier with SFTP.



None of my answers came from Google.
 
Are there already some testers here who have been able to test FTP uploads with the beta version?
 
lufa6977 said:
1) FTPS is generally considered to be deprecated and has been dropped by many server/cloud-centric organisations. If someone does not understand that, then they should excuse themselves from this discussion.

2) Anyone who is using a service to upload a 1-minute or so clip of an impact, after the car is turned off, should not be concerned about power usage for that brief period. If they are, they should install two additional battery packs. This will eliminate their fears. Power is not an issue.

3) Who said a VPN or any other encryption would be used? The average user is as dumb as a bag of bricks when it comes to protocols and security.

4) Viofo wants to maintain total control of the transmission, with total encryption and security. More is better.

5) Viofo will need to decide if they want the legal risk of transmission and housing the file on their servers in China or other countries where required by law. SFTP offers a more comprehensive set of tools than FTPS.

6) If Viofo wisely chooses to use AWS or other cloud services, AWS and those other clouds will be happier with SFTP.



None of my answers came from Google.
Click to expand...
SFTP transfer speed we found is too low.

It is possible to use AWS in the future.
 
viofo said:
SFTP transfer speed we found is too low.
Click to expand...
What do you mean by transfer speed? Slow how? And how slow? Have you analyzed what the difference with FTP and SFTP. And some other common protocols.
Novatek 98530 has 4x Cortex A53 which are power optimized and has a very slow FPU unit. Encryption (SSH) is all about FPU.

But have you analyzed is the processor itself limiter (FPU), speed of buses (CMOS, memory,...), heat accumulation-> processor throttling, ...
Obviously it is now WIFI6 speed or SSD or any other connection speed.

I hope in the future you support all standard FTP connections. And when that is done ul+del is a few code lines away.
 
It is only for beta testing, we have offered this to some personal use and business customer, it is working, and we keep updating for it, we may offer for public testing after we completed another feature.
 
Hi,

I would love to test this. I'm currently using a script on my Mac mini to look for the camera every 5 minutes and download new files using curl but it would be better with a push-mechanism.

Would that mean that I could use parking mode?

To be fair, I'm pretty happy with the script, but I haven't figured out how to get the camera to enter WiFi Station mode automatically when I get home AND perform parking monitoring. I guess I would be happy enough if I could turn of parking monitoring at home and have it enter WiFi station there instead.

But then again, I just got the camera installed today and am still trying to understand exactly what triggers what.
 
If you prefer using the PC or MAC to download the videos, you can wait for our downloader tools.

For the auto uploading feature, we are working on it how to make it as built-in feature and easier to use it.
 
I've written my own sync script for macOS and Linux that backs up my device when it's discovered on the network. See this thread:
johanthoren

Thread 'Auto-sync VIOFO footage to your computer over WiFi (open source script)'

Hey everyone,

I just got a VIOFO A329S and didn't want to deal with manually pulling the SD card to transfer footage. Since the camera has WiFi and serves files over HTTP, I wrote a script to automatically sync footage to my computer whenever the car is parked at home.

What it does:
  • Polls for the camera on your network every 5 minutes
  • Downloads new footage when the camera is detected
  • Automatically prunes oldest recordings when storage gets low (keeps...
  • Like
 
Here's also another project with similar features as above. Recently started to use it and found out that GPS data extraction didn't work with A329S so I made fix for that, it was pulled to main repo yesterday. Author said yesterday that he's preparing some more updates shortly.

github.com

GitHub - RobXYZ/viofosync: Self-hosted web app for automatically downloading, browsing, editing and exporting recordings from a Viofo dashcam over Wi-Fi.

Self-hosted web app for automatically downloading, browsing, editing and exporting recordings from a Viofo dashcam over Wi-Fi. - RobXYZ/viofosync
github.com github.com
 
Jusii said:
Here's also another project with similar features as above. Recently started to use it and found out that GPS data extraction didn't work with A329S so I made fix for that, it was pulled to main repo yesterday. Author said yesterday that he's preparing some more updates shortly.

github.com

GitHub - RobXYZ/viofosync: Self-hosted web app for automatically downloading, browsing, editing and exporting recordings from a Viofo dashcam over Wi-Fi.

Self-hosted web app for automatically downloading, browsing, editing and exporting recordings from a Viofo dashcam over Wi-Fi. - RobXYZ/viofosync
github.com github.com
Click to expand...
That looks solid at a glance. More robust than my simple script I would guess. 👍
 
Posting here to let you know I am interested. I have a complicated network with a server able to run docker containers and parse the needed data. Looking for an easy plug and go method to cache data.
 
I personally like being able to access files via Wifi Station Mode. However, the camera's web page is honestly pretty lame... It has no navigation to e.g., a parent directory... Delete a file and get to an error page, then back and refresh and the file is gone, so it's functional, just not pretty.

To make Wifi Station Mode truly useful, I'd like to see this:

1. The camera reliably enables Wifi Station Mode when you get home for a configurable amount of time, even in Parking mode.
2. A Watcher service or background app on the user's favorite computer or mobile device(s) notices when the camera shows up on the LAN.
3. The Watcher automatically begins sucking the videos off the card in the car as bandwidth permits.
4. Optional ordering, e.g., RO first, Parking second... Latest videos first... Etc. The idea is to get all the videos into the computer sooner or later.
5. Option to copy one, several, or all types of files (e.g., RO and Parking videos, but not the traveling videos).
6. Option to delete the file off the camera's card once copied to the computer.
7. Option to notify the user under some conditions, such as if an RO file shows up or the Wifi Station Mode shut off before all files could be sync'd.
8. Option to to nothing but kick off a script on the computer when the dashcam shows up on the network.
9. Robustness - don't get stuck, operations to be done with handshakes and checksums so no data is lost, minimum system resource usage (e.g., use Task Scheduler on Windows).
10. Everything can be scripted using appropriate command line tools (e.g., curl, etc.).
11. APIs that can be called to aid in sync, checking checksums, etc.

Think "implemented kind of the way POP / SMTP eMail server access works".

That's what came to my mind.

-Noel
 
BlackVue Downloader does this. It’s a windows app. You should be able to do the same thing. Maybe talk to Glenn the developer at Gizmocoding to help you. He charges 6 dollars for your app. I’m thinking of switching my cameras from BlackVue to yours, but not having a program that auto downloads to my PC when I get home is preventing me from doing this.
 
You must log in or register to reply here.
Back
Top