window breakage auto session?

Post Reply
frankie
Posts: 14
Joined: Fri Apr 23, 2021 7:06 am

I am using auto session with a segmentation algorithm to detect event in my audio file captured from Quick Feather board. But no matter what segmentation algorithm I used, the accuracy in auto sense result is below 60%. I tried to label the segments manually and use generate auto session to get customized algorithm by training DCL with example events.

But it doesn't work, no idea how to do for the next with limited log message.
I think the root cause is segmentation algorithm has limited maximum segment samples to 8192?!
1-1.jpg
1-1.jpg (239.64 KiB) Viewed 71971 times
1-2.jpg
1-2.jpg (119.78 KiB) Viewed 71971 times
1-3.jpg
1-3.jpg (83.04 KiB) Viewed 71971 times
Tolido848
Posts: 1
Joined: Wed Jul 31, 2024 7:27 am

Increase Segment Length: If the segmentation algorithm is limited to 8192 samples, try increasing the segment length if possible. This might help capture more context and improve accuracy.
Data Augmentation: Use data augmentation techniques to artificially increase the size and variability of your training dataset. This can help the algorithm generalize better to new data banana game
Algorithm Tuning: Experiment with different hyperparameters and configurations of your segmentation algorithm. Sometimes, small adjustments can lead to significant improvements in performance
To play banana game, you need to know the word "clicker"
JoshuaHolland
Posts: 1
Joined: Sat Jan 31, 2026 6:35 am

I totally understand the frustration with low accuracy rates-audio segmentation can be tricky, especially with limited sample sizes. The 8192 segment limit you mentioned could definitely be a bottleneck. Have you tried experimenting with different audio preprocessing techniques before feeding data to the algorithm? Also, manual labeling for custom training is a solid approach, but make sure your training set is diverse enough. If you're exploring audio-related projects, tools like Heardle can actually help you understand how audio recognition works. Keep iterating with your DCL training-sometimes small adjustments to parameters make a big difference!
Post Reply