CyberLink Community Forum
where the experts meet
| Advanced Search >
EXCELLENT!!!

Thank you Optodata! I'll remeber the "?" too.

2bskyhi
OK, last BTW example... Here's a YouTube video FROM Cyberlink that shows the screen I used to see in the EDIT tab.

Scene is at about the 37seconds mark:
https://www.youtube.com/watch?v=69pqLr5bhtA

Thanks AGAIN, 2bskyhi
BTW, this Cyberlink post suggests my EDIT tab should show the Photo merge feature I'm seeking:

https://www.cyberlink.com/learning/photodirector-photo-editing-software/136/incredibly-simple-way-to-create-panoramic-photos

Thank again, 2bskyhi
Sorry for the delayed response Optodata. Crazy Covid-world/ work distractions.... I hope you & your family are well... We're good...

You shared a screen shot of the EDIT tab that matches my Edit tab... Until I upgraded to PhotoDirector 11, the Edit tab showed, among many other things, an option to do photo-merges/ sticthing with a "Panoramic" feature--NOT just "Layers."
THAT panoramic feature is what I'm looking for. I searched on YouTube & the Forum and I've found no direction or posts for How-To do Panoramics in PhotoDirector 11....

Hopefully that gets us closer to resolving my issue since PhotoDirector 11's EDIT tab has changed significantly, w/ no obvious access to the features under the old PhototDirector 10 EDIT tab...

Thank you, 2bskyhi
Quote

Did you look in the \Pictures\PhotoDirector\11.0\username folder as mentioned in the linked post? On my system the username folder is actually \optodata_11.04\ but I have a newer version of PhD11 (subscription version) and I don't know if your folder will have an appended version number or not.

If that folder doesn't exist, use PhD's File menu and click on Open Project to see where it's currently looking. Note that on my system, The Select a project file dialog window only points to the Pictures folder, so you'd have to drill down to the PhotoDirector folder from there.


Sorry Optodata, I did not look at that post originally--an urgent honey-do interupted me--then I forgot it... I have since looked at it, but didn't get to the bottom of my problem... I did find the folder you mentioned, but no project .phd files were in there. And, I don't know that I should have expected any to be in there becasue I have never saved any since installing PhD11.

So, I reinstalled PhD11, then opened an older .jpeg that I had previously never opened with the original version of PhD11.
The Layers mode is still the default, and I see no way to make it go away to access the EDIT tab.

Can I roll-back to an earlier version somehow--one that works right? Am I the only one with this problem?

Just in case, I've included a link to my latest dxdiag file.

Thank you again, 2bskyhi
Quote Sorry you're having trouble with PhD11, and thanks for the screenshot.

The first thing to try is to delete (or maybe even better, rename) the latest PhotoDirector project (.PHD) file and see if PhD will launch correctly. It will create a new .PHD file, and if you've only just started editing, that should be all you need to do.

If you had lots of previous work from previous versions of PhD that you'd like to recover, see this post for more details. Note that your folders names will end in 11.0, not 10.0 as that post was written when PhD 10 was current.


Thank you for the response Optodata. That all sounds good & I'm happy to do as you suggest, but I don't know where to find that latest .PHD file--or any .PHD file. I did a Search in Windows & got no results.
Plz advise.

Thank You, 2bskyhi
Hi all, I feel like the solution to my issue is probably REALLY simple & I'm just missing it...

In response to a screen prompt, I recently downloaded & installed the latest update to PhD11.
Sadly, after I imported a couple photos, I selected the LAYERS tab. Now, the LAYERS mode is always ON and it won't go away. I can select any other tab, but the LAYERS tab is gone & it does not return--even after closing & reopening PhD11. While in this LAYERS mode, the EDIT tab is unresponsive. I need the "EDIT" tab function so I can choose to work on Panoramics etc. See screen shot of version & issue are "Here"

Please help me get the EDIT panel/ function back & share the secret to escaping this LAYER hell.

Thank You, 2bskyhi.
Quote

happy Easter, chris.

i have made an easier tutorials for you. it's too easy. really.

how to desqueeze(de-squeeze) decompress 1.33x Anamorphic aspect ratio borderless videos with HandBrake.
핸드브레이크를 사용하여 1.33배 아나모픽 종횡비 테두리 없는 비디오를 압축 해제하는 방법: https://youtu.be/sFa4ILR9auw

it is a Covid-19 LockDown special. ^^

be safe.
happy happy joy joy

PepsiMan
'garbage in garbage out'


Hi PepsiMan, I installed Handbrake & imported the default 1:33 anamorphic "Drone.mp4" test clip we were using previously. Everything worked fine, but there were a few differences in our versions of Handbrake, because I had several different options that I just ignored. After hitting the green Encode button, the produced video was properly desqueezed, but I had a couple of little issues I was able to solve. First, I had to Save the Preset changes several times before the Preset actually "saved" them(might have been me). So now all settings are saved & the entire process repeats reliably using the Preset. The only other strange thing was the file type kept trying to save as .m4v--not the .mp4 that I kept changing it to. Anyway, it works great now, and I like having another tool that works for anamorphic desqueezing. Like you said, the upscaling is overkill for most of my needs, so I can use the Handbrake preset for 4k, and the Custom .ini in PD18 for the higher-res option that I might need occasionally...

THANK YOU VERY MUCH AGAIN for helping me with this!!!
Chris
Quote

happy Easter, chris.

i have made an easier tutorials for you. it's too easy. really.

how to desqueeze(de-squeeze) decompress 1.33x Anamorphic aspect ratio borderless videos with HandBrake.
핸드브레이크를 사용하여 1.33배 아나모픽 종횡비 테두리 없는 비디오를 압축 해제하는 방법: https://youtu.be/sFa4ILR9auw

it is a Covid-19 LockDown special. ^^

be safe.
happy happy joy joy

PepsiMan
'garbage in garbage out'


Thank you very much PepsiMan. I downloaded Handbrake last week when I reinstalled Windows on my tablet, but I've not yet had a chance to check it out.
Finally getting around to tackling my taxes... No "Happy or Joy"
I will try your workflow ASAP and let you know how it worked--can't wait to try it. I'll let you know how it goes.

Thanks again, Chris
Quote I'm really happy to hear that! Not everyone is willing to start over with a new Windows installation due to video editing problems, and yet whenever they've done so (here on the forum), it usually results in PD working properly.

Congratulations on seeing this through to the end, and now you can concentrate on making content. Nice job! cool



Yes! There is a fine line between stubborn & persistant, and I often blunder into stubborn due to enough good outcomes from my persitance... Probably a proverb in there somewhere.

Again, I coudn't have done it if you all lacked saintly patience smilesmile

Thanks again, 2bskyhi
Quote



Ok, all sounds good Tomasc & Optodata. I did download & install the .99cent codec that Optodata shared--right after he suggested it--I just forgot to let you know...

You guys have fast forwarded my learning curve on some of the MANY complexities of these format/ encoding/ hardware & software issues. Since I don't have a serious gaming PC, I should'nt expect killer performance...

I will play with(study) VDub2 and Handbrake(that I just downloaded) to see what the limits of my system/ workflow are. I am confident that you both exhausted every effort with me & that the limits are in my laptop & my expectations(hopes).

4k max seems like the reasonable res expectaion, especially since I'm prioritizing multi-platform/ player over absolute best res...

THANK YOU BOTH VERY MUCH for all your help! Sorry I can't award you both the "This solved my problem" flag...

Take care, 2bskyhi



To Tomasc, Optodata & PepsiMan. I just wanted to follow-up and let you know that all your efforts were not in vain! I was UNable to resolve my WMP issue without doing a completely fresh install of Windows(10Home). As I did the install, I VERY gradually added all my programs/ software & tip-toed thru SOO MANY settings. Now, Optodata's final set of instructions for my anamorphic workflow works PERFECTLY. I can play the full-res produced version from PD18 on all desired platforms(at full width--Letterbox), except for my Galaxy S8 phone. But, by running the hi-res video thru PD again, and producing at the second highest default res, it plays just fine on my phone too! HAPPY HAPPY, JOY JOY:

