LUNA 1.0.8

UniversalAudio

Official UA Representative
Has been released. Get it in-app.


https://help.uaudio.com/hc/en-us/articles/360041532452-LUNA-Release-Notes

New:

Direct Output Delay Compensation
All SEND and OUTPUT routings to Apollo LINE and MON outputs are now aligned
Discard Recording Shortcut
Punch out of record and move the recorded wav file to the trash: Shift + Command + "."
Tape Assign Hover Functions
Direct navigation to global assignment and control panels
Easier access to secondary track controls and functions


PDF manual has also been refreshed.

https://help.uaudio.com/hc/en-us/articles/360041758592
 

OrangeCrush

Venerated Member
As usual, field reports on bugs, issues, welcome here for anyone braver than me (and do not forget to send feedback in Luna as well). Yes, I know you can downgrade back. I have had reported render issues since 1.0.6 on my machine.
 
Last edited:

Emanon

Venerated Member
I updated and will be looking to see if Shape stops occasionally going silent.
 

veggieryan

Active Member
"Direct Output Delay Compensation
All SEND and OUTPUT routings to Apollo LINE and MON outputs are now aligned"

Does this apply to ADAT, SPDIF and AES outputs as well????
 

UniversalAudio

Official UA Representative
"Direct Output Delay Compensation
All SEND and OUTPUT routings to Apollo LINE and MON outputs are now aligned"

Does this apply to ADAT, SPDIF and AES outputs as well????
No, this is for analog outs.

Since digital outs will ultimately connect to D/A converters (all of which have their own inherent timings) there's no way to know what those timings will be.
 

veggieryan

Active Member
No, this is for analog outs.

Since digital outs will ultimately connect to D/A converters (all of which have their own inherent timings) there's no way to know what those timings will be.
That doesn't make sense... why not start out at least having them aligned instead of all over the place? Then we can use a plugin like voxengo latency delay to align them with consistent values instead of having to do it manually?
 

veggieryan

Active Member
It makes perfect sense because all D/As have unique timings.
Perhaps it would clarify if you can differentiate what changed in this release... I would assume all the D/A outputs on an Apollo have identical timing so what changed in this release?

"Direct Output Delay Compensation
All SEND and OUTPUT routings to Apollo LINE and MON outputs are now aligned"

For example I send a vocal out on Line 1 of my Apollo x6, and a guitar tracked at the same time on Line 2 of Apollo x6. The DA chips have the same timing... so what changed from 1.07?
 

UniversalAudio

Official UA Representative
For example I send a vocal out on Line 1 of my Apollo x6, and a guitar tracked at the same time on Line 2 of Apollo x6. The DA chips have the same timing... so what changed from 1.07?
In 108, regardless of plugin chains on those tracks and whatever else is going on in the mixer (delay comp etc) LUNA will now make sure they all line up. In 107 and before, only the Mon and Cue outs were delay comped.

This allows for analog summing workflows not possible until 108.

Hope this helps.
 

veggieryan

Active Member
In 108, regardless of plugin chains on those tracks and whatever else is going on in the mixer (delay comp etc) LUNA will now make sure they all line up. In 107 and before, only the Mon and Cue outs were delay comped.

This allows for analog summing workflows not possible until 108.

Hope this helps.
Yes that is what I thought... It just doesn't make sense to not do delay compensation for the ADAT outputs. 99% of the time one DA converter will be used per bank of ADAT outputs. If those outputs were delay compensated like the analog line outputs I could use them for analog summing as well... the timing of the DA chips is irrelevant unless you are trying to mix them with the line outs from the Apollo. In that mixed output scenario it sill would help to make the ADAT outputs delay compensated. Then I could drop 8 of the voxengo delay plugins with identical settings on each of the ADAT outputs to align them with the Apollo line outputs as needed. Since they are not delay compensated it means I have to just guess what setting each ADAT output needs to be aligned with anything? Is there any plan to add delay compensation to the ADAT outputs?
 

UniversalAudio

Official UA Representative
Yes that is what I thought... It just doesn't make sense to not do delay compensation for the ADAT outputs. 99% of the time one DA converter will be used per bank of ADAT outputs. If those outputs were delay compensated like the analog line outputs I could use them for analog summing as well... the timing of the DA chips is irrelevant unless you are trying to mix them with the line outs from the Apollo. In that mixed output scenario it sill would help to make the ADAT outputs delay compensated. Then I could drop 8 of the voxengo delay plugins with identical settings on each of the ADAT outputs to align them with the Apollo line outputs as needed. Since they are not delay compensated it means I have to just guess what setting each ADAT output needs to be aligned with anything? Is there any plan to add delay compensation to the ADAT outputs?
ADAT outs have to be connected to a D/A that we will don't know the timing of. They are all different.

Please submit the request as Feedback.
 

veggieryan

Active Member
ADAT outs have to be connected to a D/A that we will don't know the timing of. They are all different.
We have already established that. The question is... are the ADAT outputs delay compensated with each other?

Example:
Is ADAT output 1 with an audio unit and 2 UAD plugins delay compensated or "in phase" with ADAT output 2 with 2 different audio units and 3 different UAD plugins... Both ADAT 1 and ADAT 2 are connected to the same DA chip with same timing...
 

UniversalAudio

Official UA Representative
We have already established that. The question is... are the ADAT outputs delay compensated with each other?

Example:
Is ADAT output 1 with an audio unit and 2 UAD plugins delay compensated or "in phase" with ADAT output 2 with 2 different audio units and 3 different UAD plugins... Both ADAT 1 and ADAT 2 are connected to the same DA chip with same timing...
Not yet.
 

DavidCaraccio

Active Member
So far so good! Just finished mixing a song this morning which I had tracked last week-end with 1.0.7. Hurray! ;)
 
Have recently been using LUNA at 'edit' level consistently over the last few weeks on a number of remix projects for various stems /track bounces sent from remote locations. Aside from all the guff we read in these fora about presently 'missing features', bugs etc (many being true of course) - I just wanted to say:

Now working almost exclusively at the track editing level for these current projects has been revealing (48kHz, renders to film sound tracks). ALL of the basic editing functions (including pitch shift and gain staging etc) have been 100% brilliant, fast and reliable, as has render. Has given me a new appreciation of where much of the recent development has been going. The Edit page is quite brilliant and so solid, especially once one bites the bullet and learns all the critical key commands [still, am very much awaiting user key commands & MCU support in particular]. Great work so far, and the targeting of the dev. features makes much sense. Luna 1.08 running very well on Catalina (& Big Sur Beta 4 for that matter).
 

Tannen

Member
As usual, field reports on bugs, issues, welcome here for anyone braver than me (and do not forget to send feedback in Luna as well). Yes, I know you can downgrade back. I have had reported render issues since 1.0.6 on my machine.
Hi Orange. I just upgraded to 1.0.8 and unfortunately it has created quite a mess for me. You mentioned in your post that we can 'downgrade back'. Can you (or someone else here on the board) let me know the steps I can take to revert back to a previous version? It would save me a lot of time and frustration. Thanks in advance :cool:
 
UAD Bundle Month
Top