Recherche avancée
Médias (91)
-
Richard Stallman et le logiciel libre
19 octobre 2011, par
Mis à jour : Mai 2013
Langue : français
Type : Texte
-
Stereo master soundtrack
17 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Audio
-
Elephants Dream - Cover of the soundtrack
17 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Image
-
#7 Ambience
16 octobre 2011, par
Mis à jour : Juin 2015
Langue : English
Type : Audio
-
#6 Teaser Music
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#5 End Title
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
Autres articles (68)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)
Sur d’autres sites (7484)
-
FFmpeg WASM writeFile Stalls and Doesn't Complete in React App with Ant Design
26 février, par raiyan khanI'm using FFmpeg WebAssembly (WASM) in a React app to process and convert a video file before uploading it. The goal is to resize the video to 720p using FFmpeg before sending it to the backend.


Problem :


Everything works up to fetching the file and confirming it's loaded into memory, but FFmpeg hangs at ffmpeg.writeFile() and does not proceed further. No errors are thrown.


Code Snippet :


- 

-
Loading FFmpeg


const loadFFmpeg = async () => {
 if (loaded) return; // Avoid reloading if 
 already loaded

 const baseURL = 'https://unpkg.com/@ffmpeg/core@0.12.6/dist/umd';
 const ffmpeg = ffmpegRef.current;
 ffmpeg.on('log', ({ message }) => {
 messageRef.current.innerHTML = message;
 console.log(message);
 });
 await ffmpeg.load({
 coreURL: await toBlobURL(`${baseURL}/ffmpeg-core.js`, 'text/javascript'),
 wasmURL: await toBlobURL(`${baseURL}/ffmpeg-core.wasm`, 'application/wasm'),
 });
 setLoaded(true);
 };

 useEffect(() => {
 loadFFmpeg()
 }, [])


-
Fetching and Writing File


