I have set a fade-in from black filter at the beginning of my edit starting at 3s 500ms going to 4s 500ms. Unfortunately, every time I restart anywhere in the track this filter kicks in 3s 500ms after I restart. IOW it is not locked to the absolute time of the entire track but to the initiation of resuming play at any point in the track.
The MPlayer eq2 filter works as expected but there is no longer an option to filter only part of the track. This is unacceptable because sometimes only one or two sections need adjustment.
In 'play filtered' mode, when the track is started at the beginning and then stopped, it flips back to the very beginning. IOW, it does not stay at the point it was stopped. I only tested up to 2 minutes. There may be a threshold after which this does not happen. AFAICT this only happens when started from the beginning. When starting and stopping at other points in the track this has not happened.
I have been using Avidemux for over ten years and everything has always worked perfectly. Unfortunately it is not really usable in its current state.
Confirmed: quick test
take a 1 minute duration video clip
Using filter Black set on
Start: keyframe arround 00:00:03,000 seconds
End: Keyframe arround 00:00:05,000 seconds
play filtered from 10 seconds
arround 13 seconds Black filter kicks in for 2 seconds
Looks like Black is applied to current playing/saving time and not to the actual time of full video.
I don't know/or remember if this was intended or not.
Black was created after this discussion:
Editing: Blank video but keep audio but in a section (http://avidemux.org/smif/index.php/topic,16468.0.html)
Fixed
Fixed: commit: 68e9477 [filter/black] Also use absolute time
Just build 43594d6 and tested.
Doing the same test
==> Not OK - Play filtered does still blackout 3 seconds from playing (7 seconds starts blackout @ 10 seconds) <==
OK - The re-encoded saved video = correct, black starts @ 3 seconds for the wanted duration
Happy to help a bit.
But I just now realized that the only fade option is 'fade to black'. I'm not seeing a normal fade option which I use frequently to connect cuts. Why on earth would that be removed?
Drop 4 down down in the same list of filters:
Fade
Fade in/out
Heavy/late night?
Quote from: Jan Gruuthuse on January 01, 2016, 04:11:35 PM
Drop 4 down down in the same list of filters:
Fade
Fade in/out
Heavy/late night?
Hardly. I don't do 'holidays'. But my heater is currently non-functional so am freezing my you-know-what off.
Please see attached. What am I missing? Only available options in the dropdown are in/out. Note that 'Fade' in the filter list connects to "Fade to black' in the title bar. Something possibly missing?
Black is above, just below Add logo.
starts black from start time to end time.
The option you show has Fade type:
In or Out
Fade in starts with black and ends in image.
Fade out starts with image and ends in black.
Quote from: Jan Gruuthuse on January 01, 2016, 04:29:32 PM
Black is above, just below Add logo.
starts black from start time to end time.
The option you show has Fade type:
In or Out
Fade in starts with black and ends in image.
Fade out starts with image and ends in black.
There's a miscommunication here.
I have no need for the 'Black' option.
The 'Fade' option in the menu is linked to the the 'Fade to black' gui.
Why are there not two options 'Fade' and 'Fade to black' linking to two different interfaces?
I am not seeing anywhere a normal, un-blackened 'Fade' option.
Perhaps it is you that had a heavy/late night?
I'm not sure there were such a fade
In 2.5.X ?
yes 2.5.6, you could disable [ ] Fade to black.
2.6 never had.
Quote from: mean on January 01, 2016, 05:01:29 PM
I'm not sure there were such a fade
In 2.5.X ?
From the first day I started using Avidemux @2003, the default 'Fade' option was a normal blending of images with no black involved. There was a checkbox in that settings window that offered a 'Fade to black'. So you could choose which one to use. I'm still doing most of my editing on Avidemux 1:2.5.4-0.3squeeze1. Haven't really used the later versions that much. I do have it installed on my wheezy but haven't used it that often. I can post a screenie later when I get on that machine if that would be helpful.
Kinda cross fade from one scene to another.
Quote from: Jan Gruuthuse on January 01, 2016, 05:22:06 PM
Kinda cross fade from one scene to another.
Yes. How can anyone edit without it!
The fade to black seems to work for me
i.e.
black from 10' to 15'
go to 8' play; it starts to fade after 2 sec as expected
What am i missing ?
Quote from: mean on January 01, 2016, 05:43:12 PM
The fade to black seems to work for me
i.e.
black from 10' to 15'
go to 8' play; it starts to fade after 2 sec as expected
What am i missing ?
A cross-fade between two sections of video with no black!!
Fixed: commit:
68e9477 [filter/black] Also use absolute time
Quote from: mean on January 01, 2016, 05:43:12 PM
The fade to black seems to work for me
i.e.
black from 10' to 15'
go to 8' play; it starts to fade after 2 sec as expected
What am i missing ?
set a black fade from 0h:0m:3s,0 to 0h:0m:5s,0 seconds real time
move forward to 10 seconds in movie, now play filtered, at 13 seconds you will see preview of black of 2 seconds. It shouldn't do that as black is from 3 to 5 seconds
This for mean . . . a cross fade to blend two different sections. (Yeah, still burning dvds for an old 21" CRT!)
Fixed: commit: 68e9477 [filter/black] Also use absolute time
Desktop recording:
video loaded, selected Black filter, both keyframe:
start time: 3, 060 seconds
end time: 7, 040 seconds
with play filtered: Test:
- 36 seconds in desktop recording: filter black kicks in @ 3, 060 seconds, as it should
- 55 seconds in desktop recording: goto 10, 560 seconds, start play
- 61 seconds in desktop recording: @ 13, 980 seconds black filter kicks in
it should not, as it is defined from 3, 060 seconds to 7, 040 seconds
preview:
download 2,8 MB: Desktop recording:
Ok, it's not the fade to black filter but the blacken filter
Got it
Fixed: commit: 68e9477 [filter/black] Also use absolute time
The issue is only with Play filtered
Re-encoding and save video works fine.
So what about getting a cross-fade filter reinstated in avidemux?
Order of priorities / Time permitting: maybe. Developer(s) have a big shortage of developing time.
Your simple request may be more complicated? Probably your request is on a to do list.
ps.: my personal user opinion, this may not reflect the developer(s) point of view
It's not easy to do with the 2.6 codebase
Quote from: mean on January 03, 2016, 07:52:45 AM
It's not easy to do with the 2.6 codebase
Without a cross fade, 2.6* is useless to me. If I can't get 2.5* to work on Jessie, I have two options:
1. Keep squeeze and wheezy running indefinitely.
2. Start exploring alternate video editors (which would be so sad after all of these years)
So much for 'progress' . . .
Well, just installed Avidemux 2.5.6 Gtk from Wheezy on Jessie and IT WORKS PERFECTLY! Even better all my old project files just WORK! Have locked the version so should be OK for a few more years if I keep away from dmo updates.
I have really appreciated all your help these last few days.
You should be able to have the 2 installed alongside (2.5.6 and 2.6). Occasionally I have to use 2.5.6 for frame based not handled by 2.6.#
Quote from: Jan Gruuthuse on January 04, 2016, 12:33:57 PM
You should be able to have the 2 installed alongside (2.5.6 and 2.6). Occasionally I have to use 2.5.6 for frame based not handled by 2.6.#
I have never had a problem with frame-based editing. In it's current state (with crippled filters) 2.6* is useless to me.
concept between the 2 versions: 2.5 (frame based) & 2.6 (time based).
Quote from: Jan Gruuthuse on January 05, 2016, 05:21:24 PM
concept between the 2 versions: 2.5 (frame based) & 2.6 (time based).
I understand that. Not ever having a problem with frames, I don't know what the advantages might be. My requirements are rather simple - auto dvd edited from from vobs. But regardless, 2.6* is too broken (and not pleasant to look at). I posted in the 2.5 forum a request to keep 2.5 as a legacy option alongside the 'newer' 2.6. I suspect that thread will go unanswered . . .