I suspect a codec or somehing got broke in all my initial efforts...

Thank You all VERY MUCH again, 2bskyhi
Quote

Do not have the Drone Y clip in my download folder. You can re-download optodata’s posted clips and try them on your pc and cell phone. The created anamorphic 5k and 5.7k videos are a burden to run on any smartphone which supports only 4k videos max. Posting them to a streaming service like YT or creating the lower 4K resolution videos may be the way to go.

I downloaded 4 different video players from the Google play store including VLC and the only player that will play them is U player on an 8 core cpu smartphone. Have not found any android player that will play the HEVC 4k MOV files from my Ipad Pro or an iPhone. You are welcome to downloads the hundreds of them to see which work best on your phone.

Creating the screen capture shows that the Intel UHD 630 graphics can encode beyond the 4k to the 5.7K videos that I did not expect and svrt can be available in a Desktop but maybe not at all in a laptop it seems from your report.

Every player you mentioned played the same created anamorphic videos properly on my pc. You may have the less feature VLC win 10 app instead of the full version installed. Windows 10 removed the HEVC playback from the initial offering 4 years ago. Installing the same codec from the MS store that optodata posted the link earlier for 99 cents should allow you to play the same files on WMP that works in both optodata and my pc.

Good luck on your endeavor on your goal for the cell phone and the laptop!!



Ok, all sounds good Tomasc & Optodata. I did download & install the .99cent codec that Optodata shared--right after he suggested it--I just forgot to let you know...

You guys have fast forwarded my learning curve on some of the MANY complexities of these format/ encoding/ hardware & software issues. Since I don't have a serious gaming PC, I should'nt expect killer performance...

I will play with(study) VDub2 and Handbrake(that I just downloaded) to see what the limits of my system/ workflow are. I am confident that you both exhausted every effort with me & that the limits are in my laptop & my expectations(hopes).

4k max seems like the reasonable res expectaion, especially since I'm prioritizing multi-platform/ player over absolute best res...

THANK YOU BOTH VERY MUCH for all your help! Sorry I can't award you both the "This solved my problem" flag...

Take care, 2bskyhi
Quote OK. Back at my pc now configured to use Intel UHD 630 graphics like yours. Would like you to check out the created and uploaded 5K drone video on YouTube with any 5K capable smartphone viewer. The link is here for the 4 second video: https://youtu.be/X7c8QFQHwRU .

Before going further please view the screen recording showing the PowerDirector clips, smooth playback, their properties and resolution, svrt status, hardware encoder status, using the Intel integrated graphics on my computer. As you can see, no Hardware Acceleration was enabled and no shadow files were used. This should help answer questions on using either of the two options on my previous post that whether Intel hardware encoding or SVRT can be available. SVRT is available in the right circumstances. Hardware Intel OS encoding is always available. Link to this screen recording: https://youtu.be/g3vWq5gAVMc .

The same SVRT and Hardware encoding are available in PD14 and PD17.



Hi Tomasc, thank you, I want to try the 3 files in my PD, while following your video, but my "DroneY" clip is corrupt. It won't Import into PD 16 or 18. I checked my link to it & it seems I deleted the source. I looked in my Trash folder on PCloud & nothing with that name or file size is there??? Can you please re-share it with me. Sorry...

Thanks again, 2bskyhi
Quote



Thank you Optodata & Tomasc. Lots to tell...
First, Optodata, my PD18 is not a trial version(~$85), so I installed it, and after desqueezing "Drone.mp4" in VD2 w/ your 5184x2160HEVCRevB project, it Produced w/ your 5148x2900Intermediate.ini profile with no error messages. So progress?

