Firefox was the only major browser to not have a 64-bit version, until recently. Internet Explorer has had a 64-bit mode for several years, Chrome also has a version that was released in 2014. A well coded 64-bit application should theoretically perform better and more efficiently than it’s 32-bit counterpart on a 64-bit operating system, usually at the expense of a bit more memory. There’s a lot to like about Firefox with the thousands of available add-ons, but also it’s had it’s fair share of problems with various performance and memory related issues over the years.Īn area where Firefox fell behind is making the browser a full 64-bit application to work better with 64-bit versions of Windows. It used to run Internet Explorer close for top Windows web browser but these days has slipped to distant third behind Internet Explorer and more recently Google Chrome. Thanks for any and all help, I would love to know how to do this.Mozilla Firefox has been around for over a decade and has built up a huge following of loyal users in that time. Rtmp protocol on port 80 so add this port in rtmpdumphelper options Then Universal link, which worked for you, plays fine in Waterfox but nothing is detected by Helper Geo restriction and not rtmp protocol but hds (encrypted) by default (.f4m) but it's not a problem you can find the direct link (.mp4) in the source page Then Universal link, which worked for you, plays fine in Waterfox but nothing is detected by Helper. Clipfish playback never worked for me in any browser: it fails to initialize it's player for unknown reasons. But only Naver link downloads with that browser. so it's ok with Waterfox 圆4 you can download the video? I can connect to Waterfox without a problem. Finally, Waterfox 圆4 has worked instantly.Īdd Support keeps failing with x32 browsers as well. Then 圆4 Helper refused to see newly installed 圆4 IE, not even an error given. That's funny part: had three browsers x32 at the start and failed to connect to all with x32 Helper, which was downloaded first. I toyed with plenty rtsp/rtmp parameters without finding a single way to fix that mess. Ie with tracks at least 8-10 min long (20-24 MB 320k) you already have all chances it stops before reaching end of file. alas it ALWAYS stop 99.8%Īt first it seems to work like rtsp, alas if the streams are long enough, the download will stop before the end. If you drastically reduce buffer, you can reduce this but nonetheless you"ll never get the proper timing, there'll always be some extra.Ĭase 3 : using rtmp w/rtmpdump -LIVE modeĭld much slower obviously but at least doesn't download extra stuff. but you end up with file much.longer this time than expected length. Since these are mostly classical concert recordings, it's a real problem to get missing bits within the continous gig.Ĭase 2 : using rtmp w/ rtmpdump standard modeĭownload without problem. alas EACH stream starts 0.026212 as displayed instead of zero, ie something like one missing audio frame at the start. Now the important word is PROPERLY, since it's non protected I sure can download all of this even with just ffmpeg/avconv.īut there are ALWAYS problems with file length.Įach 320k track comes with a rtmp & rtsp adress. I'm obviously missing something, if only I knew what. It's been days I'm trying to download UNprotected rtmp/rtsp steams properly, alas without success (call me dumb )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |