I have 4 busses each sending signal to the D-Box+. I am pretty much mirroring your and Fab's Apollo/D-Box config (and adding to what you are doing). Ricky Rod: You can definitely do traditional summing in the D-Box with Luna. Thanks, Joe, for being the first to remind me to do that (and you, Ricky, for being the second). I figured if I was seeing level on the meters it would (or should) just pass the audio through to the out.
I bet the 'Real-TIME MIXDOWN' proves to be faster.Īlso, how does one change the name of the mix? What if I am bouncing alternate mixes? Do I really have to bounce each one as "(session name) - MAIN" then go to my session folders and rename each one? Looked online at some LUNA doc and this was not even covered in the places I was looking that covered 'MIXDOWN'. And similar to the OP, I also was experiencing perceptibly overly long render times considering the song is still only 6 tracks and I really am NOT doing much processing with plugins. It suddenly occurs to me as I am typing that I've not tried 'REAL-TIME MIXDOWN'.
MIXDOWN SESSION TO NEW FILE TIME SELECTION OFFLINE
One caveat - I am so use to off-line bouncing, I've been doing nothing but offline bouncing for the last 15 years with Ableton LIVE so it is all I've tried. Try as I might, I can't find an error on my part or what I may have mistakenly done to 'mute' the MIDI tracks. I figured it was something I'd accidentally done as a new user but it has happened 3 times now and my MIDI tracks are no longer bouncing with the mix. Figure I've probably got something messed up somewhere, but I'm stuck at this point.Īfter two alternate but successful mixdowns of the same song containing both audio and MIDI tracks, subsequent mixdown's of the same song are suddenly omitting the MIDI tracks from the mix.
MIXDOWN SESSION TO NEW FILE TIME SELECTION PRO
I'm sure overall render times will decrease with time, but what would explain this latest very long render time? I have an early 2019 MacBook Pro with 32 GB RAM. Not only that, but my last render of the Sum Return took well over an hour to render and it is that same 6 minute file. I am not rendering in real time, but it takes Luna 4-5 minutes to render a 6 minute file with only two audio tracks and two MIDI tracks. My third problem has to do with Render times. Even if the Main Out isn't working correctly, why do basically none of my outputs produce an audible export file? it doesn't matter what I use, Luna produces an export file of 100+ MB that produces no sound. I go to mix down and export files from one or different multiple outputs. Why is the Main Out not working properly and not showing any signal? All settings on the Main channel are at their default. But the Main Out channel meters never show any levels. It seems to be working as I do hear sound and see output showing up on Apollo monitor out meters. My first problem is that the Main Out channel never seems to engage. When I disable Input Monitoring on Sum Return, there is no sound and nothing shows on the Sum Return volume meters.
At the same time, I can see the Monitor channels on my Apollo working properly. When I play the tracks in Luna, I can hear sound and see volume levels on the Sum Return channel meter with Input Monitoring enabled. I return to Luna through a Sum Return input and the Sum Return is the only channel feeding the Main Out, which I can easily verify using Spill.
I am running an Apollo x8 and summing through a Dangerous Music D-Box+. So I am trying to export an early mix down and am unable to get any audible sound from my output files.
0 kommentar(er)
