Colin Mcfadden
Forum Replies Created
-
Hi there – you need to be running at least ClipWrap 2.5.2 on Mountain Lion. It sounds like you’ve got an older version.
Just download a fresh copy from: https://www.divergentmedia.com/filedownload/clipwrap
-Colin
support@divergentmedia.com -
That’s an interesting idea – any chance you’d be able to pass us a sample file with a known user string set? Shoot me an email at support@divergentmedia.com and I’ll give you an upload address.
We often get sample footage without any details on how the camera was setup, and metadata isn’t standardized in the spec, so we have to do reverse engineering – if we don’t know the string we’re looking for, that gets far more problematic!
-Colin
-
It’s hard to say for sure, but two things spring to mind that might be described as “warbles” – interlacing artifacts, or some sort of moire from downressing. Since dvcpro (assuming your content is 1080) is only 1280×1080 internally, you’re scaling your 1920 wide content down to 1280. That could potentially introduce some scaling artifacts.
Additionally, interlaced content being treated as progressive can sometimes look warbly, especially when further downrezzed to SD. It may be that whatever did your dvd encodes didn’t tread the dvcprohd content as interlaced properly?
In any case, feel free to shoot us an email at support@divergentmedia.com if you want to dig in further.
-Colin
-
Hey Nate – I’m one of the developers of ClipWrap, thought I’d chime in here.
The way spanning works, the split happens at a pretty low level. The camera hits the max byte limit for a file size and just starts a new file – it doesn’t pay any attention to where that split falls. The problem is that the split will almost always fall somewhere in the middle of a GOP. If the files aren’t recombined *before* transcoding, you’ll have a partial gop at the end of one file, and at the start of the next. Since GOPs needs to be complete to be reconstructed, both GOPs get tossed, and you get the missing data.
When you join files in ClipWrap, we do the join before the transcode, which means the split GOP is reconstructed and you shouldn’t have issues.
When people have sync issues during joins, it’s almost always because they’ve joined at least one file that wasn’t actually part of the split during the record. You end up mashing a complete gop and a partial gop together, which throws everything off.
If you drop a complete BDMV (or AVCHD) folder into clipwrap, instead of individual MTS files, we’ll read the metadata from the card and automatically detect which files were spanned during record. That lets us recombine them the way the camera thinks they should be combined. (if that doesn’t happen, let us know)
If you do that and still have sync issues, drop me a line at dmsupport@divergentmedia.com and we can dig into it.
-Colin
-
… or maybe he didn’t have rights to the copyrighted music he used?
-
This is relatively accurate.
-
Hi Andy – If you shoot us an email at dmsupport@divergentmedia.com we can give you a hand tracking that down. We can work on replicating your test setup to see what might be going on.
-
(Sony Europe)
You need to sign up for an account to be able to download from the support section, but it looks like they have the operation manual for the DVW-A500P, as well as a supplement.
Note – Pop-up blocking (for me at least) keeps the downloads from working on this site.