TIL that listening to alan is a good idea

yea i can just archive the project server now.

we still do them as final archives because why not , always nice to have and our archives are like 10MB anyhow

we just dont have to do daily archives as a safety as thats now happening every 20 minutes :slight_smile:

2 Likes

You’re saying you also do a full Flame media archive, and it’s 10MB? Are you working in NTSC, on 1 frame spots?

I think I’m the last person who does full media archives.

If I’m understanding @finnjaeger correctly then his archives are just like mine- he’s referring to a no-cache workflow, with no Flame generated media (no Hard commits, no batch Render node renders, no Motion Vector renders) which results in a Flame archive that’s about 10mb.

1 Like

This is the way.

what jeff said .

metadata only ftw.
coupled with snapshots.
we work smart so you don’t have to - or something like that

No, you’re not. Each to their own devices. My workflow needs that too.

It’s really not a big deal if you’re a one-seat shop. I generally start an archive the first day of loading footage before I leave for the night, to my facilis. Sometimes earlier if I’ve done a lot of work for the offline as well. After that, subsequent archives usually only take a few minutes. Of course, I do 99% tv spots. At the end of a job, my average archive is about 3tb. When I’ve collected enough to fit on a 12tb LTO, I make 2 copies. I never delete from the facilis until I need the space. Call me old fashioned, but I feel most comfortable giving my personal attention to the backup process, rather than just rely on technology to do it for me. Obviously this may not work out well in a big shop, particularly if you leave archiving to the individual artist, or if your primary work is longform, which to me is anything over 90 seconds.

@ytf - I am calling you old fashioned, making one, and drinking it in celebration of you…
you of all people know that flame is not a single track approach.
and i of all people will disagree with that.

I think I mentioned that this works for me because of my narrow field of needs.

1 Like

Besides, I prefer a Manhattan. It’s a hometown favorite.

1 Like

You mention installing the adsk VM… is that the Ami you’re referring to?

nope just the rocky linux iso as a VM.

1 Like

You are able to use the AMI - try VirtualBox as your hypervisor.
It’s not a great way - but gives you the flexibility to try a bunch of stuff, then throw it all away once you’ve worked out your blueprints.

I’ve just started playing with Proxmox… So many people kept mentioning it, I got FOMO… haha… I’ll go with the VM… not sure if my ā€˜beelink eq13’ is enough though… but for a learning experience it’s fine.

2 Likes

Yea get in the game!!

2 Likes

Could you expand on this step?
Is there a separate installer for running the Project Server as a VM?

Flame_Cloud_Reference_project_server_configuration

The link phil
oinked is for a cloud install, there actually is a guide for the regular project server.

https://help.autodesk.com/view/FLAME/2024/ENU/?guid=FLAME_install_software_config_project_server_config_html

1 Like