You can also click and drag cameras to reposition them.īlue Iris can stream any camera or group using the HLS protocol. Then, right click any camera to access a menu of options to configure the group layout. In the local console, choose the desired group and click the "Edit Layout" button to the right of the group selection dropdown list. Control of the group frame's aspect ratio will be unavailable if you have configured a fixed aspect ratio for the group within Blue Iris's local console. Here, you can force a specific aspect ratio for the group frame, adjust the streaming resolution limit to improve quality or save CPU cycles, or toggle features like the camera labels and borders. Right-click the group video in UI3, and choose "Group Settings". If you wish to adjust this behavior, there are a few ways to do it: In UI3 Since Blue Iris 5.5, group video streams have a dynamic resolution intended to best-fit within the viewport you have available. To change the order of your cameras, you must enter "Edit Layout" mode in Blue Iris's local console, and drag cameras around. #/Users/steven/Documents/TrailCameras/Working/TrailUp.20230210_3 is unable to directly control the order or exact positioning of your cameras. I was using a different automator app to truncate the filename anyway (so that I could keep re-using the same Resolve project as a template) so this doesn't make my workflow a whole lot worse: My workaround was to write a little drag-and-drop Automator app that truncates the excess part of the filename and then transcodes. Thanks for confirming that I'm not crazy. Shutter Encoder or ffmpeg can do it for you. But I simply wouldn't care, since your clip has massive VFR (variable frame rate), which can cause problems in DR anyway.Ĭonvert to a mezzanine codec and conform to the frame rate you want to use in your project. Uli Plank wrote:I can confirm your observations here. concealing 50 DC, 50 AC, 50 MV errors in P frame.error while decoding MB 161 121, bytestream -6.concealing 50 DC, 50 AC, 50 MV errors in I frame.error while decoding MB 161 121, bytestream -5.The errors are here, and the details are attached: ffprobe reports errors in the un-transcoded files, but not in the re-encoded files.VLC with Hardware Deocoding un-checked wil play them correctly from Frame 1.VLC with Hardware Deocoding checked wil play them, but the first few frames display incorrectly as a gray “snow” field before eventually rendering correctly.Finder: Cmd-I will display a thumbnail for the “bad” MP4s, and even play them back, but:.Symptoms and workarounds are the same as they were last year: If it has been re-encoded, then it will play back properly. If the MP4 has NOT been re-encoded, it won’t play properly. Whether downloaded from the BI console and then copied to my Mac or whether downloaded via Chrome/UI3 on my Mac, the behavior is the same. These are directly from the Clips view, with no edits to the start/stop points, so they should all be the exact same period of time. Here’s the direct export from UI3 without re-encoding:Īnd here’s from UI3 with the BI Re-encode video to H.264 checked: Here’s with re-encoding from the Blue Iris console on the BI PC: Here’s the direct export from the Blue Iris console on the BI PC, without re-encoding: The camera’s settings are plain h.264 (per the attached screen capture), and I’ve attached the exported camera config from BI as well. It’s great! Except that most applications still can’t read the direct exports from BI. That ‘Book died, so now I have a spiffy new M2 Max machine running macOS 13.0. I was limping along with my Intel MacBook until very recently, so it wasn’t a problem. Thanks for the reply, and sorry for the tardiness. The Blue Iris developer doesn't have an M1 Mac. I even tried changing the camera settings so that it outputs h.265 instead of h.264, but the h.265 file behaves the same way. VLC's behavior gives me some hope, because it eventually finds its way. I'm guessing these are all symptoms of the same problem, because they're presumably using the same macOS libraries. DaVinci Resolve shows the media as being Offline.VLC shows a gray screen with some evidence of something, for about a second, and then renders the remainder of the file correctly (see screen capture at bottom of post).Quicklook shows just a gray screen and a spinner that never turns into anything.I can open them in Quicklook, QuickTime Player, VLC 3.0.16, or DaVinci Resolve 17.4.5, and they look just as I expect them to. They all work fine on my ancient mid-2014 Intel MBP/10.14.6. I'm exporting security camera MP4s from Blue Iris, such as this this 3 MB sample, and I'm having trouble playing them back (and therefore editing them in DaVinci Resolve) on my M1 Mini/12.3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |