π
π
Aamen, aamen, aaa-meeen!
π
π
Aamen, aamen, aaa-meeen!
"Caustic Classics" aka I recreated my intrepretation of Caustic's 14 machines and 16 insert effects as independent CLAP plugins with UI realized using the DSP and UI framework I have for this small audio project that I'm working on :-)
Hello Autowah...
#caustic #audio #dsp #clap #linux #pipewire
Siis et kerrankin kun on niinku kiteytys ja pitchi :D Ja jotenkin aukoton tai "semihyvΓ€". Kompastellen kohti korkeuksia...
Tein elΓ€mΓ€ni ekat siedettΓ€vΓ€t PowerPoint-kalvot [x]
On epΓ€todellinen ja herkkΓ€ olo.
ja ollaman serviceen konffeja tuunasin jonkun verran kanssa. nyt on ns. semmoset "akateemiset" asetukset tai koittanut ainakin jΓ€rkeillΓ€ sellaisen stressikaton...
kaikille 16 corelle siis
Sunnuntain kunniaksi rakentelin 4090 RTX ja 24 GiB pohjalle paikallisen agenttitiimin Ollaman ja Aiderin (agentti-cli) pohjalle. Arkkitehdin ja kehittΓ€jΓ€n ModelFile-tiedostoissa vedin mallit aika ylΓ€kanttiin, ja luvan levitΓ€ 9050X:n kaikillle no rules. Nyt sitten benchmarkkaamaan :-) #tekoΓ€ly
And I think I have the right combination of experience with this one i.e., deep understanding of the tech combined with familiarity of practical day-to-day life of musicians, producers and audio engineers :-) Pipewire has a lot of uncovered potential, it just need to be represented right.
Dropping macOS support, focusing on heavy leveraging of #Pipewire.
More I work on this DAW project, more I see that this could evolve to something bigger than my original ideas.
E.g., dropping #Polyend support is what we call tech pivoting :-)
I dropped Polyend Tracker projects import because I want redefine the synth architecture to fit to like rethinking of the whole UI. But...
However, I've started to put together import for Caustic 3.2 :-) It's to stay forever but I'm sure I'll also consolidate it as DSO one day too...
Where you DON'T start it is by learning e.g., Rust async and Tokio :-) If you don't understand how hardware works, it's a lost game and tools won't keep you on surface. Rust is great if you know the platform but it cannot fix the ignorance.
Benefits. Well, speed. Can be optimized to devices, which suddenly power off with granular recovery etc. Best approach for power management when you bomb less intrusive and counter productive syscalls.
Want do e.g., an Ebook product? This is where to start system engineering in order not to fail.
There's no concept of load and save. There's only concept of open when you open another project or close the project.
There's neither read or write syscalls. TTT does what it does best being a fucking a app peeking and poking and doing silly things, and let's kernel autopilot the IO controller.
TTT file is a mmap of e.g., for the sake of an example, 32 GiB mmap. The in-memory and disk representation are 1:1.
The address pool is used for configurable level multi-level undo supporting also undoing and redoing destructive operations. The snapshot mechanism is CoW optimized.
I hope I find a custodian for this because I'm sort of done with the topic:
github.com/jarkkojs/lib...
I'll focus next on importing Caustic projects, which is not even a tracker but can be done :-) And also Caustic import and playback sidekick the architecture to the right direction.
It's also first app (like in sense "not cli") I've ever made :-)
social.kernel.org/notice/B3vXw...
Sorry, and thanks!
Plus import/playback was covered without owning the device or having access, just with public information. I'd really want to own one tho but I've promised not to buy one before I've finished this :-) It would be great because it will work great and interop with my own tools. This is how it works.
God that takes time, right now working on undo supporting rollback of destructive actions. It is surprising long distance from audio and even GUI visual side to get all editing actions right :-) And further, because I'm not a customer service and hate Github by guts, it will be mailing list project.
What I will release is LGPL v2.1 DSO for marshalling and unmarshalling Polyend file formats. It's me doing effort to support their ecosystem e.g. by lowering the threshold to implement interop to their device for DAWs like Reaper and whatnot. I'll release tracker when I reach my 3-4 track EP DoD π€·
As an open source professional I also know that if I copy user experience of a product, it is wrong and a great way gain some legal troubles. Polyend does awesome job on what they do and I want something for my laptop. And interop means equally for me how I *always* act past, now and in future π
TTT will have its own project format and set of effect commands. Given my EU protected legal rights, I can and will retain import functionality just like for Amiga Protracker/Digitracker MOD files but it will save TTT format. The software is GPLv3 and UI is fully decoupled, so you do you do π€·π 2/2
Just to clear up some facts, I'm not in #Discord but just saying this: I have no stand with Polyend Tracker. Importing the file format was just a good benchmark to get "my own thing" somewhere.
I'll add Caustic inspired mixer and evolve UI more to Octamed than Polyend. 1/2
#polyend #tracker
My new UI architecture backend side for TTTracker:
1. ttt --backend software: MiniFB + software
2 ttt --backend vulkan: Vulkan (Vk*) + GLSL
3. Input arrives always through MiniFB shenanigans.
MiniFB enables e.g., MS-DOS :-)
github.com/emoon/minifb
#tracker #musicproduction #chiptune
Longer story about my small sidekick project: social.kernel.org/notice/B3vXw...
Available here on Internet with GPLv3 license some day. Customer service will suck but contributions are welcome :-)
#tracker #polyend #daw #audio #dsp
kunhan ei oo gemini, kun se on Γ€rsyttΓ€vin :-) ennemmin vaikka skynet kuin gemini....
I don't get "AI native". I'm not "AI native". I'm neither "spoon native" or "chainsaw native". Get real, tools are fucking tools lol.
One of the more ambitious features I'm planning for the tracker is export dawproject. A tracker project can multiply in to quite many more tracks than the eight tracks in the original project as instrument can swap per step in a single track. I.e. a way to continue a song in #BitwigStudio :-)
I just learned what "JUCE" is and realized I don't have to learn further as I have my own stack from ground up :-)
#audio #dsp #JUCE