I'm not sure if this is problem that specifically concerns Trinity. I generally burn CDs and DVDs with k3b, and almost never use any other
program.
(I'm using the k3b-trinity packages.) I considered trying to use the non-Trinity version of k3b, or to boot into a KDE desktop instead of TDE, to see if that works. However, I also tried with Brasero, and had similar problems, so I'm guessing that the problem is not just with Trinity.
No problem at all burning DVDs, including dual-layer. (I don't know about Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b
goes
through the whole process, creating image, normalisation, etc., then crashes before it actually burns the CD.
I ought to say that these are audio CDs. I've tried burning flac and wav
files
to CD, both with the same bad results. Also, a few weeks back, I tried to copy a large collection of mp3 files to a DVD as a data disc, but the
program
crashed before it could complete, and ruined the disc. I don't know if that incident could be related or not.
It occurs to me to try to write a CD from the command-line, using growisofs
or
the like, but I've never done that before.
I'm running Debian Jessie 8.8.0 and Trinity r14.04.
Any help or observations would be appreciated.
Bill
To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net> For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
1. You likely did this but just in case, just k3b's perms setup/ 2. Check all related perms (dvdrecord, cdr* etc). 3. See if you can complete a burn as root (if you can, it's a perm problem) 4. Also try burning at half the adverted speed. Because of today's corner cutting standards, disks are not always adverted speeds.
Let us know what happens and good luck,
Kate
In my experience, K3B works well for burning data CDs & data DVDs, but not as well for musik CDs. I have had good luck with the version of Nero burning ROM for GNU/Linux & for Windows for burning musik CDs. I'm not a fan of non-libre software, but when I burned musik CDs using K3B, and some other libre software burning programs, I had annoying audio problems that weren't always noticeable at first.
On Thu, Jun 7, 2018 at 7:59 PM, Kate Draven borglabs4@gmail.com wrote:
I'm not sure if this is problem that specifically concerns Trinity. I generally burn CDs and DVDs with k3b, and almost never use any other
program.
(I'm using the k3b-trinity packages.) I considered trying to use the non-Trinity version of k3b, or to boot into a KDE desktop instead of
TDE, to
see if that works. However, I also tried with Brasero, and had similar problems, so I'm guessing that the problem is not just with Trinity.
No problem at all burning DVDs, including dual-layer. (I don't know
about
Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b
goes
through the whole process, creating image, normalisation, etc., then
crashes
before it actually burns the CD.
I ought to say that these are audio CDs. I've tried burning flac and wav
files
to CD, both with the same bad results. Also, a few weeks back, I tried
to
copy a large collection of mp3 files to a DVD as a data disc, but the
program
crashed before it could complete, and ruined the disc. I don't know if
that
incident could be related or not.
It occurs to me to try to write a CD from the command-line, using
growisofs or
the like, but I've never done that before.
I'm running Debian Jessie 8.8.0 and Trinity r14.04.
Any help or observations would be appreciated.
Bill
To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net> For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
- You likely did this but just in case, just k3b's perms setup/
- Check all related perms (dvdrecord, cdr* etc).
- See if you can complete a burn as root (if you can, it's a perm problem)
- Also try burning at half the adverted speed.
Because of today's corner cutting standards, disks are not always adverted speeds.
Let us know what happens and good luck,
Kate
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
On Friday 08 June 2018 08:30:37 elcaseti wrote:
In my experience, K3B works well for burning data CDs & data DVDs, but not as well for musik CDs. I have had good luck with the version of Nero burning ROM for GNU/Linux & for Windows for burning musik CDs. I'm not a fan of non-libre software, but when I burned musik CDs using K3B, and some other libre software burning programs, I had annoying audio problems that weren't always noticeable at first.
My CDs always turn out great with k3b; but the quality always depends on the quality of your original source. If you try burning from mp3 files (which are "lossy"), then you will have some problems. I always burn from either flac or wav files. Also, if the flac or wav files were converted from mp3 or another "lossy" format, then one can expect that the quality is not good. Not sure if the problems you mention have to do with quality, or something else. Skipping, hissing, etc., may be due to using a lower-quality source; it might sound pretty good on your computer, or on an mp3 player, but not when you try to play from a CD.
I refuse to use non-free / non-libre / proprietary software, unless a gun is pointed at my head.
On Thu, Jun 7, 2018 at 7:59 PM, Kate Draven borglabs4@gmail.com wrote:
I'm not sure if this problem specifically concerns Trinity. I generally burn CDs and DVDs with k3b, and almost never use any other program.
(I'm using the k3b-trinity packages.) I considered trying to use the non-Trinity version of k3b, or to boot into a KDE desktop instead of TDE, to see if that works. However, I also tried with Brasero, and had similar problems, so I'm guessing that the problem is not just with Trinity.
No problem at all burning DVDs, including dual-layer. (I don't know about Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b goes through the whole process, creating image, normalisation, etc., then crashes before it actually burns the CD.
I ought to say that these are audio CDs. I've tried burning flac and wav files to CD, both with the same bad results. Also, a few weeks back, I tried to copy a large collection of mp3 files to a DVD as a data disc, but the program crashed before it could complete, and ruined the disc. I don't know if that incident could be related or not.
It occurs to me to try to write a CD from the command-line, using growisofs or the like, but I've never done that before.
I'm running Debian Jessie 8.8.0 and Trinity r14.04.
Any help or observations would be appreciated.
Bill
- You likely did this but just in case, just k3b's perms setup/
- Check all related perms (dvdrecord, cdr* etc).
- See if you can complete a burn as root (if you can, it's a perm
problem) 4. Also try burning at half the adverted speed. Because of today's corner cutting standards, disks are not always adverted speeds.
Let us know what happens and good luck,
Kate
I tried everything on your list except burning as root. I try to avoid that, but I suppose if I disconnect from the Internet, I can minimize any risk.
Right now I am going through my permissions, to see if maybe I am not in the burning group, etc. I looked at the help file, but there seem to be a lot of instructions that refer to legacy items from the old KDE3 desktop, so I need to find where it is in TDE.
Anyway, I've been using k3b since about 2006, never with any problems. Once I had got it set up just right, in fact, I haven't changed anything in my configuration since then ... until now. I have always just cloned all my settings from one home folder to another, from one computer to another, and kept running either KDE3 or TDE. Now I have some weird issues: like how k3b refuses to use my preferred theme, and keeps reverting to the default after every reboot (except that every once in a totally random while it *does* use it, just to tease me, and then again reverts to default).
I never had to mess round with k3b, so now it's like I am a total n00bie all over again. There used to be some configuration files kept in /home/~/.kde/share/config/ (k3brc, etc), but I don't know if they affect the k3b-trinity package or not. I've looked for the corresponding file in /opt/trinity/share/config.kcfg/ (I think ...?) but nothing seems to fit.
By the way, this kind of thing only happens to me whenever I starting bragging on the virtues of GNU/Linux, or the TDE desktop, or something like that. Then, when I want to show off what I can do, I immediately have issues, and must excuse myself for a month or two, while I go into seclusion to resolve my technical problems. I believe that there is some kind of moral lesson here, but that I stubbornly keep trying to spread the gospel of enlightenment / liberation / free software to the ungrateful masses. GNU/Linux is not really an operating system or type of software, but rather a lifestyle, a secret cult, a mystical experience, reserved only to the relatively pure of heart.
Bill
I stay away from lossy audio file formats as much as I can. The poor quality musik CDs I burned with K3B & other libre burning programs were burned from flac files. It sounds like you have been able to burn high quality musik CDs using K3B in the past. That's encouraging, as it's something I wasn't able to do. I hope you're able to do it again, now.
On Fri, Jun 8, 2018 at 11:20 AM, William Morder doctor_contendo@zoho.com wrote:
On Friday 08 June 2018 08:30:37 elcaseti wrote:
In my experience, K3B works well for burning data CDs & data DVDs, but
not
as well for musik CDs. I have had good luck with the version of Nero burning ROM for GNU/Linux & for Windows for burning musik CDs. I'm not a fan of non-libre software, but when I burned musik CDs using K3B, and
some
other libre software burning programs, I had annoying audio problems that weren't always noticeable at first.
My CDs always turn out great with k3b; but the quality always depends on the quality of your original source. If you try burning from mp3 files (which are "lossy"), then you will have some problems. I always burn from either flac or wav files. Also, if the flac or wav files were converted from mp3 or another "lossy" format, then one can expect that the quality is not good. Not sure if the problems you mention have to do with quality, or something else. Skipping, hissing, etc., may be due to using a lower-quality source; it might sound pretty good on your computer, or on an mp3 player, but not when you try to play from a CD.
I refuse to use non-free / non-libre / proprietary software, unless a gun is pointed at my head.
On Thu, Jun 7, 2018 at 7:59 PM, Kate Draven borglabs4@gmail.com wrote:
I'm not sure if this problem specifically concerns Trinity. I generally burn CDs and DVDs with k3b, and almost never use any other program.
(I'm using the k3b-trinity packages.) I considered trying to use the non-Trinity version of k3b, or to boot into a KDE desktop instead of TDE, to see if that works. However, I also tried with Brasero, and
had
similar problems, so I'm guessing that the problem is not just with Trinity.
No problem at all burning DVDs, including dual-layer. (I don't know about Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b goes through the whole process, creating image, normalisation, etc., then crashes before it actually burns the CD.
I ought to say that these are audio CDs. I've tried burning flac and wav files to CD, both with the same bad results. Also, a few weeks
back,
I tried to copy a large collection of mp3 files to a DVD as a data disc, but the program crashed before it could complete, and ruined
the
disc. I don't know if that incident could be related or not.
It occurs to me to try to write a CD from the command-line, using growisofs or the like, but I've never done that before.
I'm running Debian Jessie 8.8.0 and Trinity r14.04.
Any help or observations would be appreciated.
Bill
- You likely did this but just in case, just k3b's perms setup/
- Check all related perms (dvdrecord, cdr* etc).
- See if you can complete a burn as root (if you can, it's a perm
problem) 4. Also try burning at half the adverted speed. Because of today's corner cutting standards, disks are not always adverted speeds.
Let us know what happens and good luck,
Kate
I tried everything on your list except burning as root. I try to avoid that, but I suppose if I disconnect from the Internet, I can minimize any risk.
Right now I am going through my permissions, to see if maybe I am not in the burning group, etc. I looked at the help file, but there seem to be a lot of instructions that refer to legacy items from the old KDE3 desktop, so I need to find where it is in TDE.
Anyway, I've been using k3b since about 2006, never with any problems. Once I had got it set up just right, in fact, I haven't changed anything in my configuration since then ... until now. I have always just cloned all my settings from one home folder to another, from one computer to another, and kept running either KDE3 or TDE. Now I have some weird issues: like how k3b refuses to use my preferred theme, and keeps reverting to the default after every reboot (except that every once in a totally random while it *does* use it, just to tease me, and then again reverts to default).
I never had to mess round with k3b, so now it's like I am a total n00bie all over again. There used to be some configuration files kept in /home/~/.kde/share/config/ (k3brc, etc), but I don't know if they affect the k3b-trinity package or not. I've looked for the corresponding file in /opt/trinity/share/config.kcfg/ (I think ...?) but nothing seems to fit.
By the way, this kind of thing only happens to me whenever I starting bragging on the virtues of GNU/Linux, or the TDE desktop, or something like that. Then, when I want to show off what I can do, I immediately have issues, and must excuse myself for a month or two, while I go into seclusion to resolve my technical problems. I believe that there is some kind of moral lesson here, but that I stubbornly keep trying to spread the gospel of enlightenment / liberation / free software to the ungrateful masses. GNU/Linux is not really an operating system or type of software, but rather a lifestyle, a secret cult, a mystical experience, reserved only to the relatively pure of heart.
Bill
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
Starting a new thread, since this does not specifically concern my current issues with k3b.
Bill
On Friday 08 June 2018 14:16:18 elcaseti wrote:
I stay away from lossy audio file formats as much as I can. The poor quality musik CDs I burned with K3B & other libre burning programs were burned from flac files. It sounds like you have been able to burn high quality musik CDs using K3B in the past. That's encouraging, as it's something I wasn't able to do. I hope you're able to do it again, now.
On Friday 08 June 2018 08:30:37 elcaseti wrote:
In my experience, K3B works well for burning data CDs & data DVDs, but
not as well for musik CDs. I have had good luck with the version of Nero
burning ROM for GNU/Linux & for Windows for burning musik CDs. I'm not a fan of non-libre software, but when I burned musik CDs using K3B, and
some other libre software burning programs, I had annoying audio problems
that weren't always noticeable at first.
My CDs always turn out great with k3b; but the quality always depends on the quality of your original source. If you try burning from mp3 files (which are "lossy"), then you will have some problems. I always burn from either flac or wav files. Also, if the flac or wav files were converted from mp3 or another "lossy" format, then one can expect that the quality is not good. Not sure if the problems you mention have to do with quality, or something else. Skipping, hissing, etc., may be due to using a lower-quality source; it might sound pretty good on your computer, or on an mp3 player, but not when you try to play from a CD.
I refuse to use non-free / non-libre / proprietary software, unless a gun is pointed at my head.
I am curious about what sort of problems you had with k3b. Until now, it has worked great, and the quality has been excellent. However, whether this is related to my current issues or not, I would like to know the details of your problems, if you care to elaborate.
Bill
I'm not sure if this problem specifically concerns Trinity. I generally burn CDs and DVDs with k3b, and almost never use any other program.
(I'm using the k3b-trinity packages.) I considered trying to use the non-Trinity version of k3b, or to boot into a KDE desktop instead of TDE, to see if that works. However, I also tried with Brasero, and had similar problems, so I'm guessing that the problem is not just with Trinity.
No problem at all burning DVDs, including dual-layer. (I don't know
about Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b goes through the whole process, creating image, normalisation, etc., then crashes before it actually burns the CD.
I ought to say that these are audio CDs. I've tried burning flac and wav files to CD, both with the same bad results. Also, a few weeks back, I tried to copy a large collection of mp3 files to a DVD as a data disc, but the program crashed before it could complete, and ruined the disc. I don't know if that incident could be related or not.
It occurs to me to try to write a CD from the command-line, using growisofs or the like, but I've never done that before.
I'm running Debian Jessie 8.8.0 and Trinity r14.04.
Any help or observations would be appreciated.
Bill
On Thu, Jun 7, 2018 at 7:59 PM, Kate Draven borglabs4@gmail.com wrote:
- You likely did this but just in case, just k3b's perms setup/
- Check all related perms (dvdrecord, cdr* etc).
- See if you can complete a burn as root (if you can, it's a perm
problem) 4. Also try burning at half the adverted speed. Because of today's corner cutting standards, disks are not always adverted speeds.
Let us know what happens and good luck,
Kate
I tried everything on your list except burning as root. I try to avoid that, but I suppose if I disconnect from the Internet, I can minimize any risk.
Right now I am going through my permissions, to see if maybe I am not in the burning group, etc. I looked at the help file, but there seem to be a lot of instructions that refer to legacy items from the old KDE3 desktop, so I need to find where it is in TDE.
Anyway, I've been using k3b since about 2006, never with any problems. Once I had got it set up just right, in fact, I haven't changed anything in my configuration since then ... until now. I have always just cloned all my settings from one home folder to another, from one computer to another, and kept running either KDE3 or TDE. Now I have some weird issues: like how k3b refuses to use my preferred theme, and keeps reverting to the default after every reboot (except that every once in a totally random while it *does* use it, just to tease me, and then again reverts to default).
I never had to mess round with k3b, so now it's like I am a total n00bie all over again. There used to be some configuration files kept in /home/~/.kde/share/config/ (k3brc, etc), but I don't know if they affect the k3b-trinity package or not. I've looked for the corresponding file in /opt/trinity/share/config.kcfg/ (I think ...?) but nothing seems to fit.
By the way, this kind of thing only happens to me whenever I starting bragging on the virtues of GNU/Linux, or the TDE desktop, or something like that. Then, when I want to show off what I can do, I immediately have issues, and must excuse myself for a month or two, while I go into seclusion to resolve my technical problems. I believe that there is some kind of moral lesson here, but that I stubbornly keep trying to spread the gospel of enlightenment / liberation / free software to the ungrateful masses. GNU/Linux is not really an operating system or type of software, but rather a lifestyle, a secret cult, a mystical experience, reserved only to the relatively pure of heart.
Bill
Okay, now this is new: In k3b settings, under external programs, both sox and eMovix are listed as not found. I don't know about eMovix, as I can't find any packages that mention it, but sox is definitely installed; yet k3b persists in telling me that sox is not found.
And here's another disconcerting detail. When I click on search path (still in k3b settings), I find that /opt/trinity/bin/ is not listed as a search path, but something called /opt/schily/bin/ *is listed*; I've looked round, but there is nothing I can find that corresponds to schily. Moreover, I delete the line to search the path for /opt/schily/bin/, and add the path /opt/trinity/bin/, yet when I restart I find that trinity is no longer there, but schily has returned.
Apparently schily (or something related to it) is somehow connected to this problem. Also it seems that I need whatever schily provides (cdrkit, cdrtools, etc.), so for the time being, I've put this line back in for the search path. However, this schily seems to the a controversial topic:
https://en.wikipedia.org/wiki/Talk:List_of_software_forks https://en.wikipedia.org/wiki/Talk:Cdrkit
What the *$?%!&~ is schily? It seems to refer to a person named Joerg Schilling (see links above). In any case, I have no folders named schily, so the path points to nowhere that I can find in my system.
Bill
Am Freitag, 8. Juni 2018 schrieb William Morder:
Okay, now this is new: In k3b settings, under external programs, both sox and eMovix are listed as not found. I don't know about eMovix, as I can't find any packages that mention it, but sox is definitely installed; yet k3b persists in telling me that sox is not found.
And here's another disconcerting detail. When I click on search path (still in k3b settings), I find that /opt/trinity/bin/ is not listed as a search path, but something called /opt/schily/bin/ *is listed*; I've looked round, but there is nothing I can find that corresponds to schily. Moreover, I delete the line to search the path for /opt/schily/bin/, and add the path /opt/trinity/bin/, yet when I restart I find that trinity is no longer there, but schily has returned.
Apparently schily (or something related to it) is somehow connected to this problem. Also it seems that I need whatever schily provides (cdrkit, cdrtools, etc.), so for the time being, I've put this line back in for the search path. However, this schily seems to the a controversial topic:
https://en.wikipedia.org/wiki/Talk:List_of_software_forks https://en.wikipedia.org/wiki/Talk:Cdrkit
What the *$?%!&~ is schily? It seems to refer to a person named Joerg Schilling (see links above). In any case, I have no folders named schily, so the path points to nowhere that I can find in my system.
Bill
You found the right guy :-) Ages ago Schily was the autor of THE linux cd burning software. But then he changed then licence of his programs, the world was about to end, but people forked the software which led to "wodim" and the world continued turning. Anyway, "/opt/schily/bin" is hardcoded in k3d, you find it in "/opt/trinity/lib/libk3b.so.3".
"sox" is not found on my system, too, despite the fact that sox is /usr/bin/sox and /usr/bin is included in the search path. It's no use fiddling the configfile, "sox" is simply ignored. But I don't know why k3b would need sox?
"eMoviex" is ancient, too. Ages ago you could build a CD/DVD and include eMovix "bootloader" which contained a minimal linux system. Boot from the CD/DVD and you were able to play the video content of the media ... omg, wasn't it around just yesterday? Well, follow the trail in the dust: http://movix.sourceforge.net/Docs/eMoviX/ http://movix.sourceforge.net/
Nik
On Saturday 09 June 2018 03:12:51 Dr. Nikolaus Klepp wrote:
Am Freitag, 8. Juni 2018 schrieb William Morder:
Okay, now this is new: In k3b settings, under external programs, both sox and eMovix are listed as not found. I don't know about eMovix, as I can't find any packages that mention it, but sox is definitely installed; yet k3b persists in telling me that sox is not found.
And here's another disconcerting detail. When I click on search path (still in k3b settings), I find that /opt/trinity/bin/ is not listed as a search path, but something called /opt/schily/bin/ *is listed*; I've looked round, but there is nothing I can find that corresponds to schily. Moreover, I delete the line to search the path for /opt/schily/bin/, and add the path /opt/trinity/bin/, yet when I restart I find that trinity is no longer there, but schily has returned.
Apparently schily (or something related to it) is somehow connected to this problem. Also it seems that I need whatever schily provides (cdrkit, cdrtools, etc.), so for the time being, I've put this line back in for the search path. However, this schily seems to the a controversial topic:
https://en.wikipedia.org/wiki/Talk:List_of_software_forks https://en.wikipedia.org/wiki/Talk:Cdrkit
What the *$?%!&~ is schily? It seems to refer to a person named Joerg Schilling (see links above). In any case, I have no folders named schily, so the path points to nowhere that I can find in my system.
Bill
You found the right guy :-) Ages ago Schily was the autor of THE linux cd burning software. But then he changed then licence of his programs, the world was about to end, but people forked the software which led to "wodim" and the world continued turning. Anyway, "/opt/schily/bin" is hardcoded in k3d, you find it in "/opt/trinity/lib/libk3b.so.3".
That makes no sense at all (why it should be referred to as though schily is a folder), but there is the joy of Linux.
"sox" is not found on my system, too, despite the fact that sox is /usr/bin/sox and /usr/bin is included in the search path. It's no use fiddling the configfile, "sox" is simply ignored. But I don't know why k3b would need sox?
Same here. If sox is installed, then why can't k3b find it since the correct path is listed? And if sox isn't needed, then why bother to list it? Ah, the absurdity!
"eMoviex" is ancient, too. Ages ago you could build a CD/DVD and include eMovix "bootloader" which contained a minimal linux system. Boot from the CD/DVD and you were able to play the video content of the media ... omg, wasn't it around just yesterday? Well, follow the trail in the dust: http://movix.sourceforge.net/Docs/eMoviX/ http://movix.sourceforge.net/
Nik
I will check out those links. Maybe eMovix is yet worth resurrecting. Definitely sounds useful.
Bill
-
Dr. Nikolaus Klepp -
elcaseti -
Kate Draven -
William Morder