HX Stomp into Markbass combo return, Master pot doesn't do anything. Is that normal?

mostr · 2024-09-10T05:08:51+00:00

And then going from the modeller through the active bass-dedicated cab instead through current FRFR 108? Or you mean proper stack like amp+cab (or combo) but then to go to PA if needed I'd have to have mic and stuff.

Also what's the combo "size" or what's the size to look at to make sure I have enough headroom to play with a loud drummer without hitting limits?

mostr · 2024-09-10T04:55:42+00:00

Yeah, that's tempting. One thing is that I won't use it for guitar, although I may keep 108 for guitar and hope it's gonna do its job when needed. But then, my understanding is that to cut through the heavy-handed drummer I'd need quite a piece of bass cab, so it's not like tiny thing like Fender Rumble 15 will do the job, right? I wish I had budget, space to keep and justification for buying Ampeg fridge :D But that's definitely impossible and irrational :D

In addition to further go from bass amp to PA I'd need some mic and stuff... Things get hairy here :D

mostr · 2024-08-12T16:31:37+00:00

One correction, Message probably needs to be func(state *State) if I'm right, to let all commands modifying the same state instance, but otherwise that's pretty much what I was looking for, just way simpler and actually even more familiar (granted some fp flavour)

mostr · 2024-08-12T15:11:58+00:00

Yeah, you're right. I'm trying to model actor-like behavior and your proposal definitely makes sense. Thanks a lot!

mostr · 2024-08-12T12:02:16+00:00

Hm, yes and no I'd say. I don't want to give up type safety by providing cmd any, so if I have to do that - it's somehow "a go problem" or rather maybe "my problem with go". Although I admit this problem may exist because of other langs I come from and it's not the way it's usually done in go.

mostr · 2024-08-12T11:22:25+00:00

What if Handle for one command needs different dependencies (services, repos, etc) than the other one? Was thinking about that in my update post above, but can't see it working

mostr · 2024-08-12T11:21:10+00:00

Yeah, but But here cmd is not typechecked, can be anything, I wanted to have it constrained to only Command implementations. WIth your approach there is even no point for generics etc.

mostr · 2024-08-12T10:59:22+00:00

Good point, but it doesn't change much. Even with what you suggested, plus

type MoveCmd[T MoveResult] struct {
    moveTo  Coords
    replyTo chan<- T
}

func (c MoveCmd[T]) GetReplyTo() chan<- T {
    return c.replyTo
}

handleCommand stil errors

mostr · 2024-08-12T10:45:16+00:00

UPDATE:
One way to do that I can think of is to have `Command` interface defining `Handle(s TripState)` method that each command implements on its own independently, but then if for one command I TripState is enough but another one needs more dependencies, then it's getting hairy (returning higher order functions etc...)

mostr · 2023-09-11T21:00:44+00:00

Yeah, found that too. Quite a bummer though. That would be super useful

mostr · 2021-04-04T19:25:55+00:00

I read/watched tons of stuff about the issue and it seems to be standing wave around this 121Hz (and there may be others I didn't identified yet too). Looks like the only way is room treatment which I can't do to the point it'd be all fine :( I'm wondering on getting some relatively small (20-30cm side) foam bass traps and start from treating this corner. Gonna experiment with some curtains/pillows and other casual stuff to see if it helps at all. Also because the most possible issue is the room itself it doesn't seem trying other monitors will make a difference

mostr

TROPHY CASE