Streaming integration - design doc

[Michał Bejda]

https://docs.google.com/document/d/1n3x4pDkB_lrbDZM9rMxTBuTCIG9cUE4ytM05qPKYLU4/edit

[Michał Bejda]

Blog posts: http://fsstreamingproject.blogspot.com

W dniu niedziela, 20 stycznia 2013 19:06:11 UTC+1 użytkownik Michał Bejda napisał:

https://docs.google.com/document/d/1n3x4pDkB_lrbDZM9rMxTBuTCIG9cUE4ytM05qPKYLU4/edit

[Thanh Ha]

Thanks Michał,

One thing that might help on your blog is if you post a screenshot of
your work in progress regarding the settings. This way people can give
better feedback on the layout.


Thanh

2013/2/2 Michał Bejda <mbe...@gmail.com>:

> --
> View this group at https://groups.google.com/group/freeseer
> To post to this group via email, send email to free...@googlegroups.com
> To unsubscribe from this group, send email to
> freeseer+u...@googlegroups.com
>
>

[Jakub Adamek]

Hi, I published some screenshots - hopefully you'll get the idea of what we're aiming for.

I'm not good at UI, so for my part all feedback is great :)

Thanks, Jakub

[Thanh Ha]

One quick suggestion I have is for "Audio Codec" to move the settings
button next to the drop down on the right. The UI in my opinion would
flow a little better.

For the codec settings I think you are exposing too many options.
Maybe we could give some thought on what are most useful and expose
those in a simplified settings and add an advanced button to expose
the rest. Only the most hardcore users would even know what many of
those options mean. Most regular users would be confused.

For things like bitrate, quality, etc... which most likely have a set
range I wouild use a spin box and limit the user input to the range
specified in the docs for those codecs. Also for things like bitrate
it's good to indicate the units since it's confusing if the user has
to guess what units are in. Typically for bitrate I like to make it
increments of "kb" rather than bytes since people are not very likely
to be fine tuning it to specific bytes.

Things where there's likely preselected options, it's not good to make
to make it a freeform text box where the user could type in invalid
data. Like if the only options are "option-1", "option-2", etc... than
make it a dropdown and only allow them to select said options.

The other one is true/false options where there's only 2 possible
states, then those ones you want to make it a simple checkbox.


Also many codecs share similar or the same config options, bitrate is
a good example here. Since lame, faac, vorbis, etc... all have audio
bitrate settings, you could make bitrate a common setting which is
exposed on the main settings interface (your 1st screenshot) and just
assume that setting gets carried over regardless of codec.


Thanh

[Michał Bejda]

We have updated our blog.

http://fsstreamingproject.blogspot.com/

[Dennis Ideler]

Hey Michał and Jakub,

Thanks for the update. Here's my feedback:

1. I agree that it's useful (for certain users) to be able to configure as many settings as possible. Some possibilities to consider:

- An 'Advanced' settings button that shows all the options in a new window

- Two radiobox buttons, one for 'Simple' (which is the default) and one for 'All' or 'Advanced' which will show all the options in the same window. This is how VLC does it: http://i.imgur.com/6Hk0uPp.png

- Anyone else have suggestions?

2. The new design for streaming to justin.tv is much simpler. I checked out the link that's mentioned (http://www.justin.tv/broadcast/adv_other) but I don't really see how it's relevant to finding your stream key. That page just tells me to download Wirecast or Flash Media Encoder and mentions that I need a stream key.

--

[Jakub Adamek]

Hi,

W dniu poniedziałek, 11 lutego 2013 01:29:56 UTC+1 użytkownik Dennis Ideler napisał:

Hey Michał and Jakub,

Thanks for the update. Here's my feedback:

1. I agree that it's useful (for certain users) to be able to configure as many settings as possible. Some possibilities to consider:

- An 'Advanced' settings button that shows all the options in a new window

- Two radiobox buttons, one for 'Simple' (which is the default) and one for 'All' or 'Advanced' which will show all the options in the same window. This is how VLC does it: http://i.imgur.com/6Hk0uPp.png

- Anyone else have suggestions?

Ok, I guess we'll have to rethink this.

2. The new design for streaming to justin.tv is much simpler. I checked out the link that's mentioned (http://www.justin.tv/broadcast/adv_other) but I don't really see how it's relevant to finding your stream key. That page just tells me to download Wirecast or Flash Media Encoder and mentions that I need a stream key.

When I go to that page, there's a line that says "Stream Key: Show", and pressing Show reveals my Stream Key.

We'll certainly improve that label though, since it's obviously not all that helpful. Maybe it would make sense

to describe the entire process for justin.tv on a webpage and just link to that webpage in the label?

[Dennis Ideler]

> When I go to that page, there's a line that says "Stream Key: Show", and pressing Show reveals my Stream Key.

I looked into it and that page does show your stream key, but only when you're logged in (makes sense). So I suggest editing the message to mention that the user should be logged into justin.tv first. The message can also be made as a tooltip so it only appears when the user hovers over the field or label.

Another option, which is more user friendly in my opinion, but more work on the developer side, is to use their REST API to obtain the stream key: http://apiwiki.justin.tv/mediawiki/index.php/Channel/stream_key. This option requires authorization which requires a developer account on justin.tv (you have to ask for a developer account here https://groups.google.com/forum/?fromgroups#!forum/justintv-api-developers) and then your application has to be approved. For now I'd go with the easier option and maybe open an issue on GitHub for this if you think it'd be good to add later.

I don't think that creating a webpage and directing the user to it is worth it, especially if the webpage is just used to explain where to find the stream key.

[Michał Bejda]

Blog updated.

[Jakub Adamek]

Blog updated.