2016 – coding improvements continue. This in the past would mean more feature enhancements but nowadays it means less and less is more.
APIs are constantly updating so I have been tweaking the code to work best with a bunch of third party media suppliers and their APIs. A more stable qued is the result.
I am looking to divorce the dataset from the database, or at least make it an option. Example (in text form). Build a set of cuepoints for a given piece of media. save the data set in Timed Text or SubViewer formay. Then allowing for the reimporting of the data set at a later date on another site like YouTube. So you would be correct in thinking qued allows the last bit to happen! Export we have, but what about import back into qued? Nope. This is going into the road map so data is free and im/ex/portable.
MixCloud | SoundCloud | AudioBoo(m) – yep I want to add them as sources. More code. MixCloud has the API need to investigate the others.
In 2016 I will be partnering with radio stations and using qued as an archiving solution. Who want to know what is in their archive and to me able to mine it fast?
Lastly for now an experimental viewer for qued in the making – demo page