- 01 2月, 2015 2 次提交
-
-
由 Radzaquiel 提交于
(Updated from Hitbox API's list) All cities/countries written Changed: EU-North Added: Russia, US-Central, South Korea, China & Oceania
-
由 Gol-D-Ace 提交于
-
- 28 10月, 2014 1 次提交
-
-
由 Gol-D-Ace 提交于
Server doesn't exist anymore https://api.twitch.tv/kraken/ingests http://blog.twitch.tv/2014/09/service-update-chicago-point-of-presence-closure/
-
- 21 8月, 2014 1 次提交
-
-
由 Derrick Lambert 提交于
-
- 19 7月, 2014 1 次提交
-
-
由 BtbN 提交于
Completely removes the build dir in favor of cmake based build layouting
-
- 24 4月, 2014 1 次提交
-
-
由 jp9000 提交于
- Updated the services API so that it links up with an output and the output gets data from that service rather than via settings. This allows the service context to have control over how an output is used, and makes it so that the URL/key/etc isn't necessarily some static setting. Also, if the service is attached to an output, it will stick around until the output is destroyed. - The settings interface has been updated so that it can allow the usage of service plugins. What this means is that now you can create a service plugin that can control aspects of the stream, and it allows each service to create their own user interface if they create a service plugin module. - Testing out saving of current service information. Saves/loads from JSON in to obs_data_t, seems to be working quite nicely, and the service object information is saved/preserved on exit, and loaded again on startup. - I agonized over the settings user interface for days, and eventually I just decided that the only way that users weren't going to be fumbling over options was to split up the settings in to simple/basic output, pre-configured, and then advanced for advanced use (such as multiple outputs or services, which I'll implement later). This was particularly painful to really design right, I wanted more features and wanted to include everything in one interface but ultimately just realized from experience that users are just not technically knowledgable about it and will end up fumbling with the settings rather than getting things done. Basically, what this means is that casual users only have to enter in about 3 things to configure their stream: Stream key, audio bitrate, and video bitrate. I am really happy with this interface for those types of users, but it definitely won't be sufficient for advanced usage or for custom outputs, so that stuff will have to be separated. - Improved the JSON usage for the 'common streaming services' context, I realized that JSON arrays are there to ensure sorting, while forgetting that general items are optimized for hashing. So basically I'm just using arrays now to sort items in it.
-
- 20 4月, 2014 1 次提交
-
-
由 jp9000 提交于
This plugin is just a generic service plugin for basic RTMP streaming service stuff. This just has a 'common' service that has a list of common/simple streaming services that don't have their own custom service modules, and then a 'custom' service that allows you to enter in the stream URL and key manually, without a service/server list. Also, copy the jansson VS projects file (don't modify the old one) so that it's located in the vs/2013 directory, so that other libraries can properly link with it without having to enter in extra information just to include jansson
-