|
1.5 days until departure.
I've got all of the hardware/accessories, 96gb of memory cards, and 3 batteries + a 2-battery charger. I don't plan on recording nearly as much as you did skibum, so I believe I have enough power and memory. If not, I'll buy more.
Most importantly, after some trial and error with the GoPro and PD14 I've decided to film in 1080p 30fps for the trip. I don't foresee the need for slow-mo, so 60fps will be overkill and space consuming for the circumstances. Plus, the time lapse default is 30fps so rendering will be consistent.
Thanks for all of the contributions. I can't wait.
|
|
Thanks skibum.
I took your experience, compared it to gopro's 'recording time' and 'battery life' charts, and came up with some numbers:
On the days you were using 6 batteries/day, you were recording for roughly 4.5 hours and filling about 96gb of memory card space. Does that sound about right?
|
|
Good advice all around. I do have a lot of mounts, including the smatree version of the folding stick. It is awesome. Pocket size, sturdy aluminum and light weight.
http://www.amazon.com/Smatree®-Aluminium-Foldable-Multi-functional-Thumbscrew/dp/B00SXOLT3C
I just started testing the field of view options. Each has their place. It's nice that each different FOV still produces 1080p.
For those who have the GoPro and pd14 (with hardware acceleration capabilities), which production profile do you prefer, custom or not. I'm not at home so I can't quote the profiles I've tried. When I get a chance I'll post my first GoPro video and profile settings I used. I've read that some guys don't always use HA. I haven't tried without HA yet.
|
|
Thanks for the feedback from both of you!
My gopro is mostly for home action videos, like yourself xr650Lou... But on this trip I plan to use it to record our tourism as a POV experience to be relived on screen. I know they're terrible for capturing landscapes and cityscapes but I'll add some still photos to the video for that. I won't be recording 24/7 (walking down streets, riding the elevators), but I think the footage will act as nice active pieces of a chronological slideshow type video. I can't wait to plug it in to a power supply and film a timelapse from our hotel window (we're staying ON Times Square!!).
Anyhow, back to your techinical advice... I do have 3 batteries, which should last all day and charge in the hotel room. I currently have one 32gb and one 64gb micro SD, if I need more, I'll buy em while I'm there. I too have been fliming at 1080p 60fps for action vidoes, but I'm considering 1080p 30fps for the trip (especially since timelapse is played at 30fps and I don't plan on any action slo-mo).
I've been practicing tirelessly with different production settings on PD14. I think I'll have to choose a single resolution and FPS and stick with it the whole time - whether it's narrow, medium or wide frame.
Thanks again, keep em coming. The more 2nd hand experience I can gain, the better!
|
|
Quote:
The YT quality setting (gear icon) will default to 360p unless you tag the video with "yt:quality=high" (which only forces 720p playback).
The available settings reflect to resolution of the uploaded video.
I was experiencing the same problem with my first PD14 youtube upload. I unsuccessfully tried multiple production settings and formats before finding this thread. As mentioned above, I waited a bit longer for youtube production time, refreshed, and HD options finally appeared on my video.
I'm writing to ask how to tag the video as described above. I've viewed the video in 1080p and now it defaults to that setting on my PC, but I'm not certain if thats how it's viewed by others.
|
|
I've been tinkering with the GoPro for about a month. I've been exploring PD14, reading the user guide, watching tutorials and scowering CL forums for about a week.
Because I'm so new, I'm casting this broad topic to solicit your experiences before submerging myself in a trip to New York.
I'm a fast learner, but hopefully you can help me avoid any mistakes before they're made on my trip. I have 3 weeks before I leave.
So, do you have any pointers that are need-to-know before I go? Eventually I'll be a PD14 and GoPro master, but I've got to cram now for my first big trip with my new toys.
I think my biggest concerns/questions/blind spots are GoPro video settings (or any source ie. iphone, cybershot) vs PD14 production profiles/settings. But what do I know?
Thanks in advance!
|
|
Nice work. The 60fps is amazing in slow mo. I can't really see the difference in quality otherwise.
I guess I'll just have to remove the PD14 conflicting frame rate confirmation pop-up.
Thanks for the feedback.
|
|
Like Eldor, I'm trying to learn the best FPS settings and compatibility of my GoPro and PD14.
I feel that some clips may not require extreme slow-mo, so capturing and producing everything at 30fps would be fine. Alternately, an occasional 60fps recording may be desirable for a project mostly comprised of 30fps video.
What's the best course of action? PD14 will only produce in one FPS setting, so I assume that adding a 60fps clip to a 30fps project would be better for end-product conversion than 30fps in a 60fps project?
Will the slow-mo editing advantages of 60fps clip be possible or recognizable in a 30fps production?
Or is it best to just choose a single FPS capture setting and stick with it, period, bottom line? This seems counterintuitive given the plethora of settings a GoPro offers.
|
|
Copy that. Understood. Thanks for the breakdown.
I'm probably not going to need or notice the HEVC H.265 quality at my level.
I look forward to the arrival of my new PC, PD14 and many hours lost to producing useless home videos.
Keep up the good work.
|
|
Quote:
first gen Maxwell, then PD14's HEVC H.265 decoding and encoding will not work with your GTX 745m.
that'll also translates to no HA in HEVC H.265...
happy editing.
PepsiMan
'garbage in garbage out'
thanks for the welcome. I'm still learning some abbreviations and not familiar with HEVC H.265 (plus I don't even have PD yet). I've been lead to believe that maxwell and keplers are exempt from the drivers that interfere with HA. So, I'm confused by you're reply. What am I missing?
|
|
Oops. Ya, I read/translated it correctly, but copied the wrong row. Thanks for the feedback guys! That's all good news.
I can't wait to enter the world of modern technology. My old system doesn't even compare.
|
|
I may have found my answer.
This wiki page has a Nividia spec chart:
https://en.wikipedia.org/wiki/List_of_Nvidia_graphics_processing_units#GeForce_700_Series
In the Geforce 700 series section, the writer states, "The GM107-chips are Maxwell-based, the GKxxx-chips Kepler."
My GTX 745 is listed as code name, "GK107-425-A2" which leads me to believe it is Maxwell architecture.
I won't be completely satisfied until one of you geniuses can confirm this for me. But as of now I'm breathing a sigh of relief.
|
|
Quote:
I'm afraid you're misundertsanding what the statement says. It's not your fault, it's not clearly written!
The statement ONLY applies to the listed GPUs, all of which are several years old and all of which use nVidia's older chipsets (Fermi, Tesla). For anyone with those cards, the 340.43 driver and beyond no longer support CUDA hardware, and that's why the warning statement is there.
This has NO impact on nVidia GPUs with newer chipsets (Maxwell, Kepler) because they use OpenCL and nvenc.
The best source of info I can point you to is this sticky *thread* that decribes the situation in detail. Your GTX960m is brand new and has a Maxwell chip, so you're clearly not affected!
Newb here. I just purchased a new dell XPS8700/ windows 10/ i7-4790 Processor 3.6GHz/ 16GB RAM/ 1TB hard drive, and NVIDIA GeForce GTX 745 GPU. The PC is in the mail. While shopping for PD14 I found the compatibility issues listed on the specs page - then I fell down the rabbit hole. Ive read every forum, article, driver, wiki on this topic but can't find a direct answer. Luckily, I feel much smarter, thanks to all of the contributors...
I ask, before this PC arrives, is the GTX 745 GPU a newer chipset with maxwell/kepler architecture? I can't find which side of the fence it falls on: new and uneffected by current drivers, or old and requiring driver manipulation? I'd hate to buy a new computer and immediately have a compatibility issue with the it's primary purpose.
Thanks in advance!
|