Skip to content
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

SMP folder missing in FFMPEG #5

Open
Alex44300 opened this issue Mar 11, 2021 · 9 comments
Open

SMP folder missing in FFMPEG #5

Alex44300 opened this issue Mar 11, 2021 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@Alex44300
Copy link

Hi,

I encountered some difficulties trying to build the bitstream_mode3_videoparser on Windows.
When I try to build the TestMain.sln file, libavcodec, libavformat and libavutil can't be loaded because the folder SMP is missing in ffmpeg.

Am I doing something wrong ?

Best regards

@slhck
Copy link
Member

slhck commented Mar 11, 2021

I am not sure how much I can help you, since I don't have a Windows build environment here, but have you seen the steps here?

https://github.com/Telecommunication-Telemedia-Assessment/bitstream_mode3_videoparser/blob/master/development.md

As far as I can see, those folders were never there during the development of this project, and weren't needed for building.

Does the build not succeed?

@Alex44300
Copy link
Author

Alex44300 commented Mar 11, 2021

Following this guide, when I have all the dependencies and I try to build the TestMain.sln file I have the following error :
![image](https://user-images.githubusercontent.com/59611187/110795108-c4890d00-8276-11eb-9c4d-46f1b2e0e99d.png = 250x250)

and in the TestMain.sln we can read:
image

Best regards

@slhck
Copy link
Member

slhck commented Mar 11, 2021

I assume that these have been originally generated with https://github.com/ShiftMediaProject/FFVS-Project-Generator. It might be an option to run this generator again on the source files to create the respective Visual Studio project files.

As mentioned above, I don't have a Windows build environment here. Unfortunately the original maintainer of the Windows version is not directly reachable at the moment, but I can try to find out what's going on with these folders.

@Alex44300
Copy link
Author

Thank you for your answer, I appreciate ! In the end I have built everything with Ubuntu, it was less trouble. Now it's working well. My purpose was to run the metric p1204.

@slhck
Copy link
Member

slhck commented Mar 13, 2021

Okay, good to know!

(We're still trying to find those SMP files … so I'll keep this open for the time being.)

@slhck slhck added the bug Something isn't working label Mar 13, 2021
@slhck slhck self-assigned this Mar 13, 2021
@stg7
Copy link
Member

stg7 commented Mar 19, 2021

well honestly, I would skip the windows support, because there are all external dependencies required for the build.
Besides this, with the windows linux subsystem (WLS) it should be possible to build it under windows.

@slhck
Copy link
Member

slhck commented Mar 19, 2021

Considering the added complexity and the availability of Docker as well as WSL, yes, I think Windows support is more of a burden than a benefit here.

@Alex44300
Copy link
Author

Ok thank you very much for your help, I'm running p1204 with WLS indeed. Does that also make p1204 quality metric not "buildable" with Windows only ?

@slhck
Copy link
Member

slhck commented Mar 19, 2021

The metric itself should be portable – it's just Python. In order to get the actual features, you need the bitstream parser though. The p1204 code calls the bitstream parser and generates feature files. These can be extracted offline before, too, if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants