Page 1 of 1

Burnatonce .97 features

PostPosted: Mon Apr 07, 2003 2:04 pm
by Wedge Maniac
I thought I would post development news of Burnatonce .97 as it the info becomes available to me in the pre-release news.

For you fans of EAC, Jamie (Burnatonce developer) is now working on implementing a way to import music cd images that have been extracted by EAC in order to burn them with Burnatonce.

The benefit of this?
1) If you use Exact Audio Copy, then you are probably aware that this is considered the most reliable method for getting exact copies of music cds due to it's "secure mode" setting that reads and re-reads the data until it gets 2 matching data streams, thus ensuring errors are detected and corrected during extraction. Burnatonce will be able to read these images if you generate a cue sheet along with the image, which is easily created by EAC.

2) Although EAC is capable of burning EAC-extracted music images, there are many newer recorders that are not supported by EAC. This new feature of Burnatonce will allow you to bypass that problem if you have a newer cdrw drive that isn't recongnized by EAC. Of course, your cdrw drive must be recognized by Burnatonce, but most newer drives *should* be supported by Burnatonce.

PostPosted: Mon Apr 07, 2003 5:19 pm
by cfitz
Thanks for keeping us updated, Wedge.

cfitz

PostPosted: Thu Apr 17, 2003 12:14 am
by Wedge Maniac
To just keep the interested crowd posted, Burn@once developer, Jamie, is working on a way to display actual write speed for the next version.

It's not a certainty, but progress has been made.

PostPosted: Thu Apr 17, 2003 12:36 am
by dodecahedron
hey, Wedge Maniac, waddya know! :D cool coincidence :D :D :D

just tonight i registered at the burnatonce forums.
http://www.burnatonce.com/forums/index. ... &f=7&t=435
(BTW you are Wedge there, right?)
i also posted a suggestion for the next version: to show the real burning speed!!! :P
http://www.burnatonce.com/forums/index. ... =277&st=45

PostPosted: Thu Apr 17, 2003 1:48 am
by Wedge Maniac
dodecahedron wrote:hey, Wedge Maniac, waddya know! :D cool coincidence :D :D :D

just tonight i registered at the burnatonce forums.
http://www.burnatonce.com/forums/index. ... &f=7&t=435
(BTW you are Wedge there, right?)
i also posted a suggestion for the next version: to show the real burning speed!!! :P
http://www.burnatonce.com/forums/index. ... =277&st=45



Yeah dodecahedron, I'm one and the same :)

And yes, very cool cooincidence indeed. Actually I noticed your post over at the Burnatonce forum and that prompted me to add on to this thread.

Great suggestion and it just so happens that Jamie and the pre-release members are working this one out, but I want to emphasize that this is not set in stone. Anything in pre-release stages can get the boot if it's too buggy or if we decide it's a feature that isn't necessary, or that it's simply anti-Burnatonce.
In this case, we are dealing with a feature that is not bug-free at the moment, but barring that, it is a feature we want to see materialize in an upcoming release.

I'll keep you posted.

PostPosted: Thu Apr 17, 2003 2:01 am
by dodecahedron
Wedge Maniac wrote:And yes, very cool cooincidence indeed. Actually I noticed your post over at the Burnatonce forum and that prompted me to add on to this thread.

" 'curiouser and curiouser', said Alice..." :D :D :wink:

hopefully it'll work out fine and be incorporated in the next version.

by the way i added another post with another minor suggestion/request.

Wedge Maniac wrote:if we decide it's a feature that isn't necessary, or that it's simply anti-Burnatonce.
In this case, we are dealing with a feature that is not bug-free at the moment, but barring that, it is a feature we want to see materialize in an upcoming release.


interesting choice of words.
can i infer from your use of we, that the pre-release members take a very active role in the development?
hmm...
i am a sort of beta tester of CDCheck. not in any official manner: i just use the betas all the time; am in fairly frequent correspondense with the author; have reported some bugs to him; made quite a few suggestions for improvement and requests; and a fair number of those were actually implemented eventually in newer versions.
but this is all totally unofficial, and i can't say that am in any way affiliated with the program or that i am working with the author (a very nice fellow btw).

PostPosted: Thu Apr 17, 2003 2:27 am
by Wedge Maniac
Absolutely. We have a very active role in development. We test the betas and can (if we choose) report the bugs-- it's not mandatory. The pre-release members are beta testers AND donors, so donors aren't expected to do anything but reap the benefits of new features earlier than the general public, but obviously it's in everybody's best interest if they report bugs as well. But yes we are more active than just being beta testers. Jamie gives due thought to any suggestions you might have regardless of your status, but simply put, the pre-release members get priority, and we interact with Jamie pretty much every day, if only small amount (depends on the phase of development).

It actually works great and I'm happy to be a part of it. Knowledgable members really contribute, though I don't want to pretend that I am one of them. My best input has been in spotting a bug here and there. There are other members who understand programing and it's relation to Windows and Linux who are able to tech-speak with Jamie. It's really cool to watch the progress, the changes, the report-backs.....the evolution, if you will. I manage to learn a bit here and there. It's fun and I like the guys that are involved.

EDIT/ I have to mention the obvious -- although we provide him feedback and suggestions, Jamie is the final word on what gets released and when.

PostPosted: Thu Apr 17, 2003 2:46 am
by dodecahedron
cool.
so, if i'll see that i go on using it quite regularly, i'll try and drum up the $15 and become a pre-release member.

PostPosted: Thu Apr 17, 2003 2:58 am
by Wedge Maniac
Cool, I would love to see you in there. Intelligent feedback helps Jamie to take the program to its next level.