|
|
If you are interested in getting the most out of 1080p60 have a read here.......
http://forum.cyberlink.com/forum/posts/list/15533.page
|
|
|
|
Quote:
Are you seeing any lipsync issues with GPU rendering and FixPD9?
None that I have noticed. However I don't use FixPD9 routinely as my nVidia rendered 1080p plays beautifully on my Dune 3.0. I only use it when I am exporting to other formats.
|
|
|
|
What model of TV do you have?
|
|
|
Perhaps it is time to post a native .MTS file for download and I will do some testing. I have a Panny GT30 I can test them on.
Regards
|
|
|
Told you so 
Thanks for the update.
|
|
|
|
Quote:
When you say you use progressive video in PD - is this due to a change of camera, as in the footage you are working with is progrssive?
1080p60 from the two newer Pannys and 1080p30 from the GoPro (see my signature). I rarely use the SD9 now due to the problems with interlaced format while editing (and also the SD9 uses a variation of AVCHD which PD doesn't really like much!)
|
|
|
|
Quote:
Can anyone explain why I cannot get this result from PowerDirector alone or where I am going wrong?
I am not an expert in video encoding language so my explanation is the result of reading and experimentation.
PD firstly has a problem with interlaced video. I now use progressive video in PD and am happy with the programme. I use another software if I need to produced interlaced video from progressive output from PD9.
I believe part of the problem is the information PD writes to the "header" of the video file. This is what the media player reads to know what is coming up. I can produce a video segment multiple times and it plays fine on some occasions and then has field order reversed the next. Also some media players cannot read the files correctly and has trouble displaying them but simply remuxing fixes the problem. This is indeed what you have discovered using VSX3. There is a little app written by jmone which simply demuxes and remuxes the files and fixes them. This is just rewriting the header info correctly.
The link is here but is specific for 1080p material. I haven't tested for interlaced video.
http://forum.cyberlink.com/forum/posts/list/15533.page#75776
This may be adapted for your files and save using X3.
Hope this helps.
|
|
|
Quote:
Report 001: The ticket reference numbers are being investigate - email confirmation received from CyberLink, Taiwan.
Thank you for the diagnostic data.
Gees Dafydd,
the number of times you are being used as an online support person is ridiculous! If you are not being reimbursed by Cyberlink, you are the most patient and altruistic cyberbunny I have come across. Surely free version updates just aren't worth the effort you put in 
|
|
|
|
Quote:
Even Disney is working with bitrates of 5 even 3 M for their DVDs ,
Hugo
All very well for Disney who use a hardware mpeg2 encoder costing hundreds of thousands and have source material which is film or 4K video
Quote:
the HQ encoding is as good as anyone's in the price range or 5x for that matter.
Disagree!! Google will let you know a few comparable priced encoders which do a better job. I am a fan of PD9 for HD but it is pretty poor for SD mpeg transcoding.
|
|
|
http://forum.cyberlink.com/forum/posts/list/16902.page#85006
try this (I used the search function).
|
|
|
|
Quote:
I asked this a few months back but forgot what we did.
refresh your memory using the search function?
http://forum.cyberlink.com/forum/posts/list/17144.page#86586
|
|
|
|
Quote:
In my case the single least obvious setting which made the difference and made it possible to playback perfectly on PS3 was changing the High profile (the original file was High profile) to Baseline profile.
I hope that this will help others who want to use PS3 as media player for 1080 50P.
Well done! This is an important find which I don't think has been mentioned before. If it is universally a fix for PS3 rendering then I suspect many people will benefit.
Pleased to hear you got it sorted.
|
|
|
Hi MateuszPK
1.
2.
Reduce blocky Artifacts off
Hardware decoding is for GPU playback (unlike GPU encoding which is for rendering)
I have single IDR H.264 checked (but still couldn't get SVRT to work for your file)
As above decoding is opposite of encoding.
3.
Sorry I wasn't too clear here. I rendered the files and then ran the files through the header cleaner (this just rewrites the files with the correct information so the end mediaplayer (PS3) recognises the video properly). This is Nathan's FixPD9 script. I pulled a couple of representative frames out as bitmaps to compare the video rendering with regards to blocking artifact, blurring or softening, de-interlacing artifacts (not relevant in this case) etc etc. This only gives some of the answers as motion picture is quite different from still frames but can help pin down where the problems lie.
4.
The fixPD9 (as I call header cleaner) allows the files to be recognised correctly by the mediaplayers. Dune handles the files anyway but PS3 is more fussy. My CPU (ie PD9) writes a file which results in the profile level being written as 5.1 (which it is obviously is not) and fixPD9 rewrites it back to 4.2. GPU rendered files do not have this problem (for Nvidia card with a specific driver which is not the current one!! ) So there are many variables to contend with.
|
|
|
Hi MateuszPK,
I am sorry to hear you are having troubles with your 108p50 files, because it seems you have done all the right things to get PD to perform as I know it can.
To give you my experience:
I downloaded your file.
I created a modified profile and rendered using both CPU and GPU (they produce different files).
I used another (unmentionable) programme to pull individual full frames as bitmap and png from the original and rendered files.
Comparing these images I could see a slight "softening" in the rendered frames but it was very subtle. Generally it was comparable to my previous results using Pana TM700 1080p60 files.
I ran the rendered files through Nathan's header cleaner.
I watched all files (original, rendered, cleaned) back to back on a Panasonic 50GT30 plasma using Dune mediaplayer set to 1080p 50Hz. All files looked identical in motion and resolution. Silky smooth.
So in summary, my testing produced results which I would consider excellent.
Differences to your setup:
I have a Nvidia card. I have a Q9550 processor. I have a Dune mediaplayer. Not sure where the problem lies with you.
Sorry not to have been much help.
Regards
PS: I could not tweak the profile to get SVRT to work, unlike the Pana 1080p60 files. Interestingly, I could never get my Pana SD9 to work with SVRT even with the parameters set adequately. I suspect the AVCHD profile in the files is just different enough for PD not to recognise them.
|
|
|
Yes, but there is more to it than a simple answer.
Check out this thread.
http://forum.cyberlink.com/forum/posts/list/15533.page#75540
TM900 files are same as TM700. With tweaking behind the scenes, PD9 can produce stunning output almost identical to the original files.
|
|
|
|
Thanks Tony ...speed of service is impressive as well
|
|
|
The effects you are seeing has been described in various forms on this forum and is due to the poor handling of interlaced files in PD. PD just line doubles causing awful combing, loses half of the available information and causes all that panning judder people complain about (as well as the softening you are seeing).
Simple test:
Produce a jpeg in paint of 1920x1080. Draw a diagonal line. Render the video in progressive and interlaced format. Take a still from the resulting video file. Attached is the crops to demonstrate. ( If Tony could embed them, that would be great  )
First file is original, Second is interlaced, third is progressive.
|
|
|
Whilst I know that we are not meant to mention other software, but I would like to point out that I still use PD because I can use freeware tools to overcome the inadequacies of the mpeg and h264 encoders (because they are crap after all).
PD has an excellent front end but has problems behind it and freeware can improve the final outcome. As a freeware tool, these mentioned programmes are in no way an alternative to the excellent editing abilities of PD and thus should not be a threat to their business but a resource to be utilised to make sure users can continue to enjoy PD and stay (relatively) happy customers.
|
|
|
|
Quote:
.....and requires a Blu-ray player.
This is stated often but is not true. Panasonic DVD recorders play AVCHD discs no problems. There may be other DVD recorders/players which can also play them.
|
|
|
GR,
Sorry to hear your woes. The Pana is a great camera. PD9 however is a good editing suite but has some problems which I believe you are experiencing. It has a problem with interlaced h264 video where it can produce some awful combing artifacts which it seems you may be seeing. This is why I recommend you shoot in progressive even if you render to interlaced.
If I use PD9 as my sole editor from import to final disc production, I use 1080p60 clips, edit to desired result in small sections (about 20mins), render to AVCHD 1080i60 for AVCHD disc or 480p for DVD (you would use the 50fps equivalent).
You should not keep transcoding to other formats. Stick to AVCHD (except if you are burning to bluray when for some reason mpeg2 BR profile has fewer interlacing artifacts!?!!)
If the video is for your own viewing, I highly recommend you get yourself a mediaplayer and go the 1080p50 route .....the difference is noticeable!
|
|
|
|
Quote:
Making progress I think. Although I still cannot see how I can change the camera settings to PAL from NTSC (I'm waiting to hear from Panasonic) I followed advice here and discovered that Power Director will, after importing NTSC clips, allow me to convert the edited output to PAL which will give me what I wanted.
My I ask what your final format/ use is going to be? DVD? UTube? PC?
The reason being is that it would be much better NOT to change the frame rate. You will notice judder and this can be quite distracting especially on panning. As mentioned above, virtually all recent equipment in PAL countries quite happily play NTSC media.
|
