Video file issues when re-muxing/appending (corrupted file?)

[speedingcheetah]

Before replying, I confirmed the A329S [although I do have a v2.0 firmware installed] has it listed as something like the fourth or fifth option in the list.

I just checked their product page and the product image does show power off as an option so if they’re advertising having that option, then I would assume that power off is an option in the existing version one firmware. But I guess I’ll discover that later this week when that comes in.
Any idea when V2 firmware is going to be released then?

 

[rcg530]

I just checked their product page and the product image does show power off as an option so if they’re advertising having that option, then I would assume that power off is an option in the existing version one firmware. But I guess I’ll discover that later this week when that comes in.
Any idea when V2 firmware is going to be released then?

No, I don't have any firm date(s) on when the v2.0 firmware will be publicly released. I'm fairly sure the "Power Off" option was in the older 1.x firmware as well. I have a spare unit I can downgrade the firmware version later tonight to check.

 

[speedingcheetah]

No, I don't have any firm date(s) on when the v2.0 firmware will be publicly released. I'm fairly sure the "Power Off" option was in the older 1.x firmware as well. I have a spare unit I can downgrade the firmware version later tonight to check.

with this current file issue I am chasing, that may affect things if I end up updating the firmware anyways before I finish trying different techniques of safely shutting down the camera. Or chasing power issues.
If it ends up being fixed in the newer firmware, I’m just be spinning my wheels right now then.

I most especially am anxious for better optimized firmware for boot times it’s absolutely excruciating waiting like 25 to 30 seconds or something for things to start recording. It’s excessively long.

 

[rcg530]

The latest public firmware version 1.2_250708 does have "Power Off" in the list of available commands for the 3-button Bluetooth remote.

 

[speedingcheetah]

No, I don't have any firm date(s) on when the v2.0 firmware will be publicly released. I'm fairly sure the "Power Off" option was in the older 1.x firmware as well. I have a spare unit I can downgrade the firmware version later tonight to check.

Just curious, Is such "beta/testing" firmware you and others here are given access to, under some contract or embargo etc, so that you are not allowed to share it with other form members who may want to test it too?

I have seen public posts on here from VIOFO of beta/testing firmware, but that is them choosing to publicly share it....

I am not finding a page on VIFOs website for public beta version of their cam firmware. So i gather they do not have a public "beta" firmware release channel

 

[rcg530]

Just curious, Is such "beta/testing" firmware you and others here are given access to, under some contract or embargo etc, so that you are not allowed to share it with other form members who may want to test it too?

I have seen public posts on here from VIOFO of beta/testing firmware, but that is them choosing to publicly share it....

If I'm given access to a test/beta firmware for testing, I assume it is for private use only [not to be shared]. In the past when others have wanted access to the same version of test/beta firmware, I've asked VIOFO if I can share it publicly. VIOFO may share it themselves on DCT or individually with specific users depending on their testing needs for that particular firmware version.

 

[Karagandinez]

Any idea when V2 firmware is going to be released then?

V

Post in thread 'Viofo A329S Review'

Sep 28, 2025

Strangely today I did have the camera not recognised the HK6 cable so hybrid parking wasn't available. Unplug usb c and reconnect all good.

Please update this firmware to test: https://drive.google.com/file/d/1LqXb0YFKFSQkbdMFjz__2j3W6bTfOQPO/view?usp=drive_link
The firmware version shall be V2.0 250925 after updating successfully.

• VIOFO-Support

• 

 

[Karagandinez]

Since when?

The function of turning off the DVR using BTR200 has been around for a long time.

 

[speedingcheetah]

V

Post in thread 'Viofo A329S Review'

Sep 28, 2025

Strangely today I did have the camera not recognised the HK6 cable so hybrid parking wasn't available. Unplug usb c and reconnect all good.

