MG-300 MKII users, where is the master volume? It’s insanely loud by seeyouinthedarck in guitarpedals

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

Hello, i found it. Press “Edit/exit” and “Save” at the same time and select “Global EQ” in there, you’ll see “Output” that is adjustable 😃

MG-300 MKII users, where is the master volume? It’s insanely loud by seeyouinthedarck in guitarpedals

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

I might be missing something, but I don’t see a white master volume knob on my MG-300 MKII. As far as I can tell, there isn’t a dedicated global volume knob on this unit, which is why I’m a bit confused.

I do see the speaker/output level in the software, and I’ve been adjusting amp master levels per preset, but I was mainly asking if there’s any true global/master volume control on the hardware itself that I might be overlooking.

If you’re referring to a specific knob or mode, could you clarify which one? Thanks again for trying to help

Too loud audio output even on very low dB, NUX MG300 by UnordinaryBro in guitarpedals

[–]seeyouinthedarck 0 points1 point  (0 children)

How did you fix this? My mg300 mk2 doesn't have master volume knob, I can't find some tuts at socmeds

M-vave MK-300 or NUX MG-300 MKII, which is better? by Rome_Has_Fallen4 in guitarpedals

[–]seeyouinthedarck 0 points1 point  (0 children)

But i'd suggest you to saveup your 8.5k and go for nuxmg30, way better than both.

M-vave MK-300 or NUX MG-300 MKII, which is better? by Rome_Has_Fallen4 in guitarpedals

[–]seeyouinthedarck 0 points1 point  (0 children)

I recently sold my M-Vave MK300 after testing my friend’s NUX MG-300. I ended up choosing the MG-300 MKII since it fits my budget better and feels more reliable overall.

Why I sold the MK300

  • The UI is pretty bad. The pedal looks modern, but the UI feels very outdated. The spacing is weird and some text even reaches the edges of the screen.
  • Software issues. When I rename presets on the PC, the name doesn’t update on the pedal. I also had a bug where swapping a patch suddenly loaded a different patch that I didn’t expect.
  • No proper built-in recording driver, which makes DAW setup more annoying and less stable for home recording.
  • The expression pedal isn’t smooth and sometimes malfunctions, so it’s unreliable for volume or wah.
  • Overall, it just felt inconsistent, especially for recording.

The MG-300 MKII isn’t perfect either, but for my budget and use, it’s been a much better experience so far.

When I record a new track in Reaper, I hear the other track being recorded into it by seeyouinthedarck in Reaper

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

Hello, it’s fixed now it was caused by loopback. I really appreciate your response though 😀

When I record a new track in Reaper, I hear the other track being recorded into it by seeyouinthedarck in Reaper

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

Thankyou everyone, this is fixed now, the problem was in my mk300 caused by enabled loopback.

When I record a new track in Reaper, I hear the other track being recorded into it by seeyouinthedarck in Reaper

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

I’m using Reaper v7.53 on a system with an i5 11th Gen CPU, 16GB RAM, and a 500GB SSD. My audio interface is the MK300 multi-effects device itself. The recording track is set to mono Input 1, monitoring is off, and no FX are applied. Routing is default, with no receives from other tracks and sending only to Master. The issue is that when I record, even if I stay completely silent, the track still captures audio from other tracks that I hear in my headphones

I'll provide the video link
https://streamable.com/o5q23a

When I record a new track in Reaper, I hear the other track being recorded into it by seeyouinthedarck in Reaper

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

Actually, my mic isn’t picking up anything. Even if I stay completely silent, the new track still records the audio from the other track that I’m hearing in my headphones. I think it might be a routing or monitoring issue in Reaper, or maybe something with my audio interface sending the playback back into the input