Need help, video thumbnail and walmart dvr playback upside down

[cholla]

I meant to also put this one in post#26.
It is the larger resolution 1920x1089 done with the first code in #26.
I hope that btwarden will post the software he use I would like to see what I could do with it.

[jimdagys]

goba2026FF1920x1080.mkv (118.15 MB

In Walmart dvr, "unsupported file". I think the dvr issue with high resolution (1080) and high frame rate (59.xxx).
My limited computer ability so I can't do what you did, that is, you flipped the video upright in the dvr, without flipping the video in vlc/MPC-HC (which would have flipped the video upside down in vlc/MPC-HC).

[btwarden]

Tried to make the mov a bit more blu-ray spec compliant.

ffmpeg.exe -i goba2026.MOV -flags +ildct -crf 19 -r 29.97 -b:a 192k goba2026test.MOV

[cholla]

@ jimdagys,
I have came to the conclusion that Windows 7 & maybe newer does not have a software that can convert the original "goba2026.MOV" to an upright 1920x1080 that will play on the Walmart DVR.
I believe the "goba2026.MOV" was created in the iPhone that took the video or was created with a QT or Quicktime software that is only for a Mac computer.
I have not been able to find a QT software that works with Windows 7. I downloaded & tried the suggested "QuickTime 7.7.9 for Windows".
I installed it in a virtual environment & that may be the reason it did not work.
It is supposed to be a security risk so I do not want to install it on my Windows 7 in normal mode.

If any member knows how to do the conversion of the original "goba2026.MOV" on any Windows OS to an upright 1920x1080 that will play on the Walmart DVR;then I hope they will post it.

Since btwarden is trying the "more blu-ray spec compliant" route.
Does the Walmart DVR play blu rays ?

[jimdagys]

btwarden

goba2026test.MOV (60.94 MB

That 1080 resolution plays correctly in all my media plays including Walmart dvr. However, I noticed you reduced the frame rate from 59 to 29.

I found an easy way to solve this problem. Jagabo in post 4 had the right idea, but I didn't understand the details from his brief summary. Also ProWo in post 17 had the right idea (though I didn't realize it at the time) to eliminate the 180 degree rotate flag. Likely the original recording was made with a phone held upside down. The phone realized this and so added a 180 degree rotate flag in the metadata so that the video would play upright on most media players. However, as was noted in above posts, my Walmart dvr didn't recognize the rotate flag and so played the video upside down. So the first step is to eliminate the rotate flag, which is explained in post 17. When the rotate flag is eliminated, all media players will play the video upside down. Then the video has to be re-encoded to rotate it 180 degrees to get the video back to correct orientation. I googled and found this which worked for me, although very slow- it took 30 minutes to re-encode the 20 second video.

ffmpeg -i input.mov -vf "transpose=1,transpose=1" -crf 20 -c:a copy rotated_video.mp4

The result, as expected wouldn't play in the dvr, said "unsupported file". Last step, I had to reduce the video resolution from 1080 to 720. I used Vidcoder for this and the result played fine in the Walmart dvr and all my media players. One small mystery is why the Walmart dvr played the original file (high resolution 1080, high frame rate 59), although video upside down.

[cholla]

The code I posted ion # 26 does the same & some additional.
I had been using the Transpose Parameter in ffmpeg in most of the conversions I did in x264.
It did not work in the DVR because I was not changing the resolution of the original .mov file.
Transpose Parameter
0: Rotate 90 degrees counter-clockwise and flip vertically.
1: Rotate 90 degrees clockwise.
2: Rotate 90 degrees counter-clockwise.
3: Rotate 90 degrees clockwise and flip vertically.
The only difference in "transpose=1,transpose=1" & "transpose=2,transpose=2" is the direction of the rotation.

-display_rotation:v:0 0 does this:
Resets accidental orientation: Fixes files recorded sideways or upside down on smartphones by wiping out embedded rotational flags
.Zero quality loss: Because you pair it with -c copy (stream copy),
FFmpeg simply toggles a metadata flag instead of modifying and rendering the video frames.
Your version of ffmpeg did not work with the -display_rotation:v:0 0 & it appears it is not necessary.
So it can be left out.

-vf scale=1280:720 sets the resolution. So you do not need to use Vidcoder for this all in one step.

I will give the code you posted a test with the resolution change added.
I'm curious to see what the video stats are.

[jimdagys]

cholla
If you have a simple, complete exact ffmpeg code (that works with my old ffmpeg) that will do the transposing for my dvr without quality loss (no re-encoding), please post. I still want to reduce the resolution with vidcoder, not ffmpeg.

[btwarden]

ffmpeg automatically rotates the video according to file metadata by default. So there is no need to eliminate the rotation metadata or to transpose the video.

The upside down video is a VFR quicktime. The video has a variable framerate.
Because of the variable framerate the DVR is able to play this video. The DVR is altering the framerate on the fly. Maybe you van check this if the DVR can show playback information on screen.

When you rotate the video with ffmpeg the resulting video end up with constant framerate.
Your DVR will likely follow the bly-ray specifications for playback.

So to make the rotated video playback on your DVR you can alter the framerate or the resolution.
- keep the framerate at 59.94 fps => change resolution from 1920x1080 to 1280x720 (see chart below)
- keep resolution at 1920x1080 => change framerate to 29,97i or 25i or 24p or 23,976p but keep the same resolution

[Attachment 93046 - Click to enlarge]

I chose to keep the resolution at 1920x1080 and changed to framerate to 29,97. This framerate is almost halve to original framerate to minimize jittery playback.
In order to make this blu-ray compliant the video has to be interlaced (see chart)

ffmpeg for 1920x1080i@29,97

ffmpeg.exe -i goba2026.MOV -flags +ildct -crf 19 -r 29.97 -b:a 192k goba2026test.MOV

ffmpeg for 1280x720p@59,94

ffmpeg.exe -i goba2026.MOV -vf scale=-2:720 -r 59.94 -crf 19 -b:a 192k goba2026test.MOV

[btwarden]

cholla
the transposing for my dvr without quality loss (no re-encoding), please post. I still want to reduce the resolution with vidcoder, not ffmpeg.

The video has to be rotated, so the video has to be re-encoded. If all devices (software and hardware) were honoring the rotation metadata then the video played fine without the need to rotate and re-encode.

Why do you want to sacrifice screen resolution over framerate?

It may be simpler to use an app on your phone to rotate the video and then export for playback on your DVR.

[ProWo]

@OP
Try this one

[btwarden]

I still want to reduce the resolution with vidcoder, not ffmpeg.

Vidcoder uses handbrake as the encoder. Why not use handbrake directly to rotate and reduce the resolution in one go?

[btwarden]

Is your DVR able to play HEVC/H.265 (Ultra HD Blu-ray) encoded files ?

Try this one. H265 encoded 1920×1080p @ 59.94.

[jimdagys]

Is your DVR able to play HEVC/H.265

Walmart Dvr does not play h265. If I get a h265 video, I use vidcoder on a fast computer to change to h264.

ProWo

Try this one
goba2026.mov (55.71 MB

Plays fine on Dvr, video is 29.xx frame rate.

[cholla]

See if this one will play in your DVR. It is 1920x1080. Frame Rate is 59.xx
The hard part was keeping it Variable in both Audio & Video like the original .mov file.
The best I could do with the Audio is 124 kb/s aac.
When I tried a higher bit rate the result was always Constant on the Audio bit rate.

[jimdagys]

goba2026AV.mp4 (118.08 MB

Intermittent sound (choppy) in Walmart dvr.

[cholla]

goba2026AV.mp4 (118.08 MB

Intermittent sound (choppy) in Walmart dvr.

Did the video play OK ?

I can add better sound but it will have a constant bit rate.
Typically I would never add an audio track with as low of a bit rate as I used with the last .mp4.
It was the only way I could keep it variable .
Is there an audio format your DVR plays well ?

[jimdagys]

Did the video play OK ?

Video stutter noticeable: video/audio sync not good. Easy to determine video/audio sync at end of video where the keyboard chords are pressed down.
I don't recall any audio problems in the past using the dvr. Walmart has been selling these in-store for over 15 years.
Price today is about $40. They are marketed as "digital converter", which allows old crt type TVs to receive today's over the air broadcast signals. They also record (to usb stick) any TV program. Has timer record, just like vcr. The recordings can be played back on the dvr or any computer.

[cholla]

It appears that at least Windows 7 can not do anything that will work for a 1920x1080 video that does not stutter.
If the video had played I believe I could have synced the audio with ffmpeg.
It would have required a second code for the sync.
The only place in this short video that you can check the sync is the portable keyboard player.
I assume that if you get this video working you have more & longer ones that the sync would matter more.

On my computer & set top BD player the video is in sync & does not stutter.
So I have no way to check the video before I post it.
VLC & MPC-BE & MPC-HC all play the original upright.
Zoom & DVDFAB Pro player v3 play it upside down so I have a way to check that.

I will state this again I believe the problem is this from MediaInfo:
Writing application: ProCamera 26.2.2
Writing library: Apple QuickTime
Writing hardware: Apple iPhone SE 2022
That the problem can only be corrected with a Mac computer that still has Apple QuickTime.
Or the iPhone that took the video. I believe one or both of those could rotate the video & keep the resolution.

I will check out the Walmart DVR .It sounds like a good price but I really do not need it.
I remember buying a analog to digital converter when the TV signal was first changed.
It was a RCA & only did TV.I believe it cost more than $40.00 .

This is what ffprobe finds:
A lot of apple quicktime.

  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2026-07-06T20:27:49.00000
    com.apple.quicktime.creationdate: 2026-06-2
    com.apple.quicktime.location.ISO6709: +41.0
    com.apple.quicktime.software: ProCamera 26.
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: iPhone SE 2022
  Duration: 00:00:21.88, start: 0.000000, bitra
  Stream #0:0[0x1](und): Audio: aac (LC) (mp4a
    Metadata:
      creation_time   : 2026-07-06T20:27:49.000
      handler_name    : Core Media Audio
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](und): Video: h264 (High) (av
    Metadata:
      creation_time   : 2026-07-06T20:27:49.000
      handler_name    : Core Media Video
      vendor_id       : [0][0][0][0]
      encoder         : H.264
    Side data:
      Display Matrix: rotation of -180.00 degre
  Stream #0:2[0x3](und): Data: none (mebx / 0x7
    Metadata:
      creation_time   : 2026-07-06T20:27:49.000
      handler_name    : Core Media Metadata
Unsupported codec with id 0 for input stream 2

This is what Google AI has to report about the message at the end:

The error Unsupported codec with id 0 for input stream 2 occurs because ffprobe has encountered an unrecognized data or metadata track—such as a GoPro/Apple timecode track (tmcd), camera telemetry, or non-standard subtitles—and throws a non-zero exit code because it doesn't know how to decode it.While the video and audio tracks are usually perfectly fine, this warning causes automation scripts and wrappers (like Python or Ruby FFmpeg libraries) to crash.

[cholla]

I wanted to keep this separate.
I looked up two of the Walmart digital converters/DVRs:
Is the one you have either of these?
Core Innovations CTCB105 Over the Air Digital TV Converter & DVR Box or
Mediasonic ATSC Digital TV Converter Box with TV Tuner, TV Recording, USB Multimedia Function, HDMI Output, by Mediasonic HomeWorx (HW250STB)
If it is not one of these . Could you post the brand & model ?

I checked the manuals for both. Neither list .mp4 or .mov in the "Supported file" list.
Both list .mkv . That is probably the best format to use with either of these DVRs.

[jimdagys]

Is the one you have either of these?
Core Innovations CTCB105 Over the Air Digital TV Converter & DVR Box or
Mediasonic ATSC Digital TV Converter Box with TV Tuner, TV Recording, USB Multimedia Function, HDMI Output, by Mediasonic HomeWorx (HW250STB)
If it is not one of these . Could you post the brand & model ?

My dvr is Ematic AT103B. Walmart stopped selling these about 6 years ago. Now Walmart in-store sells the Core. The Core looks EXACTLY like the Ematic. My guess is that the two are identical, except for the name. You could buy the Core, play with it and return it if you don't want it.
Make sure you turn it off when done using it. The unit gets quite warm. Maybe retrofit a fan on it.

[cholla]

Walmart still sells the Ematic-AT103B just not in the store.
https://www.walmart.com/ip/Ematic-AT103B-Digital-Converter-Box-with-LED-Display-and-Re...ities/28505040
The Core looks identical but is about 10 dollars cheaper.

This is from the manual for the Ematic-AT103B:
Any other format should be "Unsupported". So now I know what formats to use.

[Attachment 93096 - Click to enlarge]

[btwarden]

From the manual Ematic-AT103B

[Attachment 93098 - Click to enlarge]

[cholla]

The manual is a bit confusing as to what the Ematic-AT103B can play.
If you look at the section I found & the section btwarden found.
Both are in the same manual.

Here are two more to try.
On my devices they do not "stutter & the video/audio sync is correct
Like in the original there are a couple of places that have "camera movement".
Where the camera was moved fast & did not keep up.

[jimdagys]

mkv goba2026AV.mkv (118.16 MB
mkv goba2026VMTN.mkv (118.16

Both "unsupported file".

[btwarden]

Video with constant 60fps and a VBR version for you to try out

[The_Doman]

mkv goba2026AV.mkv (118.16 MB
mkv goba2026VMTN.mkv (118.16

Both "unsupported file".

Did you also try it with Avidemux?
With that you can easily experiment with some settings and formats.
Try these MP4/MKV versions i created using the older Avidemux 2.77 on a Windows 7 32bit system.
Also a MOV version using Avidemux 2.82, 2.77 does not support MOV export.

[cholla]

@ The_Doman,
The latest AviDemux version I have found for Windows 7 32-bit is 2.7.4 .
If you know of a download for 2.7.7 for Windows 7 32-bit would you send me a link.
I have read there is a newer version that is "build your own" but I believe it is 2.7.6 & Linux has to be used to compile it.

I am curious if jimdagys Ematic AT103B can play the videos you posted.
I have no explanation why the Ematic AT103B can play the original .mov file posted upside down at the 1920x1080 but no other conversion 1920x1080 conversion has played. The resolution seems to be the problem.

This is a 1280x720 that may play. But still might "stutter" on the Ematic AT103B.Specially at the 59 fps.

[The_Doman]

@ The_Doman,
The latest AviDemux version I have found for Windows 7 32-bit is 2.7.4 .
If you know of a download for 2.7.7 for Windows 7 32-bit would you send me a link.
I have read there is a newer version that is "build your own" but I believe it is 2.7.6 & Linux has to be used to compile it.

I just today googled/installed it for this topic.
The last version seems to be avidemux_2.7.7 r210228_win32.exe

Google: Avidemux last version windows 7 32 bit nightly
Google: avidemux_2.7.7 r210228_win32.exe
https://www.avidemux.org/nightly/win32/

[jimdagys]

goba2026@60fps.mov (57.13 MB
mov goba2026vbr.mov (56.51 MB

First file "unsupported file"
Second file plays, but video a little jerky and a little out of sync with audio

[cholla]

Thanks The_Doman,
The avidemux_2.7.7 r210228_win32.exe installed correctly on Windows 7 32-bit.

@ jimdagys , Did the 1280x720 goba2026AV.mkv play OK in your DVR ?