Could anyone plz compile 64 bit Yatta ?

[slayer2k]

https://github.com/myrsloik/yatta-ivtc/tree/master/yatta
https://github.com/myrsloik/yatta-ivtc/blob/master/yatta/compiled/changes.txt

I would really appreciate it

[StainlessS]

Delphi 7 (seems to be yatta compiled version) came out in 2002, maybe it dont have x64 option.
Current Delphi is v10.
Perhaps better if a Delphi coder converted to Free Pascal (which is supposed to be very similar to Delphi, and cross platform, Win/Mac/Linux),
Free Pascal can be used with Lazarus IDE.
I dont know Pascal/Delphi sorry. (I also dont have a clue about that there Github stuff, forking etc)
Delphi on Wikipedia:- https://en.wikipedia.org/w/index.php?search=Delphi+%28software&title=Special%3ASearch&fulltext=1&ns0=1

Yatta/Compiling.txt
Tested Delphi Versions:
Delphi XE7

Dependencies:
Graphics32 - http://www.graphics32.org/

EDIT:
Free Pascal:- https://en.wikipedia.org/wiki/Free_Pascal
Lazarus IDE:- https://en.wikipedia.org/w/index.php?search=Lazarus+%28software&title=Special%3ASearch&fulltext=1&ns0=1
Lazarus is a free cross-platform visual integrated development environment (IDE) for rapid application development (RAD) using the Free Pascal compiler. Its goal is to provide an easy-to-use development environment for programmers developing with the Object Pascal language, which is as close as possible to Delphi.

Cross-platform development
Interaction of class libraries and widgetsets in Lazarus and Free Pascal

Lazarus uses Free Pascal as its back-end compiler. Therefore, Lazarus can theoretically be used to develop applications for all platforms supported by Free Pascal.

Lazarus provides a cross-platform application framework called the Lazarus Component Library (LCL), which provides a single, unified interface for programmers, with different platform-specific implementations. Using LCL, it is possible to create applications in a write once, compile anywhere manner, unless system-dependent features are used explicitly.

Cross-compiling

As Free Pascal supports cross-compiling, Lazarus applications can be cross-compiled from Windows to Linux / macOS / etc. and vice versa.

Applications for embedded devices (smartphones, PDAs, routers, game consoles) can be cross-compiled from any desktop platform.

Differences from Delphi

While resembling Delphi in many ways, there are a few limitations regarding the performance and feature set, including:

Under Windows, the default size of an executable file is larger than the Delphi 6 or 7 equivalent, as Lazarus stores debug information within the executable, rather than as separate files. From 0.9.30 onwards, Lazarus supports external debug symbols; program file size can be significantly reduced (via compiler options) by using an external symbols file. Alternatively, debug info can be stripped from EXEs (e.g. using a port of the UNIX strip command).
Components for Delphi can be converted to work in Lazarus, which could be complex, but became less so since 0.9.30, based on FP 2.4.x.
Lack of Datasnap (not a publicly documented system, Embarcadero proprietary enterprise functionality).
Networking is mostly available.
No support to directly call .NET libraries. Object Pascal code can be called from .NET software.[2]
No support for dynamically loadable packages. # WOULD THIS EXCLUDE AVISYNTH
Not fully compatible with VCL. As mentioned previously, this is by design, although the LCL widget set should suffice for most applications. But this makes the deep repository of available VCL widgets inaccessible without conversion. The conversion effort mostly involves some editing, although there are a few fundamental differences. When porting, missing units in the libraries are a considerably bigger problem than incompatibilities between LCL and VCL.
Microsoft Office connectivity limited to popping up Microsoft Excel with a simple table filled out (since FPC 2.6.0).
Microsoft Component Object Model (COM) is supported (since Lazarus 2.2.0).

Examples of Delphi libraries compatible with Lazarus

GLScene is a free OpenGL-based library that provides visual components and objects allowing description and rendering of 3D scenes.
OpenWire is an open-source library that allows pin type properties to make connections between LCL components similar to LabVIEW or Agilent VEE.

Examples of applications produced with Lazarus

ASuite is a free open-source application launcher for Windows. From 2.1 Alpha 1, it's fully written in Lazarus/FPC.
Beyond Compare is a data comparison utility for Windows, macOS, and Linux. The macOS and Linux versions are compiled using Lazarus/FPC.
Cartes du Ciel is a free planetarium program for Linux, macOS and Windows. The software maps out and labels most of the constellations, planets, and objects you can see with a telescope. It is fully written in Lazarus/FPC and released under GPL.
C-evo is an open source turn-based strategy game that has been ported from Delphi to Lazarus.[8]
Cheat Engine is an open-source memory scanner/hex editor/debugger. It is useful for cheating in computer games. Since version 6.0 it is compiled with Lazarus/FPC.
EPANET, a software package for modelling water-distribution systems.
HNSKY, aka Hallo Northern Sky is a free planetarium program for Windows and Linux. Since version 3.4.0 written and compiled with Lazarus/FPC.
MyNotex is a free software for Linux useful to take and manage textual notes.
PeaZip is an open-source archiver, made with Lazarus/FPC.
TorChat is moving away from Python and is being rewritten in Lazarus + Free Pascal.
Total Commander 64-bit version.[9]
Double Commander is a cross-platform open-source file manager with two panels side by side. It is inspired by Total Commander, plus some new ideas.[10]
CudaText is a cross-platform open-source text editor.
Coedit (renamed to Dexed) is an IDE for the D programming language.
SimThyr is a continuous simulation program for thyroid homeostasis.
Tomboy-ng, the currently active manifestation of Tomboy.
Tranzistow [11] is a 32/64-bit software synthesizer for Windows and Linux developed with FreePascal/Lazarus.
Simba [12] is a automation program that facilitates the automation and repetition of certain programmable complicated tasks.
CudaText has Syntax hi-lighting for 200+ languages, including Avisynth script.

[VoodooFX]

I don't know much about compiling, I see Visual Studio files in repo, isn't it ready to be compiled with Visual Studio?

# Visual Studio Version 17
VisualStudioVersion = 17.2.32516.85
MinimumVisualStudioVersion = 10.0.40219.1

[kedautinh12]

Yes, it's can from visual studio 10 to 17

[Reel.Deel]

I don't know much about compiling, I see Visual Studio files in repo, isn't it ready to be compiled with Visual Studio?

# Visual Studio Version 17
VisualStudioVersion = 17.2.32516.85
MinimumVisualStudioVersion = 10.0.40219.1

In the compiling.txt file it says this:
Tested Delphi Versions:
Delphi XE7

Dependencies:
Graphics32 - http://www.graphics32.org/

And in an an older repo (https://github.com/hatt/Yatta) it said this:
Compiling YATTA
Supported Delphi Versions:
Compiling YATTA should work in Delphi 7 and later (2005, 2006, TurboExplorer and 2007) with all the different patching levels.
Delphi 6 may also be possible to use but it hasn't been tried recently. Earlier versions are guaranteed to fail due to missing compiler directives.

[StainlessS]

OmniPascal & FreePascal can apparently be added as VisualStudioCode extension.
https://www.google.co.uk/search?q=visual+studio+pascal&ei=j2xyY__lIIHD8gLEpbeIDw&ved=0ahUKEwi_6YTIi677AhWBoVwKHcTSDfEQ4dUDCA4&uact=5&oq=visual+studio+pascl&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzIECAAQRzIECAAQRzIECAAQRzIECAAQRzIECAAQRzIECAAQRzIECAAQRzIECAAQR0oECE0YAUoECEEYAEoFCEASATFKBAhGGABQAFgAYJ0FaABwAngAgAEAiAEAkgEAmAEAyAEIwAEB&sclient=gws-wiz-serp

Some VisualStudio / Pascal videos:- https://www.youtube.com/results?search_query=visual+studio+pascal

[gispos]

I have created the exe files. But it can't work with Avisynth.

Take a look at the Asif.pas, is unknown to me, a mixture of Avisynth and ? Is there an asif.dll ?

https://github.com/hatt/Yatta/blob/master/Asif.pas

PS:
My mistake, Dll found, but is written in C++. Now someone with C knowledge should do it :)

[Reel.Deel]

Here's the x64 dll: https://files.videohelp.com/u/223002/Asif.dll

Idk if it works, said it required v143 but changed it to 2019 v142 and compiled.

[slayer2k]

Gispos, plz share the exe files

[gispos]

Is confusing for me now, I had loaded the source from myrsloik, there is no asif.dll there either.

