hey actually realizing this is likely not a bug. do you have the `muted` prop also added? most browsers will not autoplay unless the video sound is turned off to avoid interrupting people browsing a site. so if you have it should work for you
@@colbyfayock Because instead of leveraging the built-in Next-Image component you're providing a component that will end up costing us more credits/money
@@Codementationthe goal of the video is specifically how to install Cloudinary, as mentioned in the title. Cloudinary has a generous free tier before it's paid, much like the Next.js Image component which when deployed to vercel uses the Vercel optimization service which is free to start, but becomes similarly paid once you go past that free tier. For small projects, you may not have to pay with either.
How can I get autoPlay to work? I’ve added autoPlay=“always” but it still won’t play until I click on the video.
there might be a bug, would you mind filing an issue on GitHub with more info? github.com/colbyfayock/next-cloudinary/issues
hey actually realizing this is likely not a bug. do you have the `muted` prop also added? most browsers will not autoplay unless the video sound is turned off to avoid interrupting people browsing a site. so if you have it should work for you
really useless video
why?
@@colbyfayock Because instead of leveraging the built-in Next-Image component you're providing a component that will end up costing us more credits/money
@@Codementationthe goal of the video is specifically how to install Cloudinary, as mentioned in the title. Cloudinary has a generous free tier before it's paid, much like the Next.js Image component which when deployed to vercel uses the Vercel optimization service which is free to start, but becomes similarly paid once you go past that free tier. For small projects, you may not have to pay with either.
to you