Jump to content
You must now use your email address to sign in [click for more info] ×

All Media Lab

Members
  • Posts

    470
  • Joined

  • Last visited

Posts posted by All Media Lab

  1. Hi @Beck,

    Are you sure you have set the width of the slices in the export panel by opening them all and put 1080w and Enter in the slice size field of each slice?

    About posting on Instagram (and other social media), the images should never be optimized, because they take care of that!

    https://foodphotographyguides.com/sharp-images-instagram/

    Regards,

    David 

     

  2. 58 minutes ago, R C-R said:

    It isn't negative; it is just realistic

    No it's a subjective matter! So I always look at it from a positive perspective until the opposite is proven. 

    It totally depends on the skills of the developers and the way the apps are coded.

    I presume that we deal here with highly skilled developers looking at the superb  results from the last 5 years in Photo, Designer and later Publisher. Had a look  at the Affinity code and it's well coded too. So it's just a matter of willingness and I don't see any technical obstacles on the road to webp.

    webp is just a other extension like all the others technically speaking, the difference is that the source code is freely available, including the different appi for multiple platforms, like you can see in my previous posts. And that makes it easier to implement. 

  3.  

    3 minutes ago, Alfred said:

    Nobody said it isn’t desirable, and nobody said the Affinity devs are incapable of implementing it, but you stated that it’s “easy to implement in Photo” without providing any evidence to back up that assertion.

    This is the project I'm working on right now! Is it complicated? Yes! But easy to work with? Yes! Because I'm a educated developer with more then 10 years experience!

    That's what I mean with easy to implement!

     

    Screenshot 2021-06-16 at 17.23.43.png

  4. 26 minutes ago, walt.farrell said:

    But that says nothing about:

    1. The code changes needed to add webp to the File > Export dialog.
    2. The code changes needed to add it to the Export Persona.
    3. The code changes needed to add it to the File > Export preview processing.
    4. The added testing, to make sure that the changes didn't break something else.

    It's just a very negative point of view on application development, don't see anything special in your list. You could say that about most implementations. But you could also say it would be nice if it's implemented and I'm sure the Affinity devs are capable of doing so! 

     

    26 minutes ago, walt.farrell said:

    And, by the way, as we get more and more formats added to File > Export, the dialog grows wider, and at some point will need to be redesigned, which is even more work.

    Scroll or tabs or a row beneath  is a solution and again I don't see any problem.

  5. Why does everything has to be made complicated without any reason. It's not complicated at all in a couple of day's you can have it implemented. Seen it happen in other apps and don't forget that you can already display webp in Affiniy Photo. 

    All instructions are found on the Google devs pages:

    Just two examples, want to see more?

    How do I use libwebp with C#?

    WebP can be built as a DLL which exports the libwebp API. These functions can then be imported in C#.

    1. Build libwebp.dll. This will set WEBP_EXTERN properly to export the API functions.

       
      libwebp> nmake /f Makefile.vc CFG=release-dynamic
      
    2. Add libwebp.dll to your project and import the desired functions. Note if you use the simple API you should call WebPFree() to free any buffers returned.

       
      [DllImport("libwebp.dll", CallingConvention = CallingConvention.Cdecl)]
      static extern int WebPEncodeBGRA(IntPtr rgba, int width, int height, int stride,
                                       float quality_factor, out IntPtr output);
      [DllImport("libwebp.dll", CallingConvention = CallingConvention.Cdecl)]
      static extern int WebPFree(IntPtr p);
      
      void Encode() {
        Bitmap source = new Bitmap("input.png");
        BitmapData data = source.LockBits(
            new Rectangle(0, 0, source.Width, source.Height),
            ImageLockMode.ReadOnly,
            PixelFormat.Format32bppArgb);
        IntPtr webp_data;
        const int size = WebPEncodeBGRA(data.Scan0,
                                        source.Width, source.Height, data.Stride,
                                        80, out webp_data);
        // ...
        WebPFree(webp_data);
      }

     

    How do I use the libwebp Java bindings in my Android project?

    WebP includes support for JNI bindings to the simple encoder and decoder interfaces in the swig/ directory.

    Building the library in Eclipse:

    1. Make sure you have the ADT plugin installed along the with NDK tools and your NDK path is set correctly (Preferences > Android > NDK).
    2. Create a new project: File > New > Project > Android Application Project.
    3. Clone or unpack libwebp to a folder named jni in the new project.
    4. Add swig/libwebp_java_wrap.c to the LOCAL_SRC_FILES list.
    5. Right-click on the new project and select Android Tools > Add Native Support ... to include the library in your build.
    6. Open the project properties and go to C/C++ Build > Behaviour. Add ENABLE_SHARED=1 to the Build (Incremental build) section to build libwebp as a shared library.

      Note Setting NDK_TOOLCHAIN_VERSION=4.8 will in general improve 32-bit build performance.

    7. Add swig/libwebp.jar to the libs/ project folder.

    8. Build your project. This will create libs/<target-arch>/libwebp.so.

    9. Use System.loadLibrary("webp") to load the library at runtime.

    Note that the library can be built manually with ndk-build and the included Android.mk. Some of the steps described above can be reused in that case.

  6. On 6/11/2021 at 8:23 PM, R C-R said:

    For now, they seem to be concentrating on performance improvements, something a lot more users seem to be concerned about than the lack of built-in WebP support.

    They are two different things that can both be accomplished without hurting each other! The webp source code is available for free from the Googles dev page and easy to implement in Photo.

  7. Hi @daveconrey

    Isn't supposed to be your AMD Radeon Pro 5500m activated instead of the Intel UHD Graphics 630?

    https://www.idownloadblog.com/2016/10/22/automatic-graphics-switching/

    It can because auto graphic switching is activated it switches to the wrong card. I'm not saying it is, but I had that a couple of months ago. Despite the fact that it showed the proper card. I had to switch the switching off.

    Screen Shot 2021-06-10 at 4.36.18 PM.png

  8. 30 minutes ago, GarryP said:

    Whatever is discussed after that acknowledgement is fairly pointless as only Serif have the power to do anything about it.
    If you want to keep shouting at the sky hoping to hear an echo then feel free to do so but you might want to re-think your expectations at some point. That’s just friendly advice.

    Why do you think all major browsers support webp?

    Because the users kept on shouting/asking about it and at the end it was implemented.

    32 minutes ago, GarryP said:

    Serif are aware of the request and have acknowledged it.

    Without any result, so it's wise  to keep remembering them that this feature is missing in Affinity!

  9. Nonsense!

    Everybody is entitled to discus anything when ever they want. I started the topic you are referring to years ago and till now zero result.

    Who do you think you are? The forum police? The spokesman of Serif?

    Many thing are requested multiple times, it just proves that there are more people thinking that it's a missed opportunity of Affinity.

    Webp is not only used in web design, but also in the game development industry and app development. 

    Users of Affinity just have to keep on asking about webp!!!!!

    Webp is now in all major browsers because the users kept on asking about it!!!!

  10. @NordishBen

    Don't listen to all that negative input from some user on this form! It's just plain ignorance and negativity.

    @GarryP Wonder why you spent your energy on something that's important for others and you don't seem to care about.

    Just don't use it when it is implemented!

    It's true all common browsers are supporting webp and it's unbelievable that it's still not implemented in the Affinity apps.

    https://w3techs.com/technologies/details/im-webp#:~:text=WebP is used by 1.6% of all the websites.

     

     

     

  11. Secondly I had a look at your logo and it's the wrong size. It's a error in the design of the website. 250px X 46px is a very wide ratio. Try to create a logo around the ratio 2:1. And change the size in your CSS according to the new size. Create a svg and use transparency. You can edit/crop a slice in the export persona in the proper ratio and export the svg in Affinity Designer. 

    This is how your logo is placed in your website now resulting in a small logo because of the empty space left and right:

     

    logo-100PX.png

    The best way to create the logo is in Designer using the transparency mode in the document setup. I used your png as a example that has no transparency. 

    designer-svg.png

  12. Hi @KGPX1,

    To start I would take care of the HTML& inline CSS errors on the site HTML VALIDATION your index page

    In your theme.css I see *: 

    .logo img{max-height:46px;max-width:250px}
    .logo img[src*='.svg`

    You can change the size if needed.

    *You should create/export your logo as SVG (that is recommended anyway for a website). Not like a png as you did on your site. Just svg for export and no particular size of course. SVG (Scalable Vector Graphics) have a advantage in case of a simple logo over png and jpg because it uses vectors instead of pixels.

    Like @firstdefenceis saying your logo is way to complicated for a small logo. I always test my web logo's in Affinity Designer by zooming them smaller and smaller to see if it works or not.

    Hope this helps!

    David

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.