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. |
15th December 2020, 00:06 | #1481 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
__________________
See My Avisynth Stuff |
|
22nd February 2021, 01:12 | #1482 | Link |
Registered User
Join Date: Jul 2003
Location: Italy
Posts: 1,135
|
I'm getting often "Access Violation" on HD clips with YV16 colorspace (the one I'm testing with, but haven't tried with other colorspaces or bitdepth) when calling TDecimate, and some other times I'm getting corrupted video with green horizontal/vertical stripes on the image (using AVS 3.7)
It doesn't happens always, but with a good amount. For example with this script: Code:
colorbars(width=1920,height=1080,pixel_type="yv16") assumefps("ntsc_video") assumetff() tfm(order=-1,slow=2,micmatching=3,PP=6,mode=3) tdecimate(mode=1,cycle=5) Last edited by mp3dom; 22nd February 2021 at 01:16. |
22nd February 2021, 03:16 | #1483 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,377
|
Quote:
avs+ x64 3.7 r3382 TIVTC v1.0.25 |
|
22nd February 2021, 05:03 | #1484 | Link |
Registered User
Join Date: Sep 2005
Posts: 130
|
Doesn't work for me either
PHP Code:
|
22nd February 2021, 09:30 | #1487 | Link |
Registered User
Join Date: Jul 2003
Location: Italy
Posts: 1,135
|
Well all I can say is that this happens to me on VDub2 and avsmeter too (but never tried avspmod or ffmpeg), the address changes every time so I think it's not useful (?)
On avsmeter, sometimes it doesn't complete the pre-pass process (exits without any warning to the command prompt) and some other times it show the access violation (and sometimes it completes the process as well). Can't find the rule behind this. I'm using the x86 version now, but looking at the posts below me, it seems this happens on x64 too... Last edited by mp3dom; 22nd February 2021 at 09:33. |
22nd February 2021, 09:54 | #1488 | Link |
Registered User
Join Date: Jan 2014
Posts: 2,314
|
Check v1.0.26
https://github.com/pinterf/TIVTC/releases |
27th February 2021, 23:10 | #1491 | Link |
Big Bit Savings Now !
Join Date: Feb 2007
Location: close to the wall
Posts: 1,545
|
Deepest respects for all that cleanup work across so many plugins, pinterf ! (again)
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain) "Data reduction ? Yep, Sir. We're that issue working on. Synce invntoin uf lingöage..." |
30th August 2021, 16:44 | #1493 | Link |
Registered User
Join Date: Aug 2016
Posts: 27
|
having an issue with TFM micmatching not apparently doing anything at all
I'm trying to process a DVD animation, and I keep getting bad matches which I can correct with overrides, but this is a very long and tedious process. I would rather find a way to get better matches automatically with debug=true I can see the mics for each frame, and various other info, in a debug console, and no matter what mode I set micmatching to, it makes no difference at all to the final match. if I disable it entirely, I get the exact same results as if I choose any of the micmatching settings. it apparently does nothing except slow the process down to calculate mics that arent used. also, the final match chosen invariably has a high mic value compared to other frames. the readme for TFM says for micmatching mode 1 "mics are only used to determine if of the 5 possible matches there is one match that has a significantly lower mic value than all of the other four matches" which suggests to me that lower mics are preferred for better matches. yet invariably when TFM chooses a bad match, the mic of the chosen bad match will be something like 58 and the mic of the good match that I override with will be about 11. I'm not entirely sure how this is supposed to work but as changing the micmatching setting doesn't even change anything in the output, I'm at a bit of a loss. any help understanding this would be appreciated! cheers using TFM 1.0.7 |
1st September 2021, 05:37 | #1495 | Link |
Registered User
Join Date: Jan 2015
Posts: 1,056
|
And I did. The question now is whether anyone wants to try the algorithm I suggested.
It's not difficult at all. The two are extremely dissimilar. Not when they produce crap results. Lots of things that are widely used are still crap. Windows 10, for example. No he isn't. Anyone who knows how to code AVIsynth plugins, you mean. I've tried learning C++ several times in my life. I've never gotten very far. As it turns out, there are some things that even I'm not autistic enough for.
__________________
I ask unusual questions but always give proper thanks to those who give correct and useful answers. |
1st September 2021, 05:52 | #1496 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
what about https://github.com/pinterf/TIVTC/issues/27 ?
__________________
See My Avisynth Stuff |
1st September 2021, 13:21 | #1498 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Dont give up so easily, I'm sure there is nothing that you are not autistic enough for.
__________________
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 ??? |
2nd September 2021, 13:33 | #1499 | Link | |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,904
|
Quote:
Katie, you think they're different 'cause you "see" them as being different, but a computer doesn't see, a computer works with numbers. The whole frame is divided in blocks and macroblocks of a certain size, they can be 4x4, 8x8, 16x16 etc. Each one goes through a transform which assigns a value to it. The next frame goes through the same process and values are assigned to each block. Those two frames are then compared by comparing the values of each individual block and, based on that, the algorithm tries to find out whether those blocks are the same or not. In theory, everything works out, but in practice it might not. You see, there can be tons of things that can go wrong in the motion vectors detection and it's far from easy to get this done perfectly in every scenario. If you think that the alternative would be specifying a pattern by hand and modify it over and over again when and if it changes like at commercial breaks etc by manually handling exceptions, suddenly you realize what an amazing job TDecimate is actually doing. Sure, it might not be perfect every time, but still a lot of effort has been put into it and I'm very glad that we have it. |
|
2nd September 2021, 18:56 | #1500 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,733
|
A truly autistic person would go through the videos frame by frame and create an override file for a 110% perfect result.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
Tags |
tdeint, tivtc |
Thread Tools | Search this Thread |
Display Modes | |
|
|