Free TeeBoard v0.1.5 beta

[DeezjaVu]

Works in preview with the eye mode, works when double clicking and opening the swf in flash player in \Documents\TeeBoard\widgets. But does not work when viewing teeboard-notifications.html in chrome. I tried copying over the folder as you stated above, overwrote files, still no luck when viewing the html file, or adding the html file into OBS with CLR Browser plug-in. So it seems to be half-working.

If it works in preview mode and with the swf file directly that at least says it's not a security issue (the Trusted Locations are set correctly). I'm not too worried about it not working in Chrome directly (although it should).

Have you set the CLR browser to use a single process? In OBS, click settings, select Browser and select the Runtime tab. Look for an entry called "SingleProcess" and make sure to select "True" (the default is "False") and restart OBS.
If still no joy, try running TeeBoard as Administrator. Right click the TeeBoard shortcut on the desktop and select "Run As administrator".

If with all that it still fails, contact me: https://sites.google.com/site/deezja/contact

 

[nimh]

Found the problem. It would seem that if you have the swf open and then try to test it in OBS at the same time, only the first one open (eye preview/swf in flash player or CLR Browser capture) will play the notification. This may be intented or part of flash's trusted locations setting, I'm not sure, but works so long as you don't have anything but Teeboard without preview, and OBS w/ CLR Browser capture open.

 

[DeezjaVu]

Found the problem. It would seem that if you have the swf open and then try to test it in OBS at the same time, only the first one open (eye preview/swf in flash player or CLR Browser capture) will play the notification. This may be intented or part of flash's trusted locations setting, I'm not sure, but works so long as you don't have anything but Teeboard without preview, and OBS w/ CLR Browser capture open.

That is correct :) and it should be mentioned in the readme.txt (I think). I just noticed it's not in the "help", so I'll make sure to add it.

Now as for the reason, there's a "connection" between TeeBoard and the widgets (if you know Flash, it's called a LocalConnection), which is used for communication. Sending messages from one to the other requires a unique "ID". This ID is hardcoded as both sides need to know it. A LocalConnections is a 1-to-1 communication channel (not a 1-to-many), meaning only one chain of communication per unique ID is allowed and works on a first-come first-served basis, which is why you can only have 1 copy of the widget active (well, you can have more copies running, but only the one you ran first will work).

This also brings up another issue in case you want to use the same widget across several scenes in OBS. Rather than adding a new CLR Browser instance to each scene, make one global source and add that to every scene you wish to use the widget in.

I'm glad you figured it out and got things working :)

Enjoy !

 

[nimh]

If it doesn't have an API, there's not much I can do and at first glance they don't provide an API for 3rd parties. I implemented streamdonations.net because - other than it provides a url to poll - a few of the private beta testers are using it.

Another donation provider that I might implement is donation-tracker.com as they also provide an API. I'm still on the fence on that one, as it's not 100% free (as they advertise). When making a donation, they have a slider that allows you to send money to the channel and to donation-tracker. The default is sending it to donation-tracker (at least last I tested it), which I think is kinda sketchy. If there's a demand for it, I'll implement it though.

Imraising doesn't document this, but you can access their json for each user via: http://imraising.com/ethan/json/livedata.jsonp

replace /ethan/ with your username in the url and they hand over a good amount of data in there. May be able to use this.

 

[DeezjaVu]

Imraising doesn't document this, but you can access their json for each user via: http://imraising.com/ethan/json/livedata.jsonp

replace /ethan/ with your username in the url and they hand over a good amount of data in there. May be able to use this.

Thanks for that. Quite surprised this isn't protected at all.

Now the question is, do people use this with a set goal (raise xx amount of cash in xx amount of time) or just simple donations (xyz has donated x amount)?

The latter is fairly easy to implement as that is what's already there. The first option will require a bit more work and I'd probably even do a separate tab for that. So you'd then have: followers, subs, donations, I'm raising.

 

[nimh]

From what I've seen, most people tend to use it as a payment portal for simple donations. That implementation on the most basic level would be sufficient in TeeBoard I think (So people don't have to run both). The site became popular because of it's live notification bar that's already built into the site and usable for live notifications with window capture and chroma key. I've never really seen it used to set specific goals and reach them, but they do offer a widget that could show that.

 

[DeezjaVu]

From what I've seen, most people tend to use it as a payment portal for simple donations. That implementation on the most basic level would be sufficient in TeeBoard I think (So people don't have to run both). The site became popular because of it's live notification bar that's already built into the site and usable for live notifications with window capture and chroma key. I've never really seen it used to set specific goals and reach them, but they do offer a widget that could show that.

That's good news as that makes it easier to implement since most of the groundwork is already in place.
Added to my TODO list :)

 

[Jhonny Rosa]

Sup DeezjaVu? i've figured out a little conflict between TeeBoard and the league of legends client (not the ingame client) inside OBS, if i remember, the LoL clien runs on adobe air too, like TeeBoard, so OBS kind of loose the hook on LoL client if TeeBoard is started before the stream starts, so we got a black screen where the LoL client should be. But this don't happen if i start TeeBoard after initiate the stram and the LoL client. The same thing happens if the LoL client shutdown in midstream, if i's started again with teeboard alreay running, OBS cant capture the frames (although it appears in game capture properties). Kind of a curious thing.

 

[DeezjaVu]

Sup DeezjaVu? i've figured out a little conflict between TeeBoard and the league of legends client (not the ingame client) inside OBS, if i remember, the LoL clien runs on adobe air too, like TeeBoard, so OBS kind of loose the hook on LoL client if TeeBoard is started before the stream starts, so we got a black screen where the LoL client should be. But this don't happen if i start TeeBoard after initiate the stram and the LoL client. The same thing happens if the LoL client shutdown in midstream, if i's started again with teeboard alreay running, OBS cant capture the frames (although it appears in game capture properties). Kind of a curious thing.

Well, that's unfortunate :(

Is it so that the "Game Capture" source switches to TeeBoard? If so you should be able to double click the game source in OBS to open its properties and select the proper Application from the dropdown list. If the game isn't listed, hit the refresh button. AFAIK, that should fix it.

Also, I think OBS (Game Capture source) does this with pretty much any window that is currently open (such as a browser). If it can't find the source (e.g. game) that was last selected, it selects the next in line or the next best candidate.
If the Game Source had an ignore list, that would fix it.. maybe time for an OBS feature request :)

Edit: I posted a feature request here:
https://obsproject.com/forum/thread...o-ignore-list-for-game-capture-sources.12984/

 

[Jhonny Rosa]

Hey DeezjaVu, i've read your reply now, the curious thing is that game capture cannot see teeboard, he continues too see LoL Client but doesnt render it on screen. I dont know if this happens only in my pc, you can try to reproduce the bug yourself to test. I think that game capture maybe see both LoL client and teeboard as a single app because of how adobe air works? But the ignore list is a great idea anyways! Thx for the reply.

 

[DeezjaVu]

I think that game capture maybe see both LoL client and teeboard as a single app because of how adobe air works?

I've seen this happen with DXTory, so you might be correct in that it doesn't distinguish between different AIR apps. I'll add your reply to the feature request.

 

[dodgepong]

Honestly, even though the LoL client "works" with game capture, I've seen several issues with it still (unexpectedly resizing and such). I still recommend people use Window capture to capture the LoL client and stick to game capture for the actual game.

 

[DeezjaVu]

Honestly, even though the LoL client "works" with game capture, I've seen several issues with it still (unexpectedly resizing and such). I still recommend people use Window capture to capture the LoL client and stick to game capture for the actual game.

That's actually a good idea. Basically have 2 scenes, 1 out of game (with window capture), 1 in game (with Game capture).
And for the out of game scene you could then do something like this:
http://i.imgur.com/fTyiXmn.jpg
http://i.imgur.com/xW5urI4.jpg

 

[Jhonny Rosa]

I will try that, thanks guys.

 

[varyak]

Hey, got a bit bored and just played around with your Tool. I guess it's not easy to use a different font for the clock since its some flash-thingy? Also if you use the military time it would be cool if you could disable the seconds.

 

[Ike45342]

I have followed every step in your youtube video to the letter. Installed under c:\\user\documents and everything.

When opening for instance teeboard-clock.html i can see the clock perfectly. it loads up with no problems.
In OBS when added as a source either globally or not it is always blank. It will never show up. Same for followers.

I followed steps you gave to the previous user as far as testing followers with the eye in Teeboard and it works. works with running as admin as well. But in OBS it will never show up.

 

[DeezjaVu]

I have followed every step in your youtube video to the letter. Installed under c:\\user\documents and everything.

When opening for instance teeboard-clock.html i can see the clock perfectly. it loads up with no problems.
In OBS when added as a source either globally or not it is always blank. It will never show up. Same for followers.

I followed steps you gave to the previous user as far as testing followers with the eye in Teeboard and it works. works with running as admin as well. But in OBS it will never show up.

All the required steps for the widgets are in the help documentation (F1 or via the system tray icon). One thing that is missing in the docs though (and is key), is to only have 1 copy of a specific widget running at all times. So if you're testing the clock in OBS, close the clock preview in TeeBoard first and / or the browser then start the "preview stream" in OBS.

 

[Dracorath]

Does it work using the preview in TeeBoard?
In TeeBoard:

• select notifications
• click the eye icon at the top right
• enable the "Display on stream" option" (on).
• click the "test" button

Make sure that before opening the preview in TeeBoard you don't have the widget running in the browser or OBS.

If that still doesn't work, copy the notifications folder from the install directory to your user documents directory.
The default install directory is: C:\Program Files (x86)\Air\Gip\TeeBoard. Copy the notifications folder (inside the widgets folder) to C:\Users\[USERNAME]\Documents\TeeBoard\widgets and confirm when asked to overwrite.

Restart TeeBoard and try the above steps again. Let me know if that still doesn't work.

Hi there, I seem to have the exact same problem as nimh and I've followed these steps. Unfortunately it still does not work.

-Does not work in Eye preview mode, just comes up with a white screen. Same thing for the Swf file.

 

[DeezjaVu]

Hi there, I seem to have the exact same problem as nimh and I've followed these steps. Unfortunately it still does not work.

-Does not work in Eye preview mode, just comes up with a white screen. Same thing for the Swf file.

Open the TeeBoard help (F1 or via system tray right click menu). Follow the steps explained under "widget".

 

[Ike45342]

All the required steps for the widgets are in the help documentation (F1 or via the system tray icon). One thing that is missing in the docs though (and is key), is to only have 1 copy of a specific widget running at all times. So if you're testing the clock in OBS, close the clock preview in TeeBoard first and / or the browser then start the "preview stream" in OBS.

It's like it is not meant to work for me. I dont even know what to try now. No preview open no browser open with it. still blank in OBS. Close OBS and check preview and/or browser i see it perfectly. I am completely at a loss. I want this to work so badly because I absolutely love the layout of your application. I wish there was a way you could see this as I am completely stumped.