pBurn 4.3.19

[zigbert]

aragon
I tried to install Pburn with theme in a fresh Puppy 3.01. Worked out of the box.....

[HairyWill]

Is the problem associated with updating a version of pburn >= 1.0.0.
It looks like if the version is older than this then .pburnrc is replace but if it is newer then only the release number gets updated in the config file. The "export THEME=Pburn-original" doesn't get added to the existing config.

To fix this you can just delete the .pburnrc file or if you want to keep the settings add the line
export THEME=Pburn-original

I think

[zigbert]

Thanks Will

Will be fixed!

[Jeff]

Anyone have an idea why I get the message on pburn 1.2.2

readlink: /tmp/: Invalid argument

starting from prompt with command pburn on Puppy 2.15CE

Regards

Jeff

[zigbert]

You don't mention if Pburn starts, but I guess it does, since the message occur while calculating available size on your system. Pburn checks this to report back when you burn with a temporary storage. But message shouldn't be pointed to terminal, even if it doesn't make any harm. So I have now fixed it. Thanks.

[ravensrest]

I have a couple of problems with the downloads.

First, 1.2.2 installed fine over the exisiting 0.6 version in my dingo 394. However, if I uninstall it, it leaves the pburnrc file showing that version 1.2.2 is still installed rather than the pre-exisiting 0.6

Next, I installed the newly down-sized pburn-original theme. The files installed just fine, but the interface shows no difference even after re-boot. What is needed to make the theme active?

Suggestions?

Oops, sorry! Just saw the earlier post about adding "export THEME=Pburn-original". That solved the problem.

[BarryK]

I haven't read through the entire thread, so excuse me if any comments here are a bit off.

Today I used Pburn 1.2.2 to burn some files to a DVD.

When I clicked on a directory in the left pane, I sat there for sometime waiting for the "Minimum disc size:" box to update. It didn't. Or rather it did later when I clicked on another directory. The update did not happen until there was another mouse action. This seems to be a limitation of gtkdialog, but it would be nice if there was some workaround.

After burning to DVD, I clicked the "Verify" button, and my DVD drive churned away for ages. I waited and waited. All that I got in the gtklogview box was something like "Verifying DVD..." but there was no progress indication.

Eventually I gave up and hit the "Emergency stop" button on the gtklogview box. This killed Pburn, however my DVD drive still kept churning away.

I ran 'ps' to see what was running. That's when I saw 'diff' running. Now, my understanding of 'diff' is that you should only use it to compare text files. For binary files, meaning any files, you should use 'cmp' -- Dingo has cmp, I don't know about earlier puppies.
Note, 'cmp' is part of the 'diffutils' package.

I killed diff, and my DVD drive stopped churning, but something still claimed the drive and I was unable to shut down the computer -- I had to hold down the off button for 4 seconds to do a forced power-off.

[sketchman]

Do I have to have 3.01 to use this?

I've installed it in 2.17.1, but it doesn't run. I've got both dependencies that were listed in the first post installed.

I started it from a console, and got errors. Fixed them and reinstalled Pburn.

It almost starts the first time and then never again. Run from console, I see the following only the first time I run it, along with the screenshot I attached.

Code: Select all

#pburn
EXIT="Ready"
#

All attempts after the first one give me this.

Code: Select all

#pburn
#

That's all. No splash screen. No errors.

[mikeb]

Hi barry

cmp man page says

`cmp' reports the differences between two files character by character, instead of line by line. As a result, it is more useful than `diff' for comparing binary files. For text files, `cmp' is useful mainly when you want to know only whether two files are identical.
.........
Unlike `diff', `cmp' cannot compare directories; it can only compare two files.

Gcombust uses diff for verification so the technique was adopted for pburn.
It seems that although not invalid to use diff to compare binary files it may well not be the most efficient method.(--speed-large-files option is used)

Another factor is that dma is not being used to read the disk...compare times are similar to nero with dma off....for CD's this is acceptable though for dvd's is a bit on the slow side it seems. Cmp could be implemented but I'm not sure if there would be a significant speed increase....I will investigate. Cmp is present in 2.xx puppies.

Being able to compare directories recusively is very useful for pburn as the disc contents are mirrored in a temp directory.

I'm not sure about the effectiveness of the kill function....burner drives once instructed to do something are on a mission of there own and this seems to tie up the operating system until it is complete...a general observation.Though in this case I don't think diff has been included in the kill list.

Not sure about the size problem...I usually find the size updates as files are added to the burnlist which is the intended behaviour.

mike

[zigbert]

sketchman
Have you upgraded to the latest version 1.3.0?
There has been a bug in the version-upgrade-function fixed in 1.3.0. HairyWill pointed this out some posts ago.

BarryK

When I clicked on a directory in the left pane, I sat there for sometime waiting for the "Minimum disc size:" box to update.

When you click on a item in the left pane, Pburn starts function -add_selection from gtkdialog:
<action signal=\"button-release-event\">. $APPDIR/func -add_selection</action>
Function -add_selection checks if you clicked with right button.
if [ $BUTTON = 3 ]; then
...
I have not seen this function fail, but I'm still mostly in Puppy 3.01.

Eventually I gave up and hit the "Emergency stop" button on the gtklogview box. This killed Pburn, however my DVD drive still kept churning away.

This is a very clear BUG. diff is not killed!!! Thanks.

Sigmund

[sketchman]

Yes, I have 1.3.0. I didn't upgrade from any previous version, so that shouldn't be the problem.

[zigbert]

sketchman
Ok, I see.... If using Puppy 2, you also need the latest gtkdialog-0.7.20

[sketchman]

Eureka. Pburn works. Thank you very much.

[Henry]

Hi, Sigmund,

Congratulations on the great progress of Pburn and your other fine programs.

I do have one question: I have Pburn 1.3 installed (I think completely and correctly) in Nop 3.01 with the original theme. It works fine. The problem is I dislike unnecessary "themes," but if I disable this one by setting preferences to none, the next time I open Pburn it searches about a minute before it opens. Somewhat quicker on subsequent tries, but it seems "confused" without a theme :-)

What to do?

[zigbert]

Henry
With your description, I think of the command 'find' (maybe also in a subshell), on a system with
- lot of files
- vfat filessystem
- or old cpu

I think your trouble is starting in line 158 of /usr/local/pburn/pburn

Code: Select all

if [ `find "$APPDIR"/themes/$THEME/heading-main.png` ]; then

Try to change it to

Code: Select all

if [ -s $APPDIR/themes/$THEME/heading-main.png ]; then

The same occur in line 162, 167, 172
if you edit those 4 lines, I hope you'll get more speed.
Please give feedback

Thanks for bugreport
Sigmund

[Henry]

Thanks, Sigmund,

I edited the 4 lines as suggested. It did not make a significant difference. That is, the first time after a reboot, with no theme, opening Pburn still takes about a minute, thereafter about 4 sec.

With the theme enabled, it's quite fast, so I will just "tolerate" the theme :-) It's not important.

BTW very nice how the verify function works now.

Henry

[mikeb]

Hi zigbert

I've been looking at a way of easily ordering tracks for audio CD's
This is what I've come up with so far...

When audio CD is selected :-
Added tracks are indexed and added to the end of the list thus preserving order.
Tracks can be moved up and down.
Removing tracks preserves the order of the remainder.
For convenience when switching to 'audio' any files already added are indexed.
The indexing method matches the system used when importing a playlist.

The attachement is a hacked down version of pburn I use for trying out ideas but the system of indexing should integrate with the latest version if deemed suitable.
Changes are in 'func' with additional buttons in 'pburn'.

mike

[zigbert]

Hi Mike
Thanks for your input. It will be in the next 1.4.0.
I reorganized it a bit. Your function 'index_list' is now called from 'build_burn_list'. Like this we don't need any changes in
'-add_selection'
'-add_all'
'-burnlist_remove'
Also no extra trouble integrating it with the search engine.

The annoying thing is that after moved song up/down, variable $BURNLIST is empty, and I have to select song again to move futher.

Here's the /usr/local/pburn/pburn and /usr/local/pburn/func

[mikeb]

Hi Zigbert

I reorganized it a bit. Your function 'index_list' is now called from 'build_burn_list'. Like this we don't need any changes in
'-add_selection'
'-add_all'
'-burnlist_remove'
Also no extra trouble integrating it with the search engine.

This is why 2 heads are often better than one good thinking...cheers for posting the changes I look forward to having a look. Glad you liked the idea.

The annoying thing is that after moved song up/down, variable $BURNLIST is empty, and I have to select song again to move futher.

Yes i know...I am a bit hazy on how to solve that one or is it a gtkdialog limitation?

In the demo I sent you I modded the temporary directory function to call gtkdialog fileselect directly so simplifying box_chooser...which in itself I added a box to input a filename for saving..might be handy.
Also added ability to open from a .pbn file (eg with rox mime type) though this would need refining to integrate with other opening options.

Another idea which occured to me was to be able to distinguish between an audio and data .pbn file so the appropriate mode would be selected when opening.
I was thinking in terms of including a file called '.data' in the pburn folder which is removed for audio compilations....would be insignificant for a data burn and not present to cause a problem for audio if you see what I mean.

Ok off to play with the greatest and smallest burning utility in thee world

regards

mike

ps I missed the 'add_all' ahhhhhhhhhhhhhh

[zigbert]

In the demo I sent you I modded the temporary directory function to call gtkdialog fileselect directly so simplifying box_chooser...which in itself I added a box to input a filename for saving..might be handy.

This is correct, and the logic way to do it, as long as you don't have language support. Also <button cancel></button> shows a prebuild button, but it can't view label 'Avslutt', - as we cancel in Norway.

Also added ability to open from a .pbn file (eg with rox mime type) though this would need refining to integrate with other opening options.

In 1.3.0 you can open Pburn with a *.pbn file with 'pburn /path/file.pbn'

Another idea which occured to me was to be able to distinguish between an audio and data .pbn file so the appropriate mode would be selected when opening.
I was thinking in terms of including a file called '.data' in the pburn folder which is removed for audio compilations....would be insignificant for a data burn and not present to cause a problem for audio if you see what I mean.

A .data file will be visible in the burnlist , and must be removed while *.pbn opens. Still I personally feel that the 'import playlist' is most logical way to handle this. I use Picker for this purpose. BUT indeed, I'm not the negative guy. Enhanced *.pbn detection - ok with me.

Ok off to play with the greatest and smallest burning utility in thee world Smile

It is hard to disagree about the point: 'smallest'

Sigmund