Recent Posts

Pages: [1] 2 3 ... 10
1
Main version 2.6 / Re: Crash when muxing AAC
« Last post by AQUAR on Today at 12:07:56 PM »
IIRC, some time ago you could not import AAC at all.
People were saving (exporting) AAC from ADM and also found that they could not even import that file (raw data).
Then on request,  Mean added basic functionality that exported the AAC audio in ADTS and allowed its importation.

Probably the reason why there are issues with non ADM created external AAC audio.

 
2
Windows / [bug] Filter 'Blacken Borders' not available in CLI
« Last post by p3trus on Today at 09:45:29 AM »
(Don't know if it's windows only)

Any project using the 'Blacken Borders" video filter doesn't run with avidemux_cli; excerpt from the CLI output:
Quote
...
[ADM_vf_plugin] Plugin loaded version 1.0.0, name vflip/Vertical Flip
[ADM_vf_plugin] Plugin loaded version 1.0.0, name yadif/Yadif
[ADM_vf_plugin] Scanning done, found 36 video filer(s) so far
[parseOneFolder] 09:25:59-446 Feature Mask = 0x0
[DynaLoader] Cannot find function create
[ADM_vf_plugin] Unable to load libADM_vf_blackenBordersCli.dll
[ADM_vf_plugin] Plugin loaded version 1.0.0, name chromashift/ChromaShift
...

[goToTimeVideo] 09:25:59-901 Seek done, in reference, gone to 1592144 with segment start at 1592144
[partialFilter] 09:25:59-901 Creating partial filter for mpdelogo2, with 6 params
[ADM_vf_getPluginFromInternalName] 09:25:59-902 Cannot get video filter from name <blackenBorder>
[abortExitHandler] 09:25:59-975 already done, nothing to do
<EOF>
(Full log attached)

- project runs fine in GUI version
- \plugins\videoFilters\cli\libADM_vf_blackenBordersCli.dll exists
- happens with 2.6.19 Final, r170420_win64Qt5_402 & r170425_win64Qt5_4 (all x64)
3
Nice!
4
This bothered me too, should be fixed now ([UI] Add a file name extension when saving projects). The fix will be included into the 2.6.20 release as well.
5
Main version 2.6 / Re: Crash when muxing AAC
« Last post by eumagga0x2a on Today at 07:11:01 AM »
The E-AC3 detection has been fixed: [audio] Check deeper if it is eac3, the 2 frames must be right after one another. The fix will be in the 2.6.20 release as well.

Thank you for your report.
6
Main version 2.6 / Re: Crash when muxing AAC
« Last post by Jan Gruuthuse on Today at 05:50:59 AM »
What I could think of (wild guessing)

- relation between actual channels (2,2.1, 5.0,5.1, ...) and used bitrate (compounded)
- limitation in maximum (allowed?) bitrate, bitrate/channel
- limitation in maximum (allowed?) kHz

above usage against different libraries: AAC (FDK),AAC (Faac), AAC (lav)

some more info: https://trac.ffmpeg.org/wiki/Encode/AAC
- As a rule of thumb, for audible transparency, use 64kb/s for each channel (so 128kb/s for stereo, 384 kb/s for 5.1 surround sound)
- Note: A bug exists in libfdk-aac 0.1.3 and earlier that will cause a crash when using high sample rates, such as 96kHz, with VBR mode 5.
7
e6a88d5            [plugin/hue] Define M_PI if it was not defined previously
3a7237f            [UI] Add a file name extension when saving projects

ubuntu 16.04.2 LTS 64 bit x86 SMP, QT5, x265 version 1.9: avidemux 2.7.0 170427-64bit Xenial with x265 version 1.9
8
Avidemux-French / pb de coupure imprécise
« Last post by topinrouen on April 26, 2017, 09:15:24 PM »
Bonjour

je fais une coupure d'un fichier au format TS encodé en h264 (enregistrement TNT-HD) en placant le curseur de début (A)
sur une frame I et le curseur de fin (B) sur une frame P. Pas de reencodage video et sauvegarde en mkv.
Quand j'ouvre le fichier mkv avec avidemux, pour vérifier si la coupure s'est bien faite, il semble que la dernière frame ne soit pas de type P et il est impossible de naviguer jusqu'à la dernière frame. J'avoue ne pas comprendre pourquoi la coupure entre une frame I et une frame P ne semble pas fonctionner (en mpeg2 h263, cela fonctionnait sans souci).
Quelqu'un aurait une idée sur cette question ou une suggestion pour couper proprement (sans réencodage) ?
merci

Yann
9
Main version 2.6 / Re: Crash when muxing AAC
« Last post by eumagga0x2a on April 26, 2017, 08:00:44 PM »
Okay, idAAACADTS always reports 128k as bitrate for AAC, so nothing surprising here :)

Swapping the order of checks for E-AC3 and AAC in ADM_identifyAudioStream sort of fixes this bug which originates from AAC getting misidentified as E-AC3 (on the other hand even misidentified stream should not result in a crash). I have no idea what will break if this band-aid gets applied, however.
10
Main version 2.6 / Re: [bug] using GUIs in scripts
« Last post by eumagga0x2a on April 26, 2017, 04:56:12 PM »
although some progress seems to have been made, since clicking Cancel doesn't produce any error [for itself];

No, no changes on that at all. If the return value of the dialog is evaluated and exit() called on false like in dvd.py, clicking Cancel results in the very same error.
Pages: [1] 2 3 ... 10