If you switch from flame to resolve you can be a millionare in

Made a calculator to show how expensive flame is compared to resolve/fusion (which is free)

here is the code for fun

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>šŸ’ø Savings Calculator</title>
    <link href="https://cdnjs.cloudflare.com/ajax/libs/animate.css/4.1.1/animate.min.css" rel="stylesheet">
</head>
<body class="bg-purple-100">
    <div class="max-w-md mx-auto mt-10 p-6 bg-white rounded-3xl shadow-xl">
        <h1 class="text-4xl font-bold mb-6 text-center animate__animated animate__fadeIn">
            šŸ’ø Money Saved Calculator
        </h1>
        
        <div class="space-y-6">
            <div class="animate__animated animate__fadeInUp">
                <label class="block text-lg font-medium mb-2">
                    Number of Flame Licenses šŸ”„
                </label>
                <input 
                    type="number" 
                    id="licenses"
                    min="1"
                    value="1"
                    class="w-full p-3 border border-purple-300 rounded-xl focus:ring-2 focus:ring-purple-500 focus:border-purple-500"
                >
            </div>

            <div class="animate__animated animate__fadeInUp" style="animation-delay: 0.2s">
                <label class="block text-lg font-medium mb-2">
                    Years Not Using Flame āŒ›
                    <span id="yearValue" class="text-purple-600">1</span>
                </label>
                <input 
                    type="range" 
                    id="years"
                    min="1"
                    max="10"
                    value="1"
                    class="w-full h-2 bg-purple-200 rounded-lg appearance-none cursor-pointer"
                >
            </div>

            <div class="mt-8 p-6 bg-gradient-to-r from-purple-500 to-pink-500 rounded-2xl text-white animate__animated animate__fadeInUp" style="animation-delay: 0.4s">
                <div class="text-center">
                    <h2 class="text-2xl font-bold mb-4">Total Savings šŸ’°</h2>
                    <p id="totalSavings" class="text-4xl font-bold">$0</p>
                </div>
                <div class="mt-4 text-center">
                    <h3 class="text-xl font-bold mb-2">With S&P 500 Returns šŸ“ˆ</h3>
                    <p id="withInvestment" class="text-3xl font-bold">$0</p>
                </div>
            </div>
        </div>
    </div>

    <script>
        const licenseInput = document.getElementById('licenses');
        const yearsSlider = document.getElementById('years');
        const yearValue = document.getElementById('yearValue');
        const totalSavings = document.getElementById('totalSavings');
        const withInvestment = document.getElementById('withInvestment');

        function calculateSavings() {
            const licenses = parseInt(licenseInput.value);
            const years = parseInt(yearsSlider.value);
            const monthlyPerLicense = 610;
            
            const monthlySavings = licenses * monthlyPerLicense;
            const totalSaved = monthlySavings * 12 * years;
            
            // Calculate compound interest with monthly contributions
            let investmentValue = 0;
            const monthlyRate = 0.10 / 12; // 10% annual return divided by 12 months
            
            for (let month = 0; month < years * 12; month++) {
                investmentValue = (investmentValue + monthlySavings) * (1 + monthlyRate);
            }

            totalSavings.textContent = `$${totalSaved.toLocaleString()}`;
            withInvestment.textContent = `$${Math.round(investmentValue).toLocaleString()}`;
        }

        licenseInput.addEventListener('input', calculateSavings);
        yearsSlider.addEventListener('input', (e) => {
            yearValue.textContent = e.target.value;
            calculateSavings();
        });

        // Initial calculation
        calculateSavings();
    </script>

    <style>
        @import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&display=swap');
        
        body {
            font-family: 'Inter', sans-serif;
            background-color: #F3E8FF;
            margin: 0;
            padding: 20px;
            min-height: 100vh;
        }

        input[type="range"] {
            -webkit-appearance: none;
            height: 8px;
            background: #E9D5FF;
            border-radius: 5px;
            background-image: linear-gradient(#A855F7, #A855F7);
            background-repeat: no-repeat;
        }

        input[type="range"]::-webkit-slider-thumb {
            -webkit-appearance: none;
            height: 20px;
            width: 20px;
            border-radius: 50%;
            background: #A855F7;
            cursor: pointer;
            box-shadow: 0 0 2px 0 #555;
            transition: background .3s ease-in-out;
        }

        input[type="range"]::-webkit-slider-thumb:hover {
            background: #9333EA;
        }

        .animate__animated {
            --animate-duration: 0.8s;
        }
    </style>
</body>
</html>
1 Like

I would LOVE to use flame IF it ever work native with h265 10bit 4k6k8k material. Until then, no subscription and no single request of use since the codec dictate the toolset; I use dr-studio instead. The work I have done with it, it is my main income. For superfast pitchdecks, I now use apple motion. For UE and Virtual production, Assimilate does the job. Flame just need to implement h265 as it is since YEARS in mac silicon as hardware embeddedā€¦ smooth and small in filesize! All of my clients footage is delivered nowadays in HEVC h265 codec in 10bit. Interesting topic btw. But ā€¦ Flame is a dino! Some real oldschool agency supervisors still remember the power of inferno/flame. I see them drop out of position man by man by the days. pity! Anyway, I have to move on! Cheers

1 Like

Hahahahaha
Yep
Thatā€™s gonna work!
Love ya @finnjaeger
You need tobe compensated for your brilliance
You are a treasure
Do not defect to that dessert called other softwareā€¦
We love you

1 Like

Well, by similar logic

If I replaced our $300/wk grocery bills (2 people) with each of us eating two value meals at McDonalds per day ($5/ea), over my lifetime assuming Iā€™ll make it to 85 (doubtful on value meals), I could save $1.016M.

I think Iā€™ll stick with my steaks, organic veggies, and fruitā€¦

4 Likes

Even in the new version there is no h265 native implementaton. Guys, you are 10 years behind now. I serve with ComfyUI and CapCut 90% of flame requests.
What is it, to NOT implement h265? In my case 100% comes in 10bit 422h265 footage. And I do not have a quantillion TB superfast drive. So just tell me WHEN Flame eats 10bit/422 h265 HEVC? This makes a NO or a GO for 2025!

1 Like

while I do not ever have h265 footage .

This extends to the pure lack of support for any camera media in flame, its made to work on dpx sequences from color / everything else is a hack.

even raw formats that exist are ill supported or buggy

flame needs to be much better here, if a tiny company like assimilate can support everything on earth with metadata and autodesk cant is just weird and sad.

I started in my 90ies with Discreet Edit, Paint, Effect, and later Combustionā€¦then Nothingreal Shakeā€¦2010 on Smac, 2018 Flame on Macā€¦ But I am also an old fashioned inferno magician in the asian space. Nowadays Flame is not really called up anymore. Even by 4A Agencies. They want realtime Unreal and such beautiful reliable systems. So Please implement h265 HEVC nativ into flame. This makes it a changer in everything. I dont need onnx inference within flame! I need h265!

H265 adoption has been hobbled by complex patent agreements and expensive licensing fees. itā€™s been estimated to be nearly 7x the licensing cost of H264 which is widely adopted by hardware/sofware/browsers. so i think iā€™ts not a great choice to pay expensive fees only to find out it doesnā€™t work everywhere? it seems like theyā€™ve tried to reign in costs a bit with some modifications to the fees but Nuke doesnā€™t read it either and AV1 (which would essentially be royalty free) is on the horizon as well. Oddly it seems the entire industry is influenced by the surveillance camera market which seems to be adopting H265 finallyā€¦ who knowsā€¦ i rarely need to deal with H265ā€¦

2 Likes

licensing is always extremely annoying.

I have no idea what a ā€œunitā€ is but apaprently h265 wants like 20c per unit.

and then on top
of that its like sonys own XAVC-S/H stuff thats h265 under the hood no idea how thats licensed.

However all the competitors at MUCH cheaper price points have figured this outā€¦ i mean even adobe got it

That said I also will aknowledge that flame is probably not the same target audience as users shooting with consumer cameras , i know it sounds elitist af, but if you save a few dollars on the camera you probably save a few more dollars in postproductionā€¦

Main things I have to personally pre-convert

ā†’ ARRIRAW due to the crash-bug and no support for 13bit?

ā†’ ProresRAW (DJI)

ā†’ CinemaDng ( DJI )

ā†’ Phantom .cine raw

we use assimilate scratch to convert things

if flame wants to be the center of the pipeline it needs to properly support codecs used on set today, everytime I get dji drones and ronin4D stuff now.

1 Like