private async Task<byte[]> DownloadChunk(HttpResponseMessage response, long start, long end)
{
    using(var memoryStream = new MemoryStream())
    using(var responseStream = await response.Content.ReadAsStreamAsync())
    {
        var bufferSize = 10 * 1024 * 1024; // 10MB
        var buffer = new byte[bufferSize];
        int bytesRead;
        int totalBytesRead = 0;

        // Seek to the start position
        responseStream.Seek(start, SeekOrigin.Begin);

        while(totalBytesRead < end - start && (bytesRead = await responseStream.ReadAsync(buffer, 0, bufferSize)) > 0)
        {
            await memoryStream.WriteAsync(buffer, 0, bytesRead);
            totalBytesRead += bytesRead;
        }

        return memoryStream.ToArray();
    }
}

private async Task<byte[]> DownloadChunk(HttpResponseMessage response, long start, long end)
{
    using(var memoryStream = new MemoryStream())
    using(var responseStream = await response.Content.ReadAsStreamAsync())
    {
        var bufferSize = 10 * 1024 * 1024; // 10MB
        var buffer = new byte[bufferSize];
        int bytesRead;
        int totalBytesRead = 0;

        // Seek to the start position
        responseStream.Seek(start, SeekOrigin.Begin);

        while(totalBytesRead < end - start && (bytesRead = await responseStream.ReadAsync(buffer, 0, bufferSize)) > 0)
        {
            await memoryStream.WriteAsync(buffer, 0, bytesRead);
            totalBytesRead += bytesRead;
        }

        return memoryStream.ToArray();
    }
}

Cons:

Increased Payload Size: String representations generally occupy more space in JSON payloads compared to integer representations, potentially increasing network bandwidth usage and storage requirements.

Performance Overhead: Converting between enum values and strings requires additional processing compared to direct integer serialization/deserialization, which may have a slight impact on performance, especially in high-throughput scenarios.

Parsing Complexity: If using custom string representations, it might introduce parsing complexities, especially when dealing with edge cases or legacy data.

Compatibility with Existing Clients: If the consumers of your JSON data are expecting integer representations of enum values, switching to string representations might require updates on their end.

Loss of Type Safety: Using string representations loses some type safety compared to using integer values, as there's no compile-time check to ensure that the provided string corresponds to a valid enum value.

Cons:

Increased Payload Size: String representations generally occupy more space in JSON payloads compared to integer representations, potentially increasing network bandwidth usage and storage requirements.

Performance Overhead: Converting between enum values and strings requires additional processing compared to direct integer serialization/deserialization, which may have a slight impact on performance, especially in high-throughput scenarios.

Parsing Complexity: If using custom string representations, it might introduce parsing complexities, especially when dealing with edge cases or legacy data.

Compatibility with Existing Clients: If the consumers of your JSON data are expecting integer representations of enum values, switching to string representations might require updates on their end.

Loss of Type Safety: Using string representations loses some type safety compared to using integer values, as there's no compile-time check to ensure that the provided string corresponds to a valid enum value.

builder.Services.AddControllers()
            .AddNewtonsoftJson(options =>
            {
                options.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore;
                options.SerializerSettings.Converters.Add(new StringEnumConverter());
            });

public enum SourceType
{
    [Description("Source Link")]
    [EnumMember(Value = "Source Link")]
    SourceLink = 1,
    [Description("Channel")]
    [EnumMember(Value = "Channel")]
    Channel = 2,
    [Description("Video")]
    [EnumMember(Value = "Video")]
    Video = 3
}

builder.Services.AddControllers()
            .AddNewtonsoftJson(options =>
            {
                options.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore;
                options.SerializerSettings.Converters.Add(new StringEnumConverter());
            });

public enum SourceType
{
    [Description("Source Link")]
    [EnumMember(Value = "Source Link")]
    SourceLink = 1,
    [Description("Channel")]
    [EnumMember(Value = "Channel")]
    Channel = 2,
    [Description("Video")]
    [EnumMember(Value = "Video")]
    Video = 3
}