griff / metaz

Two letters better than MetaX
https://metaz.maven-group.org/
MIT License
411 stars 56 forks source link

Opening movie returns AtomicParsley code 2 #272

Closed andyrings closed 1 year ago

andyrings commented 1 year ago

"Failed to process file 'Star Wars VHS Widescreen 03-08-23.mov'. AtomicParsley failed with exit code 2"

I'd be glad to send the file itself to someone to see what's going on. Nothing out of the ordinary, a file created with HandBrake on MacOS Ventura. Never ran into this before.

dagronf commented 1 year ago

A quick look through the AtomicParsley code shows the following two cases where it can fail with error 2

  1. "AtomicParsley error: unsupported MPEG-4 file brand found '%s'\n",
  2. "AtomicParsley error: Quicktime movie files are not supported.\n");

Both of these cases seem to indicate that the movie file type isn't supported. I noticed that the file you've put into the issue has the extension .mov (which is a quicktime movie file)...

Could you try re-encoding the file (using Handbrake) to an mp4 format instead and see if it works in MetaZ?

andyrings commented 1 year ago

Yeah, that was the problem. I accidentally grabbed a .mov version of the video file and not the .mp4 version.

All is well.


Andy Ringsmuth 5609 Harding Drive Lincoln, NE 68521-5831 (402) 202-1230 @.***

On Mar 9, 2023, at 6:21 PM, Darren Ford @.***> wrote:

A quick look through the AtomicParsley code shows the following two cases where it can fail with error 2 • "AtomicParsley error: unsupported MPEG-4 file brand found '%s'\n", • "AtomicParsley error: Quicktime movie files are not supported.\n"); Both of these cases seem to indicate that the movie file type isn't supported. I noticed that the file you've put into the issue has the extension .mov (which is a quicktime movie file)... Could you try re-encoding the file (using Handbrake) to an mp4 format instead and see if it works in MetaZ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>