PgcEdit v9.2 released! (16 February 2009)

[r0lZ]

No. The CLB format is just a binary dump of the palette as it is stored in the IFO. The important thing is to output the original color values, without converting them. The file format doesn't matter much, as long as it can be easily parsed.

[turbojet]

Ok I'll have to wait and see what that program will output. Currently only seems like a standalone ifo is in the works which I don't think will help my situation one bit.

In the mean time I can use pgcedit's idx import feature for everything but colored subs. I don't mind the 1 tone lighter gray, in fact I wouldn't even notice it without comparing to original.

Thanks for adding it and will I'll patiently await the release.

[turbojet]

I thought of another way to get sub colors (maybe accurate?) in BDtoDVD process is from the BDsup. Is there any chance of adding support for this?

[r0lZ]

Hum, I don't think so. The SUP file does not contain the palette information. Furthermore, it contains several subpics, and they may have different colors.

[0xdeadbeef]

Just in case anybody is interested: BDSup2Sub is now able to optionally export the text file containing the palette when exporting SUB/IDX or SUP/IFO.
A quick test indicates that it seems to work although I took the liberty of adding a comment line (starting with "#") and removing the leading tabs.
Hope this helps.

[r0lZ]

Thanks for your work, 0xdeadbeef!

Can you post an example of a file produced by BDSup2Sub here?

[0xdeadbeef]

Originally Posted by r0lZ

Thanks for your work, 0xdeadbeef!

Can you post an example of a file produced by BDSup2Sub here?

Sure. It's not overwhelmingly interesting though:

# Palette file for PGCEdit - colors given as R,G,B components (0..255)
Color 0=0, 0, 0
Color 1=240, 240, 240
Color 2=204, 204, 204
Color 3=153, 153, 153
Color 4=51, 51, 250
Color 5=17, 17, 187
Color 6=250, 51, 51
Color 7=187, 17, 17
Color 8=51, 250, 51
Color 9=17, 187, 17
Color 10=250, 250, 51
Color 11=187, 187, 17
Color 12=250, 51, 250
Color 13=187, 17, 187
Color 14=51, 250, 250
Color 15=17, 187, 187

As I said, I just added a comment line and removed the tabs. PGCEdit seems to cope with that just fine though.

[Robotik]

wow, i'm so outdated! i expected the new version to be announced in the 8.6 thread, kept on checking it ))))
even though i haven't been doing much dvd editing nowadays, i'm so glad v9 is out!
what else did i miss? i'm gonna check for VobBlanker, too, right away!

maybe i should post to all previous PgcEdit posts that the new version is out for losers like me to notice it
who knows it might boost the donations, too

anyway, as always, thanks for all your effort and keep up the good job.

[r0lZ]

Why don't you use the Check For New Version option in the Help menu from time to time?
Remember also that you can be noticed of the changes on my homepage. See the changedetection gadget at the bottom of the page. It works well, it is more reliable then the thread notifications, and is totally SPAM free. I try to modify my homepage only when it's really needed to avoid "false positives".

[mikenadia]

Is it safe to blank all those cells whose duration is equal or less that 1/4 s (size going from 384K to 10K), and if the answer is "yes" , any function in PGCedit that will help me speed us the process.
Thanks in advance.

[blutach]

Not all of them. Say they have cell still time and some buttons. Then you'd be causing errors.

Otherwise, yes. No function available (yet).

Regards

[Robotik]

grammatical mistake in 9.2, when can't open a dvd (double negation):
*** Dialog title: "PgcEdit: Read DVD"
*** Dialog type: warning
*** Dialog message:
Can't open VIDEO_TS.IFO
or file empty!
No BUP file available neither. This is not a DVD folder.
*** Dialog buttons: [OK]

the correct sentence would be:
No BUP file available, either.

btw, it seems to be a bug as both video_ts.ifo and bup are present. i go and check it

[M_Knox]

Windows or Linux version? If the latter, please check the filenames - they have to be all-uppercase.

[r0lZ]

Under Windows, check also the path name. Tcl/Tk has trouble with foreign or accented characters, and some special characters like [ and ].

[Robotik]

Hi,

it is the Windows version and yep, it is the path name, it contains the Hungarian character, ő.
i know that the easy way to make it work is renaming the folder, but i tried to make it work with PGCEDIT_ENCODING, and also with the command lines 'pgcedit -e=unicode' and 'pgcedit /E=utf-8', and i couldn't. how does it go?

also, is it possible to check for foreign characters in the path during startup, so it doesn't give a false alert of having an empty file? it gave me the creeps
and is it possible to check if the path can be opened before the nag screen comes up? it took me some time to test what the problem is, having to wait quarter a minute each time

[r0lZ]

I have to say that I have never really understood the origin of the foreign characters problem. I have added the encoding option so that you should be able to specify the right character encoding for your system, but I have no way to know what encoding must be used (otherwise I would have added the code to select it automatically.) So, sorry, but you have to experiment with the different encoding schemes supported by Tcl/Tk, until the problem disappears. I gave up when I have tried with a French system. If you can find the right encoding for your language, please let me know.

Note that the problem with the [ and ] characters is not related to the encoding, and appears only in some functions of PgcEdit (such as when you launch a tool that contains such characters from the Tools menu.)

Unfortunately, I can't check for the problem at startup, as the filename appears correctly to PgcEdit. I have no way to compare it with the real filename. It's only when PgcEdit has to call an external program that the problem occurs, and PgcEdit can only understand that the program has failed, but doesn't know the exact reason.

It is easy to remove the nag screen. Just donate!

[Robotik]

hmm

i tried to open the dvd from command line and if i use the short dos name, it works!
i wasn't sure of the naming convention of dos, so i looked it up on Microsoft's site.

in the command window, instead of writing
pgcedit "F:\FullDisc\1 reteg\A csendőr nősül\VIDEO_TS"
i wrote
pgcedit "F:\FullDisc\1 reteg\ACSEND~1"
and PgcEdit opened it with no complaints, saved it with no complaints, even more the window title says PgcEdit - "F:\FullDisc\1 reteg\A csendőr nősül\VIDEO_TS" - untitled

maybe there is a similar workaround possible in Tcl/Tk.

[r0lZ]

Nice trick. I'm not sure it is possible to know the DOS pathname from PgcEdit, but I will have a look...

[M_Knox]

@r0lZ:
This is damn strange.

I have this folder: E:\ĄĘ\VIDEO_TS
When I double-click the VIDEO_TS.IFO in the Explorer, I get the message:

*** Dialog type: error
*** Dialog message:
Error 1 opening file "E:/ﾥÊ/VIDEO_TS/VIDEO_TS.IFO" for read:
couldn't open "E:/ﾥÊ/VIDEO_TS/VIDEO_TS.IFO": no such file or directory
*** Dialog buttons: [OK]

Now, I go to the console mode, chdir to E:\ĄĘ\VIDEO_TS and issue:

"c:\program files\dvdutils\pgcedit\pgcedit" video_ts.ifo

Everything goes fine (because PgcEdit does not receive diacritical charactes on the command line).

This one:

"c:\program files\dvdutils\pgcedit\pgcedit" e:\ąę\video_ts\video_ts.ifo

gives the same error as double-clicking VIDEO_TS.IFO

But this one:

"c:\program files\dvdutils\pgcedit\pgcedit" - e:\ąę\video_ts\video_ts.ifo

goes JUST FINE

Instead of "-" you may place whichever character (well, almost) you want, even a diacritical one

(all of the above done with PGCEDIT_ENCODING environment variable NOT SET)

[r0lZ]

Ah, yes, that's really strange! Maybe the presence of a second argument forces PgcEdit to try to interpret it as a change of encoding. I have to read my code...