Thank you for the welcome!
I have at least looked at MLVFS. However, I am a bit weird. While I do have the occasional paid project, filmmaking is by far not my main income so I can afford some inefficiency and instead focus on long-term data availability, especially for my own works. Of course the main issue is vendors of editing software going bankrupt (or switching to subscriptions), making your project files useless. The other issue is the media files themselves. I'd like to have them in open, well documented and widely supported file formats while at the same time keeping most (if not all) of the original image quality. So if push came to shove I could always write my own converter. (c)DNG is my video format of choice. I have misjudged the price drop of storage space, though. But that's a different story. I'm also aware that as soon as multilayered sensors are available, debayering will become a dying art and support fill fade out ten or twenty years after that, but what can you do...
I have old projects from the 90s, already "transcoded" once from VHS to MPEG and I assume I'll have to transcode them at least once again in the next 20 years. No one really cares about MPEG any longer, even today. In a couple of years I'll be regrading this for HDR and P3 (or whatever the camera was able to capture and my future mastering display is capable of). Not a problem with the original raw files (the realtime sequences are Canon MOV, because it was before ML-RAW which meant that I wasn't using ML at the time, but I think you get where I'm going with this).
I also try to keep the editing system environment as simple as it can get. Currently I need to have Resolve Studio installed and nothing else. MLVFS and its dependency on other components is a bit too much for me. But don't get me wrong. Had I to live off of film production I would use MLVFS because of its efficiency. It seems like the perfect solution for those workflows.
Cheers...
...Mike
I have at least looked at MLVFS. However, I am a bit weird. While I do have the occasional paid project, filmmaking is by far not my main income so I can afford some inefficiency and instead focus on long-term data availability, especially for my own works. Of course the main issue is vendors of editing software going bankrupt (or switching to subscriptions), making your project files useless. The other issue is the media files themselves. I'd like to have them in open, well documented and widely supported file formats while at the same time keeping most (if not all) of the original image quality. So if push came to shove I could always write my own converter. (c)DNG is my video format of choice. I have misjudged the price drop of storage space, though. But that's a different story. I'm also aware that as soon as multilayered sensors are available, debayering will become a dying art and support fill fade out ten or twenty years after that, but what can you do...
I have old projects from the 90s, already "transcoded" once from VHS to MPEG and I assume I'll have to transcode them at least once again in the next 20 years. No one really cares about MPEG any longer, even today. In a couple of years I'll be regrading this for HDR and P3 (or whatever the camera was able to capture and my future mastering display is capable of). Not a problem with the original raw files (the realtime sequences are Canon MOV, because it was before ML-RAW which meant that I wasn't using ML at the time, but I think you get where I'm going with this).
I also try to keep the editing system environment as simple as it can get. Currently I need to have Resolve Studio installed and nothing else. MLVFS and its dependency on other components is a bit too much for me. But don't get me wrong. Had I to live off of film production I would use MLVFS because of its efficiency. It seems like the perfect solution for those workflows.
Cheers...
...Mike