Please update this firmware to test: https://drive.google.com/file/d/1LqXb0YFKFSQkbdMFjz__2j3W6bTfOQPO/view?usp=drive_link
The firmware version shall be V2.0 250925 after updating successfully.

• VIOFO-Support

• 

Ah I had glanced at that before in passing. Thanks for pointing it out what thread their post of v2 firmware was in, I couldn’t recall where I had seen it mentioned and search function did not find it for reason

However, that for A329S, and not the T variant, so that does not do me any good right now sadly.

 

[speedingcheetah]

I have dug up most of the testing footage i had saved to a random external drive.

For the first 5 or 6 days, i think, i only used the Micro SD card in the camera, not a single file had this issue.

For the days and testing drives/ errand trips after that, using external ssd only. Of the files i have saved and just now ran error scans on.

I had one file, out of about 15 files from the Vantec nvme enclosure/Mushkin ssd and usb 3.0 cable i had. (only used it on 1 short trip as that is when i discovered it would not mount at camera boot)

2 files out of about 50 from the older slower, Samsung T3 1TB ssd, i used both with 3.0 cable and later viofo cable.

But, the Sandisk Extreme ssd, VIOFO's recommended drive, its basically happening every other time the camera looses power and shuts down.
Seems like using the Sandisk, a faster nvme internal designed based drive, probably uses more power too due to its much higher performance ratings, appears to make this issue worse.

Could be a power starvation thing happening, like previous posts have brought up, where there just is not enough time for the cam to finish properly closing out the video file.
Could also be, imo, a firmware bug, or optimization issue in how it is writing to the SSD vs how it does the internal SD Card.

I still need to test if safely powering down (stop recording then power down) process will affect this issue at all.

The only thing i can confidently rule out, is heat. Both the cam and the ssd are not getting hot, they are getting warm, but not at all close to overheating. It been warm enough to have the AC on in the car, but, the max the cars cabin has got since i got the cam and ssd is around 80F. I have not let it parked in direct hot sun for hours, then did any driving.

Again, this issue is EDGE case. The single video files have no issue playing at all in any media player i have tried.

 

[speedingcheetah]

I'm not saying you're wrong, but I think Ben hit the nail on the head, (Power Starvation Malfunction).
I would rule out power starvation first before writing scrips & codes, (easiest / quickest first).
I would buy this Type-C Power Tester for $12 to check for power starvation issues;
https://www.amazon.com/gp/B0D529Z22P
It looks like this;

I was able to do some casual power tests.
Posted on a new thread.

Thread 'A329T 3CH power draw tests. SSDs'

Oct 2, 2025

On the suggestion of @Chuck McCoy in this post on my thread discussing the possible file corruption issues i am having when i go to remux/append all the cams video files into one single file, to check for Power Starvation issues using a USB C power meter.
Here is video of various tests i have done.

