This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Another weird bug
#1
Was running things in passthrough to get rid of the commentary tracks and came across another weird one where it ignores changes after the first job of a batch queued up?

To repeat it on my system:
Cut down sample to only have the video & audio + comments [attachment=1500]
then make a few copies of the file
   
remove the comment tracks
   
As can be seen with the filesizes, only the first job in the queue (Monogatari.mkv) removed did anything (Monogatari_new.mkv)
   

I haven't got a clue about this one.
Reply
#2
What? I don't get at all what I could do to reproduce the issue, since I don't get what the issue is.
Screenshots do not help at all.
Wild gues is that you did use 'Base->Processing->Audio->auto add (all)', then adjusted the audio queue without changing 'Base->Processing->Audio' to custom and Hybrid changed the audio queue afterwards,...
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
(13.08.2021, 04:42)Selur Wrote: Wild guess is that you did use 'Base->Processing->Audio->auto add (all)', then adjusted the audio queue without changing 'Base->Processing->Audio' to custom and Hybrid changed the audio queue afterwards,...

Close, I think? after reading the mouse-overs I think I see the issue...

I'd always ASSumed that the base-> audio dropdown was just how Hybrid handled populating the audio job list when it was fed input file(s) and that was as far as it went.

It would make a lot more sense if this was how it operated...

This situation where "auto add" only applies changes to the first job file then silently ignores any other changes to the audio queue of any following jobs is inconsistent and unintuitive, having to change the base->audio tab to custom to get the edits to the audio job queue to stick is also convoluted.
Reply
#4
The processing 'audio' setting is mainly for the job creation. Big Grin
If Hybrid would not support 2pass encoding and tagging population the audio queue wouldn't be necessary. Smile

Quote:It would make a lot more sense if this was how it operated...
I will think about removing the audio-tab unless:
a. no input is set
or
b. audio processing is set to 'custom'
may be that will make it more sense.


Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
(13.08.2021, 13:13)Selur Wrote: The processing 'audio' setting is mainly for the job creation.  Big Grin
If Hybrid would not support 2pass encoding and tagging population the audio queue wouldn't be necessary. Smile

Quote:It would make a lot more sense if this was how it operated...
I will think about removing the audio-tab unless:
a. no input is set
or
b. audio processing is set to 'custom'
may be that will make it more sense.

Hmmm.

a. Is logical only for the "ignore" option as Config -> Automation works on all other audio options and it would make sense to show the working audio queue (including for passthrough).

b. is it possible to automatically change the Base -> Audio option to "custom" if the "add current" or "remove current" button is clicked? that would bypass most of the issues...
Reply
#6
Quote:b. is it possible to automatically change the Base -> Audio option to "custom" if the "add current" or "remove current" button is clicked? that would bypass most of the issues...
Yes, that's would be possible.
I would probably add an option for this under "Config->Internals->Handling" to activate this, but that would be pretty easy to implement.

Quote: Is logical only for the "ignore" option as Config -> Automation works on all other audio options and it would make sense to show the working audio queue (including for passthrough).
Note that DVD and Blu-ray input behave differently then batch encoding. Wink

-> I'll think about it, but this probably will have to wait till I fixed a few bugs.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#7
(13.08.2021, 16:18)Selur Wrote:
Quote:Is logical only for the "ignore" option as Config -> Automation works on all other audio options and it would make sense to show the working audio queue (including for passthrough).
Note that DVD and Blu-ray input behave differently then batch encoding. Wink

Didn't think you could do multiple DVD/BD anyway and thought the checkbox tells hybrid to look for an IFO/whatever the BD playlist file is called?

Quote:-> I'll think about it, but this probably will have to wait till I fixed a few bugs.

Talking about Automation reminded me of a sort of bug, probably not worth fixing:

If you select audio encoding and have set the bitrate below 192, Hybrid on the detection of a multichannel track it will reset the bitrate of all tracks to 192, which is usually acceptable, the problem is that it will do this even if automation removes all multichannel tracks (via language selection).

I've just been running batches in passthru to get rid of other languages to bypass this. (Cant figure out WTF fansubbers will pair a dodgy 5.1 dub with a 2ch original language...)
Reply
#8
Quote:Didn't think you could do multiple DVD/BD anyway and thought the checkbox tells hybrid to look for an IFO/whatever the BD playlist file is called?
You can't but the processing of those DVD and BD which multiple title is way different. Smile

Quote:If you select audio encoding and have set the bitrate below 192, Hybrid on the detection of a multichannel track it will reset the bitrate of all tracks to 192, which is usually acceptable, the problem is that it will do this even if automation removes all multichannel tracks (via language selection).
would need two short samples and some details to reproduce and may be find a workaround for this.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#9
Just did a few tests: only does it for DTS / Opus / eac3 for encoding bitrates set below 670 / 192 / 256 
Here's a sample
[attachment=1504]
5.1 Engrish / 2.0 Japanese.

Just set Config -> Automation -> "limit audio passthrough" to Japanese, encode one of these codecs to under the above value, drop the file into Hybrid and check the audio queue.
Reply
#10
So this should show the problem, right?
  • start Hybrid
  • enable "Config->Automation->Passthrough streams->Limit audio passthrough/auto add all"
  • enable "Config->Automation->Passthrough streams->Limit audio passthrough/auto add all->Japanese"
  • set "Base->Processing->Audio" to "auto add (all)"
  • enable "Audio->Base->Audio Encoding Options"
  • set ""Audio->Base->Audio Encoding Options->Encoder" to "Opus"
  • set ""Audio->Base->Audio Encoding Options->Encoder->VBR mode:" "to 128", right?
funny thing is I can't set a bit rate below '192' for opus since Hybrid assumes the default channel count is 6. Smile

So what I did it load a stereo source and set the bit rate to 128 and then loaded the file and both the audio streams was added with a bit rate of '192'.
-> I'll look into it. Smile

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)