-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bitdepth
, samplingrate
and channelCount
optional fields
#83
Conversation
✅ Deploy Preview for opensubsonic ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
We did not fully finished that discussion, we should also expose channelCount. Field doc should be more precise about the field values (with example in the doc to explain that it's full sample rate 44100 and no 44.1). Like enforced lowercase, and decide if it's the full codec codes from ffmpeg or only the short usual ones. (full codec would be better) |
Ops, sorry. Thank you |
The discussion can continue here it often works like that to finalize the details, without a PR people stops talking :p |
Indeed we can add channelCount in this PR, but I would discuss codec/format related info in another PR as it is not straightforward |
I think we should publish a list of well-known codec values, and try to be fairly extensive, whether we do the short-form or the long-form codec strings. (And I'd probably suggest the short-form, because that's what already is used de-facto for the "format" arg to the stream endpoint) |
@dweymouth @epoupon @Tolriq will we update the discussion, or can we collect the 'missing' information here in this PR? |
If this is agreed, I can remove the "codec" entries from this PR and leave this aspect for another one. |
Let's return to the discussion for codec, but it's up to you @GioF71 if you want to do this PR without codec, or let it sit until we come to an agreement on how we want to handle codec |
I would say that all the data is related and that for a server to store and expose most of the data the codec will be extracted at the same time, it's better if how it should be exposed is defined at the same time to avoid some chosing something that won't work with a future decision. |
ok I'll leave the "codec" fields, and will update the rest according to the discussion. |
Taglib can extract channel count, bitdepth and sampling rate out of the box, but this is more tricky to get exact info on formats and codecs used. |
Codec and transcoding format are unrelated as not clear enough, the format param is more container than codec. The codecs will be used in the future transcoding API as the formats/ container |
Not quite sure what you mean by this? Are you saying the client will execute something like |
To be defined, but the idea is the client says I support that that that and that with contraints on things. Then server returns either the file can be direct played or should be transcoded with x and t param. |
is this consistent with the transcodedContentType, transcodedSuffix fields that we have already? |
This would serve a different purpose as the contentType and extension fields are very non-specific about the actual codec/container. (eg there is no specific contentType for Apple Lossless, most servers would probably report |
Ok so since there's no movement on this one, let's remove the codec part and expose bitDepth, samplingRate and channelCount? Would still be nice to continue the work on the codec/container/full codec ones. |
I agree. Edit: some -> some time |
Fine for me! |
1257989
to
67282e7
Compare
Ok, I have removed the last commit, which added the codec field, so we are back with only samplingRate and bitDepth. |
Can you add the requested |
Sorry, I missed that. I will update asap. |
67282e7
to
ac2d9ab
Compare
ac2d9ab
to
c0e23a9
Compare
Field |
bitdepth
, samplingrate
and codec
optional fieldsbitdepth
, samplingrate
and channelCount
optional fields
Small @dweymouth ping before merging just in case. |
Hello, this is related to this discussion.
Thank you for your attention.