Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I want to use alize for voice recognition. I need some guidance in alize setup. I am using windows 7.
Alize is a toolkit for speaker recognition , verification and segmentation.
To set up the system once you have compiled alize binaries the easiest way is to take one of the demos avaliable in the Website.
Alize is decomposed into ALIZE library (.dll/.lib) and LIA_RAL which is a library + some tools that will allow you to build the system by command line.
Alize needs to work with signal parametrizations (features) extracted by other libraries like : SPRO and HTK. I will recommend you to compile SPRO because most of the examples use it, however HTK file format is also allowed or even with matlab you can save your own parametrization in SPRO/HTK format.
once you got you binaries , spro binaries and your demo folder , just copy the requiered files into the bin folder. Now read the readme and follow the script execution , you may prefer work in cygwin or use a window bash port.
the tricky parts with ALIZE/LIA-RAL are the path manipulation. Most of the "File not found" exceptions com from un-appropiated format in guide files: paths must be relative, without starting slash and the files does not contain extensions. ej: "emocions/angry/15a04Wa". You have to remember that the C code includes the slash and appends the extension to the name using the information present in the corresponding config file.
Check the code for details about parameter meaning , its the easiest way.
Related
This question already has answers here:
Is there a Visual Basic 6 decompiler? [closed]
(6 answers)
Closed 1 year ago.
A few days ago, I have formated my disk and I have lost all datas.
Now I have only two VB6 exe files and I want source code from those.
Is there any way to recover source code from VB6 exe files?
Please help me.
You cannot, in general, retrieve source code from an executable as it's a one-way transformation from in this case visual basic to binary machine code. If you compiled your binary with debug information you have more information available. You can of course obtain assembly and there are a class of tools that is called decompilers that ease transformation to a high-level language like C. See for example https://reverseengineering.stackexchange.com/questions/8038/exe-to-c-source-code-decompiler. Sorry.
This is a very simple question but I have been searching for a while now and have no luck. Im supposed to add it to the linker I beleive? Which is Project Properties > Linker > Input > Additional Dependencies. Im just confused on exactly what to do. Thank you.
The simplest solution is to add the Microsoft.DXSDK.D3DX NuGet package to your project and not use the legacy DirectX SDK at all. This puts the headers d3dx9*.h, d3dx10*.h, and d3dx11*.h into your include path. It also adds d3dx9.lib, d3dx10.lib, and d3dx11.lib to your link settings, and provides the required runtime DLLs 'side-by-side'. See this blog post.
Otherwise, to integrate the legacy DirectX SDK requires some special include/lib path ordering in VC++ Directories, and you'll have a number of other quirks to contend with. See Microsoft Docs for the details.
Of course, the real question is "Why are you using legacy Direct3D 9 in the first place instead of Direct3D 11?". For Direct3D 11 or Direct3D 12, you should avoid the legacy DirectX SDK and D3DX9/D3DX10/D3DX11 entirely. See Living without D3DX.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
This post contains all the problems I (and other users) had while building the library from sources. As there is no tutorial, I decided to create this sort of FAQ post to put all the solutions together. Hope it will help!
Configuration:
OpenCV 3.2.0
MinGW-w64 x86_64-6.1.0-win32-seh-rt_v5-rev0
You are welcome to add more information in the answers, as it is more handy to have everything in one place.
Download and unpack OpenCV to a folder of your choice.
opencv\sources now contains CMakeLists.txt and all the other files necessary. Configure the project in CMake. CLion users may just open CMakeLists.txt.
Fix 1: sprintf () family security error.
Add add_definitions(-DSTRSAFE_NO_DEPRECATE) to the beginning of CMakeLists.txt. This will define STRSAFE_NO_DEPRECATE symbol for the project and suppress the error.
Fix 2: 'too many sections' as.exe error.
Add the following lines to the beginning of CMakeLists.txt (source):
set(CMAKE_CXX_FLAGS ${CMAKE_CXX_FLAGS} "-Wa,-mbig-obj")
set(CMAKE_C_FLAGS ${CMAKE_C_FLAGS} "-Wa,-mbig-obj")
Fix 3: 'the last argument must be an 8-bit immediate'.
Found nothing better than hardcoding 0x88 instead of mask_lo = _MM_SHUFFLE(2, 0, 2, 0) (binary 10 00 10 00) and 0xDD instead of mask_hi.
As soon as my question gets a better answer, I will update this paragraph.
Fix 4: no c++11 threads in MinGW.
Again, a dirty solution: added #include <mingw.*.h> to <mutex>, <thread>, <condition_variable> before #endif // C++11. (Source)
Build it! It will take about 30-40 minutes.
Find the output folder. It is still a mess but contains a Makefile.
Launch cmd, cd to the output folder and call [path to compiler]\mingw32-make.exe install. (Source)
Voila, your library is in the install folder! Now you can move it to a desired destination and set up environment variables.
I want to export some strings in my application into CSS format. For example,
[00:01:14.20] {RU2}{RU2}{CR}{CR}{1500}{1500}YOUR PLACE TO LEARN AND TALK
to:
00:01:14:20 9425 9425 94ad 94ad 9470 9470 d94f d552 20d0 4cc1 4345 2054 4f20 4c45 c152 ce20 c1ce c420 54c1 4ccb
Is there any gem that takes care of this? Or, do I need to create my own logic?
The Scenarist Closed Captions format tools have no bindings for ruby, AFAIK. The possible solution would be to download the tools from the author’s site, extract the perl scripts from SOURCE folder inside zip archive, bundle these perl scripts with your project and call these scripts as linux system utilities via %x||.
I know no better alternative to implementing the logic yourself / porting these perls to ruby.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
This is probably a silly question but here goes:
I like to be able to see the source code of third party (OSS) libraries from within my projects. I always setup my projects like this when using java. Is this possible in Visual Studio? I am not interested in building them! Only have them available for reference if lets say an exception stack trace points to a third party component...
Debugging a third-party DLL in Visual Studio.NET? covers much of the details if you're trying to do this for debugging purposes. But in general, two points to take away. First, it's unfortunately a little bit harder than it would be in Java. Second, it depends heavily on what language you're using.
Essentially, you do the following if it's a .NET assembly you're working against.
Decompile the source code with something like Reflector, then treat the decompiled source code as a new library within your project and set breakpoints in the source.
Remove all references to the 3rd party library so that it is the decompiled code that is executing.
Don't forget to remove references to the source elements later.
If it's an existing open-source library, you can just compile the source yourself into program database (PDB) files, assuming there's a corresponding VS project. More on that here.
To achieve this you have to have pdb files.
If library is provided with debug symbol file you have to place pdb file in the same location that dll. During debug VS will ask you about location of source files.
You can read about it here http://msdn.microsoft.com/en-us/library/ms241613.aspx
The problem you will get if library is provided without pdb. If it is OSS dll you can compile it by yourself with pdb files. You will have to do it once.