|
Post by TDifEQ on Feb 24, 2020 12:41:17 GMT -5
Shared PCM7.1 info with KeithL regarding the "loud noise" issue. He talked to his developers and concluded the feedback made sense and they are "working on it" … which is good news. Hopefully (don't know) the fix will get into 1.8.
|
|
|
Post by bluescale on Feb 24, 2020 13:04:35 GMT -5
Shared PCM7.1 info with KeithL regarding the "loud noise" issue. He talked to his developers and concluded the feedback made sense and they are "working on it" … which is good news. Hopefully (don't know) the fix will get into 1.8. Considering 1.8 comes out (supposedly) today, I don't see how the fix could make it in.
|
|
|
Post by rhale64 on Feb 24, 2020 13:30:36 GMT -5
Yeah that will probably come later I would imagine. To late in the game for that to be implemented this quick I would assume.
|
|
richb
Sensei
Oppo Beta Group - Audioholics Reviewer
Posts: 854
|
Post by richb on Feb 24, 2020 13:34:57 GMT -5
If you are have had or have worries about the loud noise at startup, make sure you have the power-on volume set to something reasonably low, for example, -35.
- Rich
|
|
|
Post by TDifEQ on Feb 24, 2020 14:14:56 GMT -5
At -60dB, "loud noise" is comfortably noticeable where one can rarionally observe what is going on. lol.
|
|
|
Post by rhale64 on Feb 24, 2020 15:24:01 GMT -5
Mine is at -40 startup volume. I haven't ever had that problem but want to just make sure.
|
|
|
Post by Hair Nick on Feb 24, 2020 15:37:17 GMT -5
|
|
|
Post by steelman1991 on Feb 24, 2020 15:47:01 GMT -5
Great stuff thanks Nick - bit too late for me to test, but will do first thing in the morning
|
|
|
Post by hsamwel on Feb 24, 2020 15:55:51 GMT -5
Nice, thanks! Installing just before bedtime.. Work early tomorrow..
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 24, 2020 16:18:06 GMT -5
Hi. Are there any differences to the Beta 1.8?
|
|
|
Post by fjd on Feb 24, 2020 16:45:25 GMT -5
1.8 'Locked & Loaded ' @ 13:45
|
|
|
Post by PaulBe on Feb 24, 2020 16:47:19 GMT -5
The setup features are quite powerful. I am creating an excel spreadsheet to keep track of everything. Not finished with it yet. You know, that's a great idea! And I'm a big fan of spreadsheets but I never thought of doing that. Wonderful! When I finish, I'll post the Master as an attachment, if any would like it. Another poster here has offered to collaborate, sharing spreadsheet ideas. Perhaps we can bring something good to the board. It may take a while. Maybe someone else here will modify it and make it better.
|
|
|
Post by megash0n on Feb 24, 2020 17:12:45 GMT -5
I just installed 1.8. Upon booting the first time, I waited until it was up and running and then turned on my Xbox and tv. I get the same "no signal" I've gotten the whole time. I believe it to be on the output side as the processor's screen shows Dolby atmos as soon as it syncs with my Xbox. I switched to my HTPC, same issue. Switch back.. Same issue. The only way to fix this is to swap inputs back and forth on the TV or to reseat the HDMI cable.
Switching inputs, on the processor, seems to be faster though. All menu items also seem to be far more responsive.
|
|
Lonnie
Emo Staff
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Feb 24, 2020 17:33:35 GMT -5
Hi. Are there any differences to the Beta 1.8? Yes, significant ones. Lonnie
|
|
Lonnie
Emo Staff
admin
Pay no attention to the man behind the curtain
Posts: 6,999
|
Post by Lonnie on Feb 24, 2020 17:36:48 GMT -5
I just installed 1.8. Upon booting the first time, I waited until it was up and running and then turned on my Xbox and tv. I get the same "no signal" I've gotten the whole time. I believe it to be on the output side as the processor's screen shows Dolby atmos as soon as it syncs with my Xbox. I switched to my HTPC, same issue. Switch back.. Same issue. The only way to fix this is to swap inputs back and forth on the TV or to reseat the HDMI cable. Switching inputs, on the processor, seems to be faster though. All menu items also seem to be far more responsive. Turn everything off, unplug the TV, processor and all sources. Give it 15 seconds or so and then plug it all back in. Give everything a minute to do their behind the scenes stuff. Turn on the processor and then the TV and then sources. I would recommend doing this after a firmware update so everything gets a clean boot. Lonnie
|
|
|
Post by ttocs on Feb 24, 2020 17:54:18 GMT -5
^^^^^^ What he said.
I don't know if it's necessary these days, but I got into the habit of Backing Up settings, then Factory Reset, shut down, unplug all HDMI, Switch Off, wait a couple minutes, turn on, Firmware Update, after it shuts itself off I switch off, wait couple minutes, switch on and wait for the Button to turn different colors and stop, then power on.
This time I got greedy and plugged in the HDMI cables for TV, TiVo, and ATV4k, then powered on and I got the Please Wait hang. After 8 minutes I switched off, unplugged all HDMI, switched on, powered on using the Front Panel Button, all is good. Then power off, plug in HDMI cables, turn back on and happiness ensues.
|
|
|
Post by Vermont99 on Feb 24, 2020 17:59:29 GMT -5
1.8 Installed and good to go. Locks on to everything I have connected and seems a lot faster. I tried switching back and forth between inputs and it's working as it should. So far I'm a happy camper.
|
|
|
Post by hsamwel on Feb 24, 2020 18:01:14 GMT -5
First try.. Started AppleTV checled some series on HBO and Netflix. Everything works fine.and pretty snappy. HD, 4k, HDR, Dolby Vision, 5.1 and Atmos.
Although still reporting Dolby Digital + with Atmos meta data as Dolby True HD with Atmos.
Still want the info window with ”show until clicked away” when manually shown.
Want the double bass feature to have a cross over setting that’s visable instead of just ”taking” the cross over setting from the normal small setting.
Is the DTS Neural:X volume difference issue fixed?
Seems to detect audio quicker. Feels a little quicker genrally.
|
|
|
Post by bluescale on Feb 24, 2020 18:59:52 GMT -5
Want the double bass feature to have a cross over setting that’s visable instead of just ”taking” the cross over setting from the normal small setting. Can you explain this? I'm assuming by double bass you mean setting the mains to large. If that's the case, what crossover are you referring to?Edit: After thinking about this for just a few moments, I figured it out. <sigh> It's been a long day.
|
|
|
Post by megash0n on Feb 24, 2020 19:17:58 GMT -5
I just installed 1.8. Upon booting the first time, I waited until it was up and running and then turned on my Xbox and tv. I get the same "no signal" I've gotten the whole time. I believe it to be on the output side as the processor's screen shows Dolby atmos as soon as it syncs with my Xbox. I switched to my HTPC, same issue. Switch back.. Same issue. The only way to fix this is to swap inputs back and forth on the TV or to reseat the HDMI cable. Switching inputs, on the processor, seems to be faster though. All menu items also seem to be far more responsive. Turn everything off, unplug the TV, processor and all sources. Give it 15 seconds or so and then plug it all back in. Give everything a minute to do their behind the scenes stuff. Turn on the processor and then the TV and then sources. I would recommend doing this after a firmware update so everything gets a clean boot. Lonnie Ok, I have completed this. Here is the only change that is different, but an improvement. When I switch to the HTPC, I receive the same issue I reported and have received virtually every time with 3 different FW versions. Switching back to the XBOX did not work prior to unplugging everything. Now, when I switch to the HTPC, it doesn't work, but switching back to the XBOX comes back every time. So, it is an improvement. My video card is an AMD RX 480. Again, reseating the HDMI out to the TV or swapping inputs on the TV correct the issue everytime.
|
|