Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
29th March 2016, 03:27 | #2201 | Link | |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Quote:
The specified module could not be found. Usually it's a permissions issue, yes. Dunno what else can cause it. Last edited by TheFluff; 29th March 2016 at 03:30. |
|
29th March 2016, 06:53 | #2202 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
126 (0x7E) ERROR_MOD_NOT_FOUND
It seems to use a lot of external dll's, check it out with Dependency Walker or Groucho2004 Avisynth Info tool (for missing requirements).
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
31st March 2016, 21:56 | #2205 | Link |
Registered User
Join Date: May 2005
Posts: 1,462
|
Just out of curiosity, why can't FFVideoSource be frame-safe after all these years?! I'm using DGSource again (for my more demanding projects, that use QTGMC and MCTemporalDenoise and such), so I'm okay; but just wondering why that can't happen with FFVideoSource (it's indexing, after all).
__________________
Gorgeous, delicious, deculture! |
1st April 2016, 19:02 | #2206 | Link | |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Quote:
Last edited by TheFluff; 1st April 2016 at 20:22. |
|
2nd April 2016, 03:33 | #2207 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
__________________
Gorgeous, delicious, deculture! |
|
2nd April 2016, 10:33 | #2209 | Link | |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
Quote:
|
|
5th April 2016, 12:57 | #2211 | Link |
Registered User
Join Date: Mar 2016
Posts: 1
|
Build ffms2 dll?
It's happiness, 5 days passed!
Hi! I have problem to build FFms2 with shared DLL with Minwg64 in Msys2. This is my config --prefix=xxx --enable-shared --disable-static CXXFLAGS='-static-libgcc -static-libstdc++ -Wl,-Bstatic -lpthread -lwinpthread' error: undefined "___imp_pthread_once" use flags to import static libgcc and libwinpthread. Its working for another source but not working for ffms2. Its successful when i used config --enbale-static --disable-shared to build only ffmsindex.exe Am i wrong or is that bugs? Please help! Thank you! |
11th April 2016, 18:07 | #2212 | Link | |
unsigned int
Join Date: Oct 2012
Location: 🇪🇺
Posts: 760
|
Quote:
Code:
--- mingw-w64-libraries/winpthreads/include/pthread.h 2014-10-26 04:11:33.000000000 +0200 +++ mingw-w64-libraries/winpthreads/include/pthread.h 2014-12-10 14:17:45.542746397 +0200 @@ -82,7 +82,9 @@ /* MSB 8-bit major version, 8-bit minor version, 16-bit patch level. */ #define __WINPTHREADS_VERSION 0x00050000 -#if defined DLL_EXPORT +/* No __declspec crap needed when winpthreads is static. + * In fact, it produces linker errors (can't find __imp_blah). */ +#if defined DLL_EXPORTzzzzzzzzzzz #ifdef IN_WINPTHREAD #define WINPTHREAD_API __declspec(dllexport) #else
__________________
Buy me a "coffee" and/or hire me to write code! |
|
17th April 2016, 23:28 | #2213 | Link | |
Registered User
Join Date: Nov 2005
Posts: 693
|
Quote:
Today I've updated r944+69 to r1110+98, but only to find out that it doesn't work anymore, because AvsPmod and FFPlay now report: Unable to load C Plugin: "ffms2.dll", error=0x5. So far r944+69 is the latest build that works for me, because I can't test r1015+85 and newer as their downloadlinks don't work anymore.
__________________
My hobby website |
|
18th April 2016, 00:37 | #2214 | Link |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
SSE2 and Vista+ are a minimum requirement for a lot of things these days - it's been fifteen years since SSE2 was introduced, so if you want to do anything that requires even a moderate amount of computing power today, you're kind of expected to have it. I don't think anyone (except possibly qyot27) will go out of their way to release builds that work on CPU's without SSE2. If XP support starts requiring even a minuscule amount of developer effort, expect that to disappear as well.
|
18th April 2016, 00:42 | #2215 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Here, Win XP32SP3 C plug r1110+98 working OK here (at least that is the recorded version number that I believe I have, 14,731,264 bytes. Just checked,
is same as one I'm using). I'm not using AvsPMod and Intel CPU here (Core Duo). EDIT: OK, Fluffy seems to have pin pointed problem.
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 18th April 2016 at 00:44. |
18th April 2016, 01:19 | #2216 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
In the interest of full disclosure, I do very little in the way of anything video related on my Coppermine anymore, and the builds are mainly still built for it out of habit and that i686 is a fairly normalized baseline target for 32-bit; and it lets me test stability since older machines run into problems much faster if something starts eating memory for breakfast and sparks a crash. But for the last seven months I've mostly used a Silvermont-based mini-PC for my video tasks (along with most everything else; the Coppermine setup is now mainly a jukebox, storage area, and disc burner). Prices on similar machines are very affordable (read: I bought mine for $170), so the cost argument of staying on really old hardware isn't nearly as powerful as it once was - and it's a lot more powerful than the PIII is, although that should be pretty obvious. I can downscale from 720p to 720x480 with Lanczos4 for encoding with HCenc for DVD authoring and get usually in the 18-23fps range, compared to ~2fps on the Coppermine.
The weird nature of this particular situation makes me think it's something that changed somewhere deep in the MinGW-w64 or GCC parts, which would be a nightmare to untangle (and at some point I'm sure this will happen in regard to XP support; in which case the only hope is that ReactOS reaches general viability* before then). The most optimistic scenario is that I misconfigured something when building those pieces and all I'd have to do is rebuild them to fix everything. *the key word there being 'general'; it seems to already be more or less capable of running the AviSynth and VapourSynth ecosystems and at least the CLI tools (which shouldn't be a surprise, since Wine has been able to do most of that for years now). It's just the rest of system that presents a challenge for everyday use at the present time. Last edited by qyot27; 18th April 2016 at 01:23. |
18th April 2016, 10:53 | #2217 | Link |
Registered User
Join Date: Nov 2005
Posts: 693
|
It seems the lifespan of my secondary computer is really approaching its end, because not only with AviSynth (plugins), but with a lot more software it's getting harder and harder to keep up-to-date.
Thanks for the legacy support this far, qyot27.
__________________
My hobby website |
18th April 2016, 15:11 | #2219 | Link |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,905
|
Sounds kinda weird 'cause the C++ Redistributable 2015 (the last released) works under XP, so, basically, it should run on XP.
I'm gonna try it as soon as I get home. EDIT: I confirm it works in XP SP4. p.s it's not a spam, but check MSFN for Win XP mods. Last edited by FranceBB; 18th April 2016 at 17:01. |
18th April 2016, 19:08 | #2220 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Also MinGW/G++ does not use Microsoft's MSVCP.DLL (Standard C++ Library), it uses the Libstdc++ by GNU. Finally, latest Visual Studio can still produce binaries for Windows XP, but does not do so by default. Not sure about latest MinGW (Mingw-w64), but I wouldn't be surprised if they start using API's not preset in XP sooner or later. And, of course, the compiler (runtime libs) is only one side. If the application code or any of the third-party libs uses API's not present in XP, then the whole thing won't work on XP - regardless what compiler you use. (BTW: AVX unavoidably requires Windows 7 with SP-1 or later, no matter what. Older Windows versions did not save/restore the AVX registers on task switch)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 18th April 2016 at 19:21. |
|
|
|