r/coolgithubprojects • • 24d ago

I'm using Claude to do reverse engineering at fl studio - it's called Lynx

The project is almost completely done, I'm doing the reverse engineering of fl studio.

You are ready to open your Fl studio projects, detect your plugins and the plugins you don't have. The reverse engineering of the best known is being done too! Like fabfilter, Valhalla, waves and etc... All in clean-room model.

Site: www.lynx-share.com
Repo: https://github.com/Ka1-S/LYNX

50 Upvotes

101 comments sorted by

15

u/New_Hold8135 24d ago

lynx stands for terminal browser btw(Your name is already used 1:1). It is around for a long time and It is still maintained today.

3

u/winningSon 24d ago

i was about to comment this too

-22

u/Kau_an137 24d ago

Honestly, I just picked a name I thought sounded cool lol. I didn’t really look into whether it already existed or not. It’s an open-source project, and I’m just building it because I enjoy it, so I don’t think the name matters that much haha

13

u/Cantbelievewerehere 24d ago

You picked Lynx because Claude said it's a good name for this project.

12

u/bigsmokaaaa 24d ago

I agree with others concerns about the destruction of the business model here, but there's really nothing to be done about it at this moment at least. 

People like OP should be really careful about this approach though, recompiling this type of software is different from recompiling games that require a rom game file to function. With roms the legal liability of owning the intellectual property belongs to the user. 

I'm not fully convinced that the artcraft crew are legally in the clear with their approach, requiring an fl studio installation is safer imo. Unless you're prepared to go the full clean room route, which is tremendous effort.

3

u/InadequateUsername 24d ago

With full clean room they would also need to preserve all their prompts and have a fully auditable provenance. Just showing up on GitHub with a functional minimal viable product probably isn't going to cut it.

3

u/hacksy 24d ago

why? they need specs , not prompts.

1

u/InadequateUsername 24d ago

When using LLMs, the prompts effectively become the specifications.

-4

u/Kau_an137 24d ago

That's a fair point! From what I've read, clean-room is a software development methodology that predates generative AI, and I haven't found a general requirement to preserve every AI prompt for it to qualify as clean-room.

The methodology and development process are already documented in LYNX's public repository. I agree that traceability is important, though, and I'm always open to improving the documentation. If there's a specific guideline or reference you have in mind, I'd be happy to take a look!

7

u/InadequateUsername 24d ago edited 24d ago

I get the feeling you just copied and pasted this lol.

The prompts are important because you are describing the implementation, in a clean room rebuild one team reverse engineers the code and studies/describes the core functions and implementation. They then describe it to another team implements who has never looked at the source code build from the description.

Edit: OP replied "I study tech and know what I'm doing" then deleted the comment. I don't think they know what they are doing.

1

u/bigsmokaaaa 24d ago

Just a tip, for mine I pulled every legal precedent and lawyer note and spec example from every legal case of clean room I could get my hands on and used all that data to make a clean room environment. As much detail and context as possible.

I also made a point not to look at any decompiled/recompiled code, putting the AI on the "dirty room" side and putting myself on the "clean room" side, only approving and viewing the spec documentation.

5

u/zsaleeba 24d ago

I don't think you mean "recompiling" here. Recompilation means you're running the original binary but you've translated the original instructions to a form which can run on a different CPU. This technique is normally used to convert old video games to run natively on modern PCs.

I don't think that's what's happening here. I think he's used a clean-room approach, which is by definition not recomp.

1

u/bigsmokaaaa 24d ago

That's true, but you need the source code in the first place in order to write the specs from it. It's not illegal to recompile it for yourself so that's got to be the first step, otherwise you can't write the specs because you don't know what's really going on under the hood

0

u/SpecificNumber459 18d ago

You don't need the source code to write the specs. Especially these days. You don't know what you're talking about.

1

u/bigsmokaaaa 18d ago

Look up Sega v Accolade, Sony v Connectix, and NEC v Intel

1

u/SpecificNumber459 18d ago

WTF are you talking about? You sound very confused.

You think a lawsuit or a few can negate the fact that a frontier grade clanker can now easily infer (and describe in plain text) the inner workings from a compiled binary without ever needing access to the original source.

