[GH-ISSUE #108] Windows explorer thinks that the exported .ogg files are at 1411 kbps, when they are actually at 320 kbps #97

Closed
opened 2026-02-27 15:48:15 +03:00 by kerem · 1 comment
Owner

Originally created by @wayfarren on GitHub (Jun 26, 2024).
Original GitHub issue: https://github.com/Rafiuth/Soggfy/issues/108

I'm using the default configuration, and I have the output format set to "Original OGG", thinking this would give me the highest quality. It seems it did, and when running the exported track through Spek, it shows that the track is 320kbps.

This is fine, but I fear the file may be much larger than it needs to be as a result. I'm a noob to audio stuff (like encoding) so bear with me, but I'm wondering if I can get the file any smaller (like bumping it down to 320kbps from 1411kbps) while keeping (even though the bitrate is technically at 320kbps) the maximum quality.

Or, is this already the smallest the file can be at the given audio quality of 320kbps, and windows explorer is just being weird?

Originally created by @wayfarren on GitHub (Jun 26, 2024). Original GitHub issue: https://github.com/Rafiuth/Soggfy/issues/108 I'm using the default configuration, and I have the output format set to "Original OGG", thinking this would give me the highest quality. It seems it did, and when running the exported track through [Spek](https://www.spek.cc/p/download), it shows that the track is 320kbps. This is fine, but I fear the file may be much larger than it needs to be as a result. I'm a noob to audio stuff (like encoding) so bear with me, but I'm wondering if I can get the file any smaller (like bumping it down to 320kbps from 1411kbps) while keeping (even though the bitrate is technically at 320kbps) the maximum quality. Or, is this already the smallest the file can be at the given audio quality of 320kbps, and windows explorer is just being weird?
kerem closed this issue 2026-02-27 15:48:16 +03:00
Author
Owner

@Rafiuth commented on GitHub (Sep 14, 2024):

This is a bug in windows explorer, yes. For some reason they show the bitrate as if the files were uncompressed in some cases.

<!-- gh-comment-id:2350727308 --> @Rafiuth commented on GitHub (Sep 14, 2024): This is a bug in windows explorer, yes. For some reason they show the bitrate as if the files were uncompressed in some cases.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Soggfy#97
No description provided.