export ftom samsung 360 action director to youtube

The smallest issue is that you are using a laptop that is marginally underpowered and using a display setting greater than 100% and using a shared graphic memory Look neare the end of your dxdiag.exe file and yo9u will see several issues that need to be fixed. Always start your own thread so replies to you don't end up being mistaken for replies to others. It almost looks like you were trying to do a telophoto capture. The solution here may literally be to keep an older system around so that the software functions on hardware from the era it originated from.Quote Update your computer especially the drivers for your video card. So I wanted to ask the rest of you with the issue, are you using newer computers with modern NVIDIA graphics cards? I wonder if there is just a bug with newer architecture systems. Meanwhile, the properly converted photos are measurably larger at 5-6MB. There was something I noticed during this process, the grey photos on my primary PC were only about 400-500KB in size.

While the conversion took longer, the photos came out excellent. I decided to try something else, I switched to my church work laptop, a more modest Intel Core i5 with weaker integrate HD Graphics. I have the original 2016 version of the Gear 360, FYI. I was exploring using other tools, but found them lacking when it came to stitching 360-degree photos with this particular model of camera. I tried a couple settings tweaks, but nothing seemed to solve the issue. Low and behold, when I imported the photos on my primary edit bay, a beefy machine with a 12-core AMD CPU and RTX graphics card, I was left with nothing but strange grey photos. I work at a TV station as a video engineer / IT technician, and recently took some 360-degree photos for a political debate.

I just wanted to bump this thread since you're definitely not the only one getting this issue with ActionDirector.

Export ftom samsung 360 action director to youtube