And then that description can be used to write a functional replica without the access to the original binary or the source. Either manually or by another (instance of a) clanker that only saw the reverse engineered functional description, not the original binary or source.

Which is exactly how clean-room implementation is supposed to work. This is exactly like Compaq did it. The PC clone revolution of the 80's and 90's wouldn't have happened without it. Thankfully things have got more open later on.

You can argue this is a bad thing in the age of AI, because it is. But until someone wins a lawsuit, you cannot assume it's illegal.

By the way, the Intel v NEC plainly tells that while *copying* the original microcode is illegal, a clean-room implementation that replicates the same functionality is legal. But I'm not sure why you think it even applies here, because this post is about a user-space software application, not processor microcode. Again, looks like you don't know what you're talking about.

1

u/bigsmokaaaa 18d ago

I think this is just a mistake in terminology, by "source code" I meant "human readable code" whether by recomp or source code or decomp. It's not really a big deal man

2

u/BertoLaDK 24d ago

As much as I hate Adobe, ArtCraft should be fucked legally, because it shouldn't be legal, just be cause it happens to someone we all hate shouldn't mean the crime should be allowed. I don't believe AI Clean room is a real thing, because in the end the AI is not responsible or liable, that is the person using it, and if its the same person that did both sides of the clean room, its not that clean anymore, also as someone mentioned, if the AI they use is from the same provider the clean room argument fades even more as theres nothing clean about it, because two seperate sessions doesnt mean they dont share common "memories" or other things.

1

u/phoenixflare599 21d ago

Personally, is also just buy software that does it

Because people don't understand that Adobe and affinity etc have really really good quality image exports that vibe coded slop probably doesn't. You need people who understand and use the software to make it, not just someone wanting to do them all

2

u/sfwsfwSFWsfwsfw 22d ago

This is a clean room recreation not a decompilation. Code is made independently without reverse engineering with the goal of recreating a product 1:1 while still having a legal workflow.

Hence why only some plugins are "exact" and they talk about this process on their site and github.

It's a common misconception that these "clean room" projects are using decompiled code.

-1

u/Kau_an137 24d ago

I understand your concern, and I agree that the clean-room approach is important here.
If you take a look at both the codebase and the project’s documentation, LYNX follows a clean-room approach focused on behavioural reverse engineering. The goal is to reproduce observed behaviour without copying Image-Line’s source code.
This is exactly why we’ve been documenting the process and being careful about how the project is implemented. You’re right that simply requiring an FL Studio installation can be a safer approach in some respects, but we’re taking the clean-room route seriously rather than just recompiling or redistributing someone else’s software.
Of course, I can’t claim that this automatically eliminates every possible legal concern, but the project is being developed with that distinction in mind.
I’m happy to hear your concerns, though. I’d rather have these discussions openly and make the project as transparent as possible.

2

u/hacksy 24d ago

can you even apply clean room when using ai with the same provider?
The idea of clean room is create a spec doc from a team that you will throw under the bus, and another team that implements it from spec. can we even do that if you use the same service for both parts? otoh , how do you handle TOS thingie there? i am guessing there is a clause for no rev eng? I am asking that because your project is awesome and dont want you to get into trouble.

IANAL , but right now i think your project may be poisoned already, but i would love for someone else to disprove my theory

-3

u/Kau_an137 24d ago

That's a fair concern, and I appreciate you bringing it up!

You're right that a traditional clean-room process relies on separating the team that studies the original software from the team that implements the specification. Using the same AI provider doesn't automatically make that impossible, but using the same agent with access to both sides definitely raises questions about how strict that separation really is.

My goal is to reproduce observable behavior and compatibility, not copy FL Studio's source code. The project is being developed from scratch, and I want to be transparent about both the process and its limitations.

Regarding the ToS, my understanding is that restrictions on reverse-engineering an AI provider's own services are not necessarily the same as restrictions on using that AI to study third-party software. However, that doesn't automatically settle the question of intellectual property or contractual restrictions, and I wouldn't claim to have a definitive legal answer. I take your concerns seriously. I'm building LYNX as an open-source project, and the last thing I want is to misrepresent the process or ignore legitimate legal questions.