To begin addressing Tomasc's playback format question: the above mentioned video only plays in WinMovies/TV--NOT in WMP, VLC or on my phone. WMP is the only one that gave an error message & it is here, and the produced video is here. The playing results are the same with & without running the PostPDRevA.vdproject thru VD2. Also w/ PD18, I now have IQSV checked beside the checked box for FVRT.

So to elaborate on my intended uses: I am a fledgling commercial drone pilot &, to date, the most my customers have wanted to do is put my drone video on websites--as background to a homepage, like a winery, or for multi-use like a wedding or 5k race--including sharing on phones--social media. My default resolution preference not surprisingly, is to produce max resolution where possible, but I acknowledge the overkill for most of these uses. Ultimately, I would prefer the option to produce a high-res version for saving--then share the lower res version for platform universality....

So when I try Tomasc's option 1 in PD18, with the "Drone.mp4" video first desqueezed in VD2 w/ the 5184--revB project, it "Produces" error-free using the default HEVC 3840x2160 37Mbps, and it plays great on VLC & Win Movies&TV, but NOT on my phone or in WMP(& for WMP it produces same error message linked above). Here is that default profile video. Do I need to desqueeze with a different project-spec since I'm producing at the lower res/ default profile?

I also tried option 1 with same workflow & files using PD16. The only difference is: the video plays great on my phone, & the FVRT is still not selectable...

Sorry if I'm driving you both crazy....

Thank you AGAIN, 2bskyhi



BTW, not sure why I didn't think of this sooner, (drinking now)but do either of you have a small, but high-res video reference clip you can share, that I can download to acid-test my "players" mentioned above. If my players/ graphics prove worthy, then we'll know my issues are program/ profile/ project related right?...
Quote I added that post because I wanted to make sure you didn't have any 1s in the registry profiles that would keep you from using either of the quicker production routes: SVRT (CPU-only copying with little to no actual producing); but mostly Intel Quick Sync Video (aka hardware producing).

In all honesty, SVRT won't work here because we're working waaayyy outside PD's normal working profiles. Also, if I'd checked my system before posting, I would have seen that neither option is available to me when working with the desqueezed project either. I was just trying to think of things for you to try to get past the production error...

Since you have PD18, I think it's worth a try, especially since all of the clips work for me and I don't see any schizophrenic behavior with AVC/HEVC clips and PD/VLC. Please make sure you don't install the trial version (or that you uninstall it if you've already installed it), because it won't let you work with any 4K or higher clips at all.



Thank you Optodata & Tomasc. Lots to tell...
First, Optodata, my PD18 is not a trial version(~$85), so I installed it, and after desqueezing "Drone.mp4" in VD2 w/ your 5184x2160HEVCRevB project, it Produced w/ your 5148x2900Intermediate.ini profile with no error messages. So progress?

To begin addressing Tomasc's playback format question: the above mentioned video only plays in WinMovies/TV--NOT in WMP, VLC or on my phone. WMP is the only one that gave an error message & it is here, and the produced video is here. The playing results are the same with & without running the PostPDRevA.vdproject thru VD2. Also w/ PD18, I now have IQSV checked beside the checked box for FVRT.

So to elaborate on my intended uses: I am a fledgling commercial drone pilot &, to date, the most my customers have wanted to do is put my drone video on websites--as background to a homepage, like a winery, or for multi-use like a wedding or 5k race--including sharing on phones--social media. My default resolution preference not surprisingly, is to produce max resolution where possible, but I acknowledge the overkill for most of these uses. Ultimately, I would prefer the option to produce a high-res version for saving--then share the lower res version for platform universality....

So when I try Tomasc's option 1 in PD18, with the "Drone.mp4" video first desqueezed in VD2 w/ the 5184--revB project, it "Produces" error-free using the default HEVC 3840x2160 37Mbps, and it plays great on VLC & Win Movies&TV, but NOT on my phone or in WMP(& for WMP it produces same error message linked above). Here is that default profile video. Do I need to desqueeze with a different project-spec since I'm producing at the lower res/ default profile?

I also tried option 1 with same workflow & files using PD16. The only difference is: the video plays great on my phone, & the FVRT is still not selectable...

Sorry if I'm driving you both crazy....

Thank you AGAIN, 2bskyhi
Quote Oh I'm very sorry to hear about the job situation, and I hope that everything will eventually work out for you.

The issue you found was caused by me having your original clip open in VD2 when I saved the RevA project, and so it also wanted to open that clip from the same location on your computer. I've removed the clip and saved the project as RevB, attached. Please let me know if there are any other issues!

There was another problem relating to you being unable to produce using the F.r.v.t. box, and it might help to review this post to see if you can recover that capability. It would help to know if either of these methods will let you produce the clip without the error message from PD.


Thanks for your kind words Optodata, my employer actually loves me, so I'm good. They have no work now, so they're just furloughing me so I can get unemployment... And they're covering my health insurance costs for as long as the Virus takes to subside... all too soon, I'll be back at work with unlimited O.T....

Unfortunatly, I'm still not able to Produce the video in PD. Your RevB VDub2 desqueeze seems OK, but I don't know why the Production is failing. I get this same error as before when I hit "Produce". I read thru the SVRT thread you shared, but no luck. Not sure it matters, but most of that thread looked to be dealing with PD13 & 14. My registry shows all data logger values are zero with PD closed...

Just a thought, if the VDub2 project & .ini file are good, maybe there's a problem with my PD16--SVRT or otherwise. Since I bought the PD18 upgrade, and, so-far I'm UNABLE to recover the SVRT, should I try installing PD18? I have my saved copy of the .ini file...

Thanks again, 2bskyhi
Quote So tomasc PM'd me with some findings on the bitrate of the VD2 files, and he noticed that I had the quality set improperly. I've made the necessary adjustments to both .vdproject files so that the bitrates of the videos produced by VD2 are equal to the original, which is 35Mbps.

Use the attached RevA versions to get higher quality desqueezed and final videos cool



Thanks Optodata, sorry I was slow responding, but I had to apply for unemployment today...

Unfortunately there seems to be a problem w/ the 5184x2160 HEVC RevA Project file. When I try to do Step 1 of your instructions and load that project into VDub2, I get the error message shown: Here

Thanks again, 2bskyhi
Quote Thanks for sending that over. I think that 4096 profile was the last one in my system's Profile.ini and I mistakenly kept it when I was adding the intended version.

So right now, the only time you can produce is when you select the 4096 profile and you get the error message if you try to produce using the 5184 one, correct? Have you tried producing with the Fast video rendering technology box on the Produce page unchecked?

Also, your Intel video driver is almost 7 months old (v7262) and there's a much newer version out now (v7985). However, Dell makes it hard to install "OEM" drivers, so your best bet is to go to their support website and make sure everything else is up to date. For one thing, there's a BIOS update available if you're up for installing that, but I wouldn't expect that to be related to the producing issue.


Thanks for still responding Optodatasmile. Yes, only succesful "Produce" is with the lower res 4096 profile & error message pops up wheever I try the 5184 profile. And its interesting that you ask about the Fast Video Rendering Technology(SVRT). That box is not checked & it is not illuminated such that I am able to check it... Don't know what that means...

I will will try to persue the driver & BIOS updates after dinner.

Thanks, again, 2bskyhi
Quote OK, but first another forum tip: the forum index doesn't update or send out any notifications if you edit an existing post, so whenever you have new info please use the Reply to this topic button. That has the added benefit of not copying the entirety of the previous post

So I've looked at the two intermediate profiles I shared, and none of them have "4096" in them anywhere. The first (sent Mar 26) was 5148x2880, and the one from yesterday (Mar 28 ) was 5184x2990. They're tied directly into the VD profiles so you can't mix & match them.

Take a look at the properties of each clip in PD so you can see the actual resolution and let us know what each of the individual clips shows on your successful run.



