However, after opening the app here and there to check on things, I regularly see that the left channel fader for Line Out changes to -12 and the right channel to 0.0 when really, the scene calls for both channels to be -2.0.

The sound seems to be correct but visually it looks wrong until I reload the scene.

Is this a bug, or something I'm not understanding?

Below is a link to a screen shot and as you can see, the left/right channels are linked so I have no idea how they could even be different.

https://www.dropbox.com/s/c09kgucsd4vvkah/Screen%20Shot%202017-10-09%20at%209.30.19%20AM.png?dl=0" rel="nofollow - https://www.dropbox.com/s/c09kgucsd4vvkah/Screen%20Shot%202017-10-09%20at%209.30.19%20AM.png?dl=0

I know it's not an urgent bug but it's kind of disconcerting.

Here is another picture:

https://www.dropbox.com/s/p4suneiwdjrj65x/Screen%20Shot%202017-10-10%20at%208.47.52%20AM.png?dl=0" rel="nofollow - https://www.dropbox.com/s/p4suneiwdjrj65x/Screen%20Shot%202017-10-10%20at%208.47.52%20AM.png?dl=0

https://www.dropbox.com/s/ji2wjutj6xnjnd7/Screen%20Shot%202017-10-10%20at%209.40.09%20AM.png?dl=0" rel="nofollow - https://www.dropbox.com/s/ji2wjutj6xnjnd7/Screen%20Shot%202017-10-10%20at%209.40.09%20AM.png?dl=0

Sure, let me know if this tells us anything:

https://www.dropbox.com/s/n9sxar6sj6d8o0m/Screen%20Shot%202017-10-10%20at%206.58.34%20PM.png?dl=0" rel="nofollow - https://www.dropbox.com/s/n9sxar6sj6d8o0m/Screen%20Shot%202017-10-10%20at%206.58.34%20PM.png?dl=0

https://www.lynxstudio.com/downloads/hilo/hilo-remote-version-1-0-15/" rel="nofollow - https://www.lynxstudio.com/downloads/hilo/hilo-remote-version-1-0-15/

Sure but initially it doesn't look good. Here is a screen shot of how it looked when I first opened the new version:

https://www.dropbox.com/s/3jz0uzm2u0fvz52/Screen%20Shot%202017-10-14%20at%208.58.20%20AM.png?dl=0

I'm not sure why "Record 13 + 14+" is down to -62.0

I had all those channels at 0.0 and muted. You also see the left channel of line in is muted but not the right even though they are linked. 

Also, some how it's stuck on ADAT as the clock source.

I'll have to dick around with it more now and see what's up.

I don't have time right now to beta test this stuff for you. I'm getting random channels that unmet or change level (at least on the GUI) even though the stereo channels are linked so it should be impossible for the left and right to be different. 

I'm happy to report issues but if you're just going to tell me to use an older version that has even weirder issues, I don't see the point.

I recently replaced my AES16e with the RME HDSPe AES card and couldn't be happier with the sound (SyncroLock sounds weird/bad), the stability of the card and software, the look of the RME mixer, and the DIGICheck stuff is great.

Generally speaking the sound of the HILO is pretty good for a clean alternative to my HEDD but if it's going to be like this, I may look into replacing it with something more fitting and less hassle.

https://www.dropbox.com/s/3yvuxfg4x45pw8g/RME%202017%20HEDD%20Calibrated.hrs?dl=0" rel="nofollow - https://www.dropbox.com/s/3yvuxfg4x45pw8g/RME%202017%20HEDD%20Calibrated.hrs?dl=0

The Hilo Remote simply reveals the hardware state. As much as it seems like a software bug, that is not likely the issue, or it would appear this way to others. The versions you are using are fine. 

It seems more likely that there is a basic communication flaw here. It's possible that it is a hardware problem, but first I'd want to look at other operational conditions. 

have you tried a different thunderbolt cable? Do you have any other thunderbolt devices connected? If so, what are they and where are they connected (daisy chained to or from the Hilo, or on a separate port)? 

 Have you tried a low-level reset of the Hilo? 

You do this by holding down the front panel standby button while flipping on the back panel AC switch. Keep holding standby until the screen calibration page comes up. Calibrate the screen, then test. 

Keep me posted. 

 

I'm out of commission for a few days but I'll report back.

I can say that what I'm seeing on the Hilo Remote Mixer App does not reflect what I'm hearing. Having the left channel on that output be down by 12dB would be extremely obvious.

I see, while my iMac has maxed out specs, it's a 2013 and the last Thunerbolt 1 iMac. I'm holding out for the iMac Pro to be released.

I do have other things connected such as a Sonnet TB chassis containing my RME AES card, and a UAD-2 card. I also have a Blackmagic hard drive dock, UA Apollo Twin MKII, and two external displays connected.

I use two of the OWC Thunderbolt docks to connect it all.

Maybe this is a bit too much of a strain though other than this weird issue, everything still runs strong.

I'm not exactly where in the chain the Hilo is connected but I can check probably tomorrow.

Either way, it's probably best to just wait until I have the new computer rig up and running and see if the problem still exists.

I do have a UA Apollo connected to the 2nd port of the Lynx Hilo but the Hilo itself is directly connected to the iMac Pro which should be plenty powerful. 

Are you using the Hilo Remote that came with that driver?

Let me know if this screen shot helps and if I'm out of date:

https://www.dropbox.com/s/uh0eku3c02xy1ih/Screen%20Shot%202018-01-05%20at%208.57.10%20AM.png?dl=0" rel="nofollow - https://www.dropbox.com/s/uh0eku3c02xy1ih/Screen%20Shot%202018-01-05%20at%208.57.10%20AM.png?dl=0

If I had your system in front of me, I would start by swapping out each piece of hardware until the problem went away - assuming it is a hardware problem.  Since you are using the Hilo stand-alone and Thunderbolt isn't that important, we would be happy to loan you an LT-USB to see if the issue is related to Thunderbolt or not (I doubt it is).  That would require you to open up the Hilo and swap the LSlot card - which isn't too hard.

Let me know how you would like to proceed.

Thanks David, 

I've updated the Lynx Mixer and LT-TB so I'll see if that makes a difference.

I appreciate your offer to try a USB version but since this issue isn't major, I'll have to find a time when I am a bit less busy to worry about it.