
Recherche avancée
Autres articles (28)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
Les images
15 mai 2013
Sur d’autres sites (1646)
-
How to compile FFmpeg with bash on Windows 10 ?
10 août 2017, par user2980183In the Creators Update (1703), the Windows 10 bash linux (WSL) can run native windows tools. So, under Windows 10, you can now compile FFmpeg with Visual Studio and the required linux utilities, natively, without having to install MinGW or other interop crap software.
Here is how I tried to compile FFmpeg (using MSVC 2017 toolchain) :
-
I started the bash shell from "Developer Command Prompt for VS 2017" to set PATH variable to find the MSVC compiler/linker.
-
I installed the "make" tool with the following command : "sudo apt-get install make".
-
To call Windows program from the bash shell, I have to type the command with its .exe extension. So, I must adapt the "configure" and "compat/windows/makedef" files to add ".exe" at the end of "cl", "link" (no confusion possible with the /usr/bin/link), "dumpbin" and "lib" executables :
configure
cl_major_ver=$(cl 2>&1 | sed -n 's/.*Version \([[:digit:]]\{1,\}\)\..*/\1/p')
if [ -z "$cl_major_ver" ] || [ $cl_major_ver -ge 18 ]; then
cc_default="cl.exe"
else
cc_default="c99wrap cl"
fi
ld_default="link.exe"
nm_default="dumpbin.exe -symbols"
ar_default="lib.exe"compat/windows/makedef
lib.exe -out:${libname} $@ >/dev/null
arch=$(dumpbin.exe -headers ${libname} |
tr '\t' ' ' |
grep '^ \+.\+machine \+(.\+)' |
head -1 |
sed -e 's/^ \{1,\}.\{1,\} \{1,\}machine \{1,\}(\(...\)).*/\1/')
dump=$(dumpbin.exe -linkermember:1 ${libname})I hope the FFmpeg build tool chain will be adapted in the future to support natively compiling on bash on Windows...
- If you want to set an absolute path for YASM in the "configure", you have to use the following pattern
/mnt/[letter_partition]/path/yasm.exe
.
./configure --toolchain=msvc --yasmexe='/mnt/e/Home/Important/Development/Toolkit/Tools/yasm-1.3.0-win32.exe' [all other settings you need]
-
The
make
command should generate the lib as expected. -
I tried to type
make install
but I get the following error :
No rule to make the target "libavutil\x86\x86util.asm", needed for "libavutil/x86/cpuid.o".
I don’t know what is wrong...
As you can see, building FFmpeg on bash under Windows is not very developer friendly yet. Compiling FFmpeg in Windows should be as easy as Linux. Do you know if there is an easier way to proceed ? Do you know if this compilation scenario will be officially supported in next versions of FFmpeg (I don’t find any roadmap) ?
Thanks.
-
-
Matomo NAMED 2023 Hi-Tech Awards finalist
1er août 2023, par Lance — Press Releases -
Issue with Asynchronous Video Processing and New Window Creation in Windows Forms Application
2 août 2023, par sadra hoseiniI have a Windows Forms application that uses FFmpeg for video processing tasks. In this application, I have a textBox2_TextChanged event handler that performs some video processing tasks based on user input.


However, I noticed that when textBox2_TextChanged is called, the UI becomes unresponsive, and it seems like another window is being created but doesn't show up. I suspect that this issue is related to threading.


Here's a simplified version of the problematic code :


// Relevant code snippet:
private async void textBox2_TextChanged(object sender, EventArgs e)
{
 if (listBox1.Items.Count > 0 && int.TryParse(textBox2.Text, out int itemvalue) && int.TryParse(textBox1.Text, out int ratio))
 {
 await Task.Run(() =>
 {
 // Video processing code using FFmpeg (e.g., creating thumbnails).
 // This code seems to cause the UI to freeze and prevent new windows from showing up.
 });
 }
}



Expected Behavior :


When a user enters a valid input in textBox2, the video processing tasks should be executed in the background without freezing the UI. The application should remain responsive, and any new windows, including message boxes or progress dialogs, should show up as expected.


Actual Behavior :


When a user enters a valid input in textBox2, the video processing tasks appear to be running, but the UI becomes unresponsive, and new windows, such as message boxes, do not show up as expected. This makes it challenging to display any progress or error messages to the user during video processing.


Steps to Reproduce :


Open the Windows Forms application.
Add some video files to the list (listBox1) and provide valid input in textBox2.
Observe the UI behavior and any new windows that should be displayed, such as progress dialogs or message boxes.
Additional Notes :


I am using Visual Studio [version] for development.
The application uses FFmpeg for video processing tasks, and I've verified that FFmpeg is functioning correctly.
I've also tried using proper error handling to catch any exceptions, but no exceptions are thrown during the video processing tasks.
Any help or suggestions on how to resolve this issue and enable new window creation during video processing would be greatly appreciated. Thank you !