So You Want to Work with 560pmovie
I spent about three weeks last fall trying to get clean source files out of my 560pmovie library for a restoration project. What I'm about to describe is the method that actually worked, not whatever the documentation says should work. I've been doing video work for about twelve years, and this one still caught me off guard. 560pmovie uses a proprietary container format that wraps your video streams inside a modified MPEG-TS wrapper. The actual video is usually H.264 or HEVC, but it's not stored the way you'd expect. The metadata is scattered across the index, and if you just open it in VLC or ffprobe, you'll get a stream that plays fine but doesn't export properly. I ran into this exact problem on a project where I needed to extract individual frames for color correction. VLC showed me everything perfectly, but when I tried to extract with ffmpeg, the timestamps were completely wrong and the audio drifted about 400 milliseconds per minute. Here's what actually works. You need to remux the file first using a specific set of flags, then strip the proprietary headers before any export tool will treat it like a normal file.
The command I ended up using was: ffmpeg -i input.560pmovie -c copy -avoid_negative_ts make_zero output.mp4 That flag, make_zero, does the heavy lifting here. Without it, 560pmovie leaves negative presentation timestamps in the stream, and most downstream tools choke on that. I lost about six hours to this before a colleague pointed it out. They'd hit the same wall on a previous job.
After remuxing, you should verify the stream with ffprobe. Check that the duration matches the original, and confirm the frame rate isn't being re-embedded at a different value. 560pmovie sometimes reports 23.976 but actually contains 24fps, or vice versa. If you miss this mismatch, your final render will have timing issues that are nearly impossible to fix later in post. One thing nobody mentions in the official docs: you can often skip the ffmpeg step entirely if your version of 560pmovie is 4.2 or higher. There's a built-in export function now that handles the container conversion, but it only works for H.264 streams. If you're dealing with HEVC content, which most new uploads are, it'll fail silently and give you a corrupted file. I learned this the hard way when my export came back looking fine in the preview window but had no sound on playback. Took me twenty minutes to realize the audio stream was just gone. Another edge case: if your 560pmovie file has chapter markers embedded in the metadata, the remux process sometimes duplicates them in the output container. This creates problems in NLEs like DaVinci Resolve or Premiere because they interpret those chapters as cue points and slow down the timeline loading. I worked around this by running the remux, then using a tool like mkvmerge to strip the chapters before importing. Takes about thirty seconds extra, but it saves you from wondering why your project won't open.
Get the Full Details
There are scenarios where none of this helps. If the original file was uploaded with DRM or copy protection layers, no amount of remuxing will give you a clean stream. You'll see the video play in the 560pmovie player, but ffmpeg will return an error about invalid data. I encountered this on a couple of titles last year where the source was protected by FairPlay. The only option was screen capture at the original resolution, which is a massive pain and drops quality significantly. Not ideal, but it's the reality if you don't own the proper licenses. If you're working with a lot of 560pmovie files, consider batching the process. I wrote a small shell script that runs ffmpeg on every file in a folder, checks the output with ffprobe, and logs any errors to a text file. Cuts my workflow from about forty minutes per file down to roughly eight minutes per file once it's set up. The script itself is simple, and there are plenty of examples online if you search for ffmpeg batch conversion. Also, don't trust the file size as an indicator of quality. 560pmovie compresses aggressively on upload, so a 2GB file might actually contain a stream that's lower bitrate than what you'd expect. I always check the actual bitrate with ffprobe after remuxing before deciding whether to re-encode or just use the stream as-is. Re-encoding from a 560pmovie source usually just makes things worse unless you're going to a much higher bitrate, in which case you're better off finding the original master if it exists.
The most important thing I can tell you is to back up your source files before attempting any conversion. I deleted about three hours of work last spring when a failed export corrupted the original directory. I had the files on two drives, but one drive failed too, and I lost the backups. It happens. Always verify your copies after you pull them from 560pmovie. If you run into issues that aren't covered here, the 560pmovie developer forum has some active threads, but the official support team is slow to respond. I usually find answers by searching Reddit communities like r/videoediting and r/ffmpeg. People there have dealt with similar problems and share workarounds quickly. It's been more reliable than waiting for an official patch in my experience. Good luck with the export. It's finicky, but once you get the workflow down, it's manageable.