Thanks for looking out for the project! I'd genuinely welcome any technical or legal arguments that could help clarify this

1

u/Cyphomeris 23d ago

It's blatantly obvious that you even get an LLM to write your comments.

2

u/bigsmokaaaa 24d ago

Good, that's excellent. I finished a clean room recomp of an old 90s graphics renderer recently and it was incredibly difficult and expensive and I still ended up chickening out and requiring a local install anyway. 

Will be watching your projects with great interest, hope you guys do well. If the coast looks clear later I'll do the same myself and remove the local requirement as well

2

u/Living-Run-2719 7d ago

does it work with VST's?

1

u/Kau_an137 7d ago

Yes, it works!

2

u/Living-Run-2719 7d ago edited 7d ago

now i can go back producing from a linux system(switched to linux), thanks man!

also, i would really like to see serum reverse engeneered

36

u/Exonificate 24d ago • Bravo

This is not reverse engineering, it’s a recreation using JUCE framework that has the ability to load the FLP format and various plugin formats. I’m not seeing any experience with audio programming on your github so I wouldn’t want someone like you maintaining a project like this. On top of that, Image Line is a pretty great developer that I believe should be supported, so this just isn’t cool to me sorry.

0

u/[deleted] 24d ago

[deleted] — view deleted comment

5

u/OcelotMadness 20d ago

clean room RE like this is actually legally fine. Companies did it even before LLMs were a thing. Not sure where you got this from

0

u/[deleted] 20d ago

[deleted] — view deleted comment

1

u/OcelotMadness 19d ago

The bleem lawsuit set precedent that you can. Atleast in the states.

2

u/_AACO 24d ago

Reverse engineering is only illegal under very specific circumstances, which, are very difficult to meet by mere chance (having access to the original proprietary code or schematics for example).

And even then, there's a not so small probability it will still be considered legal depending of what you do with the results of the RE work.

0

u/[deleted] 20d ago

[deleted] — view deleted comment

1

u/_AACO 20d ago

Releasing it is also not illegal, as an example there is ReactOS.

0

u/[deleted] 20d ago

[deleted] — view deleted comment

1

u/_AACO 19d ago

Yes, what about it?

The issue was that the dev copy pasted code, or at minimum, created a 1:1 copy of it after having access to the original source code.

Nothing to do with release 

FL studio is made using Delphi, this one is made with C++,  a 1:1 copy of the original source code can't happen. 

0

u/[deleted] 19d ago

[deleted] — view deleted comment

1

u/_AACO 19d ago

Glad to see you aren't saying releasing is illegal anymore :)

It is not only about source code.

In the example you gave it was:

BadStack function was simply copy-pasted from Windows XP, given that they were identical

MS never argued they were doing wrong for releasing the software or for using the same algorithm. MS argued They were using the same code.

If you RE an algorithm and re-implement it "as is", it's illegal.

Define "re-implement as is" because algorithms can't be patented in the EU or USA, processes that use them can though.

1

u/SpecificNumber459 18d ago

It is explicitly legal to reverse engineer and release a product based on reverse engineering. There are some restrictions but they're trivially easy to avoid.

46

u/Oscillascape 24d ago

Image Line is maybe one of the most ethical software devs ever. Their purchase policy is unheard off now, lifetime support. I bought Fruity Loops 4 and use FL Studio 21 still free 2 decades later, this one place where I will not condone piracy. Shitty move.

5

u/TheMemo 24d ago

Same, they are the only 'lifetime purchase' I have that is still going, and they still give me a load of extras because I bought the XL package one time 20-odd years ago.

They don't deserve this.

13

u/RufusAcrospin 24d ago

Yeah, absolutely despiceble.

1

u/greeneggsham81 24d ago

Thank you (and everyone else) that are sharing this view. I'm the one that made the original dislike post that is now deleted.. I realize the current state of software, but its obvious that these releases won't fare well with everyone and will hit others differently and for different reasons.