const convertVideoTo720p = async (videoFile) => {
 console.log("Starting video 
 conversion...");



 const { height } = await getVideoMetadata(videoFile);
 console.log(`Video height: ${height}`);

 if (height <= 720) {
 console.log("No conversion needed.");
 return videoFile;
 }

 const ffmpeg = ffmpegRef.current;
 console.log("FFmpeg instance loaded. Writing file to memory...");

 const fetchedFile = await fetchFile(videoFile);
 console.log("File fetched successfully:", fetchedFile);

 console.log("Checking FFmpeg memory before writing...");
 console.log(`File size: ${fetchedFile.length} bytes (~${(fetchedFile.length / 1024 / 1024).toFixed(2)} MB)`);

 if (!ffmpeg.isLoaded()) {
 console.error("FFmpeg is not fully loaded yet!");
 return;
 }

 console.log("Memory seems okay. Writing file to FFmpeg...");
 await ffmpeg.writeFile('input.mp4', fetchedFile); // ❌ This line hangs, nothing after runs
 console.log("File successfully written to FFmpeg memory.");
 };








Debugging Steps I've Tried :


- 

- Ensured FFmpeg is fully loaded before calling
writeFile()
✅ffmpeg.isLoaded()returnstrue. - Checked file fetch process :
✅
fetchFile(videoFile)successfully returns aUint8Array. - Tried renaming the file to prevent caching issues
✅ Used a unique file name like
video_${Date.now()}.mp4, but no change - Checked browser console for errors :
❌ No errors are displayed.
- Tried skipping FFmpeg and uploading the raw file instead :
✅ Upload works fine without FFmpeg, so the issue is specific to FFmpeg.












Expected Behavior


- 

ffmpeg.writeFile('input.mp4', fetchedFile);should complete and allow FFmpeg to process the video.




Actual Behavior


- 

- Execution stops at
writeFile, and no errors are thrown.




Environment :


- 

- React : 18.x
- FFmpeg WASM Version : @ffmpeg/ffmpeg@0.12.15
- Browser : Chrome 121, Edge 120
- Operating System : Windows 11










Question :
Why is FFmpeg's
writeFile()stalling and never completing ?
How can I fix or further debug this issue ?

Here is my full code :




import { useNavigate } from "react-router-dom";
import { useEffect, useRef, useState } from 'react';
import { Form, Input, Button, Select, Space } from 'antd';
const { Option } = Select;
import { FaAngleLeft } from "react-icons/fa6";
import { message, Upload } from 'antd';
import { CiCamera } from "react-icons/ci";
import { IoVideocamOutline } from "react-icons/io5";
import { useCreateWorkoutVideoMutation } from "../../../redux/features/workoutVideo/workoutVideoApi";
import { convertVideoTo720p } from "../../../utils/ffmpegHelper";
import { FFmpeg } from '@ffmpeg/ffmpeg';
import { fetchFile, toBlobURL } from '@ffmpeg/util';


const AddWorkoutVideo = () => {
 const [videoFile, setVideoFile] = useState(null);
 const [imageFile, setImageFile] = useState(null);
 const [loaded, setLoaded] = useState(false);
 const ffmpegRef = useRef(new FFmpeg());
 const videoRef = useRef(null);
 const messageRef = useRef(null);
 const [form] = Form.useForm();
 const [createWorkoutVideo, { isLoading }] = useCreateWorkoutVideoMutation()
 const navigate = useNavigate();

 const videoFileRef = useRef(null); // Use a ref instead of state


 // Handle Video Upload
 const handleVideoChange = ({ file }) => {
 setVideoFile(file.originFileObj);
 };

 // Handle Image Upload
 const handleImageChange = ({ file }) => {
 setImageFile(file.originFileObj);
 };

 // Load FFmpeg core if needed (optional if you want to preload)
 const loadFFmpeg = async () => {
 if (loaded) return; // Avoid reloading if already loaded

 const baseURL = 'https://unpkg.com/@ffmpeg/core@0.12.6/dist/umd';
 const ffmpeg = ffmpegRef.current;
 ffmpeg.on('log', ({ message }) => {
 messageRef.current.innerHTML = message;
 console.log(message);
 });
 await ffmpeg.load({
 coreURL: await toBlobURL(`${baseURL}/ffmpeg-core.js`, 'text/javascript'),
 wasmURL: await toBlobURL(`${baseURL}/ffmpeg-core.wasm`, 'application/wasm'),
 });
 setLoaded(true);
 };

 useEffect(() => {
 loadFFmpeg()
 }, [])

 // Helper: Get video metadata (width and height)
 const getVideoMetadata = (file) => {
 return new Promise((resolve, reject) => {
 const video = document.createElement('video');
 video.preload = 'metadata';
 video.onloadedmetadata = () => {
 resolve({ width: video.videoWidth, height: video.videoHeight });
 };
 video.onerror = () => reject(new Error('Could not load video metadata'));
 video.src = URL.createObjectURL(file);
 });
 };

 // Inline conversion helper function
 // const convertVideoTo720p = async (videoFile) => {
 // // Check the video resolution first
 // const { height } = await getVideoMetadata(videoFile);
 // if (height <= 720) {
 // // No conversion needed
 // return videoFile;
 // }
 // const ffmpeg = ffmpegRef.current;
 // // Load ffmpeg if not already loaded
 // // await ffmpeg.load({
 // // coreURL: await toBlobURL(`${baseURL}/ffmpeg-core.js`, 'text/javascript'),
 // // wasmURL: await toBlobURL(`${baseURL}/ffmpeg-core.wasm`, 'application/wasm'),
 // // });
 // // Write the input file to the ffmpeg virtual FS
 // await ffmpeg.writeFile('input.mp4', await fetchFile(videoFile));
 // // Convert video to 720p (scale filter maintains aspect ratio)
 // await ffmpeg.exec(['-i', 'input.mp4', '-vf', 'scale=-1:720', 'output.mp4']);
 // // Read the output file
 // const data = await ffmpeg.readFile('output.mp4');
 // console.log(data, 'data from convertVideoTo720p');
 // const videoBlob = new Blob([data.buffer], { type: 'video/mp4' });
 // return new File([videoBlob], 'output.mp4', { type: 'video/mp4' });
 // };
 const convertVideoTo720p = async (videoFile) => {
 console.log("Starting video conversion...");

 // Check the video resolution first
 const { height } = await getVideoMetadata(videoFile);
 console.log(`Video height: ${height}`);

 if (height <= 720) {
 console.log("No conversion needed. Returning original file.");
 return videoFile;
 }

 const ffmpeg = ffmpegRef.current;
 console.log("FFmpeg instance loaded. Writing file to memory...");

 // await ffmpeg.writeFile('input.mp4', await fetchFile(videoFile));
 // console.log("File written. Starting conversion...");
 console.log("Fetching file for FFmpeg:", videoFile);
 const fetchedFile = await fetchFile(videoFile);
 console.log("File fetched successfully:", fetchedFile);
 console.log("Checking FFmpeg memory before writing...");
 console.log(`File size: ${fetchedFile.length} bytes (~${(fetchedFile.length / 1024 / 1024).toFixed(2)} MB)`);

 if (fetchedFile.length > 50 * 1024 * 1024) { // 50MB limit
 console.error("File is too large for FFmpeg WebAssembly!");
 message.error("File too large. Try a smaller video.");
 return;
 }

 console.log("Memory seems okay. Writing file to FFmpeg...");
 const fileName = `video_${Date.now()}.mp4`; // Generate a unique name
 console.log(`Using filename: ${fileName}`);

 await ffmpeg.writeFile(fileName, fetchedFile);
 console.log(`File successfully written to FFmpeg memory as ${fileName}.`);

 await ffmpeg.exec(['-i', 'input.mp4', '-vf', 'scale=-1:720', 'output.mp4']);
 console.log("Conversion completed. Reading output file...");

 const data = await ffmpeg.readFile('output.mp4');
 console.log("File read successful. Creating new File object.");

 const videoBlob = new Blob([data.buffer], { type: 'video/mp4' });
 const convertedFile = new File([videoBlob], 'output.mp4', { type: 'video/mp4' });

 console.log(convertedFile, "converted video from convertVideoTo720p");

 return convertedFile;
 };


 const onFinish = async (values) => {
 // Ensure a video is selected
 if (!videoFileRef.current) {
 message.error("Please select a video file.");
 return;
 }

 // Create FormData
 const formData = new FormData();
 if (imageFile) {
 formData.append("image", imageFile);
 }

 try {
 message.info("Processing video. Please wait...");

 // Convert the video to 720p only if needed
 const convertedVideo = await convertVideoTo720p(videoFileRef.current);
 console.log(convertedVideo, 'convertedVideo from onFinish');

 formData.append("media", videoFileRef.current);

 formData.append("data", JSON.stringify(values));

 // Upload manually to the backend
 const response = await createWorkoutVideo(formData).unwrap();
 console.log(response, 'response from add video');

 message.success("Video added successfully!");
 form.resetFields(); // Reset form
 setVideoFile(null); // Clear file

 } catch (error) {
 message.error(error.data?.message || "Failed to add video.");
 }

 // if (videoFile) {
 // message.info("Processing video. Please wait...");
 // try {
 // // Convert the video to 720p only if needed
 // const convertedVideo = await convertVideoTo720p(videoFile);
 // formData.append("media", convertedVideo);
 // } catch (conversionError) {
 // message.error("Video conversion failed.");
 // return;
 // }
 // }
 // formData.append("data", JSON.stringify(values)); // Convert text fields to JSON

 // try {
 // const response = await createWorkoutVideo(formData).unwrap();
 // console.log(response, 'response from add video');

 // message.success("Video added successfully!");
 // form.resetFields(); // Reset form
 // setFile(null); // Clear file
 // } catch (error) {
 // message.error(error.data?.message || "Failed to add video.");
 // }
 };

 const handleBackButtonClick = () => {
 navigate(-1); // This takes the user back to the previous page
 };

 const videoUploadProps = {
 name: 'video',
 // action: 'https://660d2bd96ddfa2943b33731c.mockapi.io/api/upload',
 // headers: {
 // authorization: 'authorization-text',
 // },
 // beforeUpload: (file) => {
 // const isVideo = file.type.startsWith('video/');
 // if (!isVideo) {
 // message.error('You can only upload video files!');
 // }
 // return isVideo;
 // },
 // onChange(info) {
 // if (info.file.status === 'done') {
 // message.success(`${info.file.name} video uploaded successfully`);
 // } else if (info.file.status === 'error') {
 // message.error(`${info.file.name} video upload failed.`);
 // }
 // },
 beforeUpload: (file) => {
 const isVideo = file.type.startsWith('video/');
 if (!isVideo) {
 message.error('You can only upload video files!');
 return Upload.LIST_IGNORE; // Prevents the file from being added to the list
 }
 videoFileRef.current = file; // Store file in ref
 // setVideoFile(file); // Store the file in state instead of uploading it automatically
 return false; // Prevent auto-upload
 },
 };

 const imageUploadProps = {
 name: 'image',
 action: 'https://660d2bd96ddfa2943b33731c.mockapi.io/api/upload',
 headers: {
 authorization: 'authorization-text',
 },
 beforeUpload: (file) => {
 const isImage = file.type.startsWith('image/');
 if (!isImage) {
 message.error('You can only upload image files!');
 }
 return isImage;
 },
 onChange(info) {
 if (info.file.status === 'done') {
 message.success(`${info.file.name} image uploaded successfully`);
 } else if (info.file.status === 'error') {
 message.error(`${info.file.name} image upload failed.`);
 }
 },
 };
 return (
 <>
 <div classname="flex items-center gap-2 text-xl cursor-pointer">
 <faangleleft></faangleleft>
 <h1 classname="font-semibold">Add Video</h1>
 </div>
 <div classname="rounded-lg py-4 border-[#79CDFF] border-2 shadow-lg mt-8 bg-white">
 <div classname="space-y-[24px] min-h-[83vh] bg-light-gray rounded-2xl">
 <h3 classname="text-2xl text-[#174C6B] mb-4 border-b border-[#79CDFF]/50 pb-3 pl-16 font-semibold">
 Adding Video
 </h3>
 <div classname="w-full px-16">
 / style={{ maxWidth: 600, margin: '0 auto' }}
 >
 {/* Section 1 */}
 {/* <space direction="vertical" style="{{"> */}
 {/* <space size="large" direction="horizontal" classname="responsive-space"> */}
 <div classname="grid grid-cols-2 gap-8 mt-8">
 <div>
 <space size="large" direction="horizontal" classname="responsive-space-section-2">

 {/* Video */}
 Upload Video}
 name="media"
 className="responsive-form-item"
 // rules={[{ required: true, message: 'Please enter the package amount!' }]}
 >
 <upload maxcount="{1}">
 <button style="{{" solid="solid">
 <span style="{{" 600="600">Select a video</span>
 <iovideocamoutline size="{20}" color="#174C6B"></iovideocamoutline>
 </button>
 </upload>
 

 {/* Thumbnail */}
 Upload Image}
 name="image"
 className="responsive-form-item"
 // rules={[{ required: true, message: 'Please enter the package amount!' }]}
 >
 <upload maxcount="{1}">
 <button style="{{" solid="solid">
 <span style="{{" 600="600">Select an image</span>
 <cicamera size="{25}" color="#174C6B"></cicamera>
 </button>
 </upload>
 

 {/* Title */}
 Video Title}
 name="name"
 className="responsive-form-item-section-2"
 >
 <input type="text" placeholder="Enter video title" style="{{&#xA;" solid="solid" />
 
 </space>
 </div>
 </div>

 {/* </space> */}
 {/* </space> */}


 {/* Submit Button */}
 
 <div classname="p-4 mt-10 text-center mx-auto flex items-center justify-center">
 
 <span classname="text-white font-semibold">{isLoading ? 'Uploading...' : 'Upload'}</span>
 
 </div>
 
 
 </div>
 </div>
 </div>
 >
 )
}

