Files not passing vrecord policy check for FFV1 video #817
Comments
|
Hey @DSohl we had a change to the aspect ratio handling recently in vrecord. So now the video can be one of many slightly differing variants of 4/3 and 16/9. As a result I ultimately just removed the aspect ratio check from the mediaconch policy, but there was a lag between the feature being added and the check being removed, so your version of vrecord might be in the middle. Can you update the the vrecord released this week and retry? Or could you paste over /Users/medialab/Desktop/JPC/20240730/JPC_AV_01755/JPC_AV_01755_mediaconchreport.xml so we could take a look? |
|
Hi, @dericed - |
|
Hey @DSohl it looks like the matroska didn't finish writing properly. Normally the muxer writes all the audiovisual data and then goes back and adds the crc's and cues and some other data when it's finalizing it, but that last step didn't happen. How did you stop the recording? |
|
@dericed I've been stoppung the recording by hitting the esc key. |
|
@dericed A new maybe-related-maybe-not thing that I've started seeing this morning: when I start the vrecord GUI in the Mac terminal, I get this message: The GUI will open, and the UltraStudio 4K Extreme is listed as a device found. What's this mean? |
|
You can rewrap it with |
|
I truly appreciate your looking into this so quickly. Here's the log (and yeah, it's ffmpeg-dl) |
|
Hi @dericed and @DSohl, I'm having a very similar issue with vrecord 2024-07-09 (ffmpeg-dl). I'm using a Mac Studio (Apple M1 Max, Sonoma 14.6) with UltraStudio 4K Extreme 3. Running vrecord results in "no devices found" warning, as well as an error in the output below the video stream description (No such filter: ''), and then the policy check fails after the file is written. It looks to me like the mkv is finishing properly in the Media Conch report. I usually use q to quit or just close the video window. I put a test file with all the outputs here (unexpectedly getting an empty eia608 text and an scc file too) : https://drive.google.com/drive/folders/1cKx5SbVGIz2ab5PnR3tcORNwSJSsNE8t?usp=sharing Here is the Terminal output: |
|
HI, @dericed - the prompt you gave to rewrap the file was unsuccessful. Here's what I get: Did I do that wrong? like, am I being too literal by using "nice.mkv" |
|
you can name the output as you want, but you're missing the input flag. try |
|
@dericed @michaelangeletti @DSohl I am experiencing the same issues with the latest release of vrecord (2024-07-09). I'm running macOS Monterey 12.4 on a MacMini (M1, 2020) and using a Blackmagic UltraStudio HD Mini. Running vrecord -e results in "no devices found" warning. For all captures (regardless of ending the capture by exiting out of the playback window or setting a duration and letting it exit on its own), I receive an error in the output below the video stream description (No such filter: ''), and then the policy check fails after the file is written. It looks to me like the MKV is finishing properly in the MediaConch report, but the report looks a little wonky (randomly has According to the vrecord generated MediaConch report, it looks like the fails are happening in with the following rules:
When I run the same video through the Media Conch GUI using the example FFV1 MKV policy, it passes everything except the aspect ratio (which is likely due to what @dericed mentioned regarding the new recommended aspect ratio setting). But all of the other test that failed when vrecord ran them passed. I also noticed that the ffmpeg dependencies are stored in a different place than is mentioned here: Issue #788 (but maybe that's a separate issue/no longer where they are supposed to be). |
|
Checking in: are you still having these issues @michaelangeletti and @libbyhopfauf ? @dericed - I appreciate the rewrap directions, and it seems to be working. Any inkling where my setup's gone wrong? It'd be splendid if there's anything that I can do to remove that extra step. (cc: @BleakleyMcD ) |
|
Hi @DSohl ! This morning, I uninstalled BMD Desktop Video, vrecord and Homebrew, and reinstalled everything. I wanted to start fresh. I'm using vrecord 2024-08-23. I'm no longer getting 'no devices found', but files are still not passing the policy check: The set of files from my test are available here. |
|
Hi, @dericed - I ran @michaelangeletti how are you proceeding? Are you keeping the capture as your archival master copy, or remapping it? Or something else? |
|
@DSohl , for the time being, I'm keeping the files as they are, but I'm working on a limited collection of tapes that will get prepped for accessioning into our repository in the coming weeks. I may decide to re-wrap them in batches before accessioning. The missing crc values are a bummer, but the files still are still making it through the rest of the processes in our workflow without problems. But I am curious to know what it is about our installations that's causing it. |
|
Hey @DSohl, can you send /Users/medialab/Desktop/JPC/20240826/JPC_AV_01598/JPC_AV_01598_ffv1_mediaconchreport.xml. Also how are you going about stopping the recording? |
|
Here is mine, @dericed Like @libbyhopfauf , mine has |
|
@dericed I stop the recording via the esc key. Like @libbyhopfauf and @michaelangeletti, I've got several instances of Here's the sidecar files for the test recording I made the A.M. |
|
@DSohl and could you also go to the |
|
@dericed sure thing! |
|
hmmmm, and the terminal output when you run just |
|
≈:≈ /opt/homebrew/opt/ffmpegdecklink/bin/ffmpeg-dl Use -h to get full help or, even better, run 'man ffmpeg' |
|
This all seems right. Closing ffplay (via hitting the red-close-window button or via the ESC key), should send a SIGPIPE command to ffmpeg which will have it finalizing the container. Here's it's ending the write more abruptly, trying to think about why. Does closing ffplay via the red corner button finish differently? |
|
ESC and closing with the corner button yield the same results. |
|
I have a PR that I think might address this: #832 |
|
Same issues here...vrecord session ending with: Like @DSohl, @libbyhopfauf, & @michaelangeletti I have a couple instances of Here is the XML for the test I ran today TEST3min_BlackMagicFix.zip I was also getting the "No devices found" line on starting vrecord, but same as @michaelangeletti I uninstalled and then reinstalled the latest Blackmagic Desktop Video Setup. Then after going into System Preferences/Privacy & Security and "allowing" for Desktop Video to work, the "No Devices Found" message no longer appeared. |
|
Just tested #832 and it got rid of the FFV1 policy error |
|
Yay, IIUC this issue is still open as @DSohl has an instance where the recording process doesn't end correctly. |
|
Hey @DSohl can you |
|
@dericed - Hot dog! It's a success! Many thanks to everyone who chimed in. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Heya - since yesterday morning, every video capture I do gives me this message:
What're reasons that could cause these files to (may) not conform to digital preservation standards?
Maybe related, maybe unrelated, I ran brew update + upgrade before this started happening.
The text was updated successfully, but these errors were encountered: