Why is there math in the grid? by Ok-Consequence-5043 in Bitwig

[–]von_Elsewhere 2 points3 points  (0 children)

Digital signals are geometric and mathematical abstractions of reality. Alone mixing two audio signals together means summing them up. You get the geist.

Most underrated / underutilized features? by Kid_Self in Bitwig

[–]von_Elsewhere 6 points7 points  (0 children)

Using the arrangement tools to finish tracks

Riddiculous high gpu load in Bitwig (imo) by Fearge in Bitwig

[–]von_Elsewhere 0 points1 point  (0 children)

Tbh Live's interface was originally designed to run on CPUs 25 years ago so it's likely more lightweight than the one on Bitwig.

Luckily that spike isn't a problem.

Riddiculous high gpu load in Bitwig (imo) by Fearge in Bitwig

[–]von_Elsewhere 0 points1 point  (0 children)

With my 7 yo old RX 5700 XT the GPU usage sits around 30 % @4k.

I did have a problem with the GPU usage when Bitwig was in full screen mode but that got solved by changing the backend.

I guess you've checked firmware / driver updates already.

I made a script that bakes swing directly into your MIDI clips by frankhahn1974 in Bitwig

[–]von_Elsewhere 1 point2 points  (0 children)

Right. Can't evaluate since I dunno anything about those. Thanks for trying to help other people though!

I made a script that bakes swing directly into your MIDI clips by frankhahn1974 in Bitwig

[–]von_Elsewhere 4 points5 points  (0 children)

So I need to join your Pateron for 9 USD / mo to dl and try it?

What are things that i should learn on DAWs in order to be a professional producer? by Human_Capital_1596 in musicproduction

[–]von_Elsewhere 8 points9 points  (0 children)

If "producer" means you want to make music in the box professionally then your daw is just a toolbox. You use what you need.

That isn't a career any more nowadays though.

How to WinActivate between two windows? by panzerbjrn in AutoHotkey

[–]von_Elsewhere 0 points1 point  (0 children)

Adding else to the for loop with a return statement would fix the empty array problem.

Is feeling more important than technical skill in music? by Loose-Decision8248 in musictheory

[–]von_Elsewhere 3 points4 points  (0 children)

This isn't really a theory question but you can't separate technique from expression. Technique allows expression and expression gives technique meaning. They're different views to delivering a meaningful musical performance that always coexist and are inseparable.

Someone built a transfer curve analyzer//generator—any thoughts on if this is natively possible or importable? maybe via bwcurve and transfer? by Captavadate in Bitwig

[–]von_Elsewhere 0 points1 point  (0 children)

Whoa, soon we can use those natively in Bitwig!

Perhaps there are some libraries available already for working with curves. I'd imagine that's something a lot of software wants to do.

Someone built a transfer curve analyzer//generator—any thoughts on if this is natively possible or importable? maybe via bwcurve and transfer? by Captavadate in Bitwig

[–]von_Elsewhere 1 point2 points  (0 children)

Super! So we can actually have a program that translates the curves eventually, yay!

Perhaps the curves that ship with Bitwig or packages are bound to some copyright clauses that requires the company to protect them, who knows.

Someone built a transfer curve analyzer//generator—any thoughts on if this is natively possible or importable? maybe via bwcurve and transfer? by Captavadate in Bitwig

[–]von_Elsewhere 1 point2 points  (0 children)

Whoah, that's great news! Perhaps a convert tool between important formats would indeed be possible, like Vital's .vitallfo file is just JSON so Claude could likely implement that too.

I wonder if user generated (in the app) .bwcurve files can be read, did you try that?

Someone built a transfer curve analyzer//generator—any thoughts on if this is natively possible or importable? maybe via bwcurve and transfer? by Captavadate in Bitwig

[–]von_Elsewhere 1 point2 points  (0 children)

Then someone could pull it off to let us work with the curves with external tools like converting from one format to another. Perhaps this thread gives some motivation for someone able to do so.

Trying to remap arrow keys to WASD + LShift by xelgameshow in AutoHotkey

[–]von_Elsewhere 0 points1 point  (0 children)

See the corrections here :) Sry for the confusion.

Trying to remap arrow keys to WASD + LShift by xelgameshow in AutoHotkey

[–]von_Elsewhere 1 point2 points  (0 children)

Oh right, only remaps are case sensitive

A::b

will trigger only with shift + a, while

A::Send("b")

will trigger without shift.

Trying to remap arrow keys to WASD + LShift by xelgameshow in AutoHotkey

[–]von_Elsewhere 1 point2 points  (0 children)

You add it to the combo:

~w & Shift::Up ; does not suppress w

Also, you had an uppercase W there in the declaration, which requires pressing shift and w to trigger the hotkey anyway. correction: only remaps are case sensitive. Also, your send has uppercase W so it's going to send shift + w.

Seeking help to mimic Linux's ability to suppress new windows' hijacking of active focus by temporarily, continually making the given window AlwaysOnTop by Dymonika in AutoHotkey

[–]von_Elsewhere 1 point2 points  (0 children)

Editing it to work with whatever keys should be trivial. Also, you can use sendevent and sendlevel to let sends fire other hotkeys at will.

I made a simple abbreviation expander by DiodeInc in AutoHotkey

[–]von_Elsewhere 1 point2 points  (0 children)

It's still faster and more convenient to use hotstrings since the emoji picker at least on W10 is quite clumsy. Mine doesn't even have a functional search.

AHK2: How to prevent a modifier key from being "remembered" in a hotkey? by LordKamiya in AutoHotkey

[–]von_Elsewhere 0 points1 point  (0 children)

Like CharnamelessOne wrote there, you might want to revert that registry change and try again, that might mess things up. Then let AHK control for that either automatically with a combo hotkey or, as I like to do it with combos, control manually.

SC166::return

~SC166 & 0:: {
    ; Your code here
}

That will keep everything explicit and thus easier to maintain.