2024-11-25, 21:19
Question: why would I choose to use the FPS setting for audio delay tweaking, versus just the audio codec being used? I'm not clear under what scenarios I might choose to toggle that on or not. Thanks!
(2024-11-25, 21:19)Ozyman Wrote: Question: why would I choose to use the FPS setting for audio delay tweaking, versus just the audio codec being used? I'm not clear under what scenarios I might choose to toggle that on or not. Thanks!
(2024-11-25, 23:22)scott967 Wrote: just came across this; seems very nice. As a possible enhancement could setting "audiooutput.audiodevice" be monitored? My use case is windows and think it might help to have different syncs for DIRECTSOUNDpeakers/WASAPIpeakers/DIRECTSOUND:bt headset/WASAPI:bt headset.Hi Scott, thanks! I can look into something like that. I'm actually just learning about how Kodi works so I don't know all the ins and outs. However, I would guess that on a Windows based system it might be better to apply the specific latency of your output devices etc at the Windows level, instead of trying to also add that into the addon. The settings.xml file is already HUGE haha so I'm weary of adding more configurations. But I appreciate your feedback, I will continue to investigate and see whats possible.
Haven't experimented, but what happens if you use sync playback to display and player tempo up/down?
scott s.
.
(2024-11-30, 21:28)Ozyman Wrote: Hey Matthane,
Been watching the CoreElec audio sync issues thread you shared, just updated to latest nightly (11/29), and hoping it helps! That said, reason I'm writing is I'm trying to diagnose why setting audio sync using your tool doesn't seem to update Kodi's audio sync setting, and vice versa (and I have turned on that setting in AOM for DV, HDR, and SDR - even though my projector doesn't do DV). I've been setting the offset either manually using Kodi's audio offset slider, or using your tool when trying to play Back to the Future. For some reason setting it in one doesn't "stick" so I go to the other and see the value is different - this is for the first DTS True HD 7.1 track. I'm only setting by audio codec, not FPS. Any ideas on what I might be doing wrong, or whether there's a bug somewhere after all of these changes to CoreElec?
(2024-12-01, 20:39)matthane Wrote:Yep, definitely have "Active offset monitoring" on - so that's not the issue. However, your second point might be: I do have some dual DV/HDR videos, and for a while at least I didn't turn on the DV HDR type in the settings because I figured it was irrelevant. I'll test some more with that on and see if I have issues - if I see problems, I'll try to get more specific details to share. Thanks!(2024-11-30, 21:28)Ozyman Wrote: Hey Matthane,
Been watching the CoreElec audio sync issues thread you shared, just updated to latest nightly (11/29), and hoping it helps! That said, reason I'm writing is I'm trying to diagnose why setting audio sync using your tool doesn't seem to update Kodi's audio sync setting, and vice versa (and I have turned on that setting in AOM for DV, HDR, and SDR - even though my projector doesn't do DV). I've been setting the offset either manually using Kodi's audio offset slider, or using your tool when trying to play Back to the Future. For some reason setting it in one doesn't "stick" so I go to the other and see the value is different - this is for the first DTS True HD 7.1 track. I'm only setting by audio codec, not FPS. Any ideas on what I might be doing wrong, or whether there's a bug somewhere after all of these changes to CoreElec?
Hmm, make sure you enable "Active offset monitoring" in the "Playback Behavior" settings tab of the addon. That is the setting responsible for making sure that the audio slider in the GUI during playback matches the settings. If it's disabled (which it is by default), it won't be in sync and will only apply your settings from the addon on start of the video, and won't save any changes you make to it during playback. I have this feature disabled by default because it technically requires constant polling during playback. While I don't notice any performance issues, I want to be sensitive to all hardware setups people have and don't want to poll the processor unnecessarily.
Let me know if that solves your issue!
Edit: I should also point out that the HDR types in the addon menu are the source HDR types, not the TV's output mode. Meaning, if Kodi reads the file as a Dolby Vision file, the addon settings will be stored in the Dolby Vision category even if your display is outputting it without the DV metadata and only HDR10 base layer.
(2024-12-02, 03:46)matthane Wrote: I realize it is a bit confusing at first having the settings sorted by source type instead of TV output mode, but it's far easier in Kodi to query the source type rather than trying to sniff out what the TV is actually doing. I've built in pretty verbose logging so if it comes to that, you can enable debug level logging in Kodi and then there will be log entries prefixed with "AOM_" that will help us see what's going on behind the scenes.No, I think your decision makes sense here - it’s probably just an opportunity for some better tooltips or guidance on when to choose something. So far the only areas that have thrown me off were: