Grunster build 7748 Win 7 x64 x264 avc crash logs and pause problems.

Started by digitaltoast, March 12, 2012, 11:36:31 AM

Previous topic - Next topic

digitaltoast

Did a complete removal of previous install before installing Grunster build 7748.

Now it either crashes on completion of encoding, or once when marking an edit point.

Incidentally, now when pausing or stopping playback to mark the edit point, the seek bar jumps back to where that section started.
Am I doing something wrong or is this a "feature" of that build?

Crashed when marking edit point:
Faulting application name: avidemux.exe, version: 2.6.0.7748, time stamp: 0x4f570e65
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x1764
Faulting application start time: 0x01cd002eac5c28f8
Faulting application path: H:\Program Files\Avidemux 2.6\avidemux.exe
Faulting module path: H:\Windows\SYSTEM32\ntdll.dll
Report Id: b8423b2b-6c24-11e1-92ec-000d18114648


Crashed when completing encode:
Faulting application name: avidemux.exe, version: 2.6.0.7748, time stamp: 0x4f570e65
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x195c
Faulting application start time: 0x01cd002d61a97534
Faulting application path: H:\Program Files\Avidemux 2.6\avidemux.exe
Faulting module path: H:\Windows\SYSTEM32\ntdll.dll
Report Id: e1192973-6c21-11e1-92ec-000d18114648

Jan Gruuthuse

Quote from: digitaltoast on March 12, 2012, 11:36:31 AM
Incidentally, now when pausing or stopping playback to mark the edit point, the seek bar jumps back to where that section started.
Am I doing something wrong or is this a "feature" of that build?
Quote from: mean on January 29, 2012, 06:29:53 PM
It is because of the "play output mode"
It is not sure we can continue when reverting to play input mode
Going back to the beginning is safer
Weird having windows and programs not on drive c: ? Could that not be causing problems?
Quote from: digitaltoastNow it either crashes on completion of encoding, or once when marking an edit point
You're using keyframe to mark edit point? The crashes do these occur with specific video (container/codec video/audio)?
Some video work better with 2.5.6 others with 2.6.
Do you have zonealarm installed on your system?

digitaltoast

Quote from: Jan Gruuthuse on March 12, 2012, 01:35:08 PM
Quote from: digitaltoast on March 12, 2012, 11:36:31 AM
Incidentally, now when pausing or stopping playback to mark the edit point, the seek bar jumps back to where that section started.
Am I doing something wrong or is this a "feature" of that build?
Quote from: mean on January 29, 2012, 06:29:53 PM
It is because of the "play output mode"
It is not sure we can continue when reverting to play input mode
Going back to the beginning is safer

Tried both input and output mode - both the same "jumping back" problem.

Quote from: Jan Gruuthuse on March 12, 2012, 01:35:08 PMWeird having windows and programs not on drive c: ? Could that not be causing problems?

Not weird at all - "c" is just a letter most people choose - I installed an SSD, keeping my current drive. So when I re-installed, everything was H.
Programmes don't care where they are installed - a letter is just a letter :) Previous version was OK too.

Quote from: Jan Gruuthuse on March 12, 2012, 01:35:08 PMYou're using keyframe to mark edit point? The crashes do these occur with specific video (container/codec video/audio)?
Yes, only MPEG4 AVC crashes like this, MPEG4 ASP (xvid) works OK (but compression less good).
No idea if I'm on a keyframe when marking - I just click "a" or "b" like I've always done.

Quote from: Jan Gruuthuse on March 12, 2012, 01:35:08 PMSome video work better with 2.5.6 others with 2.6.
Was working fine on 2.6 build 7700

Quote from: Jan Gruuthuse on March 12, 2012, 01:35:08 PMDo you have zonealarm installed on your system?
Wow! ZoneAlarm... I remember that from 10 years ago! I didn't even know it was still made. No, I have Windows 7, so no need.

Jan Gruuthuse

Quote from: digitaltoast on March 12, 2012, 01:59:19 PM
Tried both input and output mode - both the same "jumping back" problem.
mean (the developer) is explaining why the jump back: it is safer to do so! It is by design.
QuoteNo idea if I'm on a keyframe when marking - I just click "a" or "b" like I've always done.
@ the mark point use up or down arrow on keyboard to select keyframe before making cut.
Hope developer finds out what is going on there.