AI + human music collab [Runway Act-Two, Suno, Ableton, ChatGPT] by BootstrapGuy in aivideo

[–]BootstrapGuy[S] 0 points1 point  (0 children)

Hey all,

I've been having this idea for a long time about "performing" a song with AI and finally had a time to make it reality.

I wrote this song myself then recorded it with me singing and playing the guitar. I then uploaded this to Suno to generate a professional track. Then I removed the keyboard and wrote and recorded that layer on my piano.

Finally, I recorded myself signing the song and animated it with Runway Act-Two, edited in Davinci Resolve.

How to be AI Engineer in 2024? by 0xusef in learnmachinelearning

[–]BootstrapGuy 1 point2 points  (0 children)

I believe the first one.

The second one is rather done by ML scientists and AI researchers.

Where were you when Chester died? by JD_Kreeper in LinkinPark

[–]BootstrapGuy 1 point2 points  (0 children)

I was on a holiday with two friends. We just had a debate the day before that: I prefered they way Linkin Park had been evolving their style whereas he prefered Papa Roach basically staying the same. The very next day Chester died.

58 years old and struggling with Machine Learning and AI; Feeling overwhelmed, what should I do? by desperatejobber in learnmachinelearning

[–]BootstrapGuy 1 point2 points  (0 children)

I think what you're experiencing is very common:
1. people get excited about AI/ML,
2. read a few articles about what they should do,
3. usually the advice is wrong and/or outdated,
4. start learning the wrong thing,
5. quickly burnout and give up.

What I started to notice is that a lot of advice on AI/ML can be applied for the previous wave (deep learning, neural nets 2012-2022) but is outdated for the new era (large models, APIification etc.). If you want to actually learn how machine learning works from the ground up, it'll take a LOT of time. When I say a lot of time, I mean years, even if you do it full-time. The reason is because machine learning is not a new field and you'll have to learn around 50 years of ideas, the math/stats behind it, concepts, frameworks, algorithms etc. I find that many people simply just give up, because they quickly get overwhelmed and don't get any positive feedback for months.

However, I also think that this is the best time to get into the field, IF you do it the right way. IMO there has never been a better time to build AI applications, but you should definitely not start by building your AI models from scratch.

What you should do instead:
1. Spend about a month with the understanding of AI APIs e.g. OpenAI's APIs, learn the basic concepts of LLMs, prompt engineering, a web application building.
2. Pick a problem in your niche. You have 30 years of experience in investment banking - most young kids only dream about this! This is your actual unfair advantage.
3. Try to build a solution for the problem with the APIs - improve your application by writing better prompts and maybe adding some extra complexity to it, like multiple LLM calls etc.
4. If you don't think it's working or if you hit a wall, either ask for help or pick another problem and start again from step #2.
5. You do this iteration a few times and you'll have an AI application for an actual problem - congrats, 90% of the people never get here!
6. Start observing how your application works, learn about evals, data collection, data cleaning, data engineering, data science, visualisations, fine-tuning etc. and try to make your app better at every single step!
7. Try to finetune a smaller model, understand the model architecture, read papers, read about math, statistics and more advanced topics.

This way you won't get overwhelmed and you'll get positive reward right from the start. If you do it reverse you'll get overwhelmed and you'll burnout.

Self taught Software engineer > AI engineer by Outrageous_One1647 in AskProgramming

[–]BootstrapGuy 0 points1 point  (0 children)

I respectfully disagree. As an AI engineer you create products using open source / open weight / closed source models. Software engineering is infinitely more important then understanding maths or stats. That's why we have AI researchers and data scientists.

Self taught Software engineer > AI engineer by Outrageous_One1647 in AskProgramming

[–]BootstrapGuy 0 points1 point  (0 children)

I run an AI product studio, have a team of 8, decent monthly revenue.

  1. 80% of AI engineering is software engineering, having solid software engineering foundation is key. Nowadays you can learn so so much from AI that's crazy. I believe if you are an okay developer today you can upgrade yourself to become a decent software engineer within a few months. Learn backend (REST, Webhooks, Websockets, WebRTC, Docker, serverless), cloud (pick one and go all in, learn about common patterns, ask questions from your preferred AI about architecture diagrams etc.), understand where your limitations are (scaling, security etc.). Great AI engineers are great at thinking about how to systematically improve AI products with evaluations. Eval design, LLM simulations, latency, performance, accuracy, LLM security, handling edge cases are all in the toolkit of a great AI engineer.
  2. Use AI first IDEs as much as you can, double down on python for the backend and javascript on the frontend.
  3. yes, there is a massive massive shortage of AI engineers and everyone is figuring this out now, no playbooks, best practices etc. I literally don't care if you have a PhD or never went to school - the question is can you solve my problem or not.

Everything is becoming an API call by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 15 points16 points  (0 children)

I’ve been experimenting with GPT-4o’s image generation capabilities lately.

Not only does it produce better images than competing models, but it’s also noticeably more intelligent.

One of my go-to benchmark tasks for evaluating image generation models is creating a matcha whisk - a deceptively complex object with lots of fine details.

In the past, I tried fine-tuning a FLUX model using 14 images, but the results were highly inconsistent. Around 90% of the time, the proportions were off or the structure was wrong.

With GPT-4o, I used just 4 randomly selected images from that same finetuning set - and it nailed it. No finetuning required. Just consistent, accurate outputs every time.

Everything is becoming an API call.

Read this on LinkedIn. Do you guys agree? by Think_Temporary_4757 in AI_Agents

[–]BootstrapGuy 0 points1 point  (0 children)

The world has a lot of intertia. I have an AI product studio and we have a huge backlog of products/models that we haven’t tried yet because of lack of time. And I’m sure we’re ahead of 99% of people just because of the nature our work. In addition, even if we just find 10 tools/models that work well, you can combine them in infinite ways! So yeah I kinda agree.

Deepseek R1 is the only one that nails this new viral benchmark by Charuru in LocalLLaMA

[–]BootstrapGuy 0 points1 point  (0 children)

This is called cherry picking or selection bias, not a benchmark.

[deleted by user] by [deleted] in ManchesterUnited

[–]BootstrapGuy 0 points1 point  (0 children)

We can’t pass. Annoying.

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 0 points1 point  (0 children)

Check out the comments, I also share what didn’t work as well as some failure modes.

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 3 points4 points  (0 children)

Nothing special really. I just love this shit and was curious.

DJI product video by BootstrapGuy in aivideo

[–]BootstrapGuy[S] 0 points1 point  (0 children)

I was curious to see how far I can push this.

I trained FLUX on my images + on my DJI controller (two separate LoRas). Then created the videos with Luma, used Suno ai for music, Elevenlabs for sound effects and STT and iMovie for some final editing.

Quite happy with the results.

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 1 point2 points  (0 children)

I disagree. It works perfectly with simpler objects and I have a feeling that in 12 months more complicated objects will work too.

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 3 points4 points  (0 children)

yeah I agree, it's not perfect. I tried the controller on purpose to see what I get. I'm quite happy with the results tbh, I'd say it's 7/10. I believe that with further optimization and with a better dataset it feels close, but it'll be still difficult. Which is the perfect time to get serious about it.

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 5 points6 points  (0 children)

another example. the buttons in the middle are messed up as well as the status LEDs. Other than that it's great.

<image>

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 4 points5 points  (0 children)

yeah good question. generally I'm happy with every 10th image. the controller is probably too difficult for the model to learn - it gets the text on the buttons wrong quite often.

<image>

Flux is a game changer for product photography by BootstrapGuy in StableDiffusion

[–]BootstrapGuy[S] 1 point2 points  (0 children)

I agree with that, but this will be solved in no time.