![]() ![]() Which is weird, because my RME interface has multiple outs. I think you're right - MB3 has somehow 'hijacked' the output on my RME interface, that does not allow other programs to utilize audio. Other DAWs don't seem to have this problem. I've also run into problems regarding getting audio from Youtube or browsers or just even my normal media player, while MB3 is running. Plus, being able to select a hardware of your choice without 'virtual' methods should be a basic thing, regardless if you run dual-core or 8 core. I know there's something to it, and was hoping that would be considered by the makers. any ASIO freezes 90 % on my dual core laptop win7 Sometimes a "non existing" works better.Īlso if V2 is opened after V3 it cannot find Jack if they were stealing Jack from one another it depends which audio engine combination was chosen before but to many variations to remember which causes what. I mean more combinations of "Audio System" and "Device" can be chosen than physically exist. My system soundcard does not have ASIO but I can select it as an option, though false, in V3 OnV3 more are listed and can be choosen though not exist in reality On V2 it listed some and they were all real The sound engine for me a bit confusing in V3. Gonna be playing around with this for awhile, see what else crops up. This time round, MB3 starts a 48khz session smoothly. Under 'Port Audio', you're still allowed to choose the audio interface of your liking, so that's cool. Actually this time, when I start MB3, instead of choosing 'ASIO', I went for 'Port Audio' instead. Hope the bugs and improvements get addressed, because just the default sound of this thing is worth the price of admission in the workflow. DAWs like Logic, Cubase, FL are really quite unbeatable for MIDI capability. Since my work primarily involves compositional work, I will still use Cubase for sequencing, editing and basic mixing, because for one I'm used to it and I just move alot faster within that environment. I can't explain it, but Harrison has definitely done something very right here, unlike other neutral DAWs. Just importing the audio tracks into MB3 makes a HUGE difference. It took me alot LESS time to mix a session I previously attempted in Nuendo, and the mix sounded BETTER! Everything just sits together like a bunch of babies' backsides nestled in a circle of pillows, without the elements actually disrupting each other. Able to change color themes without having to restart the program. Not too crazy about the compressors though, although could take alittle getting used toģ. No weird phasing or stereo-typical issues (excuse the pun)Ģ. The panning sounds and works as it should. Right now, MB3's mixbusses do not seem to be able to be routed to other mixbusses.or am I missing something here?ġ. Especially for work that involves a shitload of tracks, where there is alot more bussing involved, where a handful of busses are routed to OTHER buses, before finally reaching the Master output.īe it orchestral work, hybrid score work, or basically anything that requires alot of busses.įor example, if I have a woodwinds section with Flute 1,2, Oboes 1,2, Clarinets 1,2 Bassoons 1,2, I'd like to be able to group each instrument pair to a bus of their own, and then route ALL the busses into a MAIN bus called 'Woodwinds', before that goes to the Master fader. It would be good to be able to fluidly select a bunch of channels and collectively adjust whatever you need, and then just simply 'unlink' them.Ģ. Sometimes I want to adjust both the bass and guitars, but other times I want to adjust the guitars and something else. Why not just have a quick 'link' or 'unlink' button? But to have to create a group, and then removing the group is quite a hassle. Right now MB3 has the 'grouping' system (accessed on the left side of the mixer window), which is nice. ![]() Be it the faders, input trims, pans, EQs, or even inserting a plugin. It would be nice to be able to simply select ANY group of channels, 'link' them, and adjust ANY perimeter collectively. Although adjusting the gain on the audio events themselves work just the same.ġ. The Input-Trim seems to be more gain/'distortion'-based, rather than volume-based. This could just be a Windows-specific problem.you know.Aero ģ. I have to shift windows around just to access those and drag them to another area. Whenever I go under 'View' and summon up other windows like meter bridge, it stubbornly hides behind the editor and mixer windows. In my case I don't even see the signals coming in, inside the plugins.Ģ. Certain plugins like iZotope and Slate do not work when inserted into any channel. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |