New to our Forums? Please review our Posting Guidelines and Forum Policy before posting.
Topic RSS
I finally got the chance to try remote from my in-laws. I have Comcast and 35/5 speeds at my house. They have Fios and 10/3 speeds. Both the iPhone and iPad stayed below 1000 Kbps over wifi from there house so I am guessing there is a remote cap of 1000.
I definitely have a theory on the iPad on a local network. The behavior was VERY similar when I was remote. I think the app or the Flow thinks the iPad is remote and when it realizes that it isn't (after the 15 minutes or so), it kicks up to the awesome 3000+ Kbps speeds.
For the record, I let the iPad and iPhone both run remote for an hour at separate times (so there was no increase after 15 min or anything like that).
Can anyone from the support team chime in on this? The remote cap doesn't seem necessary and there is definitely something up with the iPad/app.
gifty74: did you try the 15 min test on your iPad at home to see if it spikes up?
I think you're spot on with your theory on the ipad app capping the speed because it thinks it's local. I've done a good deal more testing, and now it will only cap out about half the time. The other half of the time I get the 3,500+ speed. In fact, the other night I was trying to hit the cap and I couldn't do it no matter how many times I opened and closed the app. Thought by some miracle it had repaired itself, but tonight again I hit the cap. If you watch, it seems like it happens just when it starts the feed. Mine always starts at a higher resolution (if you pull the guide up you can see this right when it connects). The guide is pretty sharp on the screen. Then, it seems that if it struggles to get a good feed going, and you see "Buffering" up in the upper left where the speed shows up, it kicks down to a lower resolution to keep the stream alive. If you watch you can see the guide turn from pretty clear, to a lower resolution and kind of fuzzy. Once you see it turn fuzzy the cap stays at 1,000. I haven't yet had the patience to give it 15 min but will go try it now if I can get it to hit the cap. I also moved my Vulkano location so I'm on wifi now and still getting nice solid streaming (most of the time) unless I hit the cap. I'll post back with the result.
We need to hear from someone on the development team as to why this is happening. It seems like it notices you are remote, or senses that the stream is too weak, and switches resolution.
Ok, so I did some more testing this morning before work. Fired up the ipad app and right away started jumping up to the 3,500+ range. Closed the app and opened it two more times before I hit the 1,000Kbps cap. Like I said above, it looks to me like if it starts to struggle with the feed and keeping a steady stream, it will show "Buffering" in the upper left. If it drops too many frames (there must be a threshold for this somewhere in the app or firmware on the box) it switches over to the low res feed. On the ipad I can actually see a very slight flicker and then things turn just slightly fuzzy. It will start out on the high res but then switches over if it struggles to stream for a few seconds. I did let it continue and it was right around the 10 minute mark where it kicked back over to the high res feed and continued on fine from there. I'm going to continue testing. Hopefully they come out with an update to the app that resolves this issue.
So I broke out the stop watch on my iphone tonight and started timing from the exact point where it switches from high to low res right after opening up the app. Low and behold it is exactly 10 minutes on the nose when it switches over to high res. This should help the support team if they are trying to debug this issue (hopefully someone is monitoring the forums). From that point on it stays on the high res feed. It must check something at the 10 min interval to see if it can up the stream quality.
Ok, so I think I've figured this one out. I dug into the setup files in the Monsoon directory on my PC, the ones the setup program installs on the local computer and sends to the Flow giving it streaming instructions, etc, when you run the setup program. In those files I found the settings that I think are responsible for controlling the behavior of the streaming, and what is called "(VFR_Threshold)". It says in this setup file that VFR_Threshhold has settings of 0-4, and control "Sensitivity of the framerate switching process." It seems this controls when it switches from high to low res. The stock setting is 0. I changed that from 0 to 2, so it's less sensitive. Did testing out the wazoo last night, and it acts the same and starts to studder during the streaming process right when it connects, but with this lower sensitivity it gives it more time to get a good stream going, and has not yet kicked down to the low res. I tried it a bunch this morning too. I think this might have solved the issue.
If you don't mind, could you help me with a little step by step?
I thought I had it… I found HavaWireless.xml in the Setup/Local folder which had the VFR_Threshold = 0. I changed this to 2 and ran a very basic set-up (just OK to every step as my info was already there). It worked on the first try but reverted back to old behavior after that.
I'm curious if I did it the same as you? If so, I could try 3 or 4 as values perhaps. Just want to make sure I altered the correct file and then did the appropriate setup/reboot if required.
One other thing… while looking through the xml I saw VFRBitrateThreshold = 350. Being under this seems to trigger a VFR Mode of "4" which is "Full Half One Third." Who knows what that means, but I wonder if that has something to do with the hiccups at the beginning. Here are the other WFR Mode options:
0 = no, 1 = Enable Switching, 2 = Full Half, 3 = Full One Thrid 4 = Full Half One Third 5 = Half One Third
Thanks!
Well, I never posted back but after testing it a few days it reverted back just like what you are seeing. Something is going on and seems to be a bug that hopefully they are going to fix in the next ipad app update, or firmware. I suspect it's a firmware issue.
I tried changing several of those settings, including the VFR Mode to 0 or "no", but that didn't do the trick either.
Pretty bummed because I use the app all the time. It works great the whole night after rebooting the Flow, but after a day or two it's back to switching to a lower bit rate. I sent a request into support to ask if this is a known issue and have not gotten a response yet. I'm testing more settings now and will post if I find any earth shattering news.
Just checking in to see if there was any resolution with this issue? I've had my Flow for a couple weeks and have been very pleased with it, though I have noticed the identical 10 minute under 1000 cap when using my iPad. like others have posted, it's 10 minutes to the second and then it ramped up to 3500-4000. also like others, closing the app and rebooting the flow fixes the issues (but only until i close/hide the app and go back into it). not too practical to reboot the flow every time i open the app.
FWIW, i have a vulkano flow (wireless setup) to an apple airport router. I set everything up my my MacPro and use both it and my MacBookPro as clients and to adjust setup. However, I use my iPad 2 (wifi only) as the main client, and often just around my local network (watching on the deck, garage, etc).
Like others, I'm not expecting 3500-4000 over the internet (my connection up speed is only 1.5 mb), but it surely should be able to sling it to the iPad locally through the airport… especially since after the magic 10 minutes, it does just that.
any help would be appreciated. thanks all and i appreciate the community!
Nothing yet. I've emailed tech support direct and they don't seem to answer my direct questions on it. I'm thinking most likely it's a known bug and they will hopefully fix with the next firmware update. Seems like it's the box doing it, not the app. I've changed all of the config files I've found to prevent it from switching resolutions, but nothing worked. Like you, the first time after rebooting the box, all is great. But, after suspending the app and re opening it's back to the 1,000kbps cap. At 4,000 (which is where it usually tops out) it looks so awesome. Just want it to be there all the time. Glad to see you're seeing the same thing on an Airport router. My Netgear is a good dual band router, but though it might be something in the router…possibly. I wish Monsoon support would monitor the forum and comment like "Yes, this is a known issue that we've repeated in our lab, update coming soon" or something like that. We don't really know much other than what we can reproduce by doing our own testing. Let's stay in touch and hopefully we can push for a resolution. Thanks.
Interesting update… I got a "new" iPad (or iPad 3 or whatever they're calling it). It is a 64GB WIFI. I got it on launch day (almost 2 weeks ago) and it has worked flawlessly with the Flow. I have yet to hit the phantom 1000 kbps cap while home on my own network. It hits the 3500 range within 25 seconds and stays there. I've used the app about 50 times and over the course of this time I have extensively tested (rebooted the Flow, manually killed the app, etc). Nothing has changed the performance. Today I went to my in-laws and the 1000 cap was there as expected as I was remote on Wifi. I was tentative to try it there because I felt like that might make the cap start hitting me at home too. Crazy, I know, but I LOVE this thing when it is working right. Well still no problem at home which is great.
The only thing I can think of at this point is that my previous iPad was iPad 2 64GB Verizon. This makes me wonder if having the cell circuitry and associated software is the root cause of the 10 minute bug. gifty74 and horsepowerpro: what model iPad are you using?
EDIT: Just to be clear… I did absolutely nothing to the Flow when I got the new iPad. I restored the new iPad from a backup of the iPad 2. When I first launched the app I had to enter the name and pw for it but that was it.
Hmm, very interesting mgorsk02. So no matter what you do you can't get it to revert back to the cap? I just sold my ipad 2 for a 3, but haven't purchased it yet. My 2 was a wifi only 64gb model, so there goes the theory that it was the cellular circuitry or antenna or something. My wifi was doing it too. Well, nothing left to do but go buy a 3! I'll report back by the weekend with my findings. I too use mine up at my in-laws and parents' house and I also get the 1,000kbps cap while out and about. I wish though that there was some rhyme or reason to those config files because it would be nice to raise that limit if the upload supports it. My father connects to my Flow all the time from his laptop, and comcast recently up'd my upload to 6Mpbs. He said there was a noticeable difference after they increased it. He get close to 2,500kpbs on the PC player remote. Has to be a way to increase that on the ipad too. Let's try to figure it out as no one from tech support seems to be monitoring or giving us any advice.
Ok, so I got the new iPad (3) and put the app on. I've been playing around with it all weekend so far and like you I can't make it capped no matter what I do. I've shut it down every which way and mine jumps right up to 3,500-4,000 right away, within 10 seconds. Wtf? One side note, my new iPads screen is much yellower than the 2 and im not liking it!




Log In
Register
Forum


