Menu
▾
▴
kreatecd-devel
You can subscribe to this list here.
| 2000 |
Jan
(1) |
Feb
(4) |
Mar
(5) |
Apr
(2) |
May
(2) |
Jun
(4) |
Jul
|
Aug
(17) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(60) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(15) |
Feb
(73) |
Mar
(49) |
Apr
(38) |
May
(8) |
Jun
(4) |
Jul
(45) |
Aug
(53) |
Sep
(9) |
Oct
(35) |
Nov
(20) |
Dec
(1) |
| 2002 |
Jan
(21) |
Feb
(5) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: <jo...@bi...> - 2001-08-03 08:15:28
|
> Hi! > > I just debugged the advanced mode and I think I found the reason for its > crashes when burning the CD-R. It is probably a KDE libs problem and exact > the crashing method was touched 5 weeks ago. Does anybody have a recent KDE > snapshot on his machine. If it is recent enough, the advanced mode should not > crash. I never noticed this problem :( I'll look if I can reproduce it when I'm at home today (very late). I run KDE 2.2 (nearly final) I do a check anyways, if the dirtree part is available and use instead the built in, if the external one does not exist. Perhaps I should add an additional version check, which overrides the usage of the part. Which function does crash (in the part) ? Kind regards Joseph Wenninger |
|
From: Alexander F. <Ale...@gm...> - 2001-08-03 01:22:13
|
Hi! I just debugged the advanced mode and I think I found the reason for its crashes when burning the CD-R. It is probably a KDE libs problem and exact the crashing method was touched 5 weeks ago. Does anybody have a recent KDE snapshot on his machine. If it is recent enough, the advanced mode should not crash. Wo should check older version of KDE and should disable the konqlistview if it is not safe. The ISO size should now be calculated in all cases. ISOFile changed to a QObject - you will probably have to do a touch Makefile.am to compile kreatecd after an update - otherwise moc is not called for ISOFile Alexander |
|
From: Alexander F. <Ale...@gm...> - 2001-07-29 15:20:10
|
On Monday, 23. July 2001 14:04, Keith Refson wrote: > Dear Alexander, > > I have been trying out the recent mods to kreatecd on my home machine > and have a couple of comments. > > Firstly the CVS head would not compile because of the half-finished > Ogg Vorbis and plugin stuff. I checked out the version dated July 16, > which seems to compile consistently. Might I suggest that you add a > CVS tag for "finished" development snapshots known to compile and > work. This would help a lot with testing. Such tags can even be > added retrospectively. > Actually the kreatecd cvs snapshot should compile most of the time and you might have hit one of the ones which make real problems. The ogg vorbis problem should be fixed now - if not, it is definitly a bug. > Secondly, my first task was to copy an audio CD. This does not > exactly test the on-the-fly stuff since I only have one CD drive and > use it as both a reader and writer. So you cannot use on-the-fly to copy an audio CD at all. Kreatecd has to read and write at the same time. > On the previous development > snapshot I could do the copy using the "Audio Only" mode by selecting > the menu item copy, whereupon hitting the "write CD" button would read > all the tracks. There was a chance later to open the drive and insert > a blank. > Oh I see. The creation of temporary images was delayed to the point just before writing due to popular demand and due to the on the fly changes. I think we will have to add I dialog to insert the CD-R if you are in single-drive mode. We should be able to detect this if CD-R and CD-ROM is the same SCSI device. > This no longer works and the only way I found to do the copy was the > painful method of "Update Track" one at a time. The new copy CD mode > did not appear to do anything useful in these circumstances either. > Did you try to let the first try fail and insert the CD-R, then burn it a second time. This should be a workaround until we have a "insert-the-cd-r" dialog. > I presume the copy mode is based on the assumption that there is a > separate CD reader and writer, but please don't forget configurations > with just the one. > I just didn't have the "single-drive" usage in mind. The dialog should fix that - thanks for reporting this before the next stable release :) Alexander |
|
From: Alexander F. <Ale...@gm...> - 2001-07-29 15:19:45
|
On Sunday, 29. July 2001 14:38, Joseph Wenninger wrote: > Hi > > Just a small question > On KDE-devel and KDE-core-devel, every now and then there starts a > discussion about an CD recording application, which should be integrated > directly into the main distribution. What about talking to the kde (core) > developers about putting kreatecd into KDE ? > 1) Then there will possibly be some more developers > 2) I think kreatecd is mature enough to be part of KDE 2.3 or 2.2.1 or at > least for KDE 3.0 > I talked to a developer some months ago (in IRC). The most important feature which we need is that it is not a Linux only application. As it seems to run on Solaris too we made a huge step since version 1.0.0. We should test and fix problems on other operating systems as well (FreeBSD etc.) Integrating kreatecd into the main distribution might be related to the "CD-R standard library" topic on kde mailing lists. I missed that one on kde-devel (I had to delete most of about 1000 mailing list mails after I came back). I'm not subscribed at kde-core at the moment. Alexander |
|
From: Joseph W. <jo...@bi...> - 2001-07-29 13:02:11
|
Hi Just an interesting thread starting on KDE-Core-Devel. Why not talks to Michael Bedy and others and join forces? Kind regards Joseph Wenninger ---------- Forwarded Message ---------- Subject: Re: Standard CD creation library. Date: Sun, 29 Jul 2001 15:51:57 +0300 From: Hetz Ben Hamo <het...@co...> To: kde...@ma..., Michael Bedy <mj...@me...> Hi Michael, Funny that you mention that issue, we were talking on #kde on IRC about this at friday night ;) Anyway, if you don't mind, here are some comments that I think it might help you a bit... For burning CD's for all purposess you'll need 3 parts: 1. A Kcontrol module. In this place, a person can setup his CD-R drive, speed, erase CD-RW, select whether to use cdrecord (Linux), burncd (*BSD), and other platforms (Sun, SGI, HP/UX - I'm sure that people who use those OS's can tell you what programs they use and what parameters they need, so this could be added when configure detect the OS and compiled accordingly - of course, this is out of your scope, but it's just as an idea) One thing that is important is the setup of the Linux/Unix to use CD-R. As you know, most of the distributions are not coming ready to just put a cd-r media and burn, but you'll need to either modify the LILO or compile several items as modules. A simple routine to see if those modules are loaded/can be loaded is needed, and if it cannot be loaded - show a friendly message about this issue and pointing the person to the CD-R howto... 2. Many programs today are using a temporary file to store an image before it's actually burn to the media, so you'll need an implementation of some sort of a fixed size "virtual CD-R" (which can be sized in kcontrol) to store this media. Alternatively with the high speed CD-R/CD-RW drives today (X8 speed and above) you don't really need this, but you'll need a smart algorithm to calculate the size of the contents and when burning - doing the job directly to the CD-R drive. Something like: mkisofs <all parameters> | cdrecord -speed=X <all parameters> 3. You need a small minimal application that shows the CD-R recording, elapsed time, and any errors. This program can be used if a person has a .ISO file (such a new image of new Linux distribution), so the person can right click on it, select "open" -> your CD-R mini application, so all the person needs is to put a media, click "ok" and burn... 4. MP3/OGG -> CD-R - this is kind of a tricky thing, but here is a suggestion: make a new IO-Slave (lets call it: cdr://) - where the person can drag/drop all the MP3/OGG files into it. Your IO-Slave needs to be smart enough to block the user when he/she fiils the CD. Then it needs to convert those files to WAV format (with a small program like mpg123), and then go the routine in section 3. 4. File system backup - this is the most complicated one, so I would suggest you to use programs like cd-backup and add a front end GUI to them... I think this should cover all the issues of CD-R recording. These are of course just suggestions how it can be done IMHO ;) Thanks, -- Hetz Ben Hamo he...@kd... > 1) Your standard EasyCD, Nero looking application. > > 2) An integrated into Konqurer ioslaveish thing that allows users to > construct a CD via dragging and dropping. (a la Win XP, although I had > been thinking of this before I saw XP :-) > > 3) A KDE Media Player (or whatever) that slices and dices and, > of course, burns audio CDs created from mp3/ogg/whatever painlessly. > > 4) A backup program that can archive to multiple CDs if necessary. > > 5) I'm sure there are other good ideas. > > Anyway, the hard(est) part of all this is that actual interaction with the > hardware. On Linux one is pretty much forced to implement the horrible > hack of parsing cdrecord's output. It can be done, but it's a real pain to > get right. > > So, my proposal is to implement the horrible hack once, give it a clean > interface, and let the UI portions of CD burning programs be implemented > separately. This also would allow, as a special bonus, the implementation > of other "drivers" to the same interface. For example, IDE burners on > FreeBSD cannot use cdrecord, and must use burncd instead. Or someone might > someday create an actual library for controling CD burners without going > through a seperate program. > > I currently have a very preliminary implementation that allows for the > burning of audio CDs. It barely works, and will fall over dead if anything > bad happens. However, it works well enough to convince me that it can be > done. I have the vauge outlines of the design for the rest of it in my > head and will continue to work on it if you think it is useful. It should > take a relatively short amount of time to finish the basic skeleton, but > it will take a while to flesh it out, including error handling, etc. > > The goal of this library is to make burning a CD from a KDE application as > simple as possible. Without the ugly work of talking to the required > programs, creating such an application should be much easier. > > Of course to implement and test the library will require a program that > uses it. So it's likely that at least program #1 will come out of the > implementation of the library. > > Thanks, > - Mike ------------------------------------------------------- |
|
From: Joseph W. <jo...@bi...> - 2001-07-29 12:24:17
|
Hi Just a small question On KDE-devel and KDE-core-devel, every now and then there starts a discussion about an CD recording application, which should be integrated directly into the main distribution. What about talking to the kde (core) developers about putting kreatecd into KDE ? 1) Then there will possibly be some more developers 2) I think kreatecd is mature enough to be part of KDE 2.3 or 2.2.1 or at least for KDE 3.0 Kind regrads Joseph Wenninger |
|
From: Joseph W. <jo...@bi...> - 2001-07-23 18:26:20
|
Hi > I have been trying out the recent mods to kreatecd on my home machine > and have a couple of comments. > > Firstly the CVS head would not compile because of the half-finished > Ogg Vorbis and plugin stuff. I checked out the version dated July 16, > which seems to compile consistently. If you talk about the make -f Makefile.cvs problems, they should be fixed by now, at least it works here now. I think current CVS should compile without problems, how save it is to use it, I don't know personally, I just got my new SCSI controller and CD-Recorder (the old one gave up unexpectedly) and start testing Alexander's on the fly code. Kind regards Joseph Wenninger |
|
From: Keith R. <Kei...@ea...> - 2001-07-23 12:04:59
|
Dear Alexander,
I have been trying out the recent mods to kreatecd on my home machine
and have a couple of comments.
Firstly the CVS head would not compile because of the half-finished
Ogg Vorbis and plugin stuff. I checked out the version dated July 16,
which seems to compile consistently. Might I suggest that you add a
CVS tag for "finished" development snapshots known to compile and
work. This would help a lot with testing. Such tags can even be
added retrospectively.
Secondly, my first task was to copy an audio CD. This does not
exactly test the on-the-fly stuff since I only have one CD drive and
use it as both a reader and writer. On the previous development
snapshot I could do the copy using the "Audio Only" mode by selecting
the menu item copy, whereupon hitting the "write CD" button would read
all the tracks. There was a chance later to open the drive and insert
a blank.
This no longer works and the only way I found to do the copy was the
painful method of "Update Track" one at a time. The new copy CD mode
did not appear to do anything useful in these circumstances either.
I presume the copy mode is based on the assumption that there is a
separate CD reader and writer, but please don't forget configurations
with just the one.
Keith Refson
--
Dr Keith Refson, "Paradigm is a word too often used by those who would
Dept of Earth Sciences like to have a new idea but cannot think of one."
Parks Road, -- Mervyn King, Deputy Governor, Bank of England
Oxford OX1 3PR, UK
Keith.Refson@ Tel: 01865 272026
earth.ox.ac.uk Fax: 01865 272072
|
|
From: Alexander F. <Ale...@gm...> - 2001-07-22 06:11:01
|
On Saturday, 21. July 2001 22:49, Joseph Wenninger wrote: > On Saturday 21 July 2001 20:51, you wrote: > > Oops. Just recognized this one by my self. > > > > I forgot to "cvs add" oggvorbis.m4.in :) > > > > BTW. You forgot to add the subdirectory "kreatecd/startupscreen" too :) > > I just noticed that I forgot to remove the makefile.am entry, afer my > checkin, but then the ssh login to cvs faild for me for a long time. > > Ok, after carefully checking your changes I saw that the startup screen looked rather complete and the non-existing directory was not neccessary so I removed the subdir entry too BTW. I'm leaving now. I'll have no mail access until Saturday evening Alexander |
|
From: Joseph W. <jo...@bi...> - 2001-07-21 20:35:35
|
On Saturday 21 July 2001 20:51, you wrote: > > Oops. Just recognized this one by my self. > > I forgot to "cvs add" oggvorbis.m4.in :) > > BTW. You forgot to add the subdirectory "kreatecd/startupscreen" too :) I just noticed that I forgot to remove the makefile.am entry, afer my checkin, but then the ssh login to cvs faild for me for a long time. Kind regards Joseph Wenninger |
|
From: Alexander F. <Ale...@gm...> - 2001-07-21 18:52:03
|
On Saturday, 21. July 2001 19:43, Joseph Wenninger wrote: > >make -f Makefile.cvs > > This Makefile is only for the CVS repository > This will be deleted before making the distribution > > *** Concatenating configure tests into acinclude.m4 > make[2]: *** No rule to make target `oggvorbis.m4.in', needed by > `acinclude.m4'. Stop. > make[1]: *** [cvs] Error 2 > make: *** [all] Error 2 > Oops. Just recognized this one by my self. I forgot to "cvs add" oggvorbis.m4.in :) BTW. You forgot to add the subdirectory "kreatecd/startupscreen" too :) Alexander |
|
From: Joseph W. <jo...@bi...> - 2001-07-21 17:31:33
|
>make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution *** Concatenating configure tests into acinclude.m4 make[2]: *** No rule to make target `oggvorbis.m4.in', needed by `acinclude.m4'. Stop. make[1]: *** [cvs] Error 2 make: *** [all] Error 2 |
|
From: Alexander F. <Ale...@gm...> - 2001-07-21 16:36:24
|
On Saturday, 21. July 2001 06:17, Niels Reedijk wrote: > Op vrijdag 20 juli 2001 21:17, schreef u: > > You need vorbis.m4 and ogg.m4 at the moment to rebuild configure. I > > would suggest : > > > > - install libogg and libvorbis (including developer files) > > - copy the missing .m4 files to the /usr/share/aclocal directory > > > > It might be possible to paste these .m4 files into configure.in.in to > > remove the requirement to have these files in aclocal. But this would > > have the disadvantage that we duplicate something which is already there. > > ] > What we should do is to add these to aclocal.m4.in (in admin), however, the > changes will be lost as soon as we import from KDE-CVS. What we actually > should do is to cvs import of the admin dir and continue to use cvs imports > whenever we want to update. This keeps our changes (they are merged with > the imported source) and keeps us up to date. See the CVS manual for the > reasons behind cvs import. > I will include the missing .m4 test before I leave next morning Alexander |
|
From: Niels R. <n.r...@pl...> - 2001-07-21 04:19:21
|
Op vrijdag 20 juli 2001 21:17, schreef u: > You need vorbis.m4 and ogg.m4 at the moment to rebuild configure. I > would suggest : > > - install libogg and libvorbis (including developer files) > - copy the missing .m4 files to the /usr/share/aclocal directory > > It might be possible to paste these .m4 files into configure.in.in to > remove the requirement to have these files in aclocal. But this would > have the disadvantage that we duplicate something which is already there. ] What we should do is to add these to aclocal.m4.in (in admin), however, the changes will be lost as soon as we import from KDE-CVS. What we actually should do is to cvs import of the admin dir and continue to use cvs imports whenever we want to update. This keeps our changes (they are merged with the imported source) and keeps us up to date. See the CVS manual for the reasons behind cvs import. Niels P.S. : Leaving now :-) |
|
From: Alexander F. <Ale...@gm...> - 2001-07-20 19:49:13
|
On Friday, 20. July 2001 17:12, Joseph Wenninger wrote:
> Hi
>
> > There might be some more changes in the backend. Mostly in the audio
> > part. Where do you want to make changes in the backend?
>
> If I remember correctly I did some dirty hack for the "Create Iso Image
> from Dir" thing. I think I set the filename for the temporary file to the
> final destination. I'd like to implement it a littlebit cleaner.
>
Ok, that needs to be fixed - but I think you don't need any low-level
functionality for this.
What about using :
/**
This method sets the source of a track to a ISO 9660 filesystem - which
will be m
when the CD-R is created.
@param image pointer to a ISOImage object for the ISO9660 filesystem
*/
void setSourceFileSystem(class ISOImage *image=0);
of CDTrack? It creates a ISO 9660 track and chooses a name for it
Alexander
|
|
From: Alexander F. <Ale...@gm...> - 2001-07-20 19:17:34
|
Joseph Wenninger wrote: >Hi > >I get some errors while running make -f Makefile.cvs >*** Retrieving configure tests needed by configure.in >.(aclocal: configure.in: 465: macro `AM_PATH_OGG' not found in library >aclocal: configure.in: 467: macro `AM_PATH_VORBIS' not found in library > You need vorbis.m4 and ogg.m4 at the moment to rebuild configure. I would suggest : - install libogg and libvorbis (including developer files) - copy the missing .m4 files to the /usr/share/aclocal directory It might be possible to paste these .m4 files into configure.in.in to remove the requirement to have these files in aclocal. But this would have the disadvantage that we duplicate something which is already there. Alexander |
|
From: Joseph W. <jo...@bi...> - 2001-07-20 15:23:31
|
Hi I get some errors while running make -f Makefile.cvs *** Retrieving configure tests needed by configure.in .(aclocal: configure.in: 465: macro `AM_PATH_OGG' not found in library aclocal: configure.in: 467: macro `AM_PATH_VORBIS' not found in library Alexander ??? Kind regards Joseph Wenninger |
|
From: Joseph W. <jo...@bi...> - 2001-07-20 14:59:02
|
Hi > > There might be some more changes in the backend. Mostly in the audio part. > Where do you want to make changes in the backend? > If I remember correctly I did some dirty hack for the "Create Iso Image from Dir" thing. I think I set the filename for the temporary file to the final destination. I'd like to implement it a littlebit cleaner. Kind regards Joseph Wenninger PS: Alexander, Niels, have nice holidays. |
|
From: Alexander F. <Ale...@gm...> - 2001-07-20 14:22:10
|
On Friday, 20. July 2001 15:48, Niels Reedijk wrote: > Guys, I guess you'll have to miss me for three weeks, as I'm in sunny > France (15 degrees C, WOW). See you! > > Niels > Doesn't matter. I'm away for a week too. BTW we should plan a release as soon as all features which are vital vor version 1.1 are more or less complete Alexander |
|
From: Niels R. <n.r...@pl...> - 2001-07-20 13:50:47
|
Guys, I guess you'll have to miss me for three weeks, as I'm in sunny France (15 degrees C, WOW). See you! Niels |
|
From: Alexander F. <Ale...@gm...> - 2001-07-20 11:50:31
|
On Friday, 20. July 2001 12:26, jo...@bi... wrote: > Hi > > > > In CVS it's not really usefull, it leaks > > > memory and is not functiononing. > > > Dou you know where the problem is? It looks > > rather good and I think it would > > be very useful too. > > Yes I think I know where the problem is. > Perhaps this weekend I'll check in > Great. > > It's mostly GUI related (the andvanced widget > bugfixes + functionallity implementation). I > didn't want to work with the backend things, > till you hat finished your major rewrite, cause > merging would have been quite difficult, if both > of use made a lot of changes. > There might be some more changes in the backend. Mostly in the audio part. Where do you want to make changes in the backend? > Have you ever tried the RMB menu in konqy (for > directories) (Make ISO image from directory)? > Does it still work with your on the fly changes ? > On the other hand I'll just give it a try and > fix it, if I understand your new backend code. It seems like it works after the image is created by pressing the button to create it. This is because the image size isn't calculated - but this is required for on-the-fly burning. This is a known problem I will fix soon. BTW. I get segfauls leaving kreatecd when doing some ISO 9660 mastering at the moment. Loading of ISO 9660 trees seems to be broken too. I'll have a look at this now Alexander |
|
From: <jo...@bi...> - 2001-07-20 10:30:28
|
Hi > > In CVS it's not really usefull, it leaks memory and is not functiononing. > > Dou you know where the problem is? It looks rather good and I think it would > be very useful too. Yes I think I know where the problem is. . Perhaps this weekend I'll check in > > some things > > > > What are these things? If we want to have it in 1.1, you can commit it if it > is an addition - which doesn't make the rest of kreatecd terribly unstable. > > If you have any local changes in the non-UI part, chances are high that they > don't apply to CVS any more due to massive changes in the last weeks > It's mostly GUI related (the andvanced widget bugfixes + functionallity implementation). I didn't want to work with the backend things, till you hat finished your major rewrite, cause merging would have been quite difficult, if both of use made a lot of changes. Have you ever tried the RMB menu in konqy (for directories) (Make ISO image from directory)? Does it still work with your on the fly changes ? On the other hand I'll just give it a try and fix it, if I understand your new backend code. Kind regards Joseph Wenninger |
|
From: Alexander F. <Ale...@gm...> - 2001-07-19 22:16:44
|
On Thursday, 19. July 2001 21:52, Joseph Wenninger wrote: > Hi > > > What is the current status of "advanced" widget? (which warns with DO NOT > > USE) > > In CVS it's not really usefull, it leaks memory and is not functiononing. Dou you know where the problem is? It looks rather good and I think it would be very useful too. > I > have quite some stuff on my computer, to get nearly working in a usefull > way, but I don't want committ it yet. Perhaps this weekend I'll check in > some things > What are these things? If we want to have it in 1.1, you can commit it if it is an addition - which doesn't make the rest of kreatecd terribly unstable. If you have any local changes in the non-UI part, chances are high that they don't apply to CVS any more due to massive changes in the last weeks ALexander |
|
From: Joseph W. <jo...@bi...> - 2001-07-19 19:38:55
|
Hi > What is the current status of "advanced" widget? (which warns with DO NOT > USE) > In CVS it's not really usefull, it leaks memory and is not functiononing. I have quite some stuff on my computer, to get nearly working in a usefull way, but I don't want committ it yet. Perhaps this weekend I'll check in some things Kind regards Joseph Wenninger |
|
From: Alexander F. <Ale...@gm...> - 2001-07-19 17:38:10
|
Hi! There will be a larger commit in the next hours. To be sure that it still compiles without problems, you should do a "make -f Makefile.cvs" again. I do some checks before I commit - to make sure it breaks nothing vital. The audio file formats are compiled as libraries after this commit. Until I checked if I could use KLibLoader for the libraries, the dynamic loading code is disabled and the "plugins" are linked statically into kreatecd. It seems like I could use KLibLoader as long as I don't use KLibFactory but I have to check this first. There is an experimental Ogg Vorbis decoding support after the commit. Since the Vorbis codec is rather time consuming at decoding you will probably not able to burn it on-the-fly at full speed. I will be off for one week soon. (from 2001/07/22 until 2001/07/30) and have no possibility to answer any E-Mails. What is the current status of "advanced" widget? (which warns with DO NOT USE) |
1 message has been excluded from this view by a project administrator.
