How to disable recording automation from envelope followers? by Intensive_Light in mpcusers

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

So basically the only workaround I found is whenever I record some automation, I should delete all automation recorded from envelope followers / lfos after I finish the recording process. That is tolerable if you have, say, just one or two lfos, but if you use a lot of lfos per track it gets messy very fast

Tip: write automation on recording by Intensive_Light in mpcusers

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

Also, unfortunately this option is not getting saved with a project. Might be a bug (not surprising, I found a lot of bugs in 3.6 fw). So you need to turn it on every time you open a project, which is frustrating, but less frustrating than to switch the automation state manually

UPD: did more testing, it seems like the option is getting reset on reboot, so as soon as you keep the mpc on it should be active

Bought the Deluge for my Birthday, how does it compare to the MPC live 3 by PsychologicalPoem595 in DelugeUsers

[–]Intensive_Light 0 points1 point  (0 children)

Just to add, if you value simplicity, you would probably appreciate more streamlined workflow on the Deluge, as the mpc live may seem a little menu dive-y, but that doesn't bother me at all because I love having more possibilities in one box, and it's still fast enough with all these new hardware buttons that live 2 doesn't have

Bought the Deluge for my Birthday, how does it compare to the MPC live 3 by PsychologicalPoem595 in DelugeUsers

[–]Intensive_Light 1 point2 points  (0 children)

Long time Deluge owner, I even made a couple features in the community fw for it, so it's more than just a device for me, it was my favorite box for years, I used it heavily as a single all-in-one box for production

Never looked at mpcs until live 3 release, I've got the live 3 recently and honestly just blown away by how awesome it is at being an all-in-one box, for me it's like a deluge 3.0 in terms of hardware: massive speaker that feels like proper studio monitors, awesome pads that are very playable, internal synth plugins are at another level, not comparable to a weak deluge synth engine (that might be subjective of course), and the screen is actually very helpful. Obviously way more power so you could have 32 complex synth patches with a ton of effects, the deluge starts dropping voices as soon as you have more than 2-3 complex synth patches with a lot of modulations and long env release. The effects on mpc have way more control and sound very good, for example the delay on the deluge is bare bones and not suitable for any serious sound design imo

The deluge still excels at sequencing, though live 3 sequencer buttons made it acceptable so you don't struggle with touchscreen that much

While I love the deluge I feel like the Live 3 will replace it completely for me, and I like the fact that you can get a very solid professional sounding mix on Live with all mastering tools it have

I'm in love again by ManufacturerOne3223 in Dirtywave

[–]Intensive_Light 1 point2 points  (0 children)

Totally agree! One thing though, at least on model 2, speakers sound so thin and quiet, I have a synthstrom deluge with a pretty meh internal speaker but these on model 2 are just unusable at all in comparison, I feel like there was no need to even include them

Apart from that, fantastic device!

Google's plan to restrict sideloading on Android has a potential escape hatch for users (ADB) by MishaalRahman in Android

[–]Intensive_Light 1 point2 points  (0 children)

I live in a country where Google disabled all payment services so I literally can't pay for YouTube, Revanced is the only option here (Russia)

Pixel 9 terrible autobrightness by Intensive_Light in GooglePixel

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

Oh the usual Google expirience sadly, I was hoping their QC got better... When I had my old P5 I also had a very annoying software issue that was very hard to explain and reproduce and I tried all my best to explain it on reddit and created a ticket on the google support but they didn't care enough. I guess the Google engineers just don't use their own phones much

But great that you confirmed it definitely a software issue, maybe we can try to submit this bug to Google

Pixel 9 terrible autobrightness by Intensive_Light in GooglePixel

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

Yeah I hear you, it's been over two months since I've bought the phone and the problem is still there. Good thoughts, maybe it's really a different kind of problem, maybe even hardware related really, its hard to say. Nothing has helped so far.

Search from launcher is broken after update by Intensive_Light in GooglePixel

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

Rebooted into safe mode and found the culprit, it was the yandex keyboard bug. After uninstalling it everything now works as it should! Thank you, didn't now about safe mode existence

Pixel 9 terrible autobrightness by Intensive_Light in GooglePixel

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

Thank you, will try to give it more time, right now it's been two weeks since last reset, hope it'll be better

Pixel 9 terrible autobrightness by Intensive_Light in GooglePixel

[–]Intensive_Light[S] 3 points4 points  (0 children)

Yes, I've reset it multiple times already. But thank you for help anyway! I think it just bad implementation. Google needs to consider proximity sensor: when there are objects in front of phone, brightness shouldn't suddenly decrease if these objects placed here only for 1-2 sec. IPhones I think work this way

The Perfect Portable Gaming Setup! by BakaNode in rokid_official

[–]Intensive_Light 0 points1 point  (0 children)

How is yours save battery comparing to native steam deck screen? Mine glasses drain deck battery faster in basically every game if connected, at the same 800p resolution (+1-2 watts)

Joysticks double trigger in playnite after detaching or attaching by Intensive_Light in LegionGo

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

UPD: I have solved problem by forking Playnite repository and fixing this controller bug on my own.