Closed kaushikkunal99 closed 6 years ago
@kaushikkunal99 Can you share the source content and packaged outputs? You can email it to shaka-packager-issues@google.com if it cannot be shared publicly.
@kqyang I have emailed the urls. Can you take a look?
@kaushikkunal99 Thanks for the streams. I have traced down the bug to the handling of $Time$ in segment template. I am working on the fix.
In the mean time, you can use "$Number$" instead of "$Time$" in segment template. We recommend "$Number$" over "$Time$" as it results in more organized outputs and it is also simpler in player side.
@kaushikkunal99 Can you try the fix I just submitted?
Sure we will try it and let you know. We also found it to be issue with frame rate 23.97. When we fixed 23.97 frame rate the issue went away. We will also try the new packager.
Thanks Kunal
On Wed, Sep 12, 2018 at 7:12 PM Kongqun Yang notifications@github.com wrote:
@kaushikkunal99 https://github.com/kaushikkunal99 Can you try the fix I just submitted?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/shaka-packager/issues/472#issuecomment-420859604, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE2527Pu_wE0xBHfRPF_W5VGdxi7o_lks5uab8igaJpZM4Wkez- .
@kaushikkunal99 So looks like there are two separate issues.
Have you had a chance to try out the new packager? Can we close the issue now?
hi @kqyang seems like we are not able to install the latest version of packager on AWS ami. Below is the step its failing. Could you help us with this?
[root@ip-10-1-34-59 src]# ninja -C out/Release
ninja: Entering directory `out/Release'
[493/1609] LINK protoc
FAILED: protoc
../../packager/third_party/llvm-build/Release+Asserts/bin/clang++ -Wl,-z,now -Wl,-z,relro -Wl,--fatal-warnings -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -Wl,--disable-new-dtags -m64 --sysroot=/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot -L/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/lib/x86_64-linux-gnu -Wl,-rpath-link=/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/lib/x86_64-linux-gnu -L/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib/x86_64-linux-gnu -Wl,-rpath-link=/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib/x86_64-linux-gnu -L/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6 -Wl,-rpath-link=/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6 -L/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib -Wl,-rpath-link=/opt/software/test/shaka_packager/src/packager/build/linux/debian_wheezy_amd64-sysroot/usr/lib -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -Wl,--no-as-needed -lpthread -Wl,--as-needed -o protoc -Wl,--start-group obj/third_party/protobuf/src/google/protobuf/compiler/protoc.main.o obj/third_party/protobuf/libprotoc_lib.a obj/third_party/protobuf/libprotobuf_full_do_not_use.a -Wl,--end-group
/usr/bin/ld: this linker was not configured to use sysroots
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[530/1609] CC obj/third_party/boringssl/src/crypto/fipsmodule/boringssl.bcm.o
ninja: build stopped: subcommand failed.
@kaushikkunal99 Have you run "gclient sync" or "gclient runhooks" after syncing to latest release?
@kqyang yes i did. I am trying a fresh install per your documentation.
@kqyang any info on this?
I am trying a fresh install per your documentation.
Are you seeing the same problem with a fresh install?
@kaushikkunal99 Are you still seeing problems?
Closing due to inactivity. If this is still an issue for you or if you have further questions, you can ask us to reopen or have the bot reopen it by including @shaka-bot reopen
in a comment.
System info
AWS AMi Latest packager version
Issue and steps to reproduce the problem
Audio and Video are out of sync
Packager Command: 5fa3c3ae-63d4-41e6-8065-468c3d0f59c1.txt
/opt/software/packager in=TMP/wm/A/ToS_216p_1M/video.mp4,stream=audio,init_segment=wm/audio/und/mp4a/init.mp4,segmenttemplate=wm/audio/und/mp4a/seg\$Time\$.m4s in=TMP/wm/A/ToS_216p_1M/video.mp4,stream=video,init_segment=tmp/216/A/wm/video/avc1/ToS_216p_1M/seg_init_0.mp4,segment_template=tmp/216/A/wm/video/avc1/ToS_216p1M/seg\$Time\$.m4s in=TMP/wm/B/ToS_216p_1M/video.mp4,stream=video,init_segment=tmp/216/B/wm/video/avc1/ToS_216p_1M/seg_init_0.mp4,segment_template=tmp/216/B/wm/video/avc1/ToS_216p1M/seg\$Time\$.m4s --generate_static_mpd --mpd_output wm/.mpd --enable_widevine_encryption --key_server_url --content_id --signer spedmg --aes_signing_key --generate_dash_if_iop_compliant_mpd=false --aes_signing_iv
What is the expected result? Audio video in sync
What happens instead? We tried on bitmovin player it works fine for few minutes and then starts to go out of sync.