[BUG] File doesn't encode properly, video cuts off before it's finished

[Dyshonest]

Here is the file I am trying to encode: https://drive.google.com/file/d/1jOa-pGu...sp=sharing

Here are my x265 settings:

https://i.imgur.com/h8U3ACK.png

https://i.imgur.com/p4yOFsE.png

No cropping.

Here's my Vapoursynth settings:

None for deinterlacing/telecining, or for versions without the "none" option: https://i.imgur.com/kjqgZGp.png (this was taken in 2024.7.29.1)

https://i.imgur.com/BC24VJx.png

https://i.imgur.com/Tm80LwS.png

Here's what comes out: https://drive.google.com/file/d/1MCD9rhd...sp=sharing

See how it cuts out early? It seems to be tied to the GrainFactory3 option, as I did three encodes, one without Xsynth, one without RGBAdjust, and one without GrainFactory3, and the first two did not cut out early.

I've tried 2024.5.11.1, and I've tried 2024.6.16.1, it's bugging out on both. Didn't try 2024.7.29.1 yet, doing that now, but I'm sure it'll bug out too. As far as I can tell the video file I am putting in is fine? I'm not sure what would even be wrong with it.

[Selur]

Here's what comes out: https://drive.google.com/file/d/1dPI8hJo...sp=sharing

Links to an mpg file and Hybrid doesn't output mpg, so no clue what you are really doing.

