pBurn 4.3.19

[zigbert]

When select all items in "Add data from here..." tree using Alt+A and add them to "...burn content of the list" tree, that includes also .. and in effect parent directories gets added as well.
Have a look at the screenshot - dirs like archive, aufs, etc, home, lib and so on.

This works for me, however I don't know the code as much as you do, so I'm not sure if it's the best way:

Code: Select all

# diff -u func_org func
--- func_org	2015-05-08 16:54:01.033224803 +0200
+++ func	2015-05-08 16:56:53.073220047 +0200
@@ -676,6 +676,7 @@
 -add)
 	#---
 	if [ "$BUTTON" != "3" ] || [ "$CHOOSER" = ".." ]; then exit; fi
+	CHOOSER="${CHOOSER#..}"
 	cut -d '|' -f 4 $WORKDIR/ls > $WORKDIR/tmp2
 	if [ ! "$CHOOSER" ] && [ "$ADD" = "$(gettext 'Add selection') [$(gettext 'right click')]" ]; then #nothing is selected
 		echo -n > $WORKDIR/tmp
# 

Btw, multiple selection would be also useful in "...burn content of the list" tree.
Or at least a button to remove all entries at once.

Your fix is added. Thanks!

When it comes to multiselection in the burn-list, - I simply don't dare to do it. It would require a lot of work and testing, and pBurn is stable atm.

To clear the burn-list, choose 'New' from the 'File' menu

[zigbert]

Version 4.3.14
See main post

Changelog
- Bugfix: Add items (when all items is selected) includes parent dirs. (thanks to SFR)
- Bugfix: Import music playlist doesn't autoset correct burn-mode to Audio. (thanks to don570)

[B.K. Johnson]

@mikeslr
I am extremely grateful for sticking with me on this one. I really appreciate it.

I already backed up my pupsave, save interval is set to 0 and Ask to Save/Not Save is active, so no harm is likely. Nevertheless I'll search for jpeps' instructions to avoid Automatic Saves, as you recommend.

Re Caution 2. don't think there is any need to worry. ffmpeg does not exist in tahrpup-6.0.2. If any of the media apps I use regularly needed it they would have barfed already. The only one I needed to check was ffconvert. The conversion failed I suspect because of missing ffmpeg - see screenshot.

I'll try setting up the symlink later tonight or in the morning and report on that. Report on success/failure with the burn will be on Monday as I wan't to buy some rewritables to try the audio CD burn.
You wrote:

I am uncertain why pBurn even requires ffmpeg simply to burn audio or video files from some location to a CD/DVD. IIRC, I've used pBurn from Tahrpup to burn ISOs to CDs and DVDs.

I too have had success with ISOs to CDs and DVDs, The difference I think is that in burning an audio CD, the mp3, WAV, ogg etc have to be converted to an audio format (CD-DA) that is designed specifically for CD players. Not the same as computer audio file type.

B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM

[mikeslr]

Hi again B.K.Johnson,

After considering zigbert's clarification of the current status of ffmpeg under Tahrpup, I tried unsuccessfully to cobble together an application for Tahrpup using Trusty Tahr debs. I'll try again. But that is really a job for someone with the necessary expertise.
Regarding jpep's instructions, you'll find them here. http://murga-linux.com/puppy/viewtopic. ... 326#662326, IIRC, Tahrpup & derivatives use shinobar's PupSaveConfig, so step 3 --editing /etc/rc.shutdown -- isn't necessary. But its best to double-check. After applying steps 1 & 2, Save and reboot. Then reboot or shutdown. If you don't receive a message "already saved" then all is well.
I couldn't find a way to configure ffconvert to use the avconv libraries either. That's one reason I installed winff. Instructions here: http://murga-linux.com/puppy/viewtopic. ... c23a271c0f

If the experimentation doesn't work, winff apparently enables a conversion of audio files to "WAV for CD". I don't know what that means. Nor do I have any idea how far that might get you toward creating an audio CD.

mikesLr

[mikeslr]

Hi B.K. Johnson & All,

Thanks to zigbert pointing me in the right direction regarding Ubuntu's handling of ffmpeg, whatever else it may mean (or not) Ubuntu has officially returned to packaging ffmpeg in Vivid Vervet.
Using Vivid Vervet binaries, 666philb has packaged vividpup, albeit still at beta. http://murga-linux.com/puppy/viewtopic. ... 286#832286

Among vividpups builtins are pBurn 3.7.18 and ffconvert 1.4.2, along with most of the libs used to provide functionality to ffmpeg. See accompanying screenshot. ffmpeg, itself, is not builtin. However, ffmpeg_2.5.4 and all the libs specified in the screenshot can be downloaded and installed via Puppy Package Manager.

Whether pburn can make use of vivid's ffmpeg, and whether vivid's ffmpeg debs can be packaged for use in Tahrpup remains to be seen.

Update: Switched into TahrPup as I didn't have PaDS installed in VividPup. PaDS is an application by Lazy Puppy which can combine pets and debs --in this case the aforementioned ffmpeg and its libraries debs-- into an SFS. Built an SFS and loaded it on the fly into Tahrpup. Restarted X to reload the system. Started pBurn and ran its dependency checker it Help Menu. pBurn reported that ffmpeg was "OK".
Having I have no audio files to burn to a CD, I decided to test the ffmpeg sfs by installing winff and attempting to convert a video clip from one format to another. It failed in both Vivid and Tahr complaining of "a" missing library. Opening a terminal at /usr/bin and entering the command "ldd ffmpeg >/root/missing-libs.txt" generated a report of about a dozen missing libs. Oddly, more were missing from Tahr than from Vivid. I'll try to hunt them down.
Obviously, as is often the case when trying to use applications built for Ubuntu in Puppy, the stated dependency list leaves out structures presumed to be present as part of the Ubuntu OS.

PPM was able to identify and download probably all debs relating to the missing libraries. The deb count is now up to 26, so I'll wait until I have a reasonable amount of time to concentrate on trying to build an SFS. After the SFS is built, I'll have to mount it and create symlinks as the available debs, in several cases, appear to contain newer libraries than those reflected as missing. I have to wonder if the effort is worth it. I've used the word probably as, while in most cases, a PPM search for "libXYZ" found such lib with a description indicating it related to ffmpeg, in a couple of instances I had to drop "lib" from the search term to find anything which might be relevant, and then guess which pertained. And, of course, even if those found were the right ones, trying to employ them may reveal other missing libraries.

PPM does have an option to download a deb and all its dependencies. The problem with using it is that Puppy isn't Ubuntu and PPM isn't Synaptic. "All dependencies" may include debs for modules Puppy doesn't need and/or files which will conflict with those Puppy requires.

As I said before, creating an ffmpeg application for Puppy is something best undertaken by experts having familiarity with both Puppy and ffmpeg. And the best way is probably to compile ffmpeg in Puppy along with its dependencies and libraries rather than to try to cobble together a bunch of Ubuntu debs.

mikesLr

[B.K. Johnson]

Hi mikeslr
Sorry for the unavoidable delay in responding, but here goes.
You wrote:

Open rox and browse to /usr/bin.
Right-click an empty space and from the drop-down menu, select Windows>Terminal Here. A terminal will open. Create a symlink, named ffmpeg, to avconv. The code to type in the terminal is:

ln -s avconv ffmpeg

Press return.

I did not get the Windows>Terminal on the right-click but used emelfm2 to achieve the task of opening a terminal window at /usr/bin.
I set up the link. and followed the instructions.
As you can see from the accompanying screenshot (mikeslr_solution_ok), ffmpeg showed ok with the dependency check.

Now the burn trial
The burn of an 11 track CD succeeded and I was eventually able to play it . Thanks Sherlock .

The resultant CD appeared in the device list - sr0. I expected pmusic to be automatically launched and play but when it didn't I clicked the sr0 icon. That brought up a graphic with an invitation to play (screenshot=cd_detected)but when I clicked the play button VLC playlist panel just showed cdda.

It seems my default player VLC, needs a codec/plug-in of some sort. I guess that's a different problem to be looked into.

Launched Menu->Multimedia->pCD and though there was a short delay, the cd tracks came up and played beatifully. Played in Deadbeat also.