Which source is meant now? Or both the same?

https://github.com/hatt/Yatta
https://github.com/myrsloik/yatta-ivtc

I have created the exe files from the myrsloik source and also get with the 32bit access violations.

[Reel.Deel]

myrsloik's repo is the latest and the official one.

[gispos]

Compiled again, the Yatta.exe x64 seems to work, with the 32bit I get access violations in the ntdll.dll, but the program still starts.

With the ymc.exe the minhook.dll is missing.

https://www.mediafire.com/file/msxtt5yd6gn4ypw/Yatta_Ymc_compiled.7z/file

[slayer2k]

64 bit version works now, heres 64 bit fieldhint
https://www.mediafire.com/file/e4cdbdy10engvew/fieldhint.dll/file

[gispos]

64 bit version works now, heres 64 bit fieldhint
https://www.mediafire.com/file/e4cdbdy10engvew/fieldhint.dll/file
I've played around with it a bit, but I can't figure it out. What do you do with Yatta?

[Reel.Deel]

I've played around with it a bit, but I can't figure it out. What do you do with Yatta?

The Yatta Manifesto: http://task-force.lacumpa.biz/yatta.txt

TLDR; a tool that speeds up the process of manual IVTC.

Edit
This is an informational thread on YATTA: https://forum.doom9.org/showthread.php?t=64440

[slayer2k]

https://www.mediafire.com/file/ze9vk55pbcz375l/MinHook.dll/file

minhook.dll 64 bit

[gispos]

https://www.mediafire.com/file/e4cdbdy10engvew/fieldhint.dll/file

minhook.dll 64 bit
the fieldhint.dll again ;)

[slayer2k]

Stupid typo, i have fixed the link

[slayer2k]

Now , if anyone could compile this last one for 64 bit, we're all set

https://github.com/myrsloik/yatta-ivtc/tree/master/scxvid

[slayer2k]

Alright, here it is :-)
https://www.mediafire.com/file/wb3fybpazjwp7p0/scxvid.dll/file

[kedautinh12]

minhook i findout in here but don't know if it's same minhook.dll from slayer2k
https://github.com/TsudaKageyu/minhook/releases

[slayer2k]

It's the same

[Kogarou]

I wanted to post this yesterday but I also wanted to make sure it would be OK to do so. Here is YATTA x64 compiled by Myrsloik.
New features:
- Linked against AVS+ 3.7.2 instead of AVS 2.5.8
- 64-bit build instead of 32-bit
- Has "a working YMC"
yatta-x64-test2.7z (https://kogarou.s-ul.eu/JUKaQt72.7z)
Please note that YATTA is not exactly bug-free: It is definitely much, much more usable than dealing with an ever-more geriatric AVS. I IVTCed an entire anime episode with it just fine, but there are things that do not work well nowadays (did they ever?), like FieldHint not using AVS+ frameprops. In a better world Myrsloik would've had time to update FieldHint, but such is life.
P.s.: Please do not ask me or Myrsloik about how it works, I can't help you much and Myrsloik is currently too busy with life, read the .txt file and figure it out yourself.

[slayer2k]

thx mate

[mirkosp]

I can't tell if I'm doing something wrong, but it seems that YMC stops indexing metrics after roughly 80% of the video has been indexed. I've been trying to make multiple files with different trims to eventually have the whole video, but that roughly 80% mark still seems to apply regardless of the length of the video.
I can probably circumvent this by adding another 20-25% of blankclip at the end just to be on the safe side of the rounding, but if it can be fixed somewhere in the code itself rather than with workarounds I'd appreciate it.

For context, I only collect Telecide -> Decimate when the pattern changes are only in specific parts of the video, otherwise I collect Telecide -> SCXvid -> Decimate. I don't use YMC's cutter, so if there's a bug in the code, I doubt it's there.

Thanks in advance if anybody can solve this!

PS: I've also had a friend of mine write a simple external tool that converts fieldhint overrides to TFM overrides, so that I don't have fieldhint's limits after I'm done in Yatta, but it's a bit barebone as it stands, and as per my request to my friend it currently ignores the postprocessing hints entirely, as I prefer to postprocess through custom lists or sections in order to specify which field gets used in which way case by case, but let me know if anybody else would find this useful.