read: [INFO] Infos needed to fix&reproduce bugs,..
provide a debug output using the latest version (I don't support old version) and I can look at it after work this evening.

Cu Selur

[Dyshonest]

Here's what comes out: https://drive.google.com/file/d/1dPI8hJo...sp=sharing

Links to an mpg file and Hybrid doesn't output mpg, so no clue what you are really doing.

read: [INFO] Infos needed to fix&reproduce bugs,..
provide a debug output using the latest version (I don't support old version) and I can look at it after work this evening.

Cu Selur

That was the wrong link for the Hybrid output and from a previous thread, so sorry. Here's the proper one: https://drive.google.com/file/d/1MCD9rhd...sp=sharing

If you click "Create Debug File" during the encode, will it still be made? Or do I have to restart the encode?

---

Well I just finished an encode on the 2024.07.29.1 one, and it went through fine, no cutting out early. Too bad I have zero idea if it's being deinterlaced/telecined again since there's absolutely no indicator anywhere on Hybrid.

If this (https://i.imgur.com/TXpongi.png) is really the same behavior as none, getting rid of none was still profoundly bad, because it isn't obvious at all that it's the same as none. To the user, it's still applying a deinterlace/telecine, since it isn't being told not to. There's no indicator from Hybrid to ignore it because it's progressive, the UI indicates "it's flagged as progressive, but do this anyway".

It's a UI nightmare no matter how you look at it. I have absolutely no idea why the option was removed, there is no benefit and too much doubt or confusion.

[Selur]

If you click "Create Debug File" during the encode, will it still be made? Or do I have to restart the encode?

Debug Output starts when 'Create Debug File' is enabled and is placed inside the output folder, which is why a output folder needs to be known.

Too bad I have zero idea if it's being deinterlaced/telecined again since there's absolutely no indicator anywhere on Hybrid.

Aside from looking in the generated script, there never was an indicator that showed whether deinterlacing was done or not.
Using the latest dev, you can enable 'Create Report file' and you can see the Vapoursynth/Avisynth used.

There's no indicator from Hybrid to ignore it because it's progressive, the UI indicates "it's flagged as progressive, but do this anyway".

If you want progressive content to get deinterlaced, you need to tell Hybrid that it is not progressive but interlaced by overwriting the scan type,...

I have absolutely no idea why the option was removed, there is no benefit and too much doubt or confusion.

If you have no idea, you clearly lost your memory about what I wrote in your other thread.

It's a UI nightmare no matter how you look at it.

If you don't like the UI, don't use it.
It's as simple as that.


Cu Selur

[Dyshonest]

If you click "Create Debug File" during the encode, will it still be made? Or do I have to restart the encode?

Debug Output starts when 'Create Debug File' is enabled and is placed inside the output folder, which is why a output folder needs to be known.

Too bad I have zero idea if it's being deinterlaced/telecined again since there's absolutely no indicator anywhere on Hybrid.

Aside from looking in the generated script, there never was an indicator that showed whether deinterlacing was done or not.
Using the latest dev, you can enable 'Create Report file' and you can see the Vapoursynth/Avisynth used.

There's no indicator from Hybrid to ignore it because it's progressive, the UI indicates "it's flagged as progressive, but do this anyway".

If you want progressive content to get deinterlaced, you need to tell Hybrid that it is not progressive but interlaced by overwriting the scan type,...

I have absolutely no idea why the option was removed, there is no benefit and too much doubt or confusion.

If you have no idea, you clearly lost your memory about what I wrote in your other thread.

It's a UI nightmare no matter how you look at it.

If you don't like the UI, don't use it.
It's as simple as that.


Cu Selur

And if you have progressive content that you do NOT want deinterlaced? What do you do? You avoided that question entirely.

"If you don't like the massively upended UI that no one has reported positively on, do not use it" is a weird flex. You're a software developer who uploaded their work publicly, presumably you're developing software for people to use, not just for personal use. So far no one's commented positively on the change but it's caused a lot of confusion and negativity.

You entirely upended a crucial function of the software with no explanation why or how it's supposed to work going forward.

[Selur]

And if you have progressive content that you do NOT want deinterlaced? What do you do? You avoided that question entirely.

Deinterlacing&Co only applied if the source is not progressive.
So the setting under 'Auto deinterlace handling' is not used if your source is progressive.
What is unclear about the tool-tip of that function to you?

Deinterlace handling:
Sets what method will be used to deal with non-progressive content, assuming the output isn't marked as interlaced in the encoder.
Hybrid does only deinterlace if:
a. the source is non-progressive
b. the output is not interlaced
So:
- If your source is flagged as interlaced, but in reality is progressive: overwrite the scan type.
- If your source is flagged progressive, but in reality interlaced: overwrite the scan type.
- If your source is progressive and properly flagged, do not worry Hybrid will not try to deinterlace the source.

You entirely upended a crucial function of the software with no explanation why or how it's supposed to work going forward.

No, clue what makes that selection to the 'Auto deinterlace handling' crucial in your eyes.

You're a software developer who uploaded their work publicly, presumably you're developing software for people to use, not just for personal use.

Now that you mention it, https://www.selur.de/licence clearly states:
Hybrid itself is free for personal usage without a hassle.

Hybrid is provided "as is", without any guarantee made as to its suitability or fitness for any particular use. It may contain bugs, so the use of this tool is at your own risk. The author takes no responsibility for any damage that may unintentionally be caused through its use. You may not distribute Hybrid in any form without written permission of the author.

So far no one's commented positively on the change but it's caused a lot of confusion and negativity.

Seems, to me, like that change only caused 'a lot of confusion and negativity' to you.

"If you don't like the massively upended UI that no one has reported positively on, do not use it" is a weird flex.

'massively upended UI ' counting the removal of a single option in a drop-down menu massive seem like an overstatement.
So you expect me to change the UI however a single 'confused and aggressive' user wants it to change?
Suggesting such a user, to use another software seems to be the sensible way. (I may be wrong there.)

Cu Selur

Ps.: Just a thought, maybe hiding the whole Deinterlacing setting whenever a source that isn't marked as interlaced is loading could help confused users.

[Dyshonest]

And if you have progressive content that you do NOT want deinterlaced? What do you do? You avoided that question entirely.

Deinterlacing&Co only applied if the source is not progressive.
So the setting under 'Auto deinterlace handling' is not used if your source is progressive.
What is unclear about the tool-tip of that function to you?

Deinterlace handling:
Sets what method will be used to deal with non-progressive content, assuming the output isn't marked as interlaced in the encoder.
Hybrid does only deinterlace if:
a. the source is non-progressive
b. the output is not interlaced
So:
- If your source is flagged as interlaced, but in reality is progressive: overwrite the scan type.
- If your source is flagged progressive, but in reality interlaced: overwrite the scan type.
- If your source is progressive and properly flagged, do not worry Hybrid will not try to deinterlace the source.

You entirely upended a crucial function of the software with no explanation why or how it's supposed to work going forward.

No, clue what makes that selection to the  'Auto deinterlace handling' crucial in your eyes.

You're a software developer who uploaded their work publicly, presumably you're developing software for people to use, not just for personal use.

Now that you mention it, https://www.selur.de/licence clearly states:
Hybrid itself is free for personal usage without a hassle.

Hybrid is provided "as is", without any guarantee made as to its suitability or fitness for any particular use. It may contain bugs, so the use of this tool is at your own risk. The author takes no responsibility for any damage that may unintentionally be caused through its use. You may not distribute Hybrid in any form without written permission of the author.

So far no one's commented positively on the change but it's caused a lot of confusion and negativity.

Seems, to me, like that change only caused 'a lot of confusion and negativity' to you.

"If you don't like the massively upended UI that no one has reported positively on, do not use it" is a weird flex.

'massively upended UI ' counting the removal of a single option in a drop-down menu massive seem like an overstatement.
So you expect me to change the UI however a single 'confused and aggressive' user wants it to change?
Suggesting such a user, to use another software seems to be the sensible way. (I may be wrong there.)

Cu Selur

Ps.: Just a thought, maybe hiding the whole Deinterlacing setting whenever a source that isn't marked as interlaced is loading could help confused users.

Yes, it is a massive upending, since a video is fundamentally destroyed if it's deinterlaced when it doesn't need it, and there's absolutely no indicator if Hybrid is actually doing it or not because we can't select "none", and there's zero indicators on the screen that it is or isn't doing it. You can't say "but some random thing is greyed out", if it's not doing it, why can I select settings for the deinterlacer it's supposedly "not using"? Nothing about it makes a lick of visual sense, it makes sense to you because you made the program.

https://i.imgur.com/8B77GqF.png

There is no visual indicator there that Hybrid is NOT deinterlacing the project. There's ample evidence that it is, however.
I did two encodes of the file, one with "overwrite input type as progressive" checked and one with the box empty. There was a 3MB difference---which is far too big for variance (encoding the same file many times may see some variance but not that big) if it truly was not doing anything. The bigger one was the one with it checked. So... what is it doing? Which one is it NOT deinterlacing? Or is it doing it for both?

I'm also far from the only person who's complained about this.

https://forum.selur.net/thread-3792-post...l#pid23451

There's one such example.
It's also a bit silly to say I'm "asking you to upend the software" by... readding a basic feature that shouldn't have ever been taken away in the first place? If you took away the ability to save a file as .mkv (but not tell the user until the file is made) and made it where we needed to minimize it five times then drag it to the corner to have it save as a .mkv, is it "asking you to upend the software" to take that nonsense away and just add the .mp4/.mkv drop-down back?

It would help to hide the deinterlacing menu if it's not needed, you are right. That would actually tell the user it is not being deinterlaced.

[Bartoloni]

checked and one with the box empty. There was a 3MB difference---which is far too big for variance

umhh

[Selur]

There was a 3MB difference---which is far too big for variance (encoding the same file many times may see some variance but not that big) if it truly was not doing anything.

No debug output files, to verify what you did.
No reliable data, user must be confused or negatively impacted by the GUI.

To appease all those users to which the removal of 'none' 'caused a lot of confusion and negativity', Hybrid will now simply hide the deinterlacing controls unless:

• no source is set
  
• multiple sources (batch input) is used
  
• the input is not progressive
  

So that even if one can't read or understand the tool-tip, one should not get confused by the deinterlacing handling settings.

Cu Selur

Ps.: updated the dev download in the 'experimental'-folder.