Recent Posts

Pages: 1 [2] 3 4 ... 10
11
On a search for the declared end of the film in a manually appended file in play mode a press on the stop button has brought the time-marker back to the very beginning – instead of remaining (practically) were it previously was.

This happens when the stream is corrupted (numerous occurences of "PTS going back" in the log indicate a damaged stream) at the spot where the playback stops. The following seek back to this spot fails in somewhat unexpected way, I must look into it first to be able to judge whether it is easily fixable.

Quote
The recording device is said to break longer items into 1GB portions + the remaining

I need the exact number of bytes, "1GB" is not precise enough.

Quote
(optional) automatic appending was a problem-free part of your older versions

It wasn't.

Quote
I can hardly imagine anything to hamper you from reinstalling this optional feature anew.

If you build Avidemux yourself (which is trivial on Linux), it is just a question of chaning a "0" into "1" at the location in the source I already mentioned. To safely re-enable the prompt in official builds, I need a more or less reliable indicator for a heuristic detection like the (exact) chunk size.
12
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by manbau00 on September 22, 2018, 06:52:35 PM »
I'll tried the following:

 ffmpeg  -ss 0.2 -fflags +genpts -i Test.mpg -map 0 -c copy -f matroska -ignore_unknown -sn -y Test.mkv

But now it happens later. After the 300MB.

Input #0, mpegts, from 'Test.mpg':
  Duration: 02:05:36.08, start: 0.028789, bitrate: 8515 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
    Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
    Stream #0:1[0x101](deu): Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 448 kb/s
    Stream #0:2[0x102](mis): Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 448 kb/s
Output #0, matroska, to 'Test.mkv':
  Metadata:
    encoder         : Lavf57.83.100
    Stream #0:0: Video: h264 (High) (H264 / 0x34363248), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 50 fps, 50 tbr, 1k tbn, 90k tbc
    Stream #0:1(deu): Audio: ac3 ([0]
  • [0] / 0x2000), 48000 Hz, 5.1(side), fltp, 448 kb/s

    Stream #0:2(mis): Audio: ac3 ([0]
  • [0] / 0x2000), 48000 Hz, 5.1(side), fltp, 448 kb/s

Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
  Stream #0:2 -> #0:2 (copy)
Press [q] to stop, [?] for help
[matroska @ 0x5577f9e44f60] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[matroska @ 0x5577f9e44f60] Can't write packet with unknown timestamp
av_interleaved_write_frame(): Invalid argument
frame=19272 fps=1223 q=-1.0 Lsize=  411301kB time=00:06:25.85 bitrate=8732.3kbits/s speed=24.5x
video:368744kB audio:42220kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.081901%
Conversion failed!
13
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by manbau00 on September 22, 2018, 06:40:56 PM »
Hi,

for the first, many thanks for your analysis of the issue.

Ad practical POV, yes I am willing to do so for the future. But I have already many damaged files.

Do you think skipping the first frames and trying -ss 0.2 -fflags +genpts is a solution? Could this restore the PTS?

Could this also be fixed in Avidemux that it does not happen again?

Regards
Manfred
14
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by eumagga0x2a on September 22, 2018, 06:22:18 PM »
I can reproduce the issue (also with my own captures from DVB-C). The reason is not that PTS were unset but a few frames pretty close to the start of the cut stream get invalid (not monotonically increasing) DTS. Avidemux doesn't see DTS going back (it regards DTS of some frames as unset, which may be correct and harmless).

Interestingly, skipping the start of the stream with say ffmpeg -ss 0.2 -i Sample02_cut_with_avidemux.ts allows to remux it to MKV without errors, but PTS in this MKV are totally broken.

From the practical POV, if you have to use Avidemux anyway to delete portions of the video, why not saving the result to a MKV right away?
15
With a new batch of film to archive having gathered and available for processing I went to the task to locate and document failure-action, as you asked.
In this, I thought to save you space & trouble, so, on finding a non-normal action I started a fresh Avid-session with the problematic-item, but the previously observed failure did not occur on repeating. Hence, the here presented admlog.txt file is a bit longer: it is the second film in the session where the problem occurred – and must have left its trace on the txt-record. I keep both complete film source-files and the full adminlog.txt as well for a while, but you required only its .ZIP version, which I supply: https://we.tl/t-de4hekQjyY The failure itself as I observed was the same I previously have already described. Namely: On a search for the declared end of the film in a manually appended file in play mode a press on the stop button has brought the time-marker back to the very beginning – instead of remaining (practically) were it previously was.
On appending:
So far as I can fathom, an exact size down to the bit does not exist for the chunks. The recording device is said to break longer items into 1GB portions + the remaining, and stores them in a folder. Since this feature did not changed and (optional) automatic appending was a problem-free part of your older versions, I can hardly imagine anything to hamper you from reinstalling this optional feature anew. I would rather remain a happy end-user than messing in your prime job.
16
User interface and Usability / Re: Ouput Keyframes
« Last post by eumagga0x2a on September 22, 2018, 09:36:43 AM »
Quote
Is it possible in Avidemux to change the original video keyframing without changing codec/compression, etc. ?

Not without re-encoding the video, obviously, as the type of compressed frame is determined at the moment of encoding.

Smaller GOP sizes allow better seek granularity and strongly reduce compression rate.
17
Unix-Like (Linux/Bsd/...) / Re: AVSload: setup_exception_record stack overflow
« Last post by ANDDEMUX on September 22, 2018, 09:34:00 AM »
Translated by Google Translate

I ran the program with wine debug options active and, among the slew of rows, I found the following code:
Code: [Select]
51321.731:0008:0009:trace:module:GetModuleFileNameW L"Z:\\usr\\share\\ADM_addons\\avsload.exe"
51321.731:0008:0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0xb7c7cad9 ip=b7c7cad9 tid=0009
51321.731:0008:0009:trace:seh:raise_exception  info[0]=00000001
51321.731:0008:0009:trace:seh:raise_exception  info[1]=00340000
51321.731:0008:0009:trace:seh:raise_exception  eax=00000000 ebx=b7c7caca ecx=00000058 edx=00340028 esi=00000016 edi=0033f6de
51321.731:0008:0009:trace:seh:raise_exception  ebp=0033f8d8 esp=0033f688 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00010206
Immediately after it start with an infinite sequence of:
Code: [Select]
51321.731:0008:0009:trace:seh:call_stack_handlers calling handler at 0x7bca80c0 code=c0000005 flags=0
51321.731:0008:0009:trace:seh:call_stack_handlers handler at 0x7bca80c0 returned 2
Until it crashes with stack overflows. Periodically the fault occurs during the endless calls.

It can be helpful to find out the problem?

Thanks and bye :)
18
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by eumagga0x2a on September 22, 2018, 09:26:51 AM »
Thank you, I hope to be able to look at it later today.
19
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by manbau00 on September 22, 2018, 08:46:35 AM »
Hi!

I put the Message into a text document. Hopefully this works.

Regards
Manfred
20
Main version 2.6 / Re: avidemux works fine but trying the same with ffmpeg don't
« Last post by manbau00 on September 22, 2018, 08:35:25 AM »
Hi,

I am not allowed to post!

An Error Has Occurred!
CleanTalk: *** Forbidden. Please enable JavaScript. Message seems to be spam. ***

Can you help me?

Regards
Manfred
Pages: 1 [2] 3 4 ... 10