-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange bug in audio init segments #2773
Comments
I can reproduce with:
|
This is worse than expected, the output content is not able to be played if it contains audio tracks from my current tests |
Ok, the audio track encryption does not work even when encrypting just one track. |
Did we get any news on this bug? Can I help somehow? |
It should not, and I cannot reproduce locally with your command line.
Are you sure these are not leftovers from previous tests ? If not and still reproducible, please upload some test content. All tracks are encrypted as well, and playback / decryption is OK in GPAC. What are you using for playback validation ? |
The problem is just with the naming (The produced files can be played without any issue), as @rbouqueau said the problem is in the naming specifically. I would expect for template=seg-$Number$ Command I am using:
File pack: |
Got it, this was due to bitstream switching mode detection (in your case, audio tracks use bitstream switching mode since they have the same decoder config). This was preventing the default "init" to be appended (compat with old arch). This is now fixed, thanks for the report |
With the following gpac command:
For some unknown reason, the$Number$ does not resolve as init in the audio tracks. It does for video.
Even when nto specifying template names, I started noticing that for audio tracks the output init track was by default _dash.mp4 while for video tracks it was _dashinit.mp4.
I guess there might be a bug but I cannot find why or where. Maybe related to when there are several audio inputs? The file inputs have only one track each video or audio.
The text was updated successfully, but these errors were encountered: