You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently it is required to use a set of complicated functions to transfer the ownership between AudioFile and MemRef. It's not intuitive for end users.
Describe the solution you'd like
Integrate AudioFile functions to AudioContainer. It requires heavy rework for all AudioFile functions, but the integration would be much better and no ownership transformation is needed. We may use a modular design, like custom loaders and savers for AudioContainer, thus the actually encoding and decoding functions could be added at any time.
Describe alternatives you've considered
Let both of AudioFile and MemRef hold the pointer, then AudioContainer holds them both. Since they have similiar life cycle, this method is feasible and doesn't require much rework.
Repair the function to handover ownership. Currently this function can be invoked only once. If encapsulated well, the user could use getMemRef and getAudioFile for unlimited times. This requires the least rework, but it would not be so intuitive for future developers.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently it is required to use a set of complicated functions to transfer the ownership between AudioFile and MemRef. It's not intuitive for end users.
Describe the solution you'd like
AudioFile
functions toAudioContainer
. It requires heavy rework for allAudioFile
functions, but the integration would be much better and no ownership transformation is needed. We may use a modular design, like custom loaders and savers for AudioContainer, thus the actually encoding and decoding functions could be added at any time.Describe alternatives you've considered
AudioFile
andMemRef
hold the pointer, thenAudioContainer
holds them both. Since they have similiar life cycle, this method is feasible and doesn't require much rework.getMemRef
andgetAudioFile
for unlimited times. This requires the least rework, but it would not be so intuitive for future developers.The text was updated successfully, but these errors were encountered: