Posts: 10,530
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,530
Also note I haven't got round to doing the platform specific setting xml's yet, so that is producing some oddities at the moment such as duplicate entries, so you may have to delete these leaving just settings.xml to get a proper view of the new structure.
Posts: 10,530
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,530
How many actually use network sinks or display servers?
I would think for just about all users:
*Video output needs to take account of the capabilities of your GPU & your TV/projector/display.
*Audio output needs to take account of the capabilities of your audio sink/hardware & the connected device.
Posts: 10,530
Joined: Oct 2011
Reputation:
640
jjd-uk
Team-Kodi Member
Posts: 10,530
Just so I'm clear, is it the naming's and definition I've provided you don't like? or is it also the structure? so you'd prefer everything now under Device to remain in System?
Posts: 6,810
Joined: Jul 2010
Reputation:
198
First of all I don't like the term "Device" because it is incorrect. a/v settings can refer to the hardware running on but also to software components or connected devices. The settings define how audio and video component behave in the container they are embededed and this container is not a "device".
Posts: 6,810
Joined: Jul 2010
Reputation:
198
You should not mix up the OS layer with the application layer. That's two different stories.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
The first page is better but what you call "Video Processing" does not fit into this section. a/v output define capabilities of the entire application. Those can be used by any component, even addons. "Video Processing" belong to VideoPlayer that is going to be exchangeable in the future. In other words VideoPlayer is a client of a/v output. A future version of VideoPlayer will be capable of rendering into a stream instead of a/v output -> transcoding
Posts: 5,184
Joined: Jan 2009
Reputation:
131
IMO we have to be careful to remember that all these labels should make sense for people who have no idea how a video player works. They don't care about who is responsible for what. They want to change something in video playback so they look for (video) playback and not "video processing", "transcoding" or whatever is technically correct.
Always read the
online manual (wiki),
FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the
forum rules (wiki).
Please read the pages on
troubleshooting (wiki) and
bug reporting (wiki) before reporting issues.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
I agree but the structure need to make sense. Another example: for headless Kodi a/v output should not be presented, right? But the server can still make use of VideoPlayer, transcoder (whatever) that use hw acceleration for decoding/encoding.