Jump to content

dbeedle

Members
  • Content Count

    185
  • Joined

  • Last visited

  • Days Won

    14

dbeedle last won the day on April 9

dbeedle had the most liked content!

About dbeedle

Profile Information

  • Interests
    Array
  • Location
    Array
  • Gender
    Array
  • Occupation
    Array

Contact Methods

  • Website URL
    Array

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Until they get shut down: CamOn Live, Streamlabs several others. At least they worked the other day.
  2. I was curious why there is now a limit for YouTube and, with little googling, found that it is not a new requirement but had been dropped from 10,000 viewers to 1.000 then eliminated sometime around May of 2017. It's now back to that 1,000 viewers. I suppose, to preserve some level of quality (not that more viewers = better quality) and to make money via advertising versus the (considerable) cost of resources used to process video on such a scale. YouTube did still have requirements after that May 2017. It seems that the 1,000 viewers was still officially required but not enforced. Now they are back to enforcing it. I wonder if if some sort of open source, private server streaming service would be usable.
  3. With a good web cam, I'd say they should do, at least, reasonably well. It doesn't take a lot of CPU if the transcoding isn't needed. It seems that in may depend more on the camera. But now I'm curious! I'm tempted to get a Pi Zero W and a camera module and see how it goes! This may just be an urge to tinker!
  4. I have experimented with a Pi 3B+ using ffmpeg. Also a docker image called restreamer (https://datarhei.github.io/restreamer/) which is using ffmpeg on the back end. With the right camera I think it can perform well. In my case, the camera (a cheaper Logitech) does not output a stream that YouTube likes so, it has to transcode the stream. The quality of the stream is OK but I only get around 7 frames per second. Usable but not the smoothest. But, it's also not burying the CPU with the right (lower) quality settings. I blame the camera for the low performance in my case. With a camera that outputs a H.264 mp4 stream natively, the Pi would just act as a pass though, more or less, with no CPU spent on the transcoding, just pumping the data through. I've seen reports of folks getting pretty good results in that case.
  5. I did some experimentation last night using my own channel. I have no where near 1000 subscribers so, Live streaming from a mobile device, which did work previously, no longer is allowed. What is working is, Streamlabs and Camon Live. I also gave a web cam on a Raspberry Pi a try and had no issues with that. At least until YouTube outlaws live streaming for less that 1000 subscribers outright, there are alternatives.
  6. Hmmm...I'm just guessing here but, I would imagine YouTube is not able to determine if a device is mobile or not if it is using the RTMP stream directly rather than whatever it is that the YouTube app uses. Just a wild guess really no evidence to support the idea. Now that I think of it...and if I remember right, StreamLabs routes traffic through it's own servers rather than direct to YouTube. IF so, that would allow them to cover up the origins of a stream.
  7. I wonder of the live stream in a browser relies upon Flash. If so, Chrome no longer supports it. Steps can be taken to get Firefox to use Flash I believe. It involves downloading Flash from Adobe and installing it. It's been a while since I've used Firefox or Flash I'm afraid so going off old info here. I do know of only one mobile browser that does support flash out of the box, that one being the Puffin browser. It also works with EoE chat!
  8. I've used StreamLabs and CamOn Live. Both work well; StreamLabs seems to a more bells and whistles. I have tried neither since learing about the new restrictions but will give them both a try before an upcoming trip. I can also try a Raspberry Pi stream. I suspect that would be considered a non-mobile stream.
  9. Some things to try: Ensure you are in a strong signal area. Make sure you have the latest YouTube installed via the Play Store Clear cache and and data for YouTube. You'll need to log into YouTube again. Settings/Apps/ YouTube/Storage/Clear cache and or data/storage. You might be able to long press on YouTube from the app drawer. If so, select app info from there. Remove and reinstall YouTube. Use something else. I like CamOn Live Streaming, which I use, and Streamlabs. I have also tried CamerFi Live and YouStream. If you still have issues, reduce the resolution and/or quality of the stream and try again. I don't think the YouTube app will allow this.
  10. My honey bunny is eyeing fast passes today! Disney days are coming!
  11. I did see an announcement that Disney would be cracking down on that practice. If a room is canceled the corresponding FPs are supposed to be canceled as well. That link was missing in the past In think.
  12. Ditto on the bandwidth and stability. And welcome aboard JohnDisney! As a caveat, I haven't done a lot of streaming from Disney but I have experimented a fair bit at home... I'd add to that, the abilities of the camera and the device it may be attached to. They need to be able to reliably generate the data. I've done some experimenting with a few devices, an old android phone (low end as cameras go these days), a newer android phone, a GoPro 7 (more advanced) and a cheap web cam on a Raspberry Pi. All of them can establish a stream with varying levels of success. I would argue, however, the camera is not the deciding factor. In my case, the most successful device has been the low end android phone! The Raspberry Pi was able to sustain a reliable stream...but at 7 frames per second. It and that camera are not the best combination. It doesn't matter how snazzy the camera is, though, if you don't have the bandwidth to push the data. So, a thought on improving through put...kinda out of our control. Wifi and cellular data signal strength and congestion at that location probably has a bigger impact on the ability to send a stream than anything else. These things we can't change. Well, we may be able to do something in our own homes but while out and about we probably can't do much. Other than... Minimize how much data you need to push. My basis: I'm thinking a reliable stream is better than a choppy one at higher resolution. We all would like a 1080 HD stream. Looks good, impresses the viewers. But, unless you have a really strong signal with an un-congested network it probably can't be sustained. At least, in my experience. I've had more success sustaining a stream by going with a lower resolution and a lower frame rate. 720p or 480p at 24 fps (if you can get it) has been the most successful for me. Not cutting edge by any means but the lower end settings are far less demanding in terms of bandwidth and processing. Again, this is all just my experience trying to do a resort stream or a "home" stream in my experimentation. Your mileage may vary. I think, though, most folks will think that bigger is better and go for a higher resolution and higher frame rate not considering cutting that back a bit. Now if you do have a strong signal and open network...the HD does look durn good! I haven't done a "parks" stream. Mostly because I don't have an unlimited cellular plan but, I would imagine, the bandwidth availability is even more problematic while in the parks. WiFi in the parks typically seems to not be up to the task and the sheer concentration of people all hitting the same data "pipe" while in the parks tends to lead to low bandwidth availability and fluctuating signal strength. Even if not streaming this is noticeable. So, again, pushing less data may help to maintain a stream at a reasonable rate. Just some random musings as I'm at work on a Friday! I suppose I should go be productive now. Bummer.
  13. Still fiddling with it! Had initial promising results which I haven't been able to get consistently. The C310 (Logitech) webcam I'm using may be the real issue. The Pi doesn't have the horsepower to transcode the video in a reasonable time and send it so a cam that outputs an already encoded stream would allow the Pi act as a pass though, which it can do. Video plus sound is even more of a challenge for it. While the 310 has a compressed format, I don't know it's one YouTube likes! Fun to hack at though!
×