Forum Replies Created

Page 41 of 86
  • Andreas Kiel

    July 23, 2013 at 10:27 am in reply to: Eye balling his parse disk size

    Craig’s idea is the most obvious one — and at this moment the easiest one

    I said “Good question — I don’t know.” cause I first thought you can do it with Disk Utility -> Convert. But that doesn’t work.
    You can do it in Terminal with a command line, but that’s probably nothing an editor loves.

    I will implement this feature to the next version of X-Files Pro next week.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 23, 2013 at 10:11 am in reply to: Sparse Bundle Users: How do you backup?

    Jeff,

    It’s not a good idea to backup while things are in progress.

    Quit FCPX and any other app before backups starts.
    For your info: Apple’s Time Machine is also based on Sparsebundles.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 22, 2013 at 7:05 pm in reply to: Eye balling his parse disk size

    “… Is there any way to convert them to Sparse Bundle Images?”

    Good question — I don’t know. But I will do some research.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 22, 2013 at 2:50 pm in reply to: Eye balling his parse disk size

    Sascha,

    As said you should use sparse bundles. They make backups easier and what is more important the reconstruct after a corruption easier. Remember a disk image is just a file!!

    About the size: You should somehow know what amount of media space is needed for a complete project. Add 200 MB for each event and each project version you plan.
    Once you reach the limit of the virtual disk you can resize the sparse bundle. But you have to quit FCPX and unmount the virtual disks. The limit of size is limited to the free space you got on the volume the sparse bundle resides on.

    My free https://www.spherico.com/filmtools/createDiskImage
    and https://www.spherico.com/filmtools/X-Files/index.html
    can help a lot to handle it easily.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 21, 2013 at 9:56 am in reply to: Organizing Events

    One of the often mentioned “… FCPX is essentially a relational database” is true for sure. But FCP had been that as well. Big difference is that FCP did hold all the parts in one huge file and FCPX spreads the needed databases thru-out your file system.
    Latter can makes things more difficult if you don’t follow the rules of FCPX. In normal cases it’s easy and straight forward.
    But when comes to re-organize it get’s far more complicated. Re-organizing is not something FCPX really likes – even if you follow the rules. And it does especially hate re-organizing events.

    Simplest example: renaming an event within FCPX. YOu see a new name in FCPX (and in Finder). Internally all paths to media still rely on the former path. Means instead of …/NewName/Original Media/… it’s still …/OldName/Original Media/…
    This is not a real problem since on launch FCPX looks for the old paths and in case of an error it looks whether the media links can be found in the Original Media folder of the re-named event. Once found it’s business as usual.
    To make “operation” safer I personally do a reconnect after renaming an event by relinking all files of the event. I would recommend this practice to all. Relinking will rebuild all involved databases.

    Now the next thing: moving media from one event to another event.
    This is way more complicated.
    If the files are used in any project ID links to the old event will break and you have to step thru the projects to reference to the “new” event ID. This is step one. It might be needed or not. In any case relink any of the moved media

    Next: if you delete media in the old event or the new event it doesn’t matter as long as the files are alias files. Your projects do store the paths to the original files (as long the paths are correct — again, relink, relink, relink before doing anything above). Finally you could have hundreds of projects with no event — obviously not recommended.
    (You also can have hundreds of “projects” as compounds with no projects in the project libraries).

    If the path to a media file is not an alias, means you for example converted media on import, you can’t (or better, never ever should) delete files since the project or event will not be able in any case to find the media.
    There are some media types which are automatically converted like the sound effects in your library or iTunes stuff. Even the new event won’t be able to find it — cause it’s gone. With some luck you may have not emptied the trash.

    If you try to delete the old event X will give you a warning message. Take it serious. Do the steps I described first – otherwise hit cancel.

    A good rule for working with media with are (need to be) converted is to create dummy events for those. Once the conversion is done go to the dummy event’s Original Media folder and copy it to a safe place and rename this folder. Delete the dummy and start over with a new event as usual. It’s not elegant nor fast but safe.

    Back to the original question of Craig Alan.
    My guess (from my experience) is that the empty event still contains “original original media” and therefore will create trouble if this “empty” event is deleted. So finally in this case only a Finder based solution could help — or just using the empty event.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 19, 2013 at 9:54 am in reply to: XTI Subtitle Importer Release

    If you look at your screenshot the open panel tell you to select a fcpxml template so it’s wonder you can’t select a srt or stl 😉
    Download TitleExchange. The installer includes a newer version.

    https://www.spherico.com/filmtools/TitleExchange/TitleExchangePro_Beta.dmg

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    July 18, 2013 at 7:25 am in reply to: FCPX max size for a project file

    Maybe it is the heavy usage of effects.

    I have some projects which don’t contain any audio or video but lot of titles and effects and it takes forever to load them.
    So you may keep FCPX open over night to see what happened next morning. If there is a crash you will have at least a log with the reasons.

    You may use my myFiles (https://www.spherico.com/filmtools/myFiles/) to analyze your project regarding used files and effects.

    And for sure submit a bug report to https://developer.apple.com/bug-reporting/.
    You have to start a developer account (which is free). But you will get a “ticket number” and can track your bug.

    I know above doesn’t help at all in your situation.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    June 23, 2013 at 7:06 am in reply to: Tip for Sparse Bundle workflows

    I made some tests this morning in my “not state of the art” home office.

    -Andreas

    https://www.spherico.com/filmtools/DMGs/DMG%20Speed.pdf

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    June 22, 2013 at 12:30 pm in reply to: Marker placed at top of timeline not on clips

    andy
    …I only point this out because your solution is a nice one, but the user needs to make sure they select the adjustment layer before adding markers.

    Andy is right, that’s the main deal and it’s not that elegant.

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

  • Andreas Kiel

    June 22, 2013 at 12:25 pm in reply to: Updating Events

    Why not keeping the Event on the portable drive?

    -Andreas

    Spherico
    https://www.spherico.com/filmtools

    “He who fights with monsters should be careful lest he thereby
    become a monster. And if thou gaze long into an abyss, the abyss will
    also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil

Page 41 of 86

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy