#8 More flexible filling...

Awaiting_group
open
nobody
2
2003-03-02
2002-04-08
No

Hi Elwin!
I was among the first to try out your program. We
emailed back and fourth a couple of times and I see
that some of my suggestions like grouping and so on is
now in BTTB. Great work...

The background to my new request is that I don't really
need to fill my cd's as much as possible. I more
pleased if BTTB can fill them up to the
mediasize-slackspace (for example 700-30) and maximize
the amoung of cd's outputted instead. My wish is that
BTTB will concentrate on making as many cd's within the
670-700 intervall instead of maximizing each cd which
will often result in huge leftovers for me...
This type of need is probably only needed when burning
large directories (20-650MB a piece)... can this be done?

If you don't see what I'm getting at, tell me so that I
can clarify this somewhat blurrish request...

Thanks!

Erson

****

Hi Erson,

Sorry for the slow reply, very very hectic here...

I assume you mean if it finds a better solution using
smaller chunks big ones may be left behind? A quick n
dirty solution may be using a 1-second allowed time
which will give smaller chunks less chance to be
selected (as they're tried largest to smallest)

--Elwin

****

I tried using 1s allowed time... but apparently my
computer is way to fast...

Didn't you understand what I mean?
I want BTTB to be concentrate on maximizing the number
of cd's (minimizing the leftover) while keeping their
sizes within my allowed intervall instead of trying to
maximize each cd and not caring about the number of
cd's and leftovers...

Erson

***

I understand what you mean, as I wrote this would have
been a quick and dirty solution as only the large
chunks are a problem. I'll think about it, but it would
mean modifying the core algorithm...

--Elwin

****

Would it? Wouldn't it be sufficient if you just had it
stop when it reached the intervall and then tried to
make as many cd's as possible...

****

The algorithm is now CD-at-a-time based, not batched-
so yes, unfortunately...

--Elwin

Discussion

    • priority: 3 --> 2