Author Topic: Windows ingest behaviour not the same as mac  (Read 12985 times)

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 24731
    • View Profile
    • Camera Bits, Inc.
Re: Windows ingest behaviour not the same as mac
« Reply #15 on: June 23, 2010, 11:18:57 PM »
Adrian,

OK, I'll test my mac ingest again, but I clearly remember having to rename the avchd related files back to their original names so that I could get them into iMovie as a camera archive import.

I guess this potentially begs a slightly different angle, that of ingesting avchd files from camera cards - could they be renamed by photomechanic upon ingest as other movie formats can? I'm not aware of DSLRs using avchd format, but panasonic 4/3rds cameras certainly do.

Photo Mechanic has no knowledge of the AVCHD 'format'.

Another complication that could arise in your settings may be that flattening the directory structure could make it impossible for some software to recognize the 'format' of the files.

At this time, Photo Mechanic is suited for dealing with single movie files or photos, and not a set of related folders with various files in them.  I suggest either preserving the directory structure, or using the Finder/Windows Explorer to copy the AVCHD folder and its sub-folders to your system.

-Kirk

Offline adrianlambert

  • Full Member
  • ***
  • Posts: 105
    • View Profile
Re: Windows ingest behaviour not the same as mac
« Reply #16 on: June 23, 2010, 11:59:30 PM »
Fair enough. I can see this is a complicated one and not really part of what PM is designed to do.
For my workflow I can get just the MTS files into Final Cut Express.
Will let you know later about my experience ingesting on a mac.

Offline adrianlambert

  • Full Member
  • ***
  • Posts: 105
    • View Profile
Re: Windows ingest behaviour not the same as mac
« Reply #17 on: June 24, 2010, 05:25:46 AM »
using 10.6.4 and PM 4.6.4.1 the unknown files did indeed ingest as you have found.
I'm not sure what my procedure was previously but I can't recreate it so the mac and the windows versions do behave the same.
Sorry for your time.