Search the Community
Showing results for tags 'sizmek'.
Found 6 results
-
Hello everybody, i just had a little inconvenience occuring to me, when i wanted to animate a Sizmek Deluxe Banner (inside of their Template) using TimeLine Light and Tween Light. The code is read properly, console log is also working, no compiler errors and so on. just ... the animation wont play. I have contacted their support that is pretty good but unfortunately they also couldn't come up with a solution. Did anybody have a same experience or has an idea about how to fix that (i also tried not to use timeline but only TweenLite in its stead, but no response whatsoever)? Thanks in advance and best regards Felix 01_DeluxeBanner_2.0.0.zip
-
I am a freelance banner animator with ~12 years experience in advertising and over two years of HTML5 specific experience. I have used the GSAP for years, ever since TweenNano allowed very small Flash banners to be developed. My updated portfolio is located at mikehopkinsmm.com, and my LinkedIn profile. My rate is $45 per hour.- 1 reply
-
- 3
-
-
- banners
- rich media
- (and 2 more)
-
HI everyone, really happy to get a job animating HTML5 banners using GSAP. Making and animating the banners are not the problem, i am having a problem getting them loaded into sizmek. I followed some documentation and registered click events but the agency i have to send them to says they won't work. Does any one have a blank biolerplate i can load my project into with sizmek built into it. The static banner template from sizmek set they gave me keeps throwing errors it's just a simple one size banner that needs a to be fully clickable. Any help would be appreciated.
-
The time has came again to pour clean water into the glass. I have started to precisely unravel the mistery of Sizmek as size calculation method. I was unsuccessful. What is know at the moment from my experiments is they are definitely zipping and counting the backup image into the ad's size. But I still don't understand how they compress. I am using 7Zip with the default compression settings and my .zips are bigger than their calculated value. For instance: in case of an 213k .zip, they see 193k from it, which is a 20k difference. I have tried to delete the assest from the zip one at a time, to see what is causing this difference, but i haven't found any file which is adding 20k to the .zip. I don't think they have the ultimate comressor which is better than 7z or the default Windows zipper, this leads to the suspicion: they are excluding something. Could anyone can help me to assemble the right calculation formula? Update: It gets even weirder when I am inlining all the assets into the .html. My .htm file is 217k, backup.jpg is 24k which gives a 171k .zip. Their calculator is displaying ONLY 88k. ( Don't tell anyone but this way we can make huge ads in outstanding quality )
-
Hi guys. Finally got the powers that be to agree to switch over to GreenSock for everything and my first demo project is a few banner ads. All work perfectly except for in Firefox. I've searched and couldn't find anything that fits my scenario so posting new. Here's my script from an expanding ad. <script> var $text = $('#text'); var $lock = $('#PadLock'); var $expand = $('#expandButton'); var $close = $('#closeButton'); var $UnlockText = $('#UnlockText'); var $key = $('#ring'); var $CTA = $('#clickthroughButton'); tl = new TimelineLite({paused:true}); tl2 = new TimelineLite({}); tl2.to($lock, .5, {rotation: 25, left:'95px', ease:Sine.easeInOut, top:'60px', transformOrigin:"left 50%",}) .to($lock, .5, {rotation: 5, left:'110px', ease:Sine.easeInOut, top:'78px', transformOrigin:"left 50%",}) .to($lock, .5, {rotation: 15, left:'103px', ease:Sine.easeInOut, top:'69px', transformOrigin:"left 50%",}) .to($lock, .5, {rotation: 10, left:'106px', ease:Sine.easeInOut, top:'74px', transformOrigin:"left 50%",}); TweenLite.from($text, 2, {left: '-200px', ease:Circ.easeInOut, delay: 1}); TweenLite.from($expand, 1, {bottom: '-50px', ease:Expo.easeIn, delay: 1.75}); tl .from($key, 1.5, {rotation: -180, top: '-300px', left: '500px', ease:SteppedEase.easeIn}, '-=.5') .to ($UnlockText, 1, {opacity: 1}, '-=.5') .from($CTA, .75, {bottom:'-136px', ease:SteppedEase.easeInOut, transformOrigin:"left 50%"}, '-=.5') .from($close, 1, {top: '-40px', ease:Circ.easeInOut}); $("#expandButton").click(function() { tl.play(); }); </script> I'm sure it's just some tiny thing that Firefox hates and is choking on, but have rewritten almost the entire thing piece by piece to no avail. Any advice MUCH appreciated.
-
I'm really disappointed about this news; in the past they had always been very accepting of external libraries. Even though they even host some of the main libraries including GSAP on their own CDN, it seems that they will now start counting them against the file size of banner ads. (I discovered this today when I uploaded an ad and it gave me a new warning message about the file size, even though without the libraries the zip was well under 200k). Hopefully the IAB reevaluates their stance on this, since Sizmek is just following their guidelines... Details below: https://support.sizmek.com/hc/en-us/articles/206239683 Last Update: Wednesday at 01:47 The new methodology for calculating the HTML5 ad size follows the preliminary guidance of the IAB. The size of an HTML5 ad is the total size of all assets in the ad’s Workspace, at the compressed size. This includes images, the largest video, fonts, javascript files, html files and any other files. We do not count additional assets for dynamic creative or videos. Compression is automatically applied which reduces the size of each asset type to the compressed size. Note: Only one video is counted. The platform counts only the largest video in the Workspace. So if there are five videos in the Workspace, Sizmek counts only the largest video. One exception to this rule: If there’s an asset in the ad’s Additional Assets folder, (outside the Workspace), that is larger than the largest video in the Workspace, that asset is counted instead of the largest video. The new method takes effect on February 1, 2016 and applies as follows. Ads created before February 1, 2016 will be counted at the current methodology, even if they are not attached to a campaign. Ads created prior to February 1, 2016 and are copied to a new campaign after this date, will be counted according to the former calculation method.