NOTE: These are not meant to be 100% perfect / scientifically accurate or comprehensive tests.
It is meant as a casual testing to see if i have some sort of obvious Power Starvation issue with my current setup.
( a few videos seems to have been cropped just a little, or i...

• speedingcheetah
• a329t power usage ssd
• Replies: 2
• Forum: A329T

• 

 

[speedingcheetah]

In my drive today, after i did all the power meter tests.

I began to Remotely Power Off the camera using the BT remote, then cut power. Instead of just turning car off and it hard cutting the power.

So far, the 6 times i did that in the trip, when i stopped places, there has been no errors with the video files. Still using the external Sandisk SSD.

Will continue to do this process for the next several trips out. See if it sticks.

If this is the "fix" for this issue, then it has narrowed it down a bit at least.
______
However, there still remains my speculation to the root cause.

It does very much fell like a power issue, in that there may not be enough capacity/run time left in the super caps for the cam to complete its full safe close and write to disk, and power off code.
But, i feel, if that was the case, the video file would actually be more obviously corrupted somehow, in that would have some issue playing the single file back. And it would also be more repeatable, do it every time thing.

(Is there a difference in the actual code the camera is running, in hard power cut/on caps power shut down, vs the Remote Power Off shutdown code)?

It could just be a firmware issue, where further optimization is needed in the hard power cut shutdown functions for when using a SSD. (as it does not seem to have this issue when using internal micro sd)

Overall, safe bet to say, that the Firmware for the A329X does need some work. Significant refinement/optimization for boot time, and possibly for shutdown as well. Improvement for the SSD features as well.
It is a bit, concerning though. This is VIOFO's flagship model. I expected a bit more polished firmware that it seems to be in. Sure, it is a fairly newly launched product, but still, a tad rougher around the edges than the end user may expect, for the high cost as well.

 

[speedingcheetah]

Based on the power meter readings, the input power to the cam, looks fine. Well under the 3A that the CIG lighter USB adapter can output to it.

The Power to the SSD, also looks good, plenty of head room there.

The PC powered tests was able to push the SSDs a bit harder, with the Samsung T3 touching 0.38A at mount for a short time. (will post those vids tomorrow evening in that thread)

So... I do not think there is a "Power Starvation" issue while in normal operation with my setup.

Unless someone here sees something that i do not? Or has any other further input on this?

 

[LateralNW]

Using this check on my m.2 Sandisk 500GB in an mbeat enclosure housing, I found 6 files that play fine* but show in the test with errors similar to your first post.
That was out of ~750 files.

ffmpeg -hide_banner -v error -i "c:\dashcam_test_file.mp4" -f null -

*When I play these files in vlc they stop short of the end by about 2 to 3 secs.
Interestingly when I play other Viofo videos in vlc the files often end at 59 seconds and not the 60 seconds that they should do.

Doing some research the problem may be due to buffers not flushing completely. Of course it could also be a million other reasons.

I noticed in the early days of using the usb connection that any little movement has the potential for the unit to fail. I have found that at times the USB-C connector sucks for a reliable connection if there is any movement. That includes my desktop computer when I happen to move the cable slightly.

Because of that I have the m.2 on its side (so it is jammed in) on the sun shade with a short cable that doesn't move going to the A329 no letter model.

 

[speedingcheetah]

Using this check on my m.2 Sandisk 500GB in an mbeat enclosure housing, I found 6 files that play fine* but show in the test with errors similar to your first post.
That was out of ~750 files.

ffmpeg -hide_banner -v error -i "c:\dashcam_test_file.mp4" -f null -

*When I play these files in vlc they stop short of the end by about 2 to 3 secs.
Interestingly when I play other Viofo videos in vlc the files often end at 59 seconds and not the 60 seconds that they should do.

Doing some research the problem may be due to buffers not flushing completely. Of course it could also be a million other reasons.

I noticed in the early days of using the usb connection that any little movement has the potential for the unit to fail. I have found that at times the USB-C connector sucks for a reliable connection if there is any movement. That includes my desktop computer when I happen to move the cable slightly.

Because of that I have the m.2 on its side (so it is jammed in) on the sun shade with a short cable that doesn't move going to the A329 no letter model.

Thanks for the input here.

No issues for me with usb port looseness or cable disconnects. Solid connections with my setup. I had checked for that, wiggled the cable etc. Gone over some nasty potholes to....
Connection issues on PC, seen that, usually a damaged/worn or poorly made port or cable.

 

[speedingcheetah]

*When I play these files in vlc they stop short of the end by about 2 to 3 secs.
Interestingly when I play other Viofo videos in vlc the files often end at 59 seconds and not the 60 seconds that they should do.

Doing some research the problem may be due to buffers not flushing completely. Of course it could also be a million other reasons.

I just thought to try playing back the videos using VIOFO's own video player, I had forgotten it existed. lol.

What do you know.
The video files that ffmpeg flags to have error, stops 2 sec before they are supposed to and will not continue playback to show those last 2 secs. This is the final video files that are active just as i shut off my car when i parked at the Post Office that trip.
It does this for each channel if i play back the single channel video file, or use the 3ch multi-playback view mode.

So, i gather, the dash cam has a 2 sec buffer, and that is what needs to be written to disk when power is cut.

EDIT: and TLDR / summary of my findings up to this point.

With this added information. I very much feel the cause i 100% one of two things, or a mix of both perhaps.
The cameras firmware is not well optimized enough or has a bug that it is not fully flushing out its record buffer to the ssd when power loss is detected.
There may be a available power issue too, the caps can not provide enough powered time to complete this function. However, seeing as the behavior still happens when i used a much lower power draw usb flash drive connected to the USB C ssd port, either this is not the main cause, or there just is so little capacity left that it would affect any external device connected, no matter how low a power draw it has.

As far a power limits go, its too bad that the ssd enclosure i had tried with the cam, did not work. As it has Power Loss Protection and had its own internal caps to keep the drive powered for about 10secs after power loss. However, the A329S even in single channel model, would just hard crash and power off after less than 1 min in use, when that enclosure was in use.

I wonder if a Active USB cable would be just enough to address the possible power issue. If the ssd is fully loosing power before the camera does, having a few more ms of power to the ssd may be all it needs. Maybe the Active cable can accomplish that? (EDIT: upon more research, i am thinking not, since "Active" Extension cables are more signal amplifier than they are any sort of capacitor ability.) (EDIT2: Yea. Nope. I did a test on PC with that usb power meter to simulate in car. Had to use adapters with my A to A usb 2.0 extension cable though. So, C to A on the pc side, then A to C cable at the Active A end of the cable. Voltage drop to 4.3V and the meter glitched out during read test (flashing white screen). Drive slowed as well. so, not gonna bother trying adding in a Active cable in car. )


But, if the cam itself is loosing power fully, and it is the one that is failing to flush its cache to the ssd regardless of ssd powered state...then, i do not see a way to address that, aside from manually stopping recording, then manually power off before power is cut.
Or, VIOFO maybe just needs to improve their firmware to be more efficient and faster.

 

[viofo]

I just thought to try playing back the videos using VIOFO's own video player, I had forgotten it existed. lol.

What do you know.
The video files that ffmpeg flags to have error, stops 2 sec before they are supposed to and will not continue playback to show those last 2 secs. This is the final video files that are active just as i shut off my car when i parked at the Post Office that trip.
It does this for each channel if i play back the single channel video file, or use the 3ch multi-playback view mode.

So, i gather, the dash cam has a 2 sec buffer, and that is what needs to be written to disk when power is cut.

View attachment 86015


EDIT:

With this added information. I very much feel the cause i 100% one of two things, or a mix of both perhaps.
The cameras firmware is not well optimized enough or has a bug that it is not fully flushing out its record buffer to the ssd when power loss is detected.
There may be a available power issue too, the caps can not provide enough powered time to complete this function. However, seeing as the behavior still happens when i used a much lower power draw usb flash drive connected to the USB C ssd port, either this is not the main cause, or there just is so little capacity left that it would affect any external device connected, no matter how low a power draw it has.

As far a power limits go, its too bad that the ssd enclosure i had tried with the cam, did not work. As it has Power Loss Protection and had its own internal caps to keep the drive powered for about 10secs after power loss. However, the A329S even in single channel model, would just hard crash and power off after less than 1 min in use, when that enclosure was in use.

I wonder if a Active USB cable would be just enough to address the possible power issue. If the ssd is fully loosing power before the camera does, having a few more ms of power to the ssd may be all it needs. Maybe the Active cable can accomplish that? (EDIT: upon more research, i am thinking not, since "Active" Extension cables are more signal amplifier than they are any sort of capacitor ability.) (EDIT2: Yea. Nope. I did a test on PC with that usb power meter to simulate in car. Had to use adapters with my A to A usb 2.0 extension cable though. So, C to A on the pc side, then A to C cable at the Active A end of the cable. Voltage drop to 4.3V and the meter glitched out during read test (flashing white screen). Drive slowed as well. so, not gonna bother trying adding in a Active cable in car. )


But, if the cam itself is loosing power fully, and it is the one that is failing to flush its cache to the ssd regardless of ssd powered state...then, i do not see a way to address that, aside from manually stopping recording, then manually power off before power is cut.
Or, VIOFO maybe just needs to improve their firmware to be more efficient and faster.

I am folloing this post, but not checked each post carefully, may I know how do you power on the dascham, do you use the hardwire cable or not?

BTW, the VIOFO PC player will also support video muxing and exporting in the near future.

 

[speedingcheetah]

I am folloing this post, but not checked each post carefully, may I know how do you power on the dascham, do you use the hardwire cable or not?

BTW, the VIOFO PC player will also support video muxing and exporting in the near future.

Powered via the USB Cig adapter and USB cable that is included with the camera connected to my cars 12V accessory port (which looses power when ignition is turned off.
My power meter tests seem to show that power flow is good and no starvation issues.

EDIT: Using hardware kit would be less optimal in my case. As the incoming power run to the kit itself would be longer than using the CIG adapter directly which is only a few feet from the camera inside the vehicle. My vehicles fuse box is located at the very front of the engine bay, driver side, next to the cars 12V battery. There is no internal cabin fuse box. I also would have to punch a hole through the firewall, not something i am comfortable with doing, otherwise, snake the input power cables inbetween the drivers door frame and body of car through the outer quarter trim panel and into the engine bay. Adding even more a cable run to do that and the added stress of the door possibly pinching the power cables.
Only other option is wiring the hardware kit with a cig plug at the end, and plugging it into the cig port i am using currently. But, unless the Hardware Kit itself is superior in providing power to the cam vs the included CIG plug to USB adapter, i see no reason to try this.

 

[viofo]

If using as an SSD, it is better to use the hardwire cable, otherwise it may cause the camera not to shut down correctly.

 

[speedingcheetah]

If using as an SSD, it is better to use the hardwire cable, otherwise it may cause the camera not to shut down correctly.

Could you explain this? How is the hardware cable any different power supply wise vs USB power adapter?
Does it have a power conditioner or a capacitor of some sort in it?

Or, i surmise you are referring to the "normal" operation mode of the Hardware Kit, where constant power is always provided to the cam, since it is to supposed be connected to a always active power source, with the signal lead triggering Parking/Low Power mode. And in that scenario, the cam senses low voltage, or, reaches its timer setting, and shuts its self down, vs experiencing a immediate power cut.

SSD functions perfectly fine in all functions except for shutdown. It is only the last 2 secs of video that needs to be fixed.
If the cam can complete its shutdown operations just fine for internal sd card, then it should be able to for attached ssd, when the power is cut.

I will have the hardware kit soon enough, however, if i attempt to use it, would be on a switched circuit or connected to the Cig plug port.
I do not want or need the cam to be connected to constant power circuit. The cam shall be powered when car is on, and no power to it when car is off.
I can not afford even the slightest addition of parasitic drain.

The only possible alternative option, would be if i had a dash cam battery pack to use, where it supplies battery power to the cam for a short time after car is off.
Also in that case, again, i would wire the battery pack to cig plug outlet, for it to only charge while car was on.
I have no need to full time, multi week long recording or overnight recording.
Would be nice to have "parking recording" for a short time, for times when i am out running errands, but it is not a concern for me overall.

What is a concern for me, is the file data corruption/missing 2 secs of video that is happening with SSD when the cam loses power.
I have been successful in mitigating that, by using the Bluetooth remote to trigger a remote Power Off, then turn off car, but, that is kinda annoying and tedious a thing to do and i feel it should not be necessary at all, especially for a flagship model and top $ cost.