Year 4 — Sustainability and Ethics With hundreds of thousands of monthly visitors, MusiHacks faced choices about monetization. Lina and Mateo resisted autoplay ads and invasive tracking. Instead they launched a modest subscription tier offering ad-free reading, early access to masterclasses, downloadable presets, and monthly office-hours with guest producers. They established transparent creator revenue splits for any paid content that featured independent artists. The team also created editorial guidelines emphasizing attribution, sample-clearance education, and ethical remixing—believing that teaching legal and respectful practices was part of supporting the music ecosystem.
Year 1 — Finding a Voice Early traffic was tiny but passionate. Lina wrote interviews and breaking-down-the-track posts that attracted hobbyist producers; Mateo coded a clean, fast interface and published short explainers about sampling, vocal chaining, and arrangement. MusiHacks cultivated an ethos: curiosity first, commerce later. The founders refused adware-driven growth and focused on organic word-of-mouth. A handful of popular posts—one deconstructing an indie-pop hit’s vocal production and another showing how to recreate an ARP synth patch—brought steady growth and the first modest sponsorship from a boutique plugin maker.
Product Evolution — From Articles to Interactive Learning Technically, MusiHacks evolved into a learning platform. Interactive features let users load stems into a browser-based mixing console, toggle isolated tracks, view real-time production annotations, and experiment with suggested plugin chains. The platform integrated a simple MIDI playground where visitors could reverse-engineer iconic riffs and then export their ideas. These interactive additions transformed passive readers into active learners. musihackscom
MusiHacks.com began as a small bedroom project in 2018 when two college roommates, Lina Ortega and Mateo Chen, bonded over a shared frustration: music discovery felt siloed, opaque, and driven by algorithms that prioritized clicks over creativity. They wanted a space where curious listeners could explore fresh sounds, dive into the craft behind songs, and connect directly with independent creators. They launched a simple site with three features: short editorial spotlights on emerging artists, annotated song breakdowns explaining production tricks, and a community forum where musicians swapped tips and stems.
Today — A Sustainable Niche By 2026, MusiHacks.com remained a mid-sized, privately run hub focused on education, community, and ethical music-making. It employed a small editorial team, a product group, and a rotating roster of contributors. Revenue came from subscriptions, sponsored educational series transparently labeled, and occasional workshops—not from invasive ads or data-mining. The brand’s reputation rested on trust: clear crediting, fair compensation for contributors, and practical, hands-on teaching. Year 4 — Sustainability and Ethics With hundreds
Challenges and Criticisms MusiHacks was not without problems. Some critics said the site romanticized “hacking” music production—turning craft into commodified recipes. Others worried about gatekeeping when editorial taste shaped which artists received visibility. Lina and Mateo addressed these concerns by publishing a public editorial policy, rotating guest editors from diverse scenes, and launching a grants program to support creators outside their usual networks.
Year 2–3 — Community and Tools As the readership grew, MusiHacks expanded beyond essays into practical tools. They added downloadable project templates, a searchable database of open-license sample packs, and short video masterclasses. The forum evolved into a collaborative workspace: remix challenges, feedback threads, and producer match-making. MusiHacks introduced “Stems Night,” a weekly event where creators uploaded stems and the community remixed and critiqued them. These activities strengthened loyalty and turned casual readers into contributors. They established transparent creator revenue splits for any
Legacy and Future MusiHacks’ core legacy is cultural: it helped normalize open discussion of techniques and failures, promoted respectful remix culture, and showed that a sustainable music-education platform could exist without sacrificing principles. Looking ahead, the site planned to deepen its learning paths, launch mentorship matchmaking, and expand multilingual content to serve non-English-speaking producers—continuing its mission to make music craft accessible, practical, and humane.
This is a collection of videos in a youtube playlist demonstrating the sound of guitarix.
nextguitarix is available in most todays Linux distributions. In 9 out of 10 cases there's no need to compile guitarix but to install it via software center or package management system of your preferred distribution. guitarix is supported by the following Linux flavours and all their derivates:
To get the bleeding edge development state of guitarix you have to clone our repository and build the source from there. Please note that this kind of installation isn't recommended for productive systems at all since this is the source code we're actually working on.
git clone https://github.com/brummer10/guitarix.git
Change to the trunk directory of the source code and execute the following commands in a terminal:
git clone https://github.com/brummer10/guitarix.git cd guitarix git submodule update --init --recursive cd trunk ./waf configure --prefix=/usr --includeresampler --includeconvolver --optimization ./waf build sudo ./waf install
For compiling guitarix on your machine you have to ensure that you have the following development packages installed:
Of course you need all packages for a properly set-up build system like build-essentials, make, gcc also installed on your machine.
Creating free and open source software is fun on one hand but a huge amount of work on the other hand. Even though you're not a programmer perhaps you are willing to help this project in growing and getting better. In most cases FOSS is the success of a community, not a lonesome champion.
One of the most essential parts of a successful program aside from the code is the documentation. One can never have enough from it, but first of all we need some basic work to be done. Contact us on Github if you're willing to help us out in this topic.
Another very essential part are factory presets shipped with the product. They need to meet a specific standard in quality like an equal output volume - ask us on Github if you want to contribute.
You are able to create high quality video and/or audio material? We're always deeply grateful for some cool demos presenting guitarix' capabilities and sound.
Please file bug reports whenever you encounter a problem with our code. This helps a lot in providing something like quality management.
If you know how to handle code - we're always happy about Pull Requests!