Bug 140444 - audio project: easy to read colors and markers for 650 and 700MB
Summary: audio project: easy to read colors and markers for 650 and 700MB
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: Audio Project (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-22 16:19 UTC by Maciej Pilichowski
Modified: 2014-10-18 07:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-01-22 16:19:48 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs

I would opt for two markers not only one -- at 650 and 700MB.
Please provide also info in MB not only minutes (I know it is an audio but I think in MB).

And colors -- personally I would like three secions -- 0-650 (green?), 650-700 (yellow?) and over 700 (red?). Or maybe four -- the last point would be overburn. But solid colors, not gradient! I have real problems figuring out the indications when the colors are not solid.
Comment 1 Sebastian Trueg 2007-01-22 17:22:52 UTC
You can easily switch between MB and minutes via the context menu. How about 
K3b remembering the last setting?

As for the size: this is adjusted to the medium. So your proposal seems like a 
backstep to me...
Comment 2 Maciej Pilichowski 2007-01-22 20:03:21 UTC
> You can easily switch between MB and minutes via the context menu. How about 
> K3b remembering the last setting? 

Great!
 
> As for the size: this is adjusted to the medium. 

What medium? There is none -- and marker sits still. I inserted 650MB -- no change.

Comment 3 Maciej Pilichowski 2007-01-22 20:07:35 UTC
Ok, the medium thing, I found out this context menu and I see your point. So maybe:
a) fixing auto detection
b) extra option showing all markers

ad.a) should I fill the next report about this issue? I run k3b, marker at 700, I insert the disc 650 --> marker untouched (settings: auto)
Comment 4 Sebastian Trueg 2007-01-22 21:19:55 UTC
On Monday 22 January 2007 20:07, Maciej Pilichowski wrote:
> Ok, the medium thing, I found out this context menu and I see your point.
> So maybe: a) fixing auto detection


it works like a charm here.

> b) extra option showing all markers


nope. I don't like that.

> ad.a) should I fill the next report about this issue? I run k3b, marker at
> 700, I insert the disc 650 --> marker untouched (settings: auto)


is the disk empty?
Comment 5 Maciej Pilichowski 2007-01-22 21:45:47 UTC
> it works like a charm here. 

Do you use internal or external drive? Me -- external (usb).
 
 > > b) extra option showing all markers 
 > nope. I don't like that. 

Btw. I am talking only about those vertical small lines. Not full info. It would be really helpful because it is often I want to optimize burning. So I will see exactly how can I put files on several discs.

> > ad.a) should I fill the next report about this issue? I run k3b, marker at 
> > 700, I insert the disc 650 --> marker untouched (settings: auto) 
> is the disk empty? 

Nope. There are some data (I mean computer data, not audio, but I try to burn audio now).
Comment 6 Maciej Pilichowski 2007-01-22 21:46:23 UTC
PS. ad.b) it would be useful for creating the disc image, not actual burning
Comment 7 Sebastian Trueg 2007-01-23 09:57:57 UTC
On Monday 22 January 2007 21:45, Maciej Pilichowski wrote:
> > it works like a charm here.
>
> Do you use internal or external drive? Me -- external (usb).


both.

>  > > b) extra option showing all markers
>  >
>  > nope. I don't like that.
>
> Btw. I am talking only about those vertical small lines. Not full info. It
> would be really helpful because it is often I want to optimize burning. So
> I will see exactly how can I put files on several discs.


I do not really get yet why you need multiple markers

> > > ad.a) should I fill the next report about this issue? I run k3b, marker
> > > at 700, I insert the disc 650 --> marker untouched (settings: auto)
> >
> > is the disk empty?
>
> Nope. There are some data (I mean computer data, not audio, but I try to
> burn audio now).


only burnable media is used for the auto detection.
Comment 8 Maciej Pilichowski 2007-01-23 14:42:19 UTC
I put the autodetection issue in separate report.

> I do not really get yet why you need multiple markers 

The real scenario. I have a lot of mp3 files now (but the same applies to data as well), so I insert the first disc and add some files, let's say first 3 files. The files could fit perfectly (then I burn) or not -- then I consider deleting the last file or changing the disc (because I have mixed capacities), for example 650->700MB. 
But this works smoothly if I can see how I am doing -- the markers would be a great help, because I could immediately see that even deleting file it is more than the next markers.

Small visually, but really helpful hint from the program.