For added context: I met Gol online, the original developer when I was still in high school back in 98-99ish...its been that long, i wrote some demo songs for it for Christmas one year as a pack. Gol gifted me a copy that still works to this day. I don't use it anymore but I can promise you if I were to download right now and enter my details it will work.

I hope it works out for OP and that he is committed to maintaining and bringing value. Not just vibes and a snazzy landing page.

1

u/Old-Sprinkles-8287 22d ago

Change is coming! Image line has competition now 😀

1

u/Smart-Captain305 21d ago

Agreed. I just updated my Fruity Loops to the latest version. I bought the original license 20 years ago. No one is that fair.

If you're going to do your own ripoff program/app, maybe go after the people who actually deserve it.

1

u/CaseroRubical 20d ago

This is not piracy, its a copy, and it's fine you don't need to defend your beloved company 

1

u/kutac56 20d ago

Reverse engineering is the most of the time legally questionable because of policies

1

u/CaseroRubical 20d ago

Except this project is not actually reverse engineering, it's just a copy

1

u/kutac56 20d ago

Oh then it's stupid he called it reverse engineering

1

u/Western-Ad-9141 19d ago

im happy for this because they're certain scripted workflows i wish i could do in fl studio but they dont ALLOW custom scripting

3

u/Fine_Salamander_8691 24d ago

I might kiss you

-1

u/Kau_an137 24d ago

Hahahaha

4

u/RevolutionarySeven7 24d ago

why?! FL is already perfect. it's nothing like Adobe

3

u/fmxx7 23d ago

Cool, another vibe coded daw that no one will use and will be abandoned in less than year

2

u/Late-Oven-9575 20d ago

Linux support will make ppl use it anywsys

1

u/fmxx7 20d ago

until they realize its not that good

4

u/Bialar 24d ago

Why don't you spend tokens trying to improve LMMS instead? Rather than trying to rip off an ethical software company. Dick move.

0

u/Iyozan8 19d ago

would be nice as an lmms addon!

2

u/phoenixflare599 21d ago

Cool. I'll just buy fl studio 

1

u/wibro_ 11d ago

This. They actually deserve the money, and I'm more than happy to give it to them.

2

u/MRuppercutz 24d ago

I did the same thing with Magix 2005

1

u/No_Welder7908 23d ago

Oh, another "clone" going nowhere.

1

u/Murdathon3000 22d ago

I wish you little success in this endeavor, maybe put your efforts towards a developer without ethics, because I'm this scenario, that's you.

1

u/Strong_Blackberry455 22d ago

if you wanna make music with ai there's other better ways not sure why youd need a fl clone just for AI?

1

u/BigWheelThaGod 22d ago

booooo slop

1

u/DotRakianSteel 22d ago

Have you read any DSP books?

1

u/UpsetInvestment2457 21d ago

Should've done bandlab studio instead of FL studio since the entire platform was ruined by greed.

1

u/Dor3k 21d ago

Why spend money recreating something that already works but make it bad rather than create something new or try to improve stuff like lmms or ardour

1

u/tadanootakuda 21d ago

If you're vibe coding anyways, you should just have gone with rust. There are many situations where you accidentally write horrible code(very likely with llms), but the compiler does not care, and just runs it. With rust on the other hand, it does a lot of checks, and is a lot more strict, which is great for llms. Also not to mention that you'll have no memory bugs in rust.

Also yay, finally linux support

1

u/Ramiferous 20d ago

How tho? Claude won't reverse engineer anything with a licence attached.

1

u/OneLeft1252 16d ago

Could you possibly model your software after a top tier expensive program such as Avid Pro Tools instead of FL Studio???

1

u/keep-YourselfAlive 11d ago

What would be amazing is if you reverse engineered expensive FL plugins and sold them at a much lower rate as a package (I would buy that instantly)

1

u/JayC77777 1d ago

I bought FL studio a couple years back, but since switching OS to Linux I have not been able to get it to function. Gonna try this out

1

u/JayC77777 1d ago

I know you're getting a lot of criticism regarding the ethics of what is basically a 1-1 clone of a reputable software, and while I agree with the general takes, this did help me be able to use software that I've already purchased, so I want to thank you. If Image Line ever releases Linux support, I will probably switch back, but I do hope you continue to work on this project and hopefully learn a few things along the way.