[mikeslr]

Glad the simplest work-around worked for pBurn.

The more time-consuming possible solutions just got more time-consuming.

If I ever successfully cobble together a functional ffmpeg for Tahrpup, I'll post about it on its own thread.

Sorry zigbert for having temporarily hijacked pBurn's thread.

mikesLr

[zigbert]

Sorry zigbert for having temporarily hijacked pBurn's thread.

[bigpup]

zigbert,

Thanks for constantly improving this program!!!!!

[zigbert]

TahrPup users look here

[666philb]

here's the latest pburn with deps for tahrpup. if it's to be including in the up coming servicepack it will need to be tested.

i haven't got a cdburner so if people could test as many features as possible
particularly burning audio cds and video cds

thanks

https://www.dropbox.com/s/7wlokl3be27dd ... s.pet?dl=0

EDIT: you'll also need the gtkdialog from here .... just grab the one for precise http://murga-linux.com/puppy/viewtopic. ... 526#707526

[B.K. Johnson]

Hi All
As Yogi Berra reputedly said: It ain't over till it's over.

Mysteries in pBurn and PeasyDisc

I used a CD-RW to burn an audio cd using 666philb's pBurn-4.3.14. As reported here:
http://murga-linux.com/puppy/viewtopic. ... 310#846310
it failed.
Subsequent to the failed attempt I tried to reuse the RW disc with pBurn-3.7.18 with mikeslr's ffmpeg/avconv symlink. pBurn sees the RW as an audio CD and therefore not erasable. It does not see the disk as a rewriteable. However, I had already burnt an audio CD then erased and burn to it again on that very RW, so I could not understand why pBurn refused on several attempts to overwrite or blank the RW. bigpup's failed try with the same pBurn was with a CD-R so no help there.Was it due to the condition of the media, or the manner in which the burn was done; hence the warning in my post?

I launched rcrsn51's PeasyDisc to see it it would blank the disc. It went through the process seemingly without a problem but pBurn still reported the RW as a read only CD. I concluded that PeasyDisc only did a "Fast Blank", not a full erase.

I again blanked the RW in PeasyDisc, then chose to burn an ISO. As reported in the first line of the screen output, the media was recognized as removable and the software completed the burn of the ISO - 437MB . But when I clicked on the CD icon a pBurn dialog appeared, informing that the disc was most likely blank and invited me to run pBurn. This I did. To my surprise, pBurn now showed the RW as blank - 652 MB free. The PeasyDisc burn of the ISO did not happen, but the process fully erased the disc.

I then chose to burn with pBurn the same SRCD iso that Peasy failed to burn. It went through the process and deliveed a bootable CD.

Conclusions:
pBurn's first check ought to be whether the disc is a recordable or rewriteable and allow blanking even if it is an audio cd. Since I had deleted an audio CD on RW before, this may be irrelevant. It is just that the pBurn created a structure that made the RW unrecognizable as such.

rcrsn51's PeasyDisc needs to offer full erase, not only "fast erase". The full erase seems to have happened during the burniso but the data was not written.

Sorry, no screenies. Had them in /root but lost them on a power outage.
B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM

[666philb]

B.K.johnson

when blanking change 'audio cd' to 'CD' in the 'media type' box

[zigbert]

Through the years of pBurn development, there has been different approaches of how burning-commands should be set up. - A logic evolving of any program, but when it comes to hardware-related functions, - this is harder. Especially CD/DVD/BD-devices (and their vendors) do not agree how to do the burning in an optimal way. Blanking is for sure one of these operations where procedures differs.

I feel pBurn today offers a decent set of features that works for many/most users. It will NEVER satisfy 100% of the users because of the mentioned issues.

BUT, if we see several reports of a similar issue, I will of course evaluate the state of pBurn... What is important here, is that every new burning-command must be tested in a variety of devices to verify that the new command actually gives a better overall performance. I have found this troublesome because burning is not as common as in 2005 which gives us less testers, and I have only 1 device available.

[Flash]

As someone once said, the beautiful thing about standards is how many there are to choose from. The CD-R and drives that could use it sort of co-evolved, so the standards were sloppy and their interpretation varied according to which manufacturer you talked to. When the DVD-R and -RW came along, the industry used the lessons learned from CDs to write much tighter standards. As a result, burnable DVDs work better and burning them is more reliable. I sold all my CD-R and -RW disks at a yard sale. Now I just use DVD-R and DVD-RW disks. Much less troublesome.

[B.K. Johnson]

@Zigbert
I have happily used pBurn for the past 5 or so years. This isn't about hardware-related functions, as you allude to. I have no issues with CD/DVD/BD-devices. I have no issues with the features and functionalities of pBurn. No issues with burning per se. But recently it has become clear that there are some design flaws in the software caused by tacking on audio CD burning.
1. Take this blanking issue for example. Is it that difficult to change the logic to

Code: Select all

if disc structure is audio cd and media is cd then cannot be blanked ... appropriate error message ... exit
if audio cd and media is rewritable then blankable. 

There shouldn't be any need for the user to change the drop down menu from Audio CD to CD (666philb's solution) in order to effect blanking of a CD-RW. It is incongrous to tell a user to blank a CD when (s)he knows you can't do that er... not supposed to be able to do so.
2. I alluded to this in another thread, but you either missed it or ignored it . The Used/Free space meter is designed for operations that are file size centered (get and accumulate the size of selected files), e.g. BurnISO, Create Data CD/DVD/BR. It does a good job. But when creating an audio CD, the user's interest is metering play time against the allowed playtime for the media. The meter in place is useless in this context .

If I can suggest some changes:
1. Remove the "Blank disc" tab from the main screen. Concentrate Blank/Erase functonality in the Burn drop down menu where it already exists. Include in the functionality, test for recordable vs rewriteable and display appropriate error mesage if recordable. On the blanking screen (available only if media is rewritable), give the user the option (radio buttons) to do a "Fast erase" or "Full erase".
2. Replace the "Blank disc" tab on the main screen with "Burn Audio CD". When selected, the usage meter should change to a time based one (and if not difficult 'size' to 'Duration'). I'm sure the Red book tells how to get the media time. It should not be difficult to obtain an appropriate algorithm for a song's duration from vlc, DeaDbeef or some other player and accumulate in a meter for Audio CD burning.

The intent here is to help you make a better product for your fans, present and future. You are a man who marches to the beat of his own drum but I hope you will see some merit in these suggested changes.

Here is a link to the meaning of the above English idiom in case being Norweigan you are not famliar with it. No intent to belittle.
http://www.usingenglish.com/reference/i ... drum.html.

B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM

[B.K. Johnson]

@666philb

when blanking change 'audio cd' to 'CD' in the 'media type' box

Thanks for this tip. It worked . Kinda funny though, that in order to blank a rewriteable one has to tell the software that it's a CD, a media type we all know can't be erased

B.K. Johnson
tahrpup-6.0.2 PAE, slacko-5.7, frugal install, pupsave file, multi OS flashdrive, SYSLINUX boot, CPU-Dual E2140, 4GB RAM.

[zigbert]

@666philb

when blanking change 'audio cd' to 'CD' in the 'media type' box

Thanks for this tip. It worked . Kinda funny though, that in order to blank a rewriteable one has to tell the software that it's a CD, a media type we all know can't be erased

Does this mean: If I remove the CD-audio option as mediatype (set it to CD instead) everything would be good ?
I agree, there is no logic in providing CD-audio as an option.

[zigbert]

I went to town getting some CD-RW's to test this.
- I burnt an audio-CD ok
- When blanking you refer to

when blanking change 'audio cd' to 'CD' in the 'media type' box

... Where is this - I don't get this option in the blanking option window. Here is only CD, DVD and Blu-ray ???

Sigmund

[B.K. Johnson]

zigbert wrote:

When blanking you refer to

when blanking change 'audio cd' to 'CD' in the 'media type' box

... Where is this - I don't get this option in the blanking option window. Here is only CD, DVD and Blu-ray ???

Sigmund

You are using pBurn-4.3.14 . I'm not so interface may be different.
But at the main screen I click on the Burn disc tab see screnie

Basil