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. |
30th September 2018, 23:47 | #102 | Link |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 2,883
|
FFMS2 C-plugin r1315+119
I get an error "Unhandled C++ exception" if I try to open a .thd audio file. It's a TrueHD Dolby Atmos 7.1 audio file of about 4.7 GB. FFAudioSource starts indexing, it reaches about 512 MB of RAM and then it crashes. Can you try to index a similar TrueHD Dolby Atmos 7.1 audio file and reproduce the issue? It happens on the old ffms2 version as well (I can't test ffms2000 with XP). If you want I can upload the file. MediaInfo Audio Format : MLP FBA 16-ch Format/Info : Meridian Lossless Packing FBA with 16-channel presentation Commercial name : Dolby TrueHD with Dolby Atmos Codec ID : A_TRUEHD Duration : 2 h 29 min Bit rate mode : Variable Bit rate : 4 534 kb/s Maximum bit rate : 6 930 kb/s Channel(s) : 8 channels Channel layout : L R C LFE Ls Rs Lb Rb Sampling rate : 48.0 kHz Frame rate : 1 200.000 FPS (40 SPF) Compression mode : Lossless Stream size : 4.73 GiB (9%) Title : TrueHD Atmos 7.1 Language : English Default : Yes Forced : No Number of dynamic objects : 13 Bed channel count : 1 channel Bed channel configuration : LFE Last edited by FranceBB; 30th September 2018 at 23:49. |
24th October 2018, 18:51 | #103 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
I've added it to the first post, but I finally opted to enable the issues tracker on my personal FFMS2 repo on Github to track C plugin-related issues:
https://github.com/qyot27/ffms2_cplugin/issues |
23rd January 2019, 19:34 | #106 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
+ 1 on that, thanx muchly.
__________________
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 ??? |
24th January 2019, 03:47 | #107 | Link |
Registered User
Join Date: Jul 2018
Posts: 447
|
Thanks.
I compared the latest c-plugin version you posted vs ffms2 (non c-plugin) with QTGMC(sharpness=*) in AvsPmod. C-plugin eats ~4.4GB RAM while the othe build eats ~1.3GB RAM. * - when values from 0.1 to 1.6 are tested C-plugin continues to eat RAM for every new tested option until there is no free RAM. The non c-plugin doesn't have this behavior. I had crashes with c-plugin while using non c-plugin runs without problems in the same scenario. Can take a look for fix/solution? |
24th January 2019, 04:00 | #108 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
__________________
Groucho's Avisynth Stuff |
|
24th January 2019, 05:11 | #109 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
The problem lies with the client program re-loading the script over and over again without necessarily releasing the AviSynth script environment completely, which also unloads the C-plugin and flushes the memory. It's been an 'issue'* for years and trying to drill down to exactly where it lies is maddening.
*I mean, not for users of programs like x264 or FFmpeg, since those only load and unload the script environment once per program instance. VirtualDub can exhibit it eventually if you open the script and then repeatedly hit F2. Every time, it tacks an additional 70MB onto VirtualDub's memory allocation. |
14th March 2019, 05:33 | #110 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
A forum member at VideoHelp uploaded this 12-bit HEVC sample which causes problems with the current ffms2 C_Plugins:
https://forum.videohelp.com/attachme...test_12bit.mp4 The latest C-Plugin version which can handle this file is FFMS2 C-plugin 1140+101 from 2016. All later versions either cannot find the function "ffaudiosource", or they quit with an access violation. Repacking the file from MP4 to MKV does not help either. The file itself looks healthy, plays fine in all my media players, and MKVToolNix does not complain when remuxing it to MKV. Any thoughts? I always thought that the C-Plugin v.1140 is the most reliable one and I always use it, but it feels weird to me that for decoding a "modern" 12-bit source the old version handles it gracefully while all the newer version fail. Cheers manolito |
14th March 2019, 07:20 | #112 | Link |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
FWIW, on my PC the latest FFMS2 C-plugin returns this message:
"FFVideoSource: no suitable output format found" — whereas the DLL compiled on 2018/January/09 loads that video but makes VirtualDub crash when I click the play button. Last edited by filler56789; 14th March 2019 at 07:21. Reason: edit |
14th March 2019, 10:38 | #114 | Link | |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
UPDATE:
adding colorspace="YV12" to FFVideoSource() is the solution to the PEBKAC situation. Quote:
|
|
14th March 2019, 11:17 | #115 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Thanks, this explains it...
But for software like AVStoDVD where the user cannot alter the FFVideoSource parameter to add a colorspace value this means that for high bit depth video the current ffms2 C-Plugins will not work. I will recomend to all A2D users to revert back to ffms2_r1140+101-avs+vsp.7z to avoid these issues. |
21st March 2019, 23:58 | #116 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
New build.
Includes the AV1 parsing fix patches, along with two months' newer versions of FFmpeg and libdav1d. |
23rd March 2019, 18:04 | #117 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Thanks for the new build r1340...
I would like to make this fool proof for AVStoDVD, this means that I need to add the colorspace="YV12" param to the AVS file created by AVStoDVD somehow (not too hard, I already do intercept the encoder call). The question is if this is really worth the trouble. The older version r1140 works nicely so far, does the new version r1340 offer any real world advantages? Does it support source formats which the older version doesn't? Or does it fix some serious bugs? Cheers manolito |
23rd March 2019, 21:56 | #118 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,419
|
Quote:
|
|
24th March 2019, 10:44 | #119 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Thanks for this info...
Looks like AV1 might become an important video format in the near future, source filters will need to support it. My efforts to add the colorspace parameter to the AVS script in A2D were only halfway successful. I can manipulate the encoding script, but for the preview a separate script is used which I cannot access. Hopefully MrC will find some time to fix it... Cheers manolito |
Thread Tools | Search this Thread |
Display Modes | |
|
|