|
|
|
What are you "Produce" format and settings details in PD?
|
|
|
No - was born in Namiba - now in the US 
|
|
|
|
Ha, small word - I am from Namibia and speak German
|
|
|
I have been watching some of the PDToots videos (http://forum.cyberlink.com/forum/posts/list/30026.page) all very good stuff!
And yes, we can all learn from each other - even if it is just being reminded of things one knew but had forgotten
|
|
|
Paul you might be a "NEWBI" as you said but you hardware setup is nice!
You can swap with mine (piece of junk) anytime - ha ha
|
|
|
|
Thanks for sharing the detail about the Time Code effect. We all learn something (except Tony) - already knows it all
|
|
|
Wow - this is strange.
I could only get one to works for me.
The "60 minutes" version of the "29.97 FPS, Drop-frame (NTSC)" section - and it is an mp4 file.
All the PAL avi and mpeg2 files give me the error above.
As long as Clark711 doesn't need PAL (25fps) he should be ok.
|
|
|
Yea, much simpler, as Carl said, just revers the timer code.
I was getting an error when trying to import the tc_25fps_01min.avi - 25 FPS (PAL) - file when I was trying to test this (see screenshot).
Not sure what the issue is with that.
|
|
|
Another simple suggestion for the next PD version could be to have them use a sample video file that "Intelligent SVRT" will find (instead of using the Boat.wmv format).
This would be useful for newbies to play with and learn to use SVRT.
|
|
|
This might work:
Reverse the video.
Select a video on the timeline and click Power Tools to perform a range of powerful functions. Select Video in Reverse to enable the video clip to play backwards
Once the video is reversed you might add the timer like he did in:
https://www.youtube.com/watch?v=dpNSrP6G6k0 ), then reverse it again.
Then revers the video again
You might need to Produce it along the way and import it again.
|
|
|
I have noticed this happens to me when I added stabilizer to a clip and checked the "Use enhanced stabilizer" option, not sure if that is the case for you.
Paul1945 advice is good start though
|
|
|
I have the same result as you Heinz (with a much lower spec PC - nothing like yours).
What is interesting is the info box next to the "Use enhanced stabilizer" check-box. It said "...it is recommended that you switch to a non-real time preview or render a preview for the applied range".
The non-realtime part I understand but I'm not sure how to render a preview for the applied range? (edit: Found out how to do the render preview now - thanks to youtube )
Also I found that it will not render a title into the clip that is being stabilized as expected. In my case I have a bit of text that shows up in the middle of the clip. It looks like image stabilizer treats this as 3 diff sections.
First the section up to the title gets stabilized – then the section with the title – then the last section after the title. If you have some really shaky footage like I used then you see the “jumps” (looks like a cut) at these points in the produced video (This is not visible in the render preview - only when I produce the output).
My guess is I would have to produce stabilized clips first and then pull it back into the timeline to add the title.
|
|
|
For what you do – the beta is fine.
In future I would recommend you use the current stable version of software instead the beta version (unless you need one of the beta features).
|
|
|
Hi Babs2
2408 is the current one.
To see if it installed proper open PD.
Click on the PD camera image (top left corner).
That will bring up an about screen - and you can see the version on that page.
|
|
|
Hey Carl
I don't think Gottahaveitnow is pulling the audio files into the timeline.
I think he just downloaded them from Director Zone (and added them into PD13).
He then picked "Downloaded" in the "Media Content" dropdown (then he is getting the crash since he has downloaded more than 100 in that section).
I have only a handful so no issues (same as what he is saying when having only 10).
Gottahaveitnow this sounds like something you need to submit to support 
|
|
|
Lots of thinks come into play on this one.
How much $$ you want to spend and slots/power availability of your system.
Make sure to look at:
http://www.cyberlink.com/products/powerdirector-ultra/spec_en_US.html?&r=1
And this might also be useful (older version of PD but might help with the choice)
https://www.youtube.com/watch?v=AjPY6iY5Qxs
Review sites also tell you what card they use (so should be a good choice)
http://www.pcmag.com/article2/0,2817,2424347,00.asp
|
|
|
Thanks for the response tomasc.
My idea with this tread was to find out what others use as a good source format to keep their footage on HDD or DVD’s, but it is quite clear that it all affects the full video production life cycle.
The source is tied to what your camcorder/phone/gizmo supports and what you have it configured to create.
To save time during production and to use SVRT you need a source format that is supported and your output format to match.
The output format is critical depending on what you want to show your video on (TV/Web/other gizmo)
I captured a bunch of PAL videos from my camcorder in DV-AVI format (to get them off tape and edited) – just to find out that SVRT doesn't really work for that format (although it should). So now my “produce” time is going to be slow in any case. Next stop finding the best output format for my stuff
|
|
|
Yes - that is also a good point tomasc (and and interesting post).
I like to use Handbreak (vs 9.9 – I have issues with 10) to convert DV-AVI files for a quick review on my TV (viewable via a DLNA media server that transcodes it again for me). The Handbreak files (default settings) are good quality and much smaller size than the ones I produced in PD. The important part for me is to set the Deinterlace option to Fast on the Filters tab in Handbreak (else I see issues).
For my MP4 format output from the DV-AVI source I use a custom Profile and my Frame type is "Top field first" not Progressive (to avoid the "mice teeth" and hard coded interlaced artifacts you are talking about).
SVRT also finds this profile now when using the produced MP4 in other projects (making for faster renders).
My custom MPEG2 profile produced better quality output for me, and SVRT works perfect with it also.
|
|
|
PepsiMan you are spot on.
I have a Samsung SIII and the video I took on it is not bad (not at the Note level but ok).
PD 13’s new image stabilizer helped a lot to savage my shaky phone footage and with some funny PIP, a title and soundtrack – I created a nice short sport video - the players where happy
The only reason the Sony DV camcorder is still better is because it has an optical image stabilizer and optical zoom and no I will NOT admit how much $$ I paid for it 12 years ago.
|
|
|
Thanks for the info PepsiMan.
H.264 .MP4 is the output format I used for the first few videos I created in PD
I think I will try your suggestion of burning a Blue-ray, for an extra backup of my footage in addition to the HD backup I have.
My avatar shows my 12 year old Sony TRV60E (PAL) camcorder – that’s what I used for this project
Now all my S-VHS an S-VHS-C tapes (Camcorder died a long time ago), MiniDV tapes and my Panasonic S-VHS VCR are all in storage – to hopefully never be used again
And yes, a new camcorder and computer is on my wish list
|
|
|
I recently captured about 60 tapes in the DV-AVI format - Tape media will not last forever – or so I was told .
Half is from a Sony DV camcorder and the other half is digitized via the Sony Camcorder (using S-VHS input in the camcorder as a pass-through so the camcorder can digitize it so I can capture it via Firewire). The pass-through stuff has no useful timecode info and can be converted into any format (whatever is best – hence the tread). The Sony DV tapes do have useful timecode info (for scene analysis and knowing when footage was captured) so that would be nice to keep.
And yes, the camcorder is set to use 16bit sound – that is a good point!
My thought with the tread was not to convey what I use but rather to learn what all you guys(and gals) like best and use to store you digital video source files (if you do), so we all learn something
|
