I used to make slideshows with iPhoto and export as video. Today I'm trying to make another one but some photos appear totally black when exporting in 1080p...
I tried to export at lower resolutions, and everything works ok.
So it's only when exporting at 1080p...
The problem was that the images were all too big.
I suppose iPhoto can't handle this amount of very high res photos, all around 5616*3744px in my case.
I resized all the images to a little higher than 1080p, and it worked well.
Related
Problem I need help with
Assist with optimizing latency in its "Short-Video Feed" and solving intermittent performance bugs. A central feature of my app requires seamless plays 15 to 60 second clips when users use "swipe up" hand gestures similarly to TikTok and Instagram reels. Right now, I have performance bugs (intermittent) such as black screens, delayed loading screens, sometimes long loading, etc.
The bugs may be caused because Flutter is slower than Native iOS. However, our "Short-Video Feed" has lots of bugs whether I use a M3U8 (Mux), or whether I use a MP4 based approach with AWS S3.
If I use the Mux based approach with M3U8, "Short-Video Feed" there is a noticeable few milliseconds black screen for each short-video playback.
If I use the Amazon based approach with MP4, "Short-Video Feed" intermittently loads for a few seconds (sometimes minutes) when there is low bandwidth, and some videos get stuck even when a user returns to a location with faster bandwidth.
Open issue on Flutter
https://github.com/flutter/flutter/issues/25558
Approaches I have tried with no success:
Native Player. I tried to use a native video player for Android/iOS, with MP4 and M3U8, but the UI was still very laggy (because of data transfer between Android/iOS and flutter latenices).
Flutter Player. I tried to use a Flutter video player for Android/iOS, with MP4 and M3U8, but the UI shows a black screen with M3U8 & heavy loading for poor internet connections with MP4.
Approaches I need help to try:
Optimize M3U8 player to minimize the black screen issue. or...
Create MP4 chunks to optimize for poor reception areas (this is what I think TikTok Instagram Reels, and similar applications do based on what I can see).
Has anyone solved this issue?
How about isolating whether these lags are due to network buffering or due to Flutter (or even a device hardware limitation such as memory or GPU)?
Perhaps use a few local MP4 files with identical frame rates and encoding parameters (both video and audio) and see whether the UI lag is reproducible upon swipe-up scrolling?
Have I misunderstood the img srcset tag if I say that I'd like to specify to the browser what image to show when the screen is max-size: 599px (mobile) and when it's above that?
<img
srcset="
small.jpg 600w,
big.jpg 2000w"
sizes="
(max-width: 599px) 600w,
2000w"
src="big.jpg" alt="Some text" />
This code doesn't behave at all how I'd expect it to. I'd like the browser to show the small image when it's a mobile screen, and show the large one for every other device resolution. Is there no way to do this simply? So confusing.
I've read articles on SitePoint, Smashing Mag, etc, and none of them explains it simply as above. They go into image widths, viewports, ratios, etc. All I need is to specify in a media-query screen resolution style which image to show at which resolution.
Many thanks.
I am trying to make a simple QT android app, but basically my problem is that on my main screen I have about 250 little images that i want to scroll. But I really need the scrolling to be fluent and fast. First I tried it using QML but it wasnt really fast, then I tried to make the app in qt designer and use widgets but that was very slow. Then I tried using openGL but on android I can only use openGL ES and I cant find so much examples because every example that I find is much more advanced than I need.
But basically my main question is, what do you think is the best way to solve my problem and if its openGL which way of using it is the best that could solve it?
Thank you.
Neither approach should have problems when scrolling when compared to a native application on the same device. Check the following:
Make sure to measure performance only in release-builds, with QML debugging disabled and no debugger attached.
Maybe your device simply can't keep up with so many images in one view - then it's not a Qt problem. Compare with a 'native' java-App to see if this is the case.
Check if you implemented everything correctly; e.g. check if theres anything running in your main-loop or some events happenening repeatedly which consumes CPU time
And some more general advice:
Downscale your images to the appropriate view-size before giving them to the UI, as they might have to be re-scaled on every frame-update and/or consume graphics memory otherwise. E.g. dont set the source to a 1024x1024 image when it's going to show in a 64x64 view
Remove transparency from the images if they are going to display on solid-colored background anyway.
Dont overlay the images with other widgets/controls
If you're still getting a 'slow' UI, maybe try to merge all or multiple images and their surrounding UI/Controls into one or more bigger images
Very long views are not user-friendly. Maybe implement a pager or tab-view etc. to divide your list into multiple views. This way you can also decrease load-time
Dont try to implement an interface in openGL yourself. It's unlikely you'll make a better one than you already get with QtWidgets and QtQuick.
I am downloading the static map image from Google for my Tizen App. The code works perfectly fine with the emulator but with the real device it is not working well. It shows blank image
Sample URL we use:
http://maps.googleapis.com/maps/api/staticmap?center=38.215,35.3454&zoom=13&size=450x250&markers=icon:<markerURL>|shadow:false|38.215,35.3454&sensor=true&style=feature:water|visibility:on|hue:0x0091ff|saturation:39|lightness:-4|gamma:0.84&style=feature:poi|saturation:19|lightness:-5|gamma:0.94&style=feature:road|gamma:0.83|weight:1.1&style=feature:transit|saturation:39|gamma:0.78|hue:0xffcc00|lightness:-16&style=feature:administrative|gamma:0.5&style=feature:road.highway|visibility:on|saturation:-18&style=feature:poi.park|gamma:1.22|lightness:-4|saturation:-43&style=feature:road.arterial|saturation:-49|lightness:42|gamma:0.6.jpg
Note that the keys are not used with this URL.
When I go to the URL in your question, I see a 'blank image'. However when I adjust the zoom level to be slightly more zoomed out, decreasing it from 13 to 10, I see some map. I think you're just too zoomed in on those coordinates, so seeing a completely blank bit of map.
e.g.
http://maps.googleapis.com/maps/api/staticmap?center=38.215,35.3454&zoom=10&size=450x250&markers=icon:%3CmarkerURL%3E|shadow:false|38.215,35.3454&sensor=true&style=feature:water|visibility:on|hue:0x0091ff|saturation:39|lightness:-4|gamma:0.84&style=feature:poi|saturation:19|lightness:-5|gamma:0.94&style=feature:road|gamma:0.83|weight:1.1&style=feature:transit|saturation:39|gamma:0.78|hue:0xffcc00|lightness:-16&style=feature:administrative|gamma:0.5&style=feature:road.highway|visibility:on|saturation:-18&style=feature:poi.park|gamma:1.22|lightness:-4|saturation:-43&style=feature:road.arterial|saturation:-49|lightness:42|gamma:0.6.jpg
I hope someone can help.
I have started to build a website for a client using JA Brisk template. I notice when the width of the browser window is reduced, the content in the positions start overlapping (instead of keeping the same dimensions and introducing a horizontal scroll bar, which is what happens with the sites I developed in 2.5.9). I am wondering if this has something to do with the wrapper settings in BJA Brisk?
My website can be viewed here - http://edrivenmedic.com/
Thanks in advance,
You are using a responsive template. I'm not familiar with your JA Brisk template or the T3 framework specifically, but often with responsive sites one thing you need to avoid is setting image sizes. Instead you rely on the framework CSS to size the images relative to their container.
If the overlapping issue you refer to is with the four blocks under the carousel on the home page try removing image dimensions for the smartphone/iPhone/iPad images.
Good luck!