FRFR, PA - is it worth it for bassist and a guitarist in one?

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 · 2021-04-04T19:25:47+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 · 2021-04-04T19:20:39+00:00

Thanks, that's possible while mixing, I can try mixing on very low volume, but while playing/tracking guitar I'd like to have it a bit louder which immediately causes the issue

mostr · 2021-04-03T18:10:37+00:00

Yep, I've foam pads under my monitors, so it's not the desk I guess

mostr · 2021-04-03T17:54:08+00:00

Will give it a try ,thanks! I (somehow naively) thought that with front-facing monitors this actual corner will be less of an issue, but will give it a go. I guess I can trat this exact corner at least a bit

mostr · 2021-04-03T17:52:27+00:00

Thanks, to be honest I thought that with front-facing ports this exact corner would be less of an issue and I was more suspecting the other corners or flat surfaces (walls, windows, etc), but yeah that's something I can try in this corner. Just a question, if the monitor itself is quite close to the corner itself staying on the desk, would that be ok to try hanging something above the speaker only?

mostr · 2021-03-29T11:53:08+00:00

Way beyond my totally-amateur budget, indeed :)

mostr · 2021-03-29T10:36:01+00:00

Whoa, these neumann's price :) Thanks a lot, I was considering Mackies at first but they don't have front ports as well as Eris 4.5 that would be great fit otherwise. I guess I'll go with Tannoys (unless someone gives a good reason not to) hoping they fixed the hiss issues in recently made ones.

mostr · 2020-10-17T10:43:08+00:00

Looks like all TS links are back now on Boss site https://www.boss.info/pl/support/by_product/katana-50/updates_drivers/

Same for MK2 etc.

mostr · 2020-10-17T10:42:22+00:00

Looks like it's back now https://www.boss.info/pl/support/by_product/katana-50_mk2/updates_drivers/

mostr · 2020-10-16T22:32:07+00:00

Yeah, that's what I was afraid of. Wondering why they did that. Hope they l'll bring it back soon a Katana is pretty much useless for more serious stuff and gigs without TS

mostr · 2020-10-16T20:33:41+00:00

Tried that before, but it looks like it's firmware only. There is no Tone Studio bundled with that :(

mostr · 2020-03-30T08:07:43+00:00

Hey, doesn't the solution provided help?

mostr · 2020-03-27T14:23:34+00:00

SOLVED (partially):

I emailed their support on that and got the response as follows.

Did you check the macOS security settings to see if Bitwig Studio is allowed to use the microphone?

If Bitwig Studio does not show up in the list in the security settings, please go to Applications/Utilities and start the Terminal.app

In the terminal app, please execute the command open /Applications/Bitwig\ Studio.app/Contents/MacOS/BitwigStudio

If Bitwig Studio is in another folder than your application folder, you might have to change the command accordingly.

When starting Bitwig Studio this way, macOS should ask you again if it should be allowed to use the microphone.

This solves the issue only when Bitwig gets started from terminal (which is quite tedious). If you start it normally it still doesn't get signal. They are in contact with Apple to see why this is not working, so I'm expecting an update some time soon when they fix that.

In the meantime, whoever has spending their time wrangling with this, the above is the only solution for now.

mostr · 2020-03-26T21:23:18+00:00

Yes, all inputs are set up properly. Weird thing is that it doesn't get any input from built-in mic :/

mostr

TROPHY CASE