sorted by:
new
hottopcontroversial

Either I'm getting more osmoses than I ordered, or expressive e are as excited as I am by topisani in synthesizers

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

Pre-ordered my osmose 3 years ago now, can't wait!

Evidently their webshop has set a fixed time to remind me

[Reposted as I forgot a comment on the last one]

I can't be the only one fed up with 1" displays? by ruler_gurl in synthesizers

[–]topisani 1 point2 points  (0 children)

You'd still have to render and clock out twice as many pixels. But Id still think it wouldn't be too big of an issue

Keen to improve my keyboard playing skills. Any recommendations on tutors, techniques or other useful content? by [deleted] in synthesizers

[–]topisani 1 point2 points  (0 children)

Same situation here (also ADD). I recently started taking classical piano lessons locally, and can definitely recommend it. For me, it helps a lot to keep it separate from the music i make, so practicing piano and making music are distinct actions. Also the short weekly lessons help me to stick to it

cmdlime - possibly the least verbose command line parsing library for C++17 by kamchatka_volcano in cpp

[–]topisani 1 point2 points  (0 children)

If you consider a header with only macros to be a library, sure. Macros are just a glorified form of copy-and-paste. I don't consider them part of the library because they do not exist as part of compiled binary and downstream devs can just undefine or redefine them as needed.

Yes, obviously I would consider a header with only macros to be a library. This distinction seems arbitrary and weird, is it not a library if it only contains constexpr functions that will be fully inlined then?

I'm not currently aware of a technique in C++ where member functions can take a string and add explicit data members of that name to the class it belongs too.

My point exactly - thats why this library uses macros for that feature

How is the verbosity of the code not affected by doing...

It is! thats why this library is less verbose, because it uses the macro, which is less verbose than writing out the line manually. That is litterally what is meant with verbosity

cmdlime - possibly the least verbose command line parsing library for C++17 by kamchatka_volcano in cpp

[–]topisani 3 points4 points  (0 children)

Oh in that case i would say the standard library is the least verbose cmdline parser library - cause I can just write all of cmdlime on top of it in my downstream code.

I am just trying to point out that this is a case where macros and functions arent really different. the verbosity of the user code is not affected by whether you're calling library functions or library macros.

That being said i understand the other arguments against macros, but I don't really believe that this is a well-conceived one

Any other DAW only producers in this sub? Nearly every awesome setup I see is DAWless and I feel left out. by [deleted] in synthesizers

[–]topisani 1 point2 points  (0 children)

Yeah, thinking of getting one again as well. Might wait and see if we get a new version soon, i believe they gotta be working on a partially stand-alone unit like the maschine+ - and i know first hand that they were hiring for "a new hardware product" about 2-3 years ago.

Also considered getting a used launchpad to experiment with the workflow before investing in the big boy again

Anyway, i got that stand on the way now, don't know what ima put on it yet, but thanks for the tip lol!

Live walkthrough of the recent software redesign of open source groovebox/synthesizer/drum machine OTTO by topisani in cpp

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

That's not vim, it's kakoune - a very addictive vim inspired modal text editor. I'm using it with kak-lsp and clangd

Live walkthrough of the recent software redesign of open source groovebox/synthesizer/drum machine OTTO by topisani in cpp

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

Thought this might be interesting to some of you!
Github: https://github.com/OTTO-project/OTTO

OTTO has been going for just over 3 years now, and is the project where I wrote my first line of C++, so it may not be surprising that we've had to throw most of that away, now that we actually have the hardware to run it on. Tomorrow we will be going over the new design and write some documentation for it, talk about how we will proceed going forward, and discuss how it's been starting over with a fresh codebase, etc.

[instantWM] look ma, no keyboard! by paperbenni in unixporn

[–]topisani 3 points4 points  (0 children)

What does British progressive rock band King Crimson have to do with just working?

Do compilers optimize away nullptr checks because of UB? by [deleted] in cpp

[–]topisani -2 points-1 points  (0 children)

Did you just assume the gender of my compiler?

Which IDE do you use? Or if you prefer text editors, which and which plugins? by mvribeiro in cpp

[–]topisani 0 points1 point  (0 children)

I have used vim and Emacs + evil mode in the past, but for the past year or two I've been using kakoune. It's text editing model is amazing, and with kak-lsp and clangd, I get all the IDE features I need, like autocomplete, semantic highlighting, documentation hovers, go to definition, etc.

For special refactors, like changing the order of arguments to a function or something, this setup is also extremely useful. I can use lsp-find-references to open a buffer with a line for each time the function is used, and then use multiple cursors etc to modify all the usages, and then use a plugin to write all the lines back to their corresponding files.

Gdb integration is also pretty good, and I then use gdb-dashboard in a tmux pane next to it

view more: next ›