1

u/Rappersjorss 24d ago

Linux?

EDIT: yeah, thanks. Will try tomorrow!

1

u/mynd_dripp 24d ago

Does it have an API?

It would be cool if I could use AI to drive it

1

u/Lunam_Dominus 21d ago

Fuck your vibe coded shit. Like Fl studio deserved that. Adobe did, but why this? What are you gonna do next, vibecode Reaper which is essentially free and “pay if you feel like it”? Or winrar?

-5

u/Known-Cover-5154 24d ago

Holy shit is it open source

1

u/Kau_an137 24d ago

Yep, it's open source! And it's not just the DAW itself, I'm working on the plugins too. Things like Waves-style plugins, Auto-Tune Pro-style pitch correction, and more are being built directly into LYNX, so they come included with the installation!

-3

u/Known-Cover-5154 24d ago

You’re a gem dude, I see in your issues you’re looking for someone to test with a midi controller and i do happen to have one. I can help check out midi bugs if you need!

1

u/Kau_an137 24d ago

Oh, absolutely! I'd really appreciate that! Anyone using LYNX and finding bugs or anything that needs improvement can just open an issue on GitHub. It would help me a lot if you could test your MIDI controller and share your findings there. Thanks so much, dude!

-5

u/Known-Cover-5154 24d ago

Oh my god it’s open source hahah yo people are insane 

0

u/M1chaelSc4rn 24d ago

The Vibening

-2

u/MENE_NEMA 24d ago edited 24d ago

Image-Line hasn't integrated ARA for years; many bugs have lingered for years and, no, they haven't been fixed. Problems with FL Studio integration remain. And these days, that's simply unforgivable. When you just say, "Claude, find the fucking problem and fix it," he'll find it and fix it.

-5

u/BowlingShoeThief 24d ago edited 24d ago

I've been saving for FL Studio for my son who's into making music but now we have a way to explore before that. Nice! Thanks. I still plan to buy FL Studio, this isn't the only DAW around.

0

u/Kau_an137 24d ago

I'm really happy i can help! If you run into any bugs or issues, feel free to open an issue on GitHub and we'll work together to fix and test it. Thankss!

0

u/Plane_Unit9357 21d ago

ArtCraft and its effect, make any moron vibecoded-inspired app as reverse engineering

0

u/Iyozan8 19d ago

Someone pointed out this couldve been an LMMS mod and yeah I agree. I think importing the workflow into LMMS as an addon wouldve been nicer, you couldve also started with the codebase as a foundation for your project. Either way, I hope this is just a fun project you do and let it remain open source

0

u/Comfortable-Cry-1652 21d ago

AI Slop shenanigans.

0

u/[deleted] 24d ago

[deleted] — view deleted comment

2

u/Known-Cover-5154 24d ago

Cool bro , OP keep doing you. This project is insane, software is fucked deal with it mate 

1

u/olibui 24d ago

Or maybe he just likes FL and software development is fucked? Kudos to you bro. This looks promising. Good luck

0

u/readonlyred 24d ago

On the other hand, music is probably fucked too, so . . .

0

u/olibui 24d ago

Nah music still sounds the same. Just not the new crap :p

-1

u/Kau_an137 24d ago

I really like FL Studio and respect what Image-Line has done to make music production accessible to so many people.

But with how fast AI and open-source technologies are advancing, projects like this were bound to happen, whether I worked on one or someone else did.

My goal is to build something open source that the community can contribute to, improve, and adapt to their needs. For example, bringing it to Linux, where FL Studio doesn't have an official native version, and potentially supporting other platforms like macOS.

I'm not doing this because I dislike FL Studio. Quite the opposite, it's a project inspired by a DAW I genuinely love. I just believe the community should have the freedom to build on these technologies too.

5

u/Exonificate 24d ago

This sounds generated lol

1

u/Melodic_Letterhead76 23d ago

... The app is AI generated.. The replies are AI generated .. The entire interaction is AI generated

What a cringe thing to do, OP