Multiple Transcode directives under one vhost

[mjankovskis]

What is the business background? Please provide a description.
Everyone who wants to transcode different app on different endpoint etc.
Single transcode on single app is working, but multiple transcode in config on different apps doesn't work.

Is your feature request related to a problem? Please describe.

vhost __defaultVhost__ {
  #for example i have "msrc" app which should remove audio from input
  transcode msrc {
          enabled on;
          ffmpeg ./objs/ffmpeg/bin/ffmpeg;
          engine copy {
              enabled on;
              vcodec copy;
              acodec an;
              output rtmp://127.0.0.1:[port]/history/[stream][param];
          }
   }
  #for example i have "msrc/0" app which should remove audio but point to different endpoint
  transcode msrc/0 {
          enabled on;
          ffmpeg ./objs/ffmpeg/bin/ffmpeg;
          engine copy {
              enabled on;
              vcodec copy;
              acodec an;
              output rtmp://127.0.0.1:[port]/live/[stream][param];
          }
   }
  #for example i have "src" app which should remove audio but point to history endpoint
  transcode msrc/0 {
          enabled on;
          ffmpeg ./objs/ffmpeg/bin/ffmpeg;
          engine copy {
              enabled on;
              vcodec copy;
              acodec copy;
              output rtmp://127.0.0.1:[port]/history/[stream][param];
          }
   }

Describe the solution you'd like
When adding single transcode to vhost __defaultVhost__ it works, but when add multiple transcode, only the first one works.

Describe alternatives you've considered
Alternative is to use another server (ip:port) or domain (vhost) which handles transcoding but allowing multiple transcodes under single vhost would allow to easier maintain, as problem is that this is related to streaming devices and configurating devices is timeconsuming. as there are audio, without-audio endpoints

The transcode functionality works as is, but would be nice to pass multiple transcods by "app"

I think that this could be implemented in here, it should itereate over all "transcode" configs, instead of getting first one.

{
    SrsConfDirective* conf = get_vhost(vhost);
    if (!conf) {
        return NULL;
    }
    
    conf = conf->get("transcode");
    if (!conf || conf->arg0() != scope) {
        return NULL;
    }
    
    return conf;
}

[winlinvip]

The transcode feature is not a core feature of SRS, which means you should never overuse it.

Instead, you should create a live transcode cluster with FFmpeg for complex tasks, which supports various use scenarios and requirements.

For such a transcoding cluster, the most important thing is to schedule transcoding tasks to different FFmpeg worker nodes. In short, it is a task management cluster, rather than a media streaming server.

SRS is definitely not designed as a task management cluster, so you need to create one using Go for such purposes.