PDA

View Full Version : Can't create a new encoding profile?


oh yeah guy
11-13-2008, 07:49 PM
Recently installed PSP 4.03 from 2.25. When i attempted to create a new encoding profile in settings it doesn't ok saying The resolution you have is not supported. Please use a smaller resolution. Just to be sure i choose some of the pre-encoding installed and just named it custom or something else. Still the same message. My PSP is a 1000 type.

Gezza
11-15-2008, 11:07 AM
I dont have a solution but i do have exactly the same problem. It makes the new version
pretty useless for me, since I exclusively ise custom profiles.

Any solution gratefully accepted!

webgeek
11-16-2008, 01:13 PM
I had the same problem, you can replicate by going to the Setting tab, picking a profile with video size 480x272, pressing Edit Profile and then pressing OK - you don't even need to make any changes to the profile. I'm guessing there is a bug in the code that validates edited profiles.

I did manage to create myself a new profile, however, by editing the profile XML file directly - obviously taking a backup copy of the XML file first - I copied&pasted an existing profile and edited that new profile.

I was stumped at first though because editing the PSP.xml file in
C:\Program Files\Red Kawa\Video Converter App\Profiles
had no affect, so I did a search and found a second place the profiles are stored, namely:
C:\Users\[your user name]\AppData\Local\VirtualStore\Program Files\Red Kawa\Video Converter App\Profiles

Hope this helps.

Red Kawa
11-26-2008, 12:37 PM
It appears we had some resolution checks left over from a long time ago. These checks were not accurate since they were based on total pixels and not macroblocks like they should have been.

Since it is difficult to determine the number of macroblocks without a set fixed framerate, we've decided to just get rid of the resolution checks. We figure that people using custom profiles in power mode no what they are doing anyways.

You guys should no longer run into this message box in 4.04.

Thanks for reporting this issue.