Mync settings, copy clips from SD card

[trifo]

I just want to copy all clips from SD card to one folder with Mync, and long spaned clips to be joined in one... With default settings Mync make folder for every clip including subfolders from SD card???
Where to disable this stupidity?

[trifo]

https://1drv.ms/u/s!AuQpaXH8Re2Whh3IxB4LXnkHThgF

[David Clarke]

That is how Mync does it. If you copy with the EDIUS source browser instead it will put all the clips you decide to copy in one folder.

You can decide where EDIUS puts the clips by setting the "file transfer folder" before you import them. Go to system settings - source browser and choose a customer folder before importing clips. When you want to import to a different directory go here and change it first.

EDIUS will import the clips and make them up in the same structure as the card just with only the clips you have chosen. It will not stitch the spanned clips together although when loaded to EDIUS they will appear stitched.

[BernH]

I just want to copy all clips from SD card to one folder with Mync, and long spaned clips to be joined in one...

It will not stitch the spanned clips together although when loaded to EDIUS they will appear stitched.

Further to th point made about Mync and Edius not stitching clips together, this functionality is usually offered in software from the camera manufacturer, such as Sony Catalyst Browse or Canon RAW Development, etc., but requeres a transcode step, not just a file copy. These software are not asset cataloging/MAM applications like Mync, and Mync is really not copy and transcode software like them.

[trifo]

First just for the public record, person responsible for folder structure of recording media need serious medical observation...
Second, person who think that folder structure +1 need for every media clip on hard drive... Hmmm
Simply can't believe that someone think is useful and practical.
Also can't believe in 2018 editing or ingesting or whatever software is not recognise media files splited by filesystem limitations...

but requeres a transcode step, not just a file copy.

Don't requires transcode step just need to be joined...
Conclusion, Mync is not for importing media from source...

such as Son'y Catalyst Browse

Thanks for that info, Catalyst is free and awesome, recognise splited parts and join, clip names 0001, 0002 transform to date time taken, and miracle copy all files to ONE folder.
Unfortunately works only with SD cards recorded on Sony camcorders...

[David Clarke]

I don't like the way Mync puts the clips in individual folders either but there may be good reasons for this with other media apart from AVCHD.

EDIUS and Mync recognise spanned clips. Import using the source browser or Mync and it stitches them together as long as you have the entire card structure present. If you just copy the MTS files it does not.

I have found the way EDIUS copies AVCHD very useful - rather than just stitching together files and leaving one final file. I remember when I was first using AVCHD and I tried Apple FCP that it would not recognise AVCHD AT ALL unless it was in the same structure as on the card - EDIUS let me keep that.

For stitching together MST files on their own I use a program called MTSMerger which I downloaded ages ago. I am not sure it is still available but you may be able to Google it.

I don't use it much now. I find the way EDIUS copies is fine for me.

[trifo]

I don't have Edius just Mync.

may be good reasons for this with other media apart from AVCHD

I don't see any good reason for that mess on hard drive...

rather than just stitching together files and leaving one final file

I do not agree... Original file is one, divided to parts by filesystem limitations, divided just may cause problems for syncing and editing, or I just like to know that it's a single shoot...

[David Clarke]

Mync is designed to catalogue footage for use in other programs. As I said I know FCP7 would not take AVCHD at all unless the entire card structure was present. It would not load MTS files at all. FCP7 is dead but there may be other programs which are the same. To keep maximum compatibility they should keep it in the format in which it originated.

This also keeps all metadata. AVCHD does not have much metadata, other formats do and that cannot be stored in just one file most of the time.

Having said that I don't know why it makes one file for each clip as opposed to the way EDIUS works which is to put all clips I copy into one folder. Maybe that too is something to keep maximum compatibility.

I already send GV a feature request ages ago. You send one too as the more people that send requests the more likely it is to happen.

[BernH]

First just for the public record, person responsible for folder structure of recording media need serious medical observation...
Second, person who think that folder structure +1 need for every media clip on hard drive... Hmmm
Simply can't believe that someone think is useful and practical.
Also can't believe in 2018 editing or ingesting or whatever software is not recognise media files splited by filesystem limitations...
Don't requires transcode step just need to be joined...
Conclusion, Mync is not for importing media from source...
Thanks for that info, Catalyst is free and awesome, recognise splited parts and join, clip names 0001, 0002 transform to date time taken, and miracle copy all files to ONE folder.
Unfortunately works only with SD cards recorded on Sony camcorders...

I think you slightly misunderstand my points. I am only making the distinction between a simple file copy and a transcode when dealing with folder based clips like AVCHD, and the difference between a catalog software like Mync and a "copy and transcode" software like Catalyst Browse. The functions are different, and while they could very easily both exist in Mync, the fact is that they currently don't.

As David alluded to, the AVCHD structure has more than just the video files, and these extra sidecar files hold some camera metadata and also give software instruction on how to virtually stitch the files together when playing back a clip that exceeds the file size limitation of the camera's file system. Often these clips can have areas where a couple of frames coexist in sequential files due to the the long GOP compression spanning files. A simple join is not an easy task in these instances without causing a glitch in the resulting file. This is why I suggested a trancode as a way to stitch them together correctly. Most camera manufacturers make a piece of software to combine this copy and transcode into a single step with files from their own cameras, but not other cameras, as each camera manufacturer has their own proprietary way of writing the sidecar files.

I am not saying that this is the way it has to be, I am just saying that this is the way it is.