Recherche avancée

Sur d’autres sites (5880)

• FFmpeg crossfading with audio keeps throwing [AVFilterGraph @ 0x...] No such filter : '', but works video only

  5 décembre 2023, par J. Cravens

  I've got this script that crossfade's all mp4's in the directory. If I try to add the audio, with this, it doesn't work.

  


  VIDEO="fade=in:st=0:d=1:alpha=1,setpts=PTS-STARTPTS+(${fade_start}/TB)[v${i}];"
AUDIO="[0:a]afade=d=1[a0];"


  


  This works fine...

  


  #!/bin/bash

CMD="ffmpeg"
FILES=(*.mp4)
SIZE=${#FILES[@]}
VIDEO=""
OUT=""

i="0"
total_duration="0"
for file in "${FILES[@]}"; do
  echo "$file"
  CMD="$CMD -i '$file'"

  duration=$(ffprobe -v error -select_streams v:0 -show_entries stream=duration -of csv=p=0 "$file" | cut -d'.' -f1)

  if [[ "$i" == "0" ]]
  then
    VIDEO="[0:v]setpts=PTS-STARTPTS[v0];"
  else
    fade_start=$((total_duration))
    VIDEO="${VIDEO}[${i}:v]format=yuva420p,fade=in:st=0:d=1:alpha=1,setpts=PTS-STARTPTS+(${fade_start}/TB)[v${i}];"
    if (( i < SIZE-1 ))
    then
      if (( i == 1 ))
      then
        OUT="${OUT}[v0][v1]overlay[outv1];"
      else
        OUT="${OUT}[outv$((i-1))][v${i}]overlay[outv${i}];"
      fi
    else
      if (( SIZE == 2 ))
      then
        OUT="${OUT}[v0][v1]overlay,format=yuv420p[outv]"
      else
        OUT="${OUT}[outv$((i-1))][v${i}]overlay,format=yuv420p[outv]"
      fi
    fi
  fi

  total_duration=$((total_duration+duration))

  i=$((i+1))
done

CMD="$CMD -filter_complex \"${VIDEO}${OUT}\" -c:v libx264 -preset ultrafast -map [outv] crossfade.mp4"

echo "$CMD"

bash -c "$CMD"


  


  ...but when I try to add the audio, it's not happy. I'm missing something.

  
Anyone know what is going on ? I read of cases leaving an extra ; at the end causing "No such filter", but I tried echo ${VIDEO%?} before the command, it didn't seem to make a difference. I read acrossfade requires 32bit little endian, so I went to afade, it didn't change anything. Ideas ?

  


  Update :

  


  #!/bin/bash

duration_a=$(ffprobe -v error -select_streams a:0 -show_entries stream=duration -of csv=p=0 -i audio_02.m4a)
ffmpeg -i audio_01.m4a -i audio_02.m4a -filter_complex \
"[0:a] \
[1:a]acrossfade=d=1.0:c1=tri:c2=tri,asetpts=PTS-STARTPTS+'$duration_a'[outa]" -vn -map "[outa]" 01_02.m4a

duration_b=$(ffprobe -v error -select_streams a:0 -show_entries stream=duration -of csv=p=0 -i audio_03.m4a)
ffmpeg -i 01_02.m4a -i audio_03.m4a -filter_complex \
"[0:a] \
[1:a]acrossfade=d=1.0:c1=tri:c2=tri,asetpts=PTS-STARTPTS+'$duration_b'[outa]" -vn -map "[outa]" 01_02_03.m4a


  


  ...and so on. This still doesn't properly sync the a/v. I noticed the first 2 always had audio sync proper, so I tried to do it, one at a time, appending the next. It still goes out of sync, regardless of using asetpts=PTS-STARTPTS.

  


  Update 2 :
I've got this working via fade in/out.

  


  #!/bin/bash

if [ -e *.mkv ]; then
  file_type=".mkv"
else
  file_type=".mp4"
fi

mkdir ./temp
for file in *$file_type; do mv "$file" "in_$file"; done

# Function to fade in video
function fade_in() {
file_list1=(in_*)
  echo "Executing fade_in"
  for file in "${file_list1[@]}"; do
    ffmpeg -i "$file" -y -vf fade=in:0:30 -hide_banner -preset ultrafast "out_$file"
  done
mv in_* ./temp
}
export -f fade_in

# Function to fade out video
function fade_out() {
  file_list2=(out_*)
  echo "Executing fade_out"
  for file in "${file_list2[@]}"; do
    frame_count=$(ffmpeg -i $file -map 0:v:0 -c copy -f null -y /dev/null 2>&1 | grep -Eo 'frame= *[0-9]+ *' | grep -Eo '[0-9]+' | tail -1)
      frame_start=$((frame_count - 30))
      ffmpeg -i "$file" -y -vf fade=out:"$frame_start":30 -hide_banner -preset ultrafast "to_mux_$file"
  done
  mv out_* ./temp
}

export -f fade_out

bash -c "fade_in"
bash -c "fade_out"

ls --quoting-style=shell-always -1v *$file_type > tmp.txt
sed 's/^/file /' tmp.txt > list.txt && rm tmp.txt

ffmpeg -f concat -safe 0 -i list.txt -c copy -shortest -movflags +faststart fade_muxed$file_type

mv to_mux_* ./temp
rm list.txt
#rm -rf ./temp

exit 0


  


  Number the filename's sequentially (i.e. 01_file.mkv 02_file.mkv etc.), to ensure order, or it will be up to the directory sort.

  It's not a crossfade, but it's pretty decent and has audio.
  Still working on the crossfade + audio.

  


• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !

• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !