Hi @B3l3tte,
As of now the PopcornTeam NW.js build is used due to multiple missing codecs in the official NW.js build. Even when using an FFMpeg library with all codecs, the official NW.js build won't load them.
You can check these links:
- https://github.com/popcorn-official/popcorn-desktop/commit/8409778e7b0b0d8f92916dfa2cd24000048f197b#commitcomment-37874938 (Chat with official devs, follow the messages after)
- https://github.com/nwjs/nw.js/issues/5653 (official nw.js issue)
I will edit my comment and mention that the non-NWjs-official build is used :)
Pinned Comments
ItachiSan commented on 2018-07-24 21:01
You are free to report issues regarding the packaging here: be aware that sometimes the package will fail to build because of outdated upstream and updated dependency, which will require me some time to test and solve the problem; I do also have life stuff, packaging is a free-time activity.
Info regarding the package
The package uses the sources available at: https://github.com/popcorn-official/popcorn-desktop. I am aware of the different clones and branches; I do still believe that this code is acceptable (not affected itself from malware).
This package uses a custom NW.js build provided from the PopcornTime team; essentially, a custom compiled browser. While this won't affect you as it should be used only within the app, you are here informed that I have no power over this component.
The above point stands as the official NW.js Chromium source lacks multiple modern codecs, such as AC3 and HEVC (H.265).
Earlier this package used the official nw.js toolchain provided available at https://dl.nwjs.io/ and the prebuilt FFmpeg library with additional codecs available at https://github.com/iteufel/nwjs-ffmpeg-prebuilt/ . This was because the nw.js toolchain provided by the PopcornTime team can not be proven as non-malware easily. However, due to point 3, this approach was reverted. You are free to use an older PKGBUILD with the appropriate variable updates to re-enable this, however you will miss support for recent codecs.
In addition, the PKGBUILD won't point to the Git release reference but will also include important commits, for e.g. security reasons or providers changes.