Claude Fable is Unbelievable (A real-world scenario)

[00:00:00]Hello everyone. In this video, we are going to talk about Fable 5 and how it helped me to solve one of the annoying issue in the project. I'm not going to prompt the Fable 5 because it is very expensive, but I'm going to show you the files that it creates and the the bug that fixed for me.

[00:00:22]Um so, we know that in the cloud code, if you go for the model, there is a Fable uh which is saying most capable for your hardest and longest running task, which is uh actually for the hardest problem.

[00:00:39]Well, I saw it how it fixed my problem.

[00:00:43]So, usually I am using Opus 4.8 for most of the task or Sonnet for easier one. I rarely using the Fable, but I used it for that fixing uh the problem. Okay. So, let's go for my project. What I was doing here.

[00:01:07]So, basically, I am doing a stream server, one of my project to open and set up a stream server sending a video and streaming and we have a player for playing that stream. Okay?

[00:01:23]And it is quite easy to be honest. You can run a a docker called SRS. So, here it's the the docker image for running the SRS in the docker and it was fine.

[00:01:38]Unless, I wanted to have, based on my requirement, I wanted to have different quality such as 480, 720 for uh a video with having different uh transcoding.

[00:01:53]So, the problem actually was sometime those different qualities didn't generate for unknown issue, and when I restart the docker, it started working, but after a while, it again stopped. So, it was really annoying. I was chatting with 4.8 Opus, and it actually what it did and fixed the the problem for me.

[00:02:21]You can see that it was like the 1st of July that I was trying to fix the problem. It actually fixed, well, based on this state saying root cause and fixed, all right?

[00:02:37]And so, it did something, and it was working. So, for the 360 and 480 that it was enabled, it was working fine, the end-to-end test, player, everything was fine, unless it happened again.

[00:02:55]It came again, and it was really frustrating that the Opus 4.8 couldn't fix this problem. And then, I was like thinking, what else I can do?

[00:03:09]Then, that Fable 5 came out, Cloud announced it, and with 50% off your weekly usage, you can use it. So, and then, I gave this problem to the Fable 5. It has start investigating the the problem, what is going on there in the SRS docker image, and doing lots of testing, looping around the the problem.

[00:03:40]And then, at the end, it actually find the root cause.

[00:03:44]So, here it was like 2 days after, yeah, it is like uh, the July 3rd that it started fixing this problem.

[00:03:57]And what was the problem? Actually, it is a bug in the SRS itself.

[00:04:03]So, it's, as you can see here, the bug is still unfixed as of, like, 3rd of July. And, um, you can see that it's check the the version of the Docker image. You can see the power of uh, the fable. Where it goes to actually collect all the information reading the different, uh, sources and it check the change log from probably the the GitHub for if there is a fix for, uh, the bug, but it couldn't find, right? And, um, at the end, actually, it was kind of finding, uh, generating a a new patch for me for the the SRS source, which is written in C++.

[00:04:57]Right? So, it actually generated a patch file, which, when I opened this file, I was completely surprised that it actually created a patch for, uh, the C++. So, what was the problem first of all? The the problem was there is a a garbage collector in, uh, the SRS source code, which well, basically, garbage collector is trying to, uh, clean all the unused resources and it is happening every 3 seconds, right? So, uh, that 3 seconds wasn't enough for the, um, the other qualities to get published. And then, before even it is like getting publishing, it was cleaned up by the garbage collector. So, it was like sometimes happening for any reason, lack of resources, or any other things that it was happening in the the Docker image, it got the fix by just increasing it to 30 seconds to just give more time uh to the transcoding process to just transcode and create in different qualities for the stream server.

[00:06:18]But, anyway, this is not about the streaming server. The the thing is how it is finding and fixing the problem. How much it goes deep in the the problem and finding the solution.

[00:06:33]So, it actually it seems like reading the source source of the SRS, probably maybe reading some other community or GitHub issues to find this things and fixing the problem. But, what is like really surprising me is the the SRS itself, it didn't fix it. So, it's like as here also it mentioned, even by uh like it is not fixed as that day, and it even by upgrading the version, it's not fixing the the problem.

[00:07:15]So, what it does actually after creating this patch file, it create a created a Docker file for me to build a customized SRS by having and injecting that patch in the that Docker image and then building a new one for me.

[00:07:39]So, after that, by like running and building the the Docker image, running the Docker image, all of that, it start working.

[00:07:52]So, it is really impressive, to be honest, because well, I mean, Opus also is very powerful, but at least in this case, it couldn't go much deeper than the normal checking or kind of fixing the actual root cause for this problem.

[00:08:16]And you can see this the fable when it says it is most capable for your hardest and longest running task, it is true.

[00:08:27]Because it at least for me was very hard to fix that problem. I am a developer, not a expert in the the streaming server. I just wanted to run some Docker image and get my my stream running, right?

[00:08:45]And it was also I I'm not sure how long to to fix the the problem, but it was a little long because I told fable to do a end-to-end testing from generating the RTMP URL, streaming, the player, all it goes looping until it found the the root cause.

[00:09:10]This is for the the fable five. Really impressive, really really good. If you ask me using fable or not, so probably I would say maybe 90% as of now, Opus is doing the job, and also Sonar. Opus more for more complex things, if you want to do the refactoring or creating a big feature in your project, probably the best is at least for the planning using the uh the Opus. Plan your your feature or your refactoring using Opus, and then you can pass it to uh the Sonnet uh to implement that plan.

[00:09:57]And [snorts] also for verifying or reviewing the code, definitely Opus is the best choice.

[00:10:04]And Fable sometimes, like me, if you stuck some somewhere, if you cannot fix problem with using any of these models, then Fable is really good.

[00:10:20]And really worth if nowadays until probably uh tomorrow, which is July 19, uh we can use 50% of the weekly usage, but after that it turn to the credit, but it's still. I mean, if there is a problem, you can spend money for it if Fable can fix it.

[00:10:43]So, that is it. It is a short one. I didn't want to run again going through the process because it is already fixed, but I just wanted to show you this Fable is unbelievable.

[00:10:58]Thank you. Until next video. Bye.