Video trouble with cam v4

I know when you record from SD to the phone the file size increases a lot, not sure if cloud is like that (I would hope “download” would mean literally that). But I was guessing that when you do “share” it compresses the video further since most email/sms has size limits. May not be a correct guess though. However if those videos work and the ones in your phone’s gallery don’t, that implies some sort of conversion/re-compression has been done.

Apparently that is not without issue, in a couple other threads people have been having trouble getting the joiner and editing programs to work with the v4 at least, related to the fact that it is using G.711 for audio.

I’ve seen that on a couple of videos posted to my city’s facebook. Was wondering when that got added. If that only happens using the “share” feature then it is definitely doing something to the video before sharing it.

I was guessing the person was sharing cloud clips and maybe those all have that at the end, but if it does it with SD card too that’s BS (well it’s BS either way).

I have the logo turned off too. If they want to pay me to advertise, I’ll reconsider.

Might want to finish the sentence, it sounds a bit Deliverance - esque

I had the same issues. Tried everything but no real solution.

So, I finally solved my problem replacing my V4s with 2 OGs I bought Cyber Monday for $9.99 each (free shipping).

I use the V4s as spotter cams.

I don’t want to be seen as someone who promotes violence, but Old Yeller comes to mind :wink:

I didn’t even get into microSD recordings because that didn’t seem to be related to @henriek’s issue, at least as I understand it. As I documented above, though, the Cam v4 clip generated via the “share” feature vs. the “download” feature is ~2 seconds longer and significantly larger, so I think that feature has a problem on at least some camera models. The effect isn’t as drastic with the Cam OG Telephoto that I tested for comparison.

That’s certainly not what the evidence demonstrates. In my test data, the “share” file was larger than the “download” file with both cameras.

This certainly seems to be the case, and I wonder if the process that’s adding that has a serious flaw that’s contributing to the issue as initially described both in this topic and the others I mentioned earlier. I don’t know the answer, but it seems like something Wyze should be looking at if/when fix-it-friday resumes, if not before.

Well we know it is adding that “captured by wyze” at the end, that’s probably the 2 seconds. But why that would cause it to not play on some devices (if it isn’t re-encoding the whole thing) who knows. Maybe whatever is tacking on that 2 seconds isn’t stitching it in right.

It is. That’s part of what I’m saying.

This is also what I’m saying. What, exactly, is happening on the technical side that’s introducing the problem, though, is the big unknown for me. Here’s some more data (using the same files as noted above) that seems to show the ~2-second “Captured by…” tag is the problem (or at least related somehow):

  •  Share video from Cam v4 played in Google Chrome (PC): Browser shows playback controls for a 15-second video. Playback shows no video at all, and when the counter gets to the 13-second mark it immediately jumps to the 15-second mark and ends playback. :negative_squared_cross_mark:
  •  Download video from Cam v4 played in Google Chrome (PC): Browser shows playback controls for a 13-second video, which plays normally. :white_check_mark:
  •  Share video from Cam OG Telephoto played in Google Chrome (PC): Browser shows playback controls for a 14-second video. Playback shows no video at all, and when the counter gets to the 11-second mark it immediately jumps to the 14-second mark and ends playback. :negative_squared_cross_mark:
  •  Download video from Cam OG Telephoto played in Google Chrome (PC): Browser shows playback controls for a 11-second video, which plays normally. :white_check_mark:
  •  Share video from Cam v4 played in Mozilla Firefox (PC): Browser shows playback controls for a 13-second video. This is the same video that Chrome said was 15 seconds! Playback shows no video at all. :negative_squared_cross_mark:
  •  Download video from Cam v4 played in Mozilla Firefox (PC): Browser shows playback controls for a 13-second video, which plays normally. :white_check_mark:
  •  Share video from Cam OG Telephoto played in Mozilla Firefox (PC): Browser shows playback controls for a 12-second video. This is the same video that Chrome said was 14 seconds! Playback shows no video at all. :negative_squared_cross_mark:
  •  Download video from Cam OG Telephoto played in Mozilla Firefox (PC): Browser shows playback controls for a 12-second video, which plays normally. :white_check_mark:
  • VLC plays all four videos as expected, including the “Captured by…” tags generated in the  Share videos.

Observations:

  • I’m not surprised at VLC’s performance, because I think it’s robust enough to correct for problems in some videos where errors in packaging the video prevent playback using other common tools.
  • Other common tools that can play videos (i.e., browsers) are clearly struggling with event videos created via  Share but not with event videos created via  Download. This points to the problem being the  Share feature.
  • While suggesting that a user try different software for playback may be useful for troubleshooting, the user shouldn’t be expected to tell everyone that he or she shares videos with to also download another app just to see the video. Video playback should just work as expected across a variety of platforms, and Wyze needs to fix this. I think they should start by looking at the code (whether it’s in the app, on the server, or both) associated with the  Share feature. This should include giving the user a choice (an in-app option) regarding the addition of the “Captured by…” tag (which also seems associated with the problem).
  • Using the  Download feature, while it may require extra steps for the user in order to share the event video, is probably the best work-around at this point.

I have probably asked this before, can you as a Maven let Wyze employees know about this issue and that it needs fixing?

I’m still a Maven newbie and don’t have a direct contact for that, but I can say that I’ve reported this to Wyze outside the Forum and will explore another option for getting this issue some attention.

Thank you for the nudge on this!

That’s why we are here, to make the Wyze experience better for everyone.

1 Like

Agree :100:!

Yes I have same problem. It used to work or 1st day when I bought it. I am so fed up with Wyze. They must be doing something wrong but not sure. My App use to work before almost 3 upgrades before. Then it started slowing my phone. Freeze. delay. Then new version was released and still same. They changed some menu and made difficult to download clips. It goes to Album and not usual Photo album like before.

Now on Same phone Android 13 Downloads from V3 and OG works. But Except first V4 files now all downloads do not play. If I transfer the file to Adroind 4 then it plays on that phone.

What they heck you guys are changing Wyze. I have lost faith. Wyze need to fix on Android 13.

These are the last Two V4 I am buying from Wyze as I have no faith with these people. Bought them 8 days before.

I lost Wyze when they changed the screw size for wyze OG. What a stupid company to save $.50.

I really don’t think this issue is specific to a particular Android version. They’re doing something to the video files when the “Share” feature is invoked, and I’m trying to get some attention on this issue.

2 Likes

Soooo maybe get an iPhone. Just saying.
I’m
Kidding. I swear :pray:t3::wink:

I had iPhone just sold it in Dec end. really. Bout New Samsung and Pixel.
I got tired with ios updates every 10 days. Now only one iPad I have soon to be passed on or resold.

I agree something going on. I am installing all App on Samsung And Pixel And will test all files in exact same way. Like Whats app and sharing stuff. just to confirm sharing works fine on new ones.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.