The monoscopic bullet time video created by the Insta360 ONE camera can easily be converted to a 3D video by showing it separately to each eye with a time offset (1 frame). Because the camera is in motion (mostly) horizontally, a time delay creates a virtual left and right eye's point of view.Read More
I posted a video of my son the other day, and I was able to both shoot and participate in the video. I shot the video using an Insta360 ONE 360 camera on a light stand and "re-shot" the video as traditional video using Insta360's "FreeCapture" feature in the iOS app. All I did was frame the video in real time while watching it in FreeCapture mode and export it as a traditional video. It worked pretty well, but export took many minutes, which was challenging to complete on a smartphone (if it goes to sleep, the camera turns off, and it cancels the export).Read More
I've survived the first couple months of transition from a Mac-based workstation to a Windows-based one (still using a MacBook Pro as my main "life" computer, though). The NVIDIA GPU has been required for a lot of the work I'm doing in 360 and VR. The new machine features an overclocked 10-core i7 CPU and Titan X GPU, so it's very fast. But I was not so happy to see Adobe Media Encoder CC 2017 only using from 50-75% of my CPU. I seem to remember that AME used a higher % of available CPU resources on the Mac, but haven't done direct comparisons.
If Premiere Pro is playing clips back too quickly, check your Audio Hardware settings. If I set my Default audio input to "Microphone (Rift Audio)" (I have an Oculus Rift connected), playback is about twice too fast, and I can't get play it at normal speed. If I set Default Input back to "No Input", playback returns to 1x real time.
I hate this stuff.
I used Final Cut Pro X, Apple's controversial new "professional" video editing program to cut the trip video during my latest [Wetpixel expedition to Indonesia](http://wetpixel.com/forums/index.php?showtopic=43966). These slideshows have become a tradition for guests and combine video, stills, and music into something people can take home to show their friends and family. Using Final Cut Pro X was, for the most part, fantastic. It is really more like an "iMovie Pro" and includes one-click video stabilization, color balancing, and look filters, which were all features I used extensively. Aside from dealing with small bugs, I was able to produce a 30-minute video fairly easily, without being impeded by any critical issues. However, I am back home, and am now in the process of trying to migrate my slideshow project and event files to my main Mac Pro from my MacBook Pro. This is proving to be impossible. Two [excellent](https://discussions.apple.com/thread/3133085?start=75&tstart=0) [threads](http://www.danmccomb.com/posts/1175/tips-for-reconnecting-offline-media-in-final-cut-pro-x/) provide work-arounds for reconnecting missing media, but upon following the instructions outlined within those threads, this is what happened:
1. After copying events and projects to the Mac Pro, they showed up and opened in FCPx, but all of the media showed up as missing (red thumbnails). 2. Per suggestions, I re-imported all of the media (annoying, since the files are spread out over many folders). The red missing media icons for videos and audio were all restored to color (no longer missing). This seemed like a good sign. 3. Many JPGs in the media list were not successfully re-connected; instead, they were duplicated. I have hundreds of JPGs in the slideshow, which are now all "missing" and therefore, would need to be re-cut into the timeline. 4. Soon after re-import, I noticed an import background task running. Upon closer inspection, I realized that FCPx was in the process of *copying* over all the newly imported media instead of honoring my request to leave the files in their original location (by leaving "Copy files to Final Cut Events folder" unchecked). The source media is hundreds of gigabytes. Duplicating them is not an option. 5. Closing FCPx and re-opening it immediately causes the import process to re-spawn. If I cancel the process, the media simply does not show up in my events.
Put quite simply, there is no way to move a complicated project and its associated event media from one machine to another. The fragility of the media storage system in FCPx is shameful—it's like the product was never tested in the real world.
I will, in this case, essentially lose this project and never be able to edit it again. I suppose I'll archive the events and projects in case FCPx improves its media handling capabilities. One significant side effect: if I upgrade my machine or need to reinstall, I'll effectively lose all of my FCPx projects. Until there is serious improvement in media management, I can't see myself using Final Cut Pro X again.