Thanks for the Forum tips Optodata. Sorry I'm slow. I'll "Reply" w/ all new info. So as requested, I checked all three "succesful" clips and they are all 4096x2160. As soon as I got the 5184x2900 intermediate file from you, I deleted the 5148x2160 file--to save me from confusion. The first list of data in my Custom .ini file has frame specs 4096x2160. The second(& 'only' other data set below it) has the 5184x2900 frame specs... Here's the actual .ini file: https://my.pcloud.com/publink/show?code=XZqRvMkZh6pN73uEVTbjUSaGq3ymkVh5BgAV

Thank you AGAIN, 2bskyhi
Quote PepsiMan has a point that this is getting complicated again. Even though I also went to (only) public schools, I'm just trying to see this thing through

2bskyhi, one thing I can't tell from your screen captures is whether or not those black bars are permanently present, or are simply the result of playing a 2.4:1 video on a 16:9 monitor. The way to tell is to take the player out of full screen mode and drag one of the corners towards the middle.

If you're doing that with either of my finished clips, you should be able to get the window frame in contact with all 4 edges of the media, just like my earlier screenshot showed.

If you try to do that with the clip you've produced in PD16, you'll see that the upper and lower black bars are always present, and will even force black bars along the left and right edges if you squeeze the vertical dimension too far. That's because PD always produces to the project's fixed aspect ratio setting, even when the pixel sizes in the producing profile do not match that.

If PD could produce a 500x25 or 5184x2160 strip of video directly, we wouldn't need to use VDub2 for a post pass.

However, you'll notice that the Intermediate profile I created is 5184x2900, which is both axes desqueezed into a 16:9 frame. Since the profile's horizontal size exactly matches the clip size, PD creates the empty, black bars along the top and bottom to fill in the missing areas.

In order to remove the black bars, we need to run the clip through the post pass in VDub2 to actually crop the unwanted 370 lines of pixels above and below the clip so we end up with a video that's truly 5184x2160 (instead of what PD gave us, which is 5184x2160 content inside a 5184x2900 video frame).

Does this whole process make more sense now? I hope so, and I'll post the updated steps in the next post for clarity innocent



Thank you both so much AGAIN.
So regarding Optodata's first question re. format & Tomasc's expanded description to check it, I suspect this format issue is likely as good as it needs to be--all I hoped for.... Following Tomasc's instructions with the same "DroneX" video he used to test, I am able to eliminate all black bars in VLC, WMP & WIN Movies & TV, but I never ran it thru the post project in VDub2. Anyway, that clip is NOT the "Final" one that I produced with Optodat's last instructions. That clip is here: https://my.pcloud.com/publink/show?code=XZlk3MkZC7xwC3WiYvmOdbVaHRXBebmDtT67

So for one more func check, I decided to load the last 3 versions of my test videos(DroneX, DroneY, and Final) into my Galaxy S8. (I know I feel your eyes rolling now--justifiably so). But what I found was, that the only clip that played without stuttering, was the "Final" version. Since cell phones are a likely share platform for my productions, I think I'll quit while I'm ahead & before you all get sick of me...

I just shot a new test video & ran it thru Optodata's LATEST instructions including the post in VDub2 and it worked perfect for all 3 players & on my phone!!!!!!!!!!!!

So I can finally give you all a break. Tomasc, PepsiMan(Happy Happy, Joy Joy) & Optodata you're all rock stars. I can get pretty OCD & persistent when I need to learn something, but I don't often find other's who are so willing to tolerate this many rookie questions about such technical minutia...

THANK YOU ALL AGAIN! 2bskyhi

Well, it figures... I spoke too soon... I discovered that the Custom profile I used for step 4 of your latest instructions, was in fact the first one you sent me--with the 4096x2160 default res that is just above the 5184x2900 Intermediate.ini you sent me. When I try to use the correct profile w/ 5184x2900, I get this error in PD: https://my.pcloud.com/publink/show?code=XZJrGMkZE35IQrhP6KpsNBSYR6jdoRuvGwp7
When I examined the .ini file, I noticed several differences, but I don't know how to enterpet them....

I'll understand if you want to surrender...


Thank You, 2bskyhi
Go to:   
Powered by JForum 2.1.8 © JForum Team