|
|
Always worth a try anyway 
|
|
|
|
Try saving project, closing PD and then opening again.
|
|
|
|
Quote:
1) Getting it to work with Haali (what splitter do you use)
I used to use ffdshow and Haali with a couple of different players but now just use Splash lite (and have un-installed other codec packs). Remembering, though, I am not using my PC as a HTPC - just for playback of raw and rendered files during the editing prosess(es).
Quote:
2) Seeing why Avivo does not work for me with PD9
It seems PD have spent a little more effort being compatible with nvidia than ATI.
|
|
|
|
Quote:
I've got the same camcorder. I edited the 50p footage fine, but the final production looked choppy on a Blue Ray. I reccomend converting the 50p clips using the camcorder's software (HD Writer AE) then doind the editing. If you plug the camera in the conversion is pretty fast.
If you want to use the footage on your computer, then the above does not apply.
This brings up the whole question of why do you want 1080p50/60?
Most people's set up can only handle 1080p24/25/30 or 1080i50/60. This generally applies to those who are playing Bluray/AVCHD format discs/folder structure. Some late model Panasonic Bluray players can handle the p50/60 files natively and also in AVCHD folder structure. PS3 has its role as well.
Others like myself have 1080p50/60 playback capabilities (eg Dune mediaplayer going to 1080p panel) and can enjoy the unadulterated 1080p60 in it's glory.
Also some have been suggestion archive original footage at 1080p50/60 to maintain highest quality then you can re-edit later when their AV equipment has caught up. I suggest those who will come back and re-edit several years later are kidding themselves!
So I suspect the best solution if you are passionate about maintaing highest quality is to shoot and edit in 1080P50/60. Render in 1080p50/60 (for later) and then re-render to 1080i50/60. This may be less favourable than shooting in 1080i50/60 in terms of time and difficulty of editing and rendering quality but is a trade off.
|
|
|
|
Nathan, do you sleep?
|
|
|
|
Quote:
You really don't know the "true" bit rate only what the Camcorder or PD decided to put in the header.
Thanks
Nathan
This is the same reason encoding the same clip numerous times will result in differing bitrates and duration (albeit very small differnces)
|
|
|
Sorry but I also have tried to reproduce problem and cannot.
As you probably know just adjusting the audio levels and no other editing does not result in changes being saved (this bug is known). You need to get the "*" to appear on your project name before audio changes are registered.
|
|
|
The latest patch has fixed my GPU (CUDA) rendering at 1080p60. (It used to produce an error code)
For reference if it means anything to anyone interested:
Original raw clip is encoded at High@L4.2 with 4 reframes.
SVRT rendering after tweaking max bitrate is identical (of course).
CPU rendering default is Main@L5.1 2 reframes
GPU rendering default is Main@L4.2 2 reframes
CPU and GPU rendering at High is L4.2 2 reframes which is closest to original raw profile.
Interestingly CPU rendering often produces a variable frame rate not 59.94 and this causes havoc with my media player : takes ages to load and does not auto select frame rate properly.
Taking full frame snapshots of resulting files reveals both CPU and GPU rendering to be slightly "softer" but it is marginal and in my opinion nothing in it.
Thus I recommend using GPU rendering at High profile with a custom profile changing the average bitrate to 28Mbps and max bitrate to 32Mbps.
Hope this helps.
|
|
|
|
Quote:
As pjc3 said, if you want NOT to re-encode the video you will need to edit the min bit rate in your custom profile to accpet clips that are lower than this. You can always test that the resultant file will play but I see no reason why they would not.
Yes, credit should go to Nathan for showing us the tweak.
|
|
|
|
Quote:
clip should go through as normal providing you don't add any further transitions or video enhancements.
'tis a shame even trimming the beginning of a clip is considered a video enhancement by PD 
|
|
|
I tried to reproduce SVRT not rendering low bit rate but even with a mix of your test file (9.1Mbps) and one of 3Mbps the SVRT for a custom profile was no rendering required.
However you can change the minimum bitrate for a custom file by going here:
C:\Users\[YourUserName]\AppData\Roaming\CyberLink\PowerDirector\9.0\Profile.ini.
Then opening the file in notepad. Scan for the custom profile name eg <Custom Profile -4> and then find the min bitrate value and change to whatever you want.
Save the file and restart PD.
See how that goes.
|
|
|
|
Quote:
Hi pjc3,
Does PD9 support any surround-sound audio formats e.g. 6-channel WAV files? I suspect not.
Gary.
Amazingly yes it does! (LPCM) But not AC3 files which is unfortunate.
|
|
|
|
Quote:
I noticed that 60i video is always saved in 30p, regardless of the format chosen
No so.
Not sure what profile you are choosing but my 1080i60 is rendered at 1080i60.
|
|
|
Hi Gary,
IMO PD is poor for audio editing. It does preserve the original 5.1 audio if you select it in produce tab and it will mix stereo audio tracks to 5.1 but you have no control over the distribution of channels. Wave Editor (bundled with PD) is also only a 2 channel application.
So I use another NLE to tweak the audio if I need to.
Probably not the answer you wanted to hear.
|
|
|
|
Surely it would be best to use a custom Mpeg profile to allow SVRT and then (hopefully) a lot of the original footage is not rendered.
|
|
|
The last 3 projects I have completed with PD9 to seem to have a different audio quality when compared with PD7 (I skipped PD8 ). I render using DD 5.1 and both music tracks and recorded audio seems to have a "hollow" quality.
Any one else or just my imagination?
|
|
|
Hi Philip,
I haven't downloaded the clips but watching the Youtube clips it is apparent the mpeg clip has not been rendered at full frame and thus the effect of the filter to keep the subject stable causes the full video clip to be moved around the frame (see the black lines top and bottom) The Avi file will have the same movement but the edge of the clip is beyond the frame and hence you don't see it.
Thus I believe the problem is with the rendering which is not expanding the clip to full size.
|
|
|
Overlap for me also.
|
|
|
From the Apple TV website supported formats:
H.264 video up to 720p, 30 frames per second, Main Profile level 3.1 with AAC-LC audio up to 160Kbps per channel, 48kHz, stereo audio in .m4v, .mp4 and .mov file formats
From mediainfo from a file rendered for Apple iPad:
sure looks to me like they support Apple!!!
|
|
|
|
Quote:
The original is 1920x1080 59.94i,
Ah, interlaced not progressive as first described!
You should be selecting AVCHD 1920x1080 (fourth box down in defaults) and NTSC. This should be the correct output to match your input files.
If you really want progressive, do not select the 1920x1080p preset because it renders at 24fps.
Otherwise I cannot really help as all my interlaced footage renders as top field first and plays back as interlaced should.
|
|
|
Just a quick question.
Is the original file resolution 1080p24 or 1080p29.97?
Perhaps posting mediainfo for the original file might be helpful.
|
