Describe the Bug
The Stream Master UI displays that ffmpeg is being launched with the parameters specified in the custom profile. However, when inspecting the running container, the ffmpeg process is started with different arguments than what is shown in the UI.
Stream Master Info
Version Number: channels-0.15.0.60 (Docker image: senexcrenshaw/streammaster:channels-0.15.0.60)
Unfortunately, I do not have direct logs, but I’ve attached screenshots showing the discrepancy between the UI and the actual process arguments.
Steps to Reproduce:
Run the StreamMaster instance using the Docker image senexcrenshaw/streammaster:channels-0.15.0.60.
Configure a custom ffmpeg profile in the UI.
Start a stream.
Enter the container and check the ffmpeg process with ps aux | grep ffmpeg.
Observe that the running ffmpeg process does not match the parameters defined in the UI profile.
Expected Behavior ffmpeg should launch with the parameters defined in the custom profile set in the UI.
Additional Context
It appears the custom profile isn't correctly applied to the running ffmpeg process, causing a mismatch.
An important clarification: if you select the profile not in the stream group but in the m3u file and its settings, it applies correctly, and ffmpeg runs with the correct parameters.
Describe the Bug
The Stream Master UI displays that
ffmpeg
is being launched with the parameters specified in the custom profile. However, when inspecting the running container, theffmpeg
process is started with different arguments than what is shown in the UI.Stream Master Info
channels-0.15.0.60
(Docker image:senexcrenshaw/streammaster:channels-0.15.0.60
)Unfortunately, I do not have direct logs, but I’ve attached screenshots showing the discrepancy between the UI and the actual process arguments.
Steps to Reproduce:
senexcrenshaw/streammaster:channels-0.15.0.60
.ffmpeg
profile in the UI.ffmpeg
process withps aux | grep ffmpeg
.ffmpeg
process does not match the parameters defined in the UI profile.Expected Behavior
ffmpeg
should launch with the parameters defined in the custom profile set in the UI.Additional Context
It appears the custom profile isn't correctly applied to the running
ffmpeg
process, causing a mismatch.