export default AddWorkoutVideo






Would appreciate any insights or suggestions. Thanks !


-
-
native memory and two thread
26 février 2013, par user1978722I have two еркуфвы in each of which I cause native function of memory allocation
then function working with it and then function memory releasing this
Java codethread1 :
@Override
protected Void doInBackground(Void...params) {
width_=FFMpegWrapper.getWidth(src);
height_=FFMpegWrapper.getHeight(src);
handle = FFMpegWrapper.openFile(src);
for (int i=f1+1;i15*ost)-1000000);
ByteBuffer my_buffer2 = FFMpegWrapper.allocNative2(bufferSize);
FFMpegWrapper.getFrame2(handle, kadr, width_, height_, my_buffer2);
Bitmap dest = Bitmap.createBitmap(width_, height_, Bitmap.Config.ARGB_8888);
dest.copyPixelsFromBuffer(my_buffer2);
OutputStream outStream = null;
File file = new File(extStorageDirectory, "file"+toString().valueOf(i)+".png");
Log.v("ttag",extStorageDirectory+"/file"+toString().valueOf(i)+".png");
try {
outStream = new FileOutputStream(file);
dest.compress(Bitmap.CompressFormat.PNG, 100, outStream);
outStream.flush();
outStream.close();
}
catch(Exception e)
{}
FFMpegWrapper.freeNative2();
mProgressStatus =i;
allProgress=allProgress+1;
this.publishProgress(mProgressStatus);
}
// TODO Auto-generated method stub
return null;
}thread2 :
@Override
protected Void doInBackground(Void...params) {
width_=FFMpegWrapper.getWidth(src);
height_=FFMpegWrapper.getHeight(src);
handle = FFMpegWrapper.openFile(src);
for (int i=0;i15*ost)-1000000);
ByteBuffer my_buffer = FFMpegWrapper.allocNative(bufferSize);
FFMpegWrapper.getFrame(handle, kadr, width_, height_, my_buffer);
Log.v("ttag",toString().valueOf(kadr));
Bitmap dest = Bitmap.createBitmap(width_, height_, Bitmap.Config.ARGB_8888);
dest.copyPixelsFromBuffer(my_buffer);
OutputStream outStream = null;
File file = new File(extStorageDirectory, "file"+toString().valueOf(i)+".png");
Log.v("ttag",extStorageDirectory+"/file"+toString().valueOf(i)+".png");
try {
outStream = new FileOutputStream(file);
dest.compress(Bitmap.CompressFormat.PNG, 100, outStream);
outStream.flush();
outStream.close();
//dest.
}
catch(Exception e)
{}
FFMpegWrapper.freeNative();
mProgressStatus =i;
allProgress=allProgress+1;
this.publishProgress(mProgressStatus);
}
// TODO Auto-generated method stub
return null;
}and functions on jni side :
jint Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_getFrame(JNIEnv *env, jobject thiz, thandle_file handleFile, jlong timeUS, jint width, jint height, jobject buffer) {
// LOGI("file= %d",handleFile);
AVFormatContext* ctx = ((struct thandle*)handleFile)->ctx;
AVCodecContext* codecCtx = ((struct thandle*)handleFile)->codecCtx;
AVPacket* packet = ((struct thandle*)handleFile)->packet;
int videoStream = ((struct thandle*)handleFile)->videoStream;
jshort* buff = (jshort*) (*env)->GetDirectBufferAddress(env, buffer);
AVFrame* frame = avcodec_alloc_frame(); //YUV frame
avcodec_get_frame_defaults(frame);
int frameNumber = timeUS;
//LOGI("avtb= %d",AV_TIME_BASE);
int64_t pos = frameNumber * AV_TIME_BASE / 1000000;
int64_t seek_target= av_rescale_q(pos, AV_TIME_BASE_Q, ctx->streams[videoStream]->time_base);
int res = avformat_seek_file(ctx
, videoStream
, INT64_MIN
, seek_target//* AV_TIME_BASE
, INT64_MAX
, 0);
//LOGI("seek: %d f=%ld pos=%lld st=%lld", res, frameNumber, (int64_t)pos, seek_target);
if (res >= 0) {
avcodec_flush_buffers(codecCtx);
// LOGI("flushed");
}
av_init_packet(packet);
AVFrame* frameRGB = avcodec_alloc_frame();
avcodec_get_frame_defaults(frameRGB);
enum PixelFormat pixel_format = PIX_FMT_RGBA;
avpicture_fill((AVPicture*) frameRGB
, (uint8_t*)buff
, pixel_format
, codecCtx->width
, codecCtx->height
);
while (av_read_frame(ctx, packet) == 0) {
LOGI("pts1=%lld st1=%lld", packet->pts, seek_target);
if (packet->stream_index == videoStream) {
int gotPicture = 0;
int bytesDecompressed = avcodec_decode_video2(codecCtx, frame, &gotPicture, packet);
if (gotPicture && packet->pts >= seek_target) {
// LOGI("opana");
// конвертируем данные из формата YUV в RGB24
struct SwsContext* scaleCtx = sws_getContext(frame->width,
frame->height,
(enum PixelFormat)frame->format
, width
, height
, pixel_format
, SWS_BICUBIC
, 0, 0, 0);
int height = sws_scale(scaleCtx
, frame->data
, frame->linesize
, 0
, frame->height
, frameRGB->data
, frameRGB->linesize);
break;
}
av_free_packet(packet);
}
}
//LOGI("ended");
av_free(frameRGB);
av_free(frame);
return 0;
}
static jobject globalRef;
jobject Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_allocNative(JNIEnv* env, jobject thiz, jlong size)
{
void* buffer = malloc(size);
jobject directBuffer = (*env)->NewDirectByteBuffer(env,buffer, size);
globalRef = (*env)->NewGlobalRef(env,directBuffer);
return globalRef;
}
void Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_freeNative(JNIEnv* env, jobject thiz)
{
void *buffer = (*env)->GetDirectBufferAddress(env,globalRef);
(*env)->DeleteGlobalRef(env,globalRef);
free(buffer);
LOGI("free1");
}
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
jint Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_getFrame2(JNIEnv *env, jobject thiz, thandle_file handleFile, jlong timeUS, jint width, jint height, jobject buffer) {
//LOGI("file= %d",handleFile);
AVFormatContext* ctx = ((struct thandle*)handleFile)->ctx;
AVCodecContext* codecCtx = ((struct thandle*)handleFile)->codecCtx;
AVPacket* packet = ((struct thandle*)handleFile)->packet;
int videoStream = ((struct thandle*)handleFile)->videoStream;
jshort* buff = (jshort*) (*env)->GetDirectBufferAddress(env, buffer);
AVFrame* frame = avcodec_alloc_frame(); //YUV frame
avcodec_get_frame_defaults(frame);
int frameNumber = timeUS;
//LOGI("avtb= %d",AV_TIME_BASE);
int64_t pos = frameNumber * AV_TIME_BASE / 1000000;
int64_t seek_target= av_rescale_q(pos, AV_TIME_BASE_Q, ctx->streams[videoStream]->time_base);
int res = avformat_seek_file(ctx
, videoStream
, INT64_MIN
, seek_target//* AV_TIME_BASE
, INT64_MAX
, 0);
//LOGI("seek: %d f=%ld pos=%lld st=%lld", res, frameNumber, (int64_t)pos, seek_target);
if (res >= 0) {
avcodec_flush_buffers(codecCtx);
//LOGI("flushed");
}
av_init_packet(packet);
AVFrame* frameRGB = avcodec_alloc_frame();
avcodec_get_frame_defaults(frameRGB);
enum PixelFormat pixel_format = PIX_FMT_RGBA;
avpicture_fill((AVPicture*) frameRGB
, (uint8_t*)buff
, pixel_format
, codecCtx->width
, codecCtx->height
);
while (av_read_frame(ctx, packet) == 0) {
LOGI("pts2=%lld st2=%lld", packet->pts, seek_target);
if (packet->stream_index == videoStream) {
int gotPicture = 0;
int bytesDecompressed = avcodec_decode_video2(codecCtx, frame, &gotPicture, packet);
//LOGI("pred_opana");
if (gotPicture && packet->pts >= seek_target) {
//LOGI("opana");
// конвертируем данные из формата YUV в RGB24
struct SwsContext* scaleCtx = sws_getContext(frame->width,
frame->height,
(enum PixelFormat)frame->format
, width
, height
, pixel_format
, SWS_BICUBIC
, 0, 0, 0);
int height = sws_scale(scaleCtx
, frame->data
, frame->linesize
, 0
, frame->height
, frameRGB->data
, frameRGB->linesize);
break;
}
av_free_packet(packet);
}
}
//LOGI("ended");
av_free(frameRGB);
av_free(frame);
return 0;
}
static jobject globalRef2;
jobject Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_allocNative2(JNIEnv* env, jobject thiz, jlong size)
{
void* buffer = malloc(size);
jobject directBuffer = (*env)->NewDirectByteBuffer(env,buffer, size);
globalRef2 = (*env)->NewGlobalRef(env,directBuffer);
return globalRef2;
}
void Java_artemxxl_projects_livewallpapercreator_FFMpegWrapper_freeNative2(JNIEnv* env, jobject thiz)
{
void *buffer = (*env)->GetDirectBufferAddress(env,globalRef2);
(*env)->DeleteGlobalRef(env,globalRef2);
free(buffer);
LOGI("free2");
}when I release memory in one of threads
that I receive an error from the secondhere logs :
02-26 17:44:21.680: I/com.domain.tag(855): initialize_passed
02-26 17:44:21.810: D/dalvikvm(855): GC_CONCURRENT freed 208K, 6% free 13183K/14023K, paused 14ms+8ms, total 37ms
02-26 17:44:21.810: D/AbsListView(855): [unregisterDoubleTapMotionListener]
02-26 17:44:21.810: I/MotionRecognitionManager(855): .unregisterListener : / listener count = 0->0, listener=android.widget.AbsListView$4@42cdcda0
02-26 17:44:21.810: W/CursorWrapperInner(855): Cursor finalized without prior close()
02-26 17:44:21.930: I/com.domain.tag(855): pts2=234133 st2=235160
02-26 17:44:21.945: V/ost(855): 0
02-26 17:44:21.945: V/sec(855): 1
02-26 17:44:21.945: V/start(855): 234627000
02-26 17:44:21.945: V/start(855): 234627
02-26 17:44:21.945: I/com.domain.tag(855): pts1=232098 st1=234627
02-26 17:44:21.960: I/com.domain.tag(855): pts2=233344 st2=235160
02-26 17:44:21.960: I/com.domain.tag(855): pts2=234166 st2=235160
02-26 17:44:21.975: I/com.domain.tag(855): pts1=231125 st1=234627
02-26 17:44:21.975: I/com.domain.tag(855): pts1=232131 st1=234627
02-26 17:44:21.985: I/com.domain.tag(855): pts2=234200 st2=235160
02-26 17:44:21.995: I/com.domain.tag(855): pts1=232164 st1=234627
02-26 17:44:22.010: I/com.domain.tag(855): pts2=234233 st2=235160
02-26 17:44:22.015: I/com.domain.tag(855): pts1=232198 st1=234627
02-26 17:44:22.030: I/com.domain.tag(855): pts2=234266 st2=235160
02-26 17:44:22.040: I/com.domain.tag(855): pts1=232231 st1=234627
02-26 17:44:22.055: I/com.domain.tag(855): pts2=234300 st2=235160
02-26 17:44:22.065: I/com.domain.tag(855): pts1=232264 st1=234627
02-26 17:44:22.075: I/com.domain.tag(855): pts2=234333 st2=235160
02-26 17:44:22.085: I/com.domain.tag(855): pts1=232298 st1=234627
02-26 17:44:22.100: I/com.domain.tag(855): pts2=234366 st2=235160
02-26 17:44:22.105: I/com.domain.tag(855): pts1=232331 st1=234627
02-26 17:44:22.120: I/com.domain.tag(855): pts2=234400 st2=235160
02-26 17:44:22.130: I/com.domain.tag(855): pts1=232365 st1=234627
02-26 17:44:22.145: I/com.domain.tag(855): pts2=233685 st2=235160
02-26 17:44:22.145: I/com.domain.tag(855): pts2=234433 st2=235160
02-26 17:44:22.150: I/com.domain.tag(855): pts1=232398 st1=234627
02-26 17:44:22.165: I/com.domain.tag(855): pts2=234467 st2=235160
02-26 17:44:22.175: I/com.domain.tag(855): pts1=231509 st1=234627
02-26 17:44:22.175: I/com.domain.tag(855): pts1=232431 st1=234627
02-26 17:44:22.185: I/com.domain.tag(855): pts2=234500 st2=235160
02-26 17:44:22.195: I/com.domain.tag(855): pts1=232465 st1=234627
02-26 17:44:22.210: I/com.domain.tag(855): pts2=234533 st2=235160
02-26 17:44:22.220: I/com.domain.tag(855): pts1=232498 st1=234627
02-26 17:44:22.230: I/com.domain.tag(855): pts2=234567 st2=235160
02-26 17:44:22.245: I/com.domain.tag(855): pts1=232531 st1=234627
02-26 17:44:22.250: I/com.domain.tag(855): pts2=234600 st2=235160
02-26 17:44:22.265: I/com.domain.tag(855): pts1=232565 st1=234627
02-26 17:44:22.275: I/com.domain.tag(855): pts2=234633 st2=235160
02-26 17:44:22.290: I/com.domain.tag(855): pts1=232598 st1=234627
02-26 17:44:22.295: I/com.domain.tag(855): pts2=234667 st2=235160
02-26 17:44:22.310: I/com.domain.tag(855): pts1=232631 st1=234627
02-26 17:44:22.325: I/com.domain.tag(855): pts2=234700 st2=235160
02-26 17:44:22.335: I/com.domain.tag(855): pts1=232665 st1=234627
02-26 17:44:22.345: I/com.domain.tag(855): pts2=234734 st2=235160
02-26 17:44:22.355: I/com.domain.tag(855): pts1=232698 st1=234627
02-26 17:44:22.365: I/com.domain.tag(855): pts2=234767 st2=235160
02-26 17:44:22.380: I/com.domain.tag(855): pts1=232732 st1=234627
02-26 17:44:22.390: I/com.domain.tag(855): pts2=234800 st2=235160
02-26 17:44:22.400: I/com.domain.tag(855): pts1=232765 st1=234627
02-26 17:44:22.415: I/com.domain.tag(855): pts2=234834 st2=235160
02-26 17:44:22.425: I/com.domain.tag(855): pts1=232798 st1=234627
02-26 17:44:22.440: I/com.domain.tag(855): pts2=234069 st2=235160
02-26 17:44:22.440: I/com.domain.tag(855): pts2=234867 st2=235160
02-26 17:44:22.450: I/com.domain.tag(855): pts1=231893 st1=234627
02-26 17:44:22.450: I/com.domain.tag(855): pts1=232832 st1=234627
02-26 17:44:22.460: I/com.domain.tag(855): pts2=234900 st2=235160
02-26 17:44:22.475: I/com.domain.tag(855): pts1=232865 st1=234627
02-26 17:44:22.485: I/com.domain.tag(855): pts2=234934 st2=235160
02-26 17:44:22.500: I/com.domain.tag(855): pts1=232898 st1=234627
02-26 17:44:22.510: I/com.domain.tag(855): pts2=234967 st2=235160
02-26 17:44:22.525: I/com.domain.tag(855): pts1=232932 st1=234627
02-26 17:44:22.530: I/com.domain.tag(855): pts2=235000 st2=235160
02-26 17:44:22.555: I/com.domain.tag(855): pts1=232965 st1=234627
02-26 17:44:22.555: I/com.domain.tag(855): pts2=235034 st2=235160
02-26 17:44:22.580: I/com.domain.tag(855): pts2=235067 st2=235160
02-26 17:44:22.580: I/com.domain.tag(855): pts1=232998 st1=234627
02-26 17:44:22.605: I/com.domain.tag(855): pts2=235101 st2=235160
02-26 17:44:22.610: I/com.domain.tag(855): pts1=233032 st1=234627
02-26 17:44:22.630: I/com.domain.tag(855): pts2=235134 st2=235160
02-26 17:44:22.635: I/com.domain.tag(855): pts1=233065 st1=234627
02-26 17:44:22.655: I/com.domain.tag(855): pts2=235167 st2=235160
02-26 17:44:22.660: I/com.domain.tag(855): pts1=233099 st1=234627
02-26 17:44:22.690: I/com.domain.tag(855): pts1=233132 st1=234627
02-26 17:44:22.705: D/dalvikvm(855): GC_FOR_ALLOC freed 434K, 10% free 12753K/14023K, paused 17ms, total 17ms
02-26 17:44:22.710: I/dalvikvm-heap(855): Grow heap (frag case) to 13.759MB for 786448-byte allocation
02-26 17:44:22.715: I/com.domain.tag(855): pts1=232234 st1=234627
02-26 17:44:22.715: I/com.domain.tag(855): pts1=233165 st1=234627
02-26 17:44:22.735: D/dalvikvm(855): GC_FOR_ALLOC freed 0K, 9% free 13521K/14855K, paused 25ms, total 25ms
02-26 17:44:22.735: I/com.domain.tag(855): pts1=233199 st1=234627
02-26 17:44:22.745: V/ttag(855): /storage/sdcard0/temp1/file8.png
02-26 17:44:22.755: D/dalvikvm(855): GC_CONCURRENT freed 2K, 9% free 13527K/14855K, paused 2ms+2ms, total 20ms
02-26 17:44:22.760: I/com.domain.tag(855): pts1=233232 st1=234627
02-26 17:44:22.785: I/com.domain.tag(855): pts1=233265 st1=234627
02-26 17:44:22.810: I/com.domain.tag(855): pts1=233299 st1=234627
02-26 17:44:22.835: I/com.domain.tag(855): pts1=233332 st1=234627
02-26 17:44:22.855: I/com.domain.tag(855): pts1=233366 st1=234627
02-26 17:44:22.880: I/com.domain.tag(855): pts1=233399 st1=234627
02-26 17:44:22.905: I/com.domain.tag(855): pts1=233432 st1=234627
02-26 17:44:22.955: I/com.domain.tag(855): pts1=233466 st1=234627
02-26 17:44:23.000: I/com.domain.tag(855): pts1=233499 st1=234627
02-26 17:44:23.030: I/com.domain.tag(855): pts1=232637 st1=234627
02-26 17:44:23.030: I/com.domain.tag(855): pts1=233532 st1=234627
02-26 17:44:23.060: I/com.domain.tag(855): pts1=233566 st1=234627
02-26 17:44:23.080: I/com.domain.tag(855): pts1=233599 st1=234627
02-26 17:44:23.105: I/com.domain.tag(855): free2
02-26 17:44:23.105: I/com.domain.tag(855): pts2=234133 st2=235227
02-26 17:44:23.115: I/com.domain.tag(855): pts1=233344 st1=234627
02-26 17:44:23.115: I/com.domain.tag(855): pts1=234166 st1=234627
02-26 17:44:23.140: I/com.domain.tag(855): pts2=234200 st2=235227
02-26 17:44:23.140: I/com.domain.tag(855): pts1=234233 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234266 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234300 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234333 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234366 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234400 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=233685 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234433 st1=234627
02-26 17:44:24.035: I/com.domain.tag(855): pts1=234467 st1=234627
02-26 17:44:24.040: I/com.domain.tag(855): pts1=234500 st1=234627
02-26 17:44:24.040: I/com.domain.tag(855): pts1=234533 st1=234627
02-26 17:44:24.040: I/com.domain.tag(855): pts1=234567 st1=234627
02-26 17:44:24.040: I/com.domain.tag(855): pts1=234600 st1=234627
02-26 17:44:24.040: I/com.domain.tag(855): pts1=234633 st1=234627
02-26 17:44:24.050: I/com.domain.tag(855): pts2=234667 st2=235227
02-26 17:44:24.055: V/ttag(855): 234627000
02-26 17:44:24.075: D/dalvikvm(855): GC_FOR_ALLOC freed 776K, 15% free 12755K/14855K, paused 21ms, total 21ms
02-26 17:44:24.075: I/com.domain.tag(855): pts2=234700 st2=235227
02-26 17:44:24.080: I/dalvikvm-heap(855): Grow heap (frag case) to 13.761MB for 786448-byte allocation
02-26 17:44:24.100: I/com.domain.tag(855): pts2=234734 st2=235227
02-26 17:44:24.110: D/dalvikvm(855): GC_CONCURRENT freed <1K, 9% free 13523K/14855K, paused 13ms+2ms, total 30ms
02-26 17:44:24.110: D/dalvikvm(855): WAIT_FOR_CONCURRENT_GC blocked 17ms
02-26 17:44:24.110: D/dalvikvm(855): WAIT_FOR_CONCURRENT_GC blocked 18ms
02-26 17:44:24.110: V/ttag(855): /storage/sdcard0/temp1/file0.png
02-26 17:44:24.135: I/com.domain.tag(855): pts2=234767 st2=235227
02-26 17:44:24.170: I/com.domain.tag(855): pts2=234800 st2=235227
02-26 17:44:24.195: I/com.domain.tag(855): pts2=234834 st2=235227
02-26 17:44:24.220: I/com.domain.tag(855): pts2=234069 st2=235227
02-26 17:44:24.220: I/com.domain.tag(855): pts2=234867 st2=235227
02-26 17:44:24.245: I/com.domain.tag(855): pts2=234900 st2=235227
02-26 17:44:24.275: I/com.domain.tag(855): pts2=234934 st2=235227
02-26 17:44:24.300: I/com.domain.tag(855): pts2=234967 st2=235227
02-26 17:44:24.325: I/com.domain.tag(855): pts2=235000 st2=235227
02-26 17:44:24.350: I/com.domain.tag(855): pts2=235034 st2=235227
02-26 17:44:24.380: I/com.domain.tag(855): pts2=235067 st2=235227
02-26 17:44:24.405: I/com.domain.tag(855): pts2=235101 st2=235227
02-26 17:44:24.430: I/com.domain.tag(855): pts2=235134 st2=235227
02-26 17:44:24.445: I/com.domain.tag(855): free1
02-26 17:44:24.445: V/ost(855): 1
02-26 17:44:24.445: V/sec(855): 1
02-26 17:44:24.445: V/start(855): 234627000
02-26 17:44:24.445: V/start(855): 234627
02-26 17:44:24.445: I/com.domain.tag(855): pts1=232098 st1=234694
02-26 17:44:24.445: I/com.domain.tag(855): pts1=231125 st1=234694
02-26 17:44:24.445: I/com.domain.tag(855): pts1=232131 st1=234694
02-26 17:44:24.455: I/com.domain.tag(855): pts1=232164 st1=234694
02-26 17:44:24.485: I/com.domain.tag(855): pts2=232198 st2=235227
02-26 17:44:24.715: I/com.domain.tag(855): pts1=232231 st1=234694
02-26 17:44:24.725: I/com.domain.tag(855): pts1=232264 st1=234694
02-26 17:44:24.725: I/com.domain.tag(855): pts1=232298 st1=234694
02-26 17:44:24.725: I/com.domain.tag(855): pts1=232331 st1=234694
02-26 17:44:24.725: I/com.domain.tag(855): pts1=232365 st1=234694
02-26 17:44:24.725: I/com.domain.tag(855): pts1=232398 st1=234694
02-26 17:44:24.730: I/com.domain.tag(855): pts1=231509 st1=234694
02-26 17:44:24.730: I/com.domain.tag(855): pts1=232431 st1=234694
02-26 17:44:24.730: I/com.domain.tag(855): pts1=232465 st1=234694
02-26 17:44:24.730: I/com.domain.tag(855): pts1=232498 st1=234694
02-26 17:44:24.750: I/com.domain.tag(855): pts2=232531 st2=235227
02-26 17:44:24.960: I/com.domain.tag(855): pts1=232565 st1=234694
02-26 17:44:24.960: I/com.domain.tag(855): pts1=232598 st1=234694
02-26 17:44:24.960: I/com.domain.tag(855): pts1=232631 st1=234694
02-26 17:44:24.960: I/com.domain.tag(855): pts1=232665 st1=234694
02-26 17:44:24.965: I/com.domain.tag(855): pts1=232698 st1=234694
02-26 17:44:24.965: I/com.domain.tag(855): pts1=232732 st1=234694
02-26 17:44:24.965: I/com.domain.tag(855): pts1=232765 st1=234694
02-26 17:44:24.965: I/com.domain.tag(855): pts1=232798 st1=234694
02-26 17:44:24.980: I/com.domain.tag(855): pts2=231893 st2=235227
02-26 17:44:24.980: I/com.domain.tag(855): pts2=232832 st2=235227
02-26 17:44:25.210: I/com.domain.tag(855): pts1=232865 st1=234694
02-26 17:44:25.210: I/com.domain.tag(855): pts1=232898 st1=234694
02-26 17:44:25.210: I/com.domain.tag(855): pts1=232932 st1=234694
02-26 17:44:25.210: I/com.domain.tag(855): pts1=232965 st1=234694
02-26 17:44:25.210: I/com.domain.tag(855): pts1=232998 st1=234694
02-26 17:44:25.230: I/com.domain.tag(855): pts2=233032 st2=235227
02-26 17:44:25.245: I/com.domain.tag(855): pts1=233065 st1=234694
02-26 17:44:25.260: I/com.domain.tag(855): pts2=233099 st2=235227
02-26 17:44:25.715: I/com.domain.tag(855): pts1=233132 st1=234694
02-26 17:44:25.725: I/com.domain.tag(855): pts1=232234 st1=234694
02-26 17:44:25.725: I/com.domain.tag(855): pts1=233165 st1=234694
02-26 17:44:25.730: I/com.domain.tag(855): pts1=233199 st1=234694
02-26 17:44:25.735: I/com.domain.tag(855): pts1=233232 st1=234694
02-26 17:44:25.740: I/com.domain.tag(855): pts1=233265 st1=234694
02-26 17:44:25.740: I/com.domain.tag(855): pts1=233299 st1=234694
02-26 17:44:25.745: I/com.domain.tag(855): pts1=233332 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233366 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233399 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233432 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233466 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233499 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=232637 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233532 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233566 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233599 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233632 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233666 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233699 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233733 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233766 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233799 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=232970 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233833 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233866 st1=234694
02-26 17:44:25.755: I/com.domain.tag(855): pts1=233899 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=233933 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=233966 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=233999 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234033 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234066 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234100 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234133 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=233344 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234166 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234200 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234233 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234266 st1=234694
02-26 17:44:25.760: I/com.domain.tag(855): pts1=234300 st1=234694
02-26 17:44:25.775: I/com.domain.tag(855): pts2=234333 st2=235227
02-26 17:44:26.115: I/com.domain.tag(855): pts1=234366 st1=234694
02-26 17:44:26.120: I/com.domain.tag(855): pts1=234400 st1=234694
02-26 17:44:26.120: I/com.domain.tag(855): pts1=233685 st1=234694
02-26 17:44:26.120: I/com.domain.tag(855): pts1=234433 st1=234694
02-26 17:44:26.120: I/com.domain.tag(855): pts1=234467 st1=234694
02-26 17:44:26.125: I/com.domain.tag(855): pts1=234500 st1=234694
02-26 17:44:26.125: I/com.domain.tag(855): pts1=234533 st1=234694
02-26 17:44:26.125: I/com.domain.tag(855): pts1=234567 st1=234694
02-26 17:44:26.125: I/com.domain.tag(855): pts1=234600 st1=234694
02-26 17:44:26.130: I/com.domain.tag(855): pts1=234633 st1=234694
02-26 17:44:26.130: I/com.domain.tag(855): pts1=234667 st1=234694
02-26 17:44:26.130: I/com.domain.tag(855): pts1=234700 st1=234694
02-26 17:44:26.135: I/com.domain.tag(855): pts2=234734 st2=235227
02-26 17:44:26.135: V/ttag(855): 234693666
02-26 17:44:26.160: D/dalvikvm(855): GC_FOR_ALLOC freed 781K, 15% free 12756K/14855K, paused 21ms, total 21ms
02-26 17:44:26.160: I/dalvikvm-heap(855): Grow heap (frag case) to 13.761MB for 786448-byte allocation
02-26 17:44:26.165: I/com.domain.tag(855): pts2=234767 st2=235227
02-26 17:44:26.175: D/dalvikvm(855): GC_CONCURRENT freed <1K, 9% free 13523K/14855K, paused 2ms+2ms, total 16ms
02-26 17:44:26.175: D/dalvikvm(855): WAIT_FOR_CONCURRENT_GC blocked 14ms
02-26 17:44:26.175: D/dalvikvm(855): WAIT_FOR_CONCURRENT_GC blocked 14ms
02-26 17:44:26.180: V/ttag(855): /storage/sdcard0/temp1/file1.png
02-26 17:44:26.185: A/libc(855): @@@ ABORTING: HEAP MEMORY CORRUPTION IN tmalloc_large addr=0x0008fffb
02-26 17:44:26.185: A/libc(855): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 2047 (AsyncTask #1)in what my error ?
-
How to Check Website Traffic As Accurately As Possible
18 août 2023, par Erin — Analytics TipsIf you want to learn about the health of your website and the success of your digital marketing initiatives, there are few better ways than checking your website traffic.
It’s a great way to get a quick dopamine hit when things are up, but you can also use traffic levels to identify issues, learn more about your users or benchmark your performance. That means you need a reliable and easy way to check your website traffic over time — as well as a way to check out your competitors’ traffic levels, too.
In this article, we’ll show you how to do just that. You’ll learn how to check website traffic for both your and your competitor’s sites and discover why some methods of checking website traffic are better than others.
Why check website traffic ?
Dopamine hits aside, it’s important to constantly monitor your website’s traffic for several reasons.
Benchmark site performance
Keeping regular tabs on your traffic levels is a great way to track your website’s performance over time. It can help you plan for the future or identify problems.
For instance, growing traffic levels may mean expanding your business’s offering or investing in more inventory. On the flip side, decreasing traffic levels may suggest it’s time to revamp your marketing strategies or look into issues impacting your SEO.
Analyse user behaviour
Checking website traffic and user behaviour lets marketing managers understand how users interact with your website. Which pages are they visiting ? Which CTAs do they click on ? What can you do to encourage users to take the actions you want ? You can also identify issues that lead to high bounce rates and other problems.
The better you understand user behaviour, the easier it will be to give them what they want. For example, you may find that users spend more time on your landing pages than they do your blog pages. You could use that information to revise how you create blog posts or focus on creating more landing pages.
Improve the user experience
Once you understand how users behave on your website, you can use that information to fix errors, update your content and improve the user experience for the site.
You can even personalise the experience for customers, leading to significant growth. Research shows companies that grow faster derive 40% more of their revenue from personalisation.
That could come in the form of sweeping personalisations — like rearranging your website’s navigation bar based on user behaviour — or individual personalisation that uses analytics to transform sections or entire pages of your site based on user behaviour.
Optimise marketing strategies
You can use website traffic reports to understand where users are coming from and optimise your marketing plan accordingly. You may want to double down on organic traffic, for instance, or invest more in PPC advertising. Knowing current traffic estimates and how these traffic levels have trended over time can help you benchmark your campaigns and prioritise your efforts.
Increasing traffic levels from other countries can also help you identify new marketing opportunities. If you start seeing significant traffic levels from a neighbouring country or a large market, it could be time to take your business international and launch a cross-border campaign.
Filter unwanted traffic
A not-insignificant portion of your site’s traffic may be coming from bots and other unwanted sources. These can compromise the quality of your analytics and make it harder to draw insights. You may not be able to get rid of this traffic, but you can use analytics tools to remove it from your stats.
How to check website traffic on Matomo
If you want to check your website’s traffic, you’d be forgiven for heading to Google Analytics first. It’s the most popular analytics tool on the market, after all. But if you want a more reliable assessment of your website’s traffic, then we recommend using Matomo alongside Google Analytics.
The Matomo web analytics platform is an open-source solution that helps you collect accurate data about your website’s traffic and make more informed decisions as a result — all while enhancing the customer experience and ensuring GDPR compliance and user privacy.
Matomo also offers multiple ways to check website traffic :
Let’s look at all of them one by one.
The visits log report is a unique rundown of all of the individual visitors to your site. This offers a much more granular view than other tools that just show the total number of visitors for a given period.
You can access the visits log report by clicking on the reporting menu, then clicking Visitor and Visits Log. From there, you’ll be able to scroll through every user session and see the following information :
- The location of the user
- The total number of actions they took
- The length of time on site
- How they arrived at your site
- And the device they used to access your site
This may be overwhelming if your site receives thousands of visitors at a time. But it’s a great way to understand users at an individual level and appreciate the lifetime activity of specific users.
The Real-time visitor map is a visual display of users’ location for a given timeframe. If you have an international website, it’s a fantastic way to see exactly where in the world your traffic comes from.
You can access the Real-time Visitor Map by clicking Visitor in the main navigation menu and then Real-time Map. The map itself is colour-coded. Larger orange bubbles represent recent visits, and smaller dark orange and grey bubbles represent older visits. The map will refresh every five seconds, and new users appear with a flashing effect.
If you run TV or radio adverts, Matomo’s Real-time Map provides an immediate read on the effectiveness of your campaign. If your map lights up in the minutes following your ad, you know it’s been effective. It can also help you identify the source of bot attacks, too.
Finally, the Visits in Real-time report provides a snapshot of who is browsing your website. You can access this report under Visitors > Real-time and add it to your custom dashboards as a widget.
Open the report, and you’ll see the real-time flow of your site’s users and counters for visits and pageviews over the last 30 minutes and 24 hours. The report refreshes every five seconds with new users added to the top of the report with a fade-in effect.
The report provides a snapshot of each visitor, including :
- Whether they are new or a returning
- Their country
- Their browser
- Their operating system
- The number of actions they took
- The time they spent on the site
- The channel they came in from
- Whether the visitor converted a goal
3 other ways to check website traffic
You don’t need to use Matomo to check your website traffic. Here are three other tools you can use instead.
How to check website traffic on Google Analytics
Google Analytics is usually the first starting point for anyone looking to check their website traffic. It’s free to use, incredibly popular and offers a wide range of traffic reports.
Google Analytics lets you break down historical traffic data almost any way you wish. You can split traffic by acquisition channel (organic, social media, direct, etc.) by country, device or demographic.
It also provides real-time traffic reports that give you a snapshot of users on your site right now and over the last 30 minutes.
Google Analytics may be one of the most popular ways to check website traffic, but it could be better. Google Analytics 4 is difficult to use compared to its predecessor, and it also limits the amount of data you can track in accordance with privacy laws. If users refuse your cookie consent, Google Analytics won’t record these visits. In other words, you aren’t getting a complete view of your traffic by using Google Analytics alone.
That’s why it’s important to use Google Analytics alongside other web analytics tools (like Matomo) that don’t suffer from the same privacy issues. That way, you can make sure you track every single user who visits your site.
How to check website traffic on Google Search Console
Google Search Console is a free tool from Google that lets you analyse the search traffic that your site gets from Google.
The top-line report shows you how many times your website has appeared in Google Search, how many clicks it has received, the average clickthrough rate and the average position of your website in the search results.
Google Search Console is a great way to understand what you rank for and how much traffic your organic rankings generate. It will also show you which pages are indexed in Google and whether there are any crawling errors.
Unfortunately, Google Search Console is limited if you want to get a complete view of your traffic. While you can analyse search traffic in a huge amount of detail, it will not tell you how users who access your website directly or via social media behave.
How to check website traffic on Similarweb
Similarweb is a website analysis tool that estimates the total traffic of any site on the internet. It is one of the best tools for estimating how much traffic your competitors receive.
What’s great about Similarweb is that it estimates total traffic, not just traffic from search engines like many SEO tools. It even breaks down traffic by different channels, allowing you to see how your website compares against your competitors.
As you can see from the image above, Similarweb provides an estimate of total visits, bounce rate, the average number of pages users view per visit and the average duration on the site. The company also has a free browser extension that lets you check website traffic estimates as you browse the web.
You can use Similarweb for free to a point. But to really get the most out of this tool, you’ll need to upgrade to a premium plan which starts at $125 per user per month.
The price isn’t the only downside of using Similarweb to check the traffic of your own and your competitor’s websites. Ultimately, Similarweb is only an estimate — even if it’s a reasonably accurate one — and it’s no match for a comprehensive analytics tool.
7 website traffic metrics to track
Now that you know how to check your website’s traffic, you can start to analyse it. You can use plenty of metrics to assess the quality of your website traffic, but here are some of the most important metrics to track.
- New visitors : These are users who have never visited your website before. They are a great sign that your marketing efforts are working and your site is reaching more people. But it’s also important to track how they behave on the website to ensure your site caters effectively to new visitors.
- Returning visitors : Returning visitors are coming back to your site for a reason : either they like the content you’re creating or they want to make a purchase. Both instances are great. The more returning visitors, the better.
- Bounce rate : This is a measure of how many users leave your website without taking action. Different analytics tools measure this metric differently.
- Session duration : This is the length of time users spend on your website, and it can be a great gauge of whether they find your site engaging. Especially when combined with the metric below.
- Pages per session : This measures how many different pages users visit on average. The more pages they visit and the longer users spend on your website, the more engaging it is.
- Traffic source : Traffic can come from a variety of sources (organic, direct, social media, referral, etc.) Tracking which sources generate the most traffic can help you analyse and prioritise your marketing efforts.
- User demographics : This broad metric tells you more about who the users are that visit your website, what device they use, what country they come from, etc. While the bulk of your website traffic will come from the countries you target, an influx of new users from other countries can open the door to new opportunities.
Why do my traffic reports differ ?
If you use more than one of the methods above to check your website traffic, you’ll quickly realise that every traffic report differs. In some cases, the reasons are obvious. Any tool that estimates your traffic without adding code to your website is just that : an estimate. Tools like Similarweb will never offer the accuracy of analytics platforms like Matomo and Google Analytics.
But what about the differences between these analytics platforms themselves ? While each platform has a different way of recording user behaviour, significant differences in website traffic reports between analytics platforms are usually a result of how each platform handles user privacy.
A platform like Google Analytics requires users to accept a cookie consent banner to track them. If they accept, great. Google collects all of the data that any other analytics platform does. It may even collect more. If users reject cookie consent banners, however, then Google Analytics can’t track these visitors at all. They simply won’t show up in your traffic reports.
That doesn’t happen with all analytics platforms, however. A privacy-focused alternative like Matomo doesn’t require cookie consent banners (apart from in the United Kingdom and Germany) and can therefore continue to track visitors even after they have rejected a cookie consent screen from Google Analytics. This means that virtually all of your website traffic will be tracked regardless of whether users accept a cookie consent banner or not. And it’s why traffic reports in Matomo are often much higher than they are in Google Analytics.
Given that around half (47.32%) of adults in the European Union refuse to allow the use of personal data tracking for advertising purposes and that 95% of people will reject additional cookies when it is easy to do so, this means you could have vastly different traffic reports — and be missing out on a significant amount of user data.
If you’re serious about using web analytics to improve your website and optimise your marketing campaigns, then it is essential to use another analytics platform alongside Google Analytics.
Get more accurate traffic reports with Matomo
There are several methods to check website traffic. Some, like Similarweb, can provide estimates on your competitors’ traffic levels. Others, like Google Analytics, are free. But data doesn’t lie. Only privacy-focused analytics solutions like Matomo can provide accurate reports that account for every visitor.
Join over one million organisations using Matomo to accurately check their website traffic. Try it for free alongside GA today. No credit card required.
Syndiquer tout le site
