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
In other words, allow the ability to restrict an audiotrack to playing only assets that have a certain tag or set of tags. Lots of aesthetic possibilities for things like adjusting the frequency of field recording assets in relation to spoken assets. This would arguably be particularly useful for non-geo-listen projects, but I think it would be useful all-around as well.
Server Requirements
add new optional ManyToManyField called audiotrack.tag_filters
update admin to handle new field
update all api/2/audiotracks/ requests accordingly
update documentation
The text was updated successfully, but these errors were encountered:
Yes! And when we have the ability to have different ranges/zones for each asset (rather than just the simplistic asset center and project-level radius), then we can really start doing some awesome aesthetic stuff!
Now that we are finally moving towards client-side mixing, the only work that needs to be done on the server is adding the audiotrack.tag_filters stuff.
The actual filtering mechanism will be built in roundware-ios-framework-v2, so I will handle that there.
In other words, allow the ability to restrict an audiotrack to playing only assets that have a certain tag or set of tags. Lots of aesthetic possibilities for things like adjusting the frequency of field recording assets in relation to spoken assets. This would arguably be particularly useful for non-geo-listen projects, but I think it would be useful all-around as well.
Server Requirements
ManyToManyField
calledaudiotrack.tag_filters
api/2/audiotracks/
requests accordinglyThe text was updated successfully, but these errors were encountered: