Zippyuploader update, Docs and Videos encoding performance boost

Hey folks,

A quick update:

– Today a new version (0.0.16.0) of the Zippyuploader was released. The only change is related to an increased file size limit of 500MB. If something went wrong during the update, download the Zippyuploader again from our website.

– We are thinking about releasing the sourcecode of the Zippyuploader to the public, maybe we have a few dope C++ developers as users, which would like to add a few new funtions to it. Let us know if you are interested.

– Today a new Docs/Videos encoding system has been put into production. All the Docs/Videos are transcoded via a bunch of Nvidia GTX1080 graphic cards to an usable/previewable format. Transcoding is fully hardware-based with use of NVDEC/CUDA(scaling via NPP)/NVENC and its performance is up by 2000% in comparision to the previous CPU based solution. We have also shredded the GlusterFS (file system) which we used to transfer files to the transcoding farm and replaced it with MooseFS/LizardFS mainly due to GlusterFS stability issues.

End of technobabble.

May the Force be with you! :-)

Edit 8.12.2017 23:59 CET:
Can we fix it?Practicaly everyday we have to restart services around 23:00 0:00 CET to push the new patches on the production environment to iron out some bugs in the docs/videos encoding farm. Unfortunately it may be a bumpy ride with us at this particular time of the day. Helmets are mandatory to prevent head injuries from sudden upload/download interruptions. Aaaand buckle up!! :-)

28 responses to "Zippyuploader update, Docs and Videos encoding performance boost"

  1. HoneyFox

    Hey,
    I was wondering if you were thinking of releasing a client for Linux. I wouldn’t mind a CLI only thing too much, but a program with both would be better.
    Many Thanks

    Reply
  2. jonsweb

    Update came yesterday while uploading. Upload crashed then.
    And since then, the new 0.0.16.0 does not start any more.
    And it cannot be stopped via taskmanager, i had to restart the (WinXP Pro) computer to kill these 7 instances of zippyuploader.
    It’s completely useless for me!
    How do I get rid of this? I want 0.0.15.0 back…

    Reply
      1. jonsweb

        I had the same trouble with the next download. But now (after some restarts) the problem is solved. Caused by the new version number of the uploader and the not initializing surface of the Zone Alarm Firewall (although wainting for an answer to approve the new uploader).
        Now the programm starts, but have not tried to upload by now.
        Thx for 500 MB. Thx for your good job. Thx for the comfortable uploader :)

        BTW: wasn’t there a function to add other zippyshare-Links to your account in the past (one’s which are not uploaded directly into the account)? Where is it gone? Can this be added again?

        Reply
  3. Vito

    Please open to the public the code for making an Android app. You should make an Android app with ads, and a paid version without ads. It’s going to give great funds to you! I would be one of the first people to buy.

    Reply
  4. Vandy

    I appreciate ZippyUploader finally being updated to 500mb! I just would like to know… why does ZippyUploader crash so much more now though? When it was at 200mb, it didn’t crash *as* much, but with the 500mb, it varies for me now…

    Reply
    1. admin Post author

      Hey Vandy, Recently we have to restart services a few times a day around 23:00 0:00 CET to push the new patches on the production environment to iron out some bugs from the docs/videos encoding farm. This may be percived by you as a Zippyuploader problem.

      Reply
      1. Vandy

        Ah that would explain why. Thank you for clarifying that, I was really starting to think it was something on my end that was messing it up. I do enjoy all the hard work you guys have been doing! I thank you for your amazing services, and amazing uploader tool!

        Reply
      2. HSG

        The file manager is not working correctly. It stopped sometime yesterday. When files are downloaded, the 30-day trigger is not reset. On the file download page, the day after a file was downloaded, it’s not showing as having been downloaded within the previous day.

        Reply
  5. John LPBass

    I, unfortunately, live in a poorly served internet area; all that is available is 4 mb/s DSL, with frequent interruptions. Zippyshare is the only downloader and uploader that will handle frequent (and often lengthy) interruptions. Qudos to you all!

    – John

    Reply
  6. Zontir

    Releasing the loader code would be very useful, not only to add new functionalities but also to help you understand how it works and create an application from 0. Most of all it would help an api for music.

    Reply
  7. joshua mulder

    W10 Defender blocked the new UPLOADER bcoz TROJANHORSE ??????

    is it still safe to reup and ignore W10 Defender warning????

    but im HAPPy with the increased file size < 500MB -;)

    Reply
      1. HSG

        Once again, the file manager is not working properly. It stopped working correctly sometime yesterday. When my files are downloaded, the 30-day trigger is not being reset. On the file download page, the day after a file was downloaded, it’s not showing as having been downloaded within the previous day. I tried this with other people’s files, and theirs are not resetting for the 30-day period.

        Reply
  8. Ngoc

    Google Chrome will block some ads (like popuder, popup ads,…). Does this affect zippyshare income? How do you guys adapt to this? Thank for 500mb limit! Please keep Zippyshare alive!

    Reply
  9. chocolatkey

    Hi. If you release the C++ code, it would make it easy to make the uploader cross-platform. We could go with Qt and be compatible with Windows, Linux and OSX

    Reply

Leave a Reply to John LPBass Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>