Hi There,
Here are a number of mixers likely useful for those of you looking to minimise mixer screen real estate.
There are 2, 4, 8, 12 and 16 channel mixers in the set.
Also there is a bigger 16 Channel mixer (size wise) that is of a similar design, but with a different panel and a few extra functions.
This is the mixer I mostly use for mixing and distribution to different outputs to check mixes on different speakers and headphones, etc.
I have not exhaustively tested every last function, so if you run into a problem, please let me know and I will have a look at it for you.
regards
maus
Small Mixer Family
Small Mixer Family
- Attachments
-
- SmallMixer2.png (30.02 KiB) Viewed 10557 times
- Bud Weiser
- Posts: 2899
- Joined: Tue Sep 14, 2010 5:29 am
- Location: nowhere land
Re: Small Mixer Family
Thank you, Maus. I´ve found and downloaded.
No time for testing today, but over the weekend.
Is "phase lock" testing possible without using SDK ?
If yes,- how ?
No time for testing today, but over the weekend.
Is "phase lock" testing possible without using SDK ?
If yes,- how ?
Re: Small Mixer Family
Hey Bud,
I am not sure about phase locking.
You have peaked my interest though and I might look into phasing to see what can be done.
I personally have never had an issue.
A lot of my mixing and mastering is now done in Cubase/Wavelab so I can use Izotope, Sonible and NuGen tools.
I do bring tracks out to Scope to use scope Fxs/Synths/etc.
These tracks are then fed back to audio track s in Cubase and tweaked to eliminate recording delays.
I do use Pi in Cubase to phase align tracks like kicks and bass, and I check mixes in mono to make sure nothing disappears due to phasing, but currently that's about it.
Good luck with the new mixers.
regards
maus
I am not sure about phase locking.
You have peaked my interest though and I might look into phasing to see what can be done.
I personally have never had an issue.
A lot of my mixing and mastering is now done in Cubase/Wavelab so I can use Izotope, Sonible and NuGen tools.
I do bring tracks out to Scope to use scope Fxs/Synths/etc.
These tracks are then fed back to audio track s in Cubase and tweaked to eliminate recording delays.
I do use Pi in Cubase to phase align tracks like kicks and bass, and I check mixes in mono to make sure nothing disappears due to phasing, but currently that's about it.
Good luck with the new mixers.
regards
maus
Re: Small Mixer Family
Awesome! Thanks maus.
Re: Small Mixer Family
Thanks for the excellent devices
Re: Small Mixer Family
Bud, I am sure it is possible to check phase in both scope and scope sdk.Bud Weiser wrote: Fri Aug 15, 2025 12:21 am Is "phase lock" testing possible without using SDK ?
If yes,- how ?
I am no expert on phase measurement, but I think you can do it using similar setup to that shown below.
I just fed the same signal to all inputs and then look at the output for any distortion.
The Oscilloscope (available in Scope) and the same output signal fed to a Cubase track with plugin 'MOscilloscope' (free plugin from MelbaProduction) appears to me to have no visible phasing issues as a result of summing all the inputs associated with the Small Mix 16.
Happy to be corrected if my assumptions are incorrect.
regards
maus
- Attachments
-
- ScopePhasing.png (194.69 KiB) Viewed 10430 times
-
- MOscilloscope.png (50.93 KiB) Viewed 10430 times
Re: Small Mixer Family
Easier than that, you want a 1 cycle click or ramp that starts at 100 and goes to 0, then resets in 1 sample, etc. Record the output to see the offsets, and toggle channels to see where they misalign. it only matters where you will have parallel processing (like parallel compression, etc) or where you mix multiple mics open to the same source, and of course stereo pairs are the most critical. Send effects (100% wet return) and mixing discrete sources is much less of a concern, though when layering drums you need to again be careful (easiest in the DAW in this era).
Also, Scope projects can load differently if devices aren't locked to specific dsps. This is where the phase discontinuities tend to come from to begin with, and they can load differently on subsequent loads, though it's mostly predictable if you don't make major changes once a project has been loaded a *second time*. This is because the project tends to load in the same order on reload (once built). As a dev, locking things that should fit on a single dsp into a single block to ensure they are phase accurate was the main task. Note it's been over a decade since I was in SDK and I'm not the SDK master here, so forgive my poor choice of term(s) if that happens to be the case.
Also, Scope projects can load differently if devices aren't locked to specific dsps. This is where the phase discontinuities tend to come from to begin with, and they can load differently on subsequent loads, though it's mostly predictable if you don't make major changes once a project has been loaded a *second time*. This is because the project tends to load in the same order on reload (once built). As a dev, locking things that should fit on a single dsp into a single block to ensure they are phase accurate was the main task. Note it's been over a decade since I was in SDK and I'm not the SDK master here, so forgive my poor choice of term(s) if that happens to be the case.