AC3 to AC3 → ffmpeg crash

[ToiletDuck]

No profiles, are not freely interchangeable.

1. You can't use profiles from newer Hybrid version in older Hybrid versions.
   
2. Sometimes I mention that Hybrid that configs should be reset&co. So if you have a profile from a version and you change to a newer version and between those versions larger model changes did happen, you can not use the models. Some changes require recreation of models.
   
3. Since older models lack, newer options you always should: load an old model, make sure it still sets all the settings it should set, save the model anew and restart Hybrid.
   
4. You should always read the change log, since some times the effect of options might change. Sometimes options get split, removed etc.
   

Cu Selur

I get that selur.

I do talk about the basic stuff..  Not complex settings like models/settings of certain filters, that often breaks too once loaded in newer version of hybrid.  
And i do talk about profiles created and dragged from Old to → New hybrid releases.. that breaks compatibility, and for very basic stuff too.. in my case.

AC3 encode comes to mind.. i mean , why would that suddenly crash, when the very same settings are used..  

I mean, i can understand that some fine tuned settings from an old profile can differ from the new settings that are implemented in updated toolsets that comes with a new release of hybrid.. i.e: other cmd lines, new settings.. etc...

But iam talking about simple audio encode here , that did crashed..

cheers,
td

[Selur]

But iam talking about simple audio encode here , that did crashed..

I must have missed something, that made audio processing simple.
Whenever a new feature gets added in regard to audio processing, potentially the whole code for it gets/needs to be rewritten.
Same as for anything else.

AC3 encode comes to mind.. i mean , why would that suddenly crash, when the very same settings are used..

Different/Updated tools and features require a rewrite of sometimes huge code parts, which can always cause problems.

Cu Selur

[ToiletDuck]

But iam talking about simple audio encode here , that did crashed..

I must have missed something, that made audio processing simple.
Whenever a new feature gets added in regard to audio processing, potentially the whole code for it gets/needs to be rewritten.
Same as for anything else.

AC3 encode comes to mind.. i mean , why would that suddenly crash, when the very same settings are used.. 

Different/Updated tools and features require a rewrite of sometimes huge code parts, which can always cause problems.

Cu Selur

First, iam talking from a User point of view. Not developer... 

Are audio tools specific alway's updated with each hybrid release ?
Anyway, don't you list those ↑ changes in your release logs ? 

That ↑ would help diagnosing crashes or other issue's that occur suddenly for me as user..


cheers,
TD

[Selur]

Are audio tools specific alway's updated with each hybrid release ?

Yes, normally all tools get updated for a release. I do some small tests and if no problems occur I use them.

Anyway, don't you list those ↑ changes in your release logs ?

I try to. But changing for example (e-)ac3 might just be listed as 'audio: eac3 handling' and might under the hood include tons of changes which ideally didn't break anything. When I get proper feedback from users that used the dev versions those changes got a wider test, but sometimes users just write 'I assume it works' and that's it until they complain again months later.

That ↑ would help diagnosing crashes or other issue's that ocure suddenly for me as user..

No, it would not, since listing every small change that happened would not understandable without knowing and understanding the source code.
If a user, didn't even look at the debug output and understand what is written there, those changes would just cause more problems.
A user should not diagnose a problem, but properly report the problem. Ideally minimizing the scope of the problem, but not providing details and always waiting for me to kind of beg for them, just annoys me and hinders any progress.


Cu Selur

[ToiletDuck]

That ↑ would help diagnosing crashes or other issue's that ocure suddenly for me as user..

No, it would not, since listing every small change that happened would not understandable without knowing and understanding the source code.
If a user, didn't even look at the debug output and understand what is written there, those changes would just cause more problems.
A user should not diagnose a problem, but properly report the problem. Ideally minimizing the scope of the problem, but not providing details and always waiting for me to kind of beg for them, just annoys me and hinders any progress.


Cu Selur

By that i mean, it would help the user what setting to look for that causes the issue since update .. 

Ofcourse, details about the source is of no use.. iam talking about changes that affects the usage of any tool could be helpfull to users  ...
How else, can we know what affects what and why...

Lets not forget, users are essentially testers that help improve a piece of software ..
and therefor we need to need some specifics , right.


cheers,
Td

[Selur]

iam talking about changes that affects the usage of any tool could be helpfull to users ...

Sure, if you can tell me how to identify any change that could influence xy and somehow extend my free time to do any needed analysis etc.
If I knew for sure that for example the adjustment could break xy I would have tested for it, but even then I might miss some usage example that could trigger it or might trigger one bug that triggers another, etc. Also sometimes stuff gets only triggered for somehow broken content. For example, the delaycut thing might get triggered if the analysis reported some issues and some specific container and format combinations get triggered. Testing all this would take months.

Cu Selur

[ToiletDuck]

iam talking about changes that affects the usage of any tool could be helpfull to users  ...

Sure, if you can tell me how to identify any change that could influence xy and somehow extend my free time to do any needed analysis etc.
If I knew for sure that for example the adjustment could break xy I would have tested for it, but even then I might miss some usage example that could trigger it or might trigger one bug that triggers another, etc. Also sometimes stuff gets only triggered for somehow broken content. For example, the delaycut thing might get triggered if the analysis reported some issues and some specific container and format combinations get triggered. Testing all this would take months.

Cu Selur

Iam not talking about all that .. Sure when we talk about bugs, it can go in all sort of directions.. 


No simply put, list the tools that have been updated..with each new hybrid release.  
What about that 


cheers,
td

[Selur]

How about you compare the files of two releases?

[ToiletDuck]

How about you compare the files of two releases?

The physical files... actually .. ° ^ ° ?

C'mon now, are you kidding diz duck..  
One but significant txt file is much easier & faster for me to check then digging into my system everytime.. 

Now now, you tend to forget to be an Highness now... My "Royal" Sir Selur 

[Selur]

You could trigger: "Config->Tools->Tool Versions" on both releases and compare the output.

---------------------------
Info
---------------------------
Known tool versions:
  16bit-x265: 1.6+360-bca33880585a
  aomenc: 3.8.0-131-g77657197c7 (default)
  avs2yuv: 0.24bm6
  avs2yuv64: 0.28
  AVSMeter: 3.0.9.0
  AVSMeter64: 3.0.9.0
  bdsup2sub++: 1.03
  dcaenc: Unknown
  delaycut: 1.439
  DivX265: 1.5.0.8
  faac: 1.30
  fdkaac: 1.0.5
  ffmpeg: N-112974-gd324415563-g5256b2fbe6+2
  ffmpeg_32: N-112879-g444806f211-gd0ec826077+1
  FFVideotoolbox: no version info
  fhgaacenc: 20120806
  flac: c - Command-line FLAC encoder/decoder version git-72787c3f 20231124
  flaccl: 2.2.3
  FLVExtractCL: 1.6.2
  kvazaar: 2.2.0-15-g0d6651bf 2023-12-13
  lame: 3.100
  lsdvd: no version info
  MediaInfo: 23.11
  mencoder: 38359
  mencoder_32: 38359
  mkvextract: 81.0
  mkvinfo: 81.0
  mkvmerge: 81.0
  MP4Box: 2.3-DEV-rev696-gf8a41b2ae-ab-suite
  mp4fpsmod: 0.26
  mplayer: 38359
  mplayer_32: 38359
  mpv: no version info
  mpv_32: no version info
  neroAacEnc: 1.5.4.0
  NVEnc: 7.4
  NVEnc (FFmpeg): no version info
  oggenc: 1.4.2
  opusenc: 0.2-34-g98f3ddc
  qaac: 2.79
  QSVEnc: 7.57
  rav1e: AV1 video encoder
  sox: 14.4.2
  SVT-HEVC: 1.5.1
  telxcc: 2.6.0
  tsMuxeR: 3.1
  VCEEnc: 1
  vpxenc: 1.13.1-599-gdf655cf4f
  vspipe: R65
  vStripFree: 0.8e
  wine: no version info
  x264: 3172
  x265: 3.5+113-3fa1946b3
---------------------------
OK  
---------------------------