Sigh...
I don't want to say i told you so but, i told you so.
You cannot guess what i want. Period. End of sentence.
Scanned Episode 1 and chose the 9000kbps:
Scanned Episodes Individually and chose based on file size and runtime:
Like i have said before several times, the reported bitrate names/labels are completely wrong. They used to be somewhat accurate but not anymore.
I am assuming the "logic" implemented looks at the label to determine the closest bitrate but Amazon will label something 9000kbps when it is actually 1831kbps.
Episode 1, 9000kbps gives us a video size of 633 MB @ 1831kbps
Episode 2, 9000kbps gives us a video size of 1.42GB @ 3962kbps
Episode 3, 9000kbps gives us a video size of 617 MB @ 1842kbps
Episode 4, 9000kbps gives us a video size of 777 MB @ 2274kbps
Episode 5, 9000kbps gives us a video size of 537 MB @ 1654kbps
Episode 6, 9000kbps gives us a video size of 579 MB @ 1456kbps
In order to get Episode 2 at a size more consistent with the others, i had to choose 4000kbps which gave a video size of 546 MB @ 1483kbps.
That means if the devs insist on implementing this "feature", they need to use the file size instead of the bitrate unless they can get the REAL bitrate.
But then this opens the door to have another issue: What if all episodes are 45 minutes and you have 2 of them that are 90 minutes? You can rely on the size and you can't rely on the current bitrates. What is gonna happen then?
This won't be an issue if you give us what we are clamoring for: Individual Episode Analysis inside StreamFab.
This becoming comical. Only i am not laughing.
I don't want to say i told you so but, i told you so.
You cannot guess what i want. Period. End of sentence.
Scanned Episode 1 and chose the 9000kbps:
Scanned Episodes Individually and chose based on file size and runtime:
Like i have said before several times, the reported bitrate names/labels are completely wrong. They used to be somewhat accurate but not anymore.
I am assuming the "logic" implemented looks at the label to determine the closest bitrate but Amazon will label something 9000kbps when it is actually 1831kbps.
Episode 1, 9000kbps gives us a video size of 633 MB @ 1831kbps
Episode 2, 9000kbps gives us a video size of 1.42GB @ 3962kbps
Episode 3, 9000kbps gives us a video size of 617 MB @ 1842kbps
Episode 4, 9000kbps gives us a video size of 777 MB @ 2274kbps
Episode 5, 9000kbps gives us a video size of 537 MB @ 1654kbps
Episode 6, 9000kbps gives us a video size of 579 MB @ 1456kbps
In order to get Episode 2 at a size more consistent with the others, i had to choose 4000kbps which gave a video size of 546 MB @ 1483kbps.
That means if the devs insist on implementing this "feature", they need to use the file size instead of the bitrate unless they can get the REAL bitrate.
But then this opens the door to have another issue: What if all episodes are 45 minutes and you have 2 of them that are 90 minutes? You can rely on the size and you can't rely on the current bitrates. What is gonna happen then?
This won't be an issue if you give us what we are clamoring for: Individual Episode Analysis inside StreamFab.
This becoming comical. Only i am not laughing.
Comment