TVHeadend build/install on Lubuntu 20.04-64bit with iGPU 8+ transcoding

Alin Gherghescu · 2022-12-03T02:38:34+00:00

This tutorial is intended for beginners interested in compiling tvheadend with HW GPU transcoding (using iGPU form Intel gen 8+). It is a little messy how I...

ukn_unknown

apollo DMC posted a very detailed way to dump a mux (mux is the entity that keep one MPTS). https://docs.tvheadend.org/documentation/creating-a-mux-dump ; If you could dump the mux DVB-T2 with channel 501 for about 1-2 minutes ... would help me to investigate all fields (with TSAnalyser) present in your stream ... and try to preserve as many I can. Take note that the file will be around 250M / min. Thank you.

it doesn't preserve the MPEG network ID/transport stream ID/service ID of the original stream and arbitrarily sets all these values to 1.

This is true only if you keep the default settings ... if you want to preserve thins info you have to use the following settings:

You can see on the tooltip --> Zero means no rewrite. I think will preserve also the rest of the settings listed (beside Service ID).
You can do a VLC record for profile pass with above settings and you will see the difference (relative to the original pass profiles with Rewrite Service ID = 1).

Kévin Chalet

ukn_unknown This is true only if you keep the default settings ... if you want to preserve thins info you have to use the following settings:

You can see on the tooltip --> Zero means no rewrite. I think will preserve also the rest of the settings listed (beside Service ID).

Hey,

@apollo emailed me the link to this topic so I thought I could shed some light on why I opted for this - rather unusual - approach in that linked blog post 😁

Preserving the original MPEG service ID by using a single pass-through profile with the magic 0 value would certainly work for basic scenarios, but it would also break Windows Media Center when implementing more advanced setups: let's say you have a Tvheadend channel mapped to 2 services belonging to 2 muxes coming from 2 different networks ; for instance a DVB-T network (with a real MPEG-TS source and a "real" service ID) and an IPTV network fallback (for which a fake MPEG-TS has to be created with a fake service ID).

In that case, the MPEG-TS service, network and transport identifiers will differ between the two sources and a pass-through profile with the magic 0 value will reflect that: if you used the IDs of the DVB-T network when injecting the channels in WMC's database, it will only work when the Tvheadend stream comes from the DVB-T source: as soon as Tvheadend will try to use the IPTV source, the returned stream will have different MPEG-TS identifiers and WMC will just complain it can't find the requested service (which isn't unreasonable behavior, to be honest 😁).

Using MPEG-TS identifiers that are completely disconnected from the actual stream sources completely avoids this issue. But of course, it requires doing some gnarly things Tvheadend-side 😁

A clever way to solve that would be to have more elaborate MPEG-TS pass-through and spawn profiles that allow specifying dynamic identifiers directly in the query string. Something like http://tvheadend:9981/stream/channelnumber/2?profile=dynamic_pass&mpeg_network_id=8442&mpeg_original_network_id=8442&mpeg_transport_stream_id=1&mpeg_service_id=2. Not sure how complicated it would be to implement that, tho'.

(I'm an absolute Tvheadend lover, which is really a fantastic piece of software! ❤️)

apollo

I recorded channel 501 dvb-t2 for you, I'll check the other things as soon as possible...
Thanks again for your availability

[https://drive.google.com/drive/folders/1blISphVtiNjYZ1Ix2btnKUSWmQaufMFj?usp=sharing]

ukn_unknown

apollo I updated the branch with latest finding ... frankly I am running out of ideas. I cannot transfer al IDs to be identical, but I was able to populate most of them with original numbers. You can see here a comparison side by side:

Teletext cannot be integrated ... so is stripped down with trancoding.

apollo

Hi,
sorry, I'm having some problems lately...
I tried your new modification, with wmc the transcoding starts but doesn't display anything, there's no audio or video
I fully understand that you're trying in the dark, so if you don't have any other ideas, let's stop here.
If you want, I've attached the same file/channel transcoded with the new branch to compare it with yours...
Thanks

[https://drive.google.com/drive/folders/1blISphVtiNjYZ1Ix2btnKUSWmQaufMFj?usp=sharing]

ukn_unknown

apollo you can try to replace h264 with mpeg2 (for video) and/or AAC with mp2 (for audio). I think you are close ... is only a matter of compatibility. Maybe change settings for h264 and/or AAC.
Edit: Try to change the h264 Profile (to all 3 options) and Level (try higher or lower). As for AAC try to change Profile.

apollo

Hi unknown,
the text below has been copied from the usual link...
What you think?
is it possible to make a last attempt...?
Thanks

It's worth noting that each channel in WMC must have a unique MPEG service ID, so you basically need one streaming profile per channel with a specific service ID attached in Tvheadend for things to work correctly

ukn_unknown

apollo you already have this feature (different service ID for each program) in your build. You can use VLC and TS Analyser to confirm each channel will have a different service ID. If transcoding starts it means you already passed the 'stream ID problem'. Try to add only one channel to WMC ... that should rule out the problem of conflicting 2 channel with the same service ID.
Try to replace the H264 with MPEG2 and AAC with mp2 ... maybe the problem was with stream video/audio.
Don't understand me wrong ... I would help you, but you have to tell me what you need 🙁 . What you are asking above is already implemented.

apollo

I don't know why I was convinced it was random, sorry I got confused...:🙂🙂
Thanks

ukn_unknown

Kévin Chalet , first let me thank you for helping ... now I start to understand your proposal from document.
In that case I think we should separate your 'need' into two:

let's fix the transcoding + MPEGTS/avlib in order for mpegts metadata info to be available for all clients (WPC is one of them) --> the outcome is DVBT2 + WMC should start working ... assuming was implemented properly.
we can discuss how we can add a workaround for WMC to fix the IPTV sources (but I consider #2 as independent of #1).
We have to look at the big picture with ... all our clients / users in mind. Let me know if you disagree with statement above.

In my opinion #1 is implemented ... I tried to add as many of the info into mpegts / avlib container. Do you think you can help us test the branch: uknunknown/tvheadendtree/dev_mpegts ? Even if you only have H264 (DVBT) channels ... you can enable transcoding and re-encode H264 lower bitrate (for testing purpose). I don't have WMC to test ... and for some unknown reason apollo is not able to make it work 🙁 . The PR with this change is available in: tvheadend/tvheadend1814 --> we would appreciate if you can document your tests/results here for tracking purpose.

Kévin Chalet

ukn_unknown Kévin Chalet , first let me thank you for helping ... now I start to understand your proposal from document.

My pleasure! Thanks for taking the time to address that 😊

ukn_unknown Do you think you can help us test the branch: uknunknown/tvheadendtree/dev_mpegts ?

I just set up a Ubuntu 25.04 VM, built your dev_mpegts branch locally and configured a DVB-T network with SAT>IP tuners pointing to my production Tvheadend server.

It worked beautifully and I can confirm that the basic MPEG-TS data is now passed through when creating a "transcode/lib-av with MPEG-TS/lib-av container" stream profile. Here's an example with the LCI channel:

Using my Tvheadend production server (version 4.3-2375~g653bd0400):

===============================================================================
|  SERVICES ANALYSIS REPORT                                                   |
|=============================================================================|
|  Global PID's                                                               |
|  TS packets: 63, PID's: 2 (clear: 2, scrambled: 0)                          |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Global PID's ................................. C       23,331 b/s  |
|   Subt.  Global PSI/SI PID's (0x00-0x1F) .............. C       23,331 b/s  |
|  0x0000  PAT .......................................... C       18,887 b/s  |
|  0x0011  SDT/BAT ...................................... C        4,444 b/s  |
|=============================================================================|
|  Service: 0x0001 (1), TS: 0x0001 (1), Original Netw: 0xFF01 (65281)         |
|  Service name: Service01, provider: FFmpeg                                  |
|  Service type: 0x01 (Digital television service)                            |
|  TS packets: 7,499, PID's: 3 (clear: 3, scrambled: 0)                       |
|  PMT PID: 0x1000 (4096), PCR PID: 0x0100 (256)                              |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Digital television service ................... C    2,777,102 b/s  |
|  0x0100  AVC video (682x384, high profile, level 3.0,   C    2,516,760 b/s  |
|  0x0101  MPEG-2 AAC Audio (fre) ....................... C      241,455 b/s  |
|  0x1000  PMT .......................................... C       18,887 b/s  |
|          (C=Clear, S=Scrambled, +=Shared)                                   |
===============================================================================

Using your branch:

===============================================================================
|  SERVICES ANALYSIS REPORT                                                   |
|=============================================================================|
|  Global PID's                                                               |
|  TS packets: 83, PID's: 3 (clear: 3, scrambled: 0)                          |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Global PID's ................................. C       22,908 b/s  |
|   Subt.  Global PSI/SI PID's (0x00-0x1F) .............. C       22,908 b/s  |
|  0x0000  PAT .......................................... C       15,732 b/s  |
|  0x0010  NIT (Network: 0x20FA (8442) CNH) ............. C        3,588 b/s  |
|  0x0011  SDT/BAT ...................................... C        3,588 b/s  |
|=============================================================================|
|  Service: 0x0308 (776), TS: 0x0003 (3), Original Netw: 0x20FA (8442)        |
|  Service name: LCI, provider: CNH                                           |
|  Service type: 0x01 (Digital television service)                            |
|  TS packets: 5,869, PID's: 4 (clear: 4, scrambled: 0)                       |
|  PMT PID: 0x01F4 (500), PCR PID: 0x01FE (510)                               |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Digital television service ................... C    1,619,814 b/s  |
|  0x01F4  PMT .......................................... C       15,732 b/s  |
|  0x01FE  AVC video (682x384, high profile, level 3.0,   C    1,405,642 b/s  |
|  0x01FF  MPEG-2 AAC Audio (fre) ....................... C      198,440 b/s  |
|  0x0200  MPEG-2 PES private data ...................... C            0 b/s  |
|          (C=Clear, S=Scrambled, +=Shared)                                   |
===============================================================================

After injecting the channel in WMC's database with the correct MPEG-TS locators, you can watch TV without issues (note that you can already watch TV with the "official" Tvheadend release, but since all the channels will end up using the same hardcoded "1" service ID, the channels end up being merged automatically by WMC at some point):

The quality is terrible, but I used the default settings - that aren't really meant for quality to say the least 🤣 - to test your branch. Windows Media Center is also quite picky when it comes to codecs so I had to transcode to MPEG2 audio to hear something 😁

ukn_unknown I don't have WMC to test ... and for some unknown reason apollo is not able to make it work 🙁

I suspect that's simply because he didn't have a way to inject/update the channel with the correct MPEG-TS transport/network/service IDs: once you switch to your branch, the returned stream will now use the original identifiers and you need to change the channel data in WMC to use the same values, otherwise they won't match.

Technically, this is a potentially breaking change for users/apps that expect a stream with MPEG-TS service ID = 1. Should the transcode/lib-av profile be updated to offer the same settings as the pass profile?

ukn_unknown we can discuss how we can add a workaround for WMC to fix the IPTV sources (but I consider #2 as independent of #1).
We have to look at the big picture with ... all our clients / users in mind. Let me know if you disagree with statement above.

Yeah, I fully agree it's an orthogonal (tho' related) thing. That said, I'm not sure it should be implemented at the IPTV level, since it's not specific to IPTV at all: I used IPTV in my example scenario, but you'd have the same issue in the following cases:

When using two true MPEG-TS sources coming from DVB-T and DVB-C or DVB-S2 ; for instance, when using OTA with a cable fallback (in that case, the service IDs will be different between the two sources even if the "channel" is the same).
When having a channel that points to a UHD service but falls back to a FHD service on the same DVB-T2 network if the first one temporarily doesn't work. In that case the service IDs will be different too.

Another way to address that would be to add new channel-bound settings allowing to override the MPEG-TS ONID/TSID/NID/SID of the original source to use static, user-defined values. Assuming you're using a stream profile preserving these, it should also work flawlessly 😁

Cheers!

ukn_unknown

It worked beautifully and I can confirm that the basic MPEG-TS data is now passed through when creating a "transcode/lib-av with MPEG-TS/lib-av container" stream profile.

Is good to hear that is working.

The quality is terrible, but I used the default settings - that aren't really meant for quality to say the least 🤣 - to test your branch.

Depends .. : you selected software or hardware transcoding? Assuming you selected VAAPI, you need to force Rate Mode Control: to ICQ or QVBR. Also depends on what generation of iGPU you have. Anyway this is outside the scope.

Windows Media Center is also quite picky when it comes to codecs so I had to transcode to MPEG2 audio to hear something 😁

This is an interesting piece of information ... probably it should be documented somewhere for other users.

Kévin Chalet Technically, this is a potentially breaking change for users/apps that expect a stream with MPEG-TS service ID = 1. Should the transcode/lib-av profile be updated to offer the same settings as the pass profile?

We need to discuss with on a larger forum ... but I am tempted to say we need to add a "Reset MPEG-TS SI parameters" checkbox (that should be available only when MPEG-TS/libav is selected from the list).

Another way to address that would be to add new channel-bound settings allowing to override the MPEG-TS ONID/TSID/NID/SID of the original source to use static, user-defined values. Assuming you're using a stream profile preserving these, it should also work flawlessly 😁

This is a little more difficult ... because it can't be handled at this level. Probably need to be moved to Configuration / Channel/EPG / Channels, in order to add/override 'MPEG-TS Parameters" per channel.

Something like http://tvheadend:9981/stream/channelnumber/2?profile=dynamic_pass&mpeg_network_id=8442&mpeg_original_network_id=8442&mpeg_transport_stream_id=1&mpeg_service_id=2. Not sure how complicated it would be to implement that, tho'.

Frankly, this sounds a little strange ... but let's discuss this 'parameter pass' to profile option. Except WMC do you know any other applications that requires this rigid 'mpeg-ts parameters' to be passed? Don't understanding me wrong, I am not against it ... but is strange to ask for a "connection parameterized" that will be reflected back with the "parameters" I passed on 🙁 . But frankly if you want to override info 'per channel' ... and you don't have the ability in Configuration / Channel/EPG / Channels to manually write the parameters, also this is an option. I am tempted to say #2 is more future proof solution.

Kévin Chalet

ukn_unknown Depends .. : you selected software or hardware transcoding? Assuming you selected VAAPI, you need to force Rate Mode Control: to ICQ or QVBR. Also depends on what generation of iGPU you have. Anyway this is outside the scope.

I didn't tune anything so it's using the webtv-h264 defaults (IIRC, software decoding + the "faster" preset). Since it was just for a test and Hyper-V is likely not the best platform for any serious GPU/iGPU pass-through anyway, there was no real need to spend some time trying to make it look nice 😁

ukn_unknown This is an interesting piece of information ... probably it should be documented somewhere for other users.

Windows Media Center is compatible with the standards commonly used for DTV, so for video, only MPEG2 and H.264 - but not H.265/HEVC, hence the need for transcoding - are supported. For audio, it should be either MPEG2 or AC3/EAC3. Since it's abandoned software (for 10 years now), I wouldn't expect that list to change anytime soon 🤣

(off-topic: despite being abandoned software, it's still one of the best media center software... its UI is absolutely unmatched 🤣)

ukn_unknown We need to discuss with on a larger forum ... but I am tempted to say we need to add a "Reset MPEG-TS SI parameters" checkbox (that should be available only when MPEG-TS/libav is selected from the list).

Sounds reasonable 👌

ukn_unknown This is a little more difficult ... because it can't be handled at this level. Probably need to be moved to Configuration / Channel/EPG / Channels, in order to add/override 'MPEG-TS Parameters" per channel.

Yeah, it's exactly what I had in mind (and what I meant by "channel-bound", tho' it wasn't super clear 😁)

ukn_unknown Except WMC do you know any other applications that requires this rigid 'mpeg-ts parameters' to be passed?

Windows Media Center uses Microsoft DirectShow internally with all its BDA/DTV glory, including the Microsoft ATSC/DVB-T/DVB-S Network Provider that serves as the source filter and is the component that takes care of the tuning request (which is where the physical frequency and the MPEG-TS parameters are internally set).

I know Pouchin TV uses the same mechanism internally and I suspect other software like Media Player Classic use it too so they have the same "strictness" when it comes to MPEG-TS IDs.

ukn_unknown I am tempted to say #2 is more future proof solution.

Yeah, I agree the other option is likely better, while still being able to cover all the scenarios I have in mind. That said, I'm not super familiar with Tvheadend's code base, so maybe it's more complicated to implement?

apollo

It's nice to follow you...🙂
Thanks to both of you

ukn_unknown

Kévin Chalet I started the process to discuss what and if we should make those changes. I will try to help with what I know.
When we get the implementation of #2 I think will be helpful if you could help write a page in TVH documentation https://docs.tvheadend.org/documentation that describe how WMC is integrated TVH.
Frankly I think that even now (after PR is submitted) users might start integrate with WMC (with the limitations stated above) ... but for regular users I think is already a step forward. Maybe we can write a documentation with what works and what doesn't work and update the documentation after #2 will be implemented.
This way users will be able to find the info easier (hopefully).

ukn_unknown

Kévin Chalet I updated the branch with 1. if you have time please pull and recompile. You should see that you can override stream id and clear PMT and NIT to default values from ffmpeg. Unfortunately ffmpeg only allows for a subset of the pass parameters. Note that you need to set the Service ID to 0 in order to transfer the info (like it use to transfer before my update). Let me know how the results are looking.

Kévin Chalet

ukn_unknown Kévin Chalet I started the process to discuss what and if we should make those changes. I will try to help with what I know.

Awesome 👍

ukn_unknown When we get the implementation of #2 I think will be helpful if you could help write a page in TVH documentation https://docs.tvheadend.org/documentation that describe how WMC is integrated TVH.

Maybe we could start by adding a link to the https://kevinchalet.com/2023/07/05/connecting-windows-media-center-to-tvheadend-with-hdhrproxyiptv-an-alternative-to-dvblink/ blog post and use it as a starting point for something more Tvheadend-focused? If/once the changes you suggested are merged, I'll also need to update my WMC channels injection tool to create a unique streaming profile instead of one per channel (which will likely require enforcing the Tvheadend server version in the tool itself to ensure users use a version that supports the new model).

ukn_unknown I updated the branch with 1. if you have time please pull and recompile. You should see that you can override stream id and clear PMT and NIT to default values from ffmpeg.

I can confirm the new options are there:

I see you reused the options present in the pass profile, but maybe the first option should be renamed - or the help tooltip updated? - to indicate that it also preserves the MPEG-TS original network and transport stream IDs (i.e not just the service ID) when you set it to 0?

Using the magic 0 value works as intended and WMC renders the MPEG-TS without any issue. Here's an example with a transcoding profile that changes the video resolution to 1916x1078:

===============================================================================
|  SERVICES ANALYSIS REPORT                                                   |
|=============================================================================|
|  Global PID's                                                               |
|  TS packets: 47, PID's: 3 (clear: 3, scrambled: 0)                          |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Global PID's ................................. C       38,044 b/s  |
|   Subt.  Global PSI/SI PID's (0x00-0x1F) .............. C       38,044 b/s  |
|  0x0000  PAT .......................................... C       25,093 b/s  |
|  0x0010  NIT (Network: 0x20FA (8442) CNH) ............. C        6,476 b/s  |
|  0x0011  SDT/BAT ...................................... C        6,476 b/s  |
|=============================================================================|
|  Service: 0x0308 (776), TS: 0x0003 (3), Original Netw: 0x20FA (8442)        |
|  Service name: LCI, provider: CNH                                           |
|  Service type: 0x01 (Digital television service)                            |
|  TS packets: 18,031, PID's: 3 (clear: 3, scrambled: 0)                      |
|  PMT PID: 0x01F4 (500), PCR PID: 0x01FE (510)                               |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Digital television service ................... C   14,595,234 b/s  |
|  0x01F4  PMT .......................................... C       25,093 b/s  |
|  0x01FE  AVC video (1916x1078, main profile, level 4.0  C   13,720,216 b/s  |
|  0x01FF  MPEG-1 Audio (fre, Audio layer II, 384 kb/s,   C      849,925 b/s  |
|          (C=Clear, S=Scrambled, +=Shared)                                   |
===============================================================================

For reference, here's what you see in WMC when you don't use the MPEG-TS ONID and/or TSID and/or SID associated with the channel in WMC's database (in French, here):

ukn_unknown

Kévin Chalet I see you reused the options present in the pass profile, but maybe the first option should be renamed - or the help tooltip updated? - to indicate that it also preserves the MPEG-TS original network and transport stream IDs (i.e not just the service ID) when you set it to 0?

I update the tooltip to reflect the preservation of MPEG-TS original network and transport stream IDs.
Maybe was stated in the post above ... but can you confirm you tested with Service ID = 1 (or whatever number) and is generating the same results (in your system) with pass profile (with Service ID = 1)? sorry ... was not clear for me 🙁 .

Kévin Chalet

ukn_unknown Maybe was stated in the post above ... but can you confirm you tested with Service ID = 1 (or whatever number) and is generating the same results (in your system) with pass profile (with Service ID = 1)?

Yep, that works too!

===============================================================================
|  SERVICES ANALYSIS REPORT                                                   |
|=============================================================================|
|  Global PID's                                                               |
|  TS packets: 47, PID's: 3 (clear: 3, scrambled: 0)                          |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Global PID's ................................. C       34,510 b/s  |
|   Subt.  Global PSI/SI PID's (0x00-0x1F) .............. C       34,510 b/s  |
|  0x0000  PAT .......................................... C       22,762 b/s  |
|  0x0010  NIT (Network: 0xFF01 (65281) CNH) ............ C        5,874 b/s  |
|  0x0011  SDT/BAT ...................................... C        5,874 b/s  |
|=============================================================================|
|  Service: 0x024C (588), TS: 0x0001 (1), Original Netw: 0xFF01 (65281)       |
|  Service name: LCI, provider: CNH                                           |
|  Service type: 0x01 (Digital television service)                            |
|  TS packets: 19,521, PID's: 3 (clear: 3, scrambled: 0)                      |
|  PMT PID: 0x1000 (4096), PCR PID: 0x0100 (256)                              |
|-----------------------------------------------------------------------------|
|     PID  Usage                                     Access          Bitrate  |
|   Total  Digital television service ................... C   14,333,294 b/s  |
|  0x0100  AVC video (1916x1078, main profile, level 4.0  C   13,539,570 b/s  |
|  0x0101  MPEG-1 Audio (fre, Audio layer II, 384 kb/s,   C      770,963 b/s  |
|  0x1000  PMT .......................................... C       22,762 b/s  |
|          (C=Clear, S=Scrambled, +=Shared)                                   |
===============================================================================

ukn_unknown

Kévin Chalet thank you ... I really appreciate your help to confirm the functionality. Please keep an eye on the PR 🙂 in order to update your blog.
BTW: we didn't discuss what parameters you want to update for part 2?
FYI the following parameters are available from ffmpeg (but frankly we should override only what is needed ... at minimum):

mpegts_transport_stream_id
mpegts_service_type
mpegts_pmt_start_pid
mpegts_start_pid
mpegts_service_id
mpegts_original_network_id

Kévin Chalet

ukn_unknown Kévin Chalet thank you ... I really appreciate your help to confirm the functionality. Please keep an eye on the PR 🙂 in order to update your blog.

My pleasure! I'll wait until the second part is implemented to update the tool and the blog post, as it will drastically change how it imports channels into WMC's database: once #2 is implemented, I'll will be able to tweak it to use the API to retrieve the "MPEG-TS overrides" associated to each channel - if already set by the user - or assign default values if not already set. Without that, I'd need to retrieve the services associated to each channel, get the ONID/TSID/SID from there - if multiple conflicting values were found, it would likely have to throw - and hope the user will not add a service with different MPEG-TS IDs in the future.

ukn_unknown BTW: we didn't discuss what parameters you want to update for part 2?

To make WMC work with the scenarios we discussed, the following parameters must be overridable as they are used internally to identify a specific broadcast channel:

mpegts_original_network_id
mpegts_transport_stream_id
mpegts_service_id

While it's not strictly required, I think being able to override mpegts_service_type would be nice for users who want to use specific values (e.g users who have "radio channels", for which there's a dedicated service type value).

For the other ones, it's not clear to me what scenarios it would unlock if they were configurable.

Thanks a lot! 😍

« Previous Page