Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #932 > unrolled thread

devede? is t me, or is it rubbish?

Back to article view | Back to comp.os.linux.misc

Contents

  devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-26 21:43 +0100
    Re: devede? is t me, or is it rubbish? philo <philo@invalid.not> - 2011-04-26 16:23 -0500
      Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-26 17:43 -0400
        Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-26 23:43 +0100
          Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-26 21:48 -0400
            Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-27 08:22 +0100
              Re: devede? is t me, or is it rubbish? goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid> - 2011-04-27 10:41 +0000
                Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-27 17:58 +0100
                  Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-27 13:10 -0400
                    Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-27 18:18 +0100
                      Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-27 16:59 -0400
              Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-27 12:53 -0400
                Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-27 13:08 -0400
                  Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-27 18:17 +0100
                  Re: devede? is t me, or is it rubbish? goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid> - 2011-04-28 11:05 +0000
                    Re: devede? is t me, or is it rubbish? The Natural Philosopher <tnp@invalid.invalid> - 2011-04-28 12:20 +0100
                    Re: devede? is t me, or is it rubbish? despen@verizon.net - 2011-04-28 09:10 -0400
                      Re: devede? is t me, or is it rubbish? goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid> - 2011-04-29 08:20 +0000
                        Re: devede? is t me, or is it rubbish? goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid> - 2011-04-29 08:20 +0000
                    Re: devede? is t me, or is it rubbish? Mark Hobley <markhobley@yahoo.donottypethisbit.co> - 2011-04-29 21:11 +0000
    Re: devede? is t me, or is it rubbish? Mysterious Traveler <mysterious.traveler@dot.net> - 2011-04-27 02:20 -0500

Page 1 of 2  [1] 2  Next page →

#932 — devede? is t me, or is it rubbish?

I am trying to make an DVD ISO of a 3.5GB mpeg.

Devedee is still going 4 hours later saying 1/4 and 100%.

at least 7 GB of mpg has built up in the temporary directory.

WTF is happening? will it ever stop? where is the ISO?

[toc] | [next] | [standalone]

#934

On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
> I am trying to make an DVD ISO of a 3.5GB mpeg.
>
> Devedee is still going 4 hours later saying 1/4 and 100%.
>
> at least 7 GB of mpg has built up in the temporary directory.
>
> WTF is happening? will it ever stop? where is the ISO?


I'd stop it and get rid of any temporary file created


Personally I use k3b for burning iso burning...
Unfortunately  many of the other burning apps I've tried just did not it

[toc] | [prev] | [next] | [standalone]

#935

philo <philo@invalid.not> writes:

> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>
>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>
>> at least 7 GB of mpg has built up in the temporary directory.
>>
>> WTF is happening? will it ever stop? where is the ISO?
>
>
> I'd stop it and get rid of any temporary file created
> Personally I use k3b for burning iso burning...
> Unfortunately  many of the other burning apps I've tried just did not it

devede creates isos, not burn them.

I've had it take a long time but 4 hours is a lot.
It does need a lot of CPU.

[toc] | [prev] | [next] | [standalone]

#936

despen@verizon.net wrote:
> philo <philo@invalid.not> writes:
> 
>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>
>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>
>>> at least 7 GB of mpg has built up in the temporary directory.
>>>
>>> WTF is happening? will it ever stop? where is the ISO?
>>
>> I'd stop it and get rid of any temporary file created
>> Personally I use k3b for burning iso burning...
>> Unfortunately  many of the other burning apps I've tried just did not it
> 
> devede creates isos, not burn them.
> 
> I've had it take a long time but 4 hours is a lot.
> It does need a lot of CPU.

well its finished BUT it said the size would be 2.3GB. but the actual 
ISO is 7.3GB!!! WTF is happening?

[toc] | [prev] | [next] | [standalone]

#937

The Natural Philosopher <tnp@invalid.invalid> writes:

> despen@verizon.net wrote:
>> philo <philo@invalid.not> writes:
>>
>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>
>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>
>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>
>>>> WTF is happening? will it ever stop? where is the ISO?
>>>
>>> I'd stop it and get rid of any temporary file created
>>> Personally I use k3b for burning iso burning...
>>> Unfortunately  many of the other burning apps I've tried just did not it
>>
>> devede creates isos, not burn them.
>>
>> I've had it take a long time but 4 hours is a lot.
>> It does need a lot of CPU.
>
> well its finished BUT it said the size would be 2.3GB. but the actual
> ISO is 7.3GB!!! WTF is happening?

Hard to say.

There are 8.5GB DVDs to put the file on.

There's an "adjust disk usage" thing that lets you
control the ultimate ISO file size.

[toc] | [prev] | [next] | [standalone]

#939

despen@verizon.net wrote:
> The Natural Philosopher <tnp@invalid.invalid> writes:
> 
>> despen@verizon.net wrote:
>>> philo <philo@invalid.not> writes:
>>>
>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>
>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>
>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>
>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>> I'd stop it and get rid of any temporary file created
>>>> Personally I use k3b for burning iso burning...
>>>> Unfortunately  many of the other burning apps I've tried just did not it
>>> devede creates isos, not burn them.
>>>
>>> I've had it take a long time but 4 hours is a lot.
>>> It does need a lot of CPU.
>> well its finished BUT it said the size would be 2.3GB. but the actual
>> ISO is 7.3GB!!! WTF is happening?
> 
> Hard to say.
> 
> There are 8.5GB DVDs to put the file on.
> 
> There's an "adjust disk usage" thing that lets you
> control the ultimate ISO file size.

The actual tunable turned out to be 'video bit rate' or something.


The 'adjust disk image' does nothing, it seems.

And the telltale that goes from 0-100% is valueless. It goes to 100% 
about 1/4 of the way through.

This is probably the worst piece of Linux software I have used. But then 
it appears to be written in Python, so no surprises there..

[toc] | [prev] | [next] | [standalone]

#940

On Wed, 27 Apr 2011 08:22:46 +0100, The Natural Philosopher wrote:

> despen@verizon.net wrote:
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>> 
>>> despen@verizon.net wrote:
>>>> philo <philo@invalid.not> writes:
>>>>
>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>
>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>
>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>
>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>> use k3b for burning iso burning... Unfortunately  many of the other
>>>>> burning apps I've tried just did not it
>>>> devede creates isos, not burn them.
>>>>
>>>> I've had it take a long time but 4 hours is a lot. It does need a lot
>>>> of CPU.
>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>> ISO is 7.3GB!!! WTF is happening?
>> 
>> Hard to say.
>> 
>> There are 8.5GB DVDs to put the file on.
>> 
>> There's an "adjust disk usage" thing that lets you control the ultimate
>> ISO file size.
> 
> The actual tunable turned out to be 'video bit rate' or something.
> 
> 
> The 'adjust disk image' does nothing, it seems.
> 
> And the telltale that goes from 0-100% is valueless. It goes to 100%
> about 1/4 of the way through.
> 
> This is probably the worst piece of Linux software I have used. But then
> it appears to be written in Python, so no surprises there..

have some quarrel with python or with using scripting languages
for heavy GUI apps in general ?

[toc] | [prev] | [next] | [standalone]

#945

goarilla wrote:
> On Wed, 27 Apr 2011 08:22:46 +0100, The Natural Philosopher wrote:
> 
>> despen@verizon.net wrote:
>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>
>>>> despen@verizon.net wrote:
>>>>> philo <philo@invalid.not> writes:
>>>>>
>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>
>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>
>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>
>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>>> use k3b for burning iso burning... Unfortunately  many of the other
>>>>>> burning apps I've tried just did not it
>>>>> devede creates isos, not burn them.
>>>>>
>>>>> I've had it take a long time but 4 hours is a lot. It does need a lot
>>>>> of CPU.
>>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>>> ISO is 7.3GB!!! WTF is happening?
>>> Hard to say.
>>>
>>> There are 8.5GB DVDs to put the file on.
>>>
>>> There's an "adjust disk usage" thing that lets you control the ultimate
>>> ISO file size.
>> The actual tunable turned out to be 'video bit rate' or something.
>>
>>
>> The 'adjust disk image' does nothing, it seems.
>>
>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>> about 1/4 of the way through.
>>
>> This is probably the worst piece of Linux software I have used. But then
>> it appears to be written in Python, so no surprises there..
> 
> have some quarrel with python or with using scripting languages
> for heavy GUI apps in general ?
Both :-)

But its more that the sort of person who choose python, tends to 
be..ahem..an enthusiastic amateur

[toc] | [prev] | [next] | [standalone]

#947

The Natural Philosopher <tnp@invalid.invalid> writes:

> goarilla wrote:
>> On Wed, 27 Apr 2011 08:22:46 +0100, The Natural Philosopher wrote:
>>
>>> despen@verizon.net wrote:
>>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>>
>>>>> despen@verizon.net wrote:
>>>>>> philo <philo@invalid.not> writes:
>>>>>>
>>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>>
>>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>>
>>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>>
>>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>>>> use k3b for burning iso burning... Unfortunately  many of the other
>>>>>>> burning apps I've tried just did not it
>>>>>> devede creates isos, not burn them.
>>>>>>
>>>>>> I've had it take a long time but 4 hours is a lot. It does need a lot
>>>>>> of CPU.
>>>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>>>> ISO is 7.3GB!!! WTF is happening?
>>>> Hard to say.
>>>>
>>>> There are 8.5GB DVDs to put the file on.
>>>>
>>>> There's an "adjust disk usage" thing that lets you control the ultimate
>>>> ISO file size.
>>> The actual tunable turned out to be 'video bit rate' or something.
>>>
>>>
>>> The 'adjust disk image' does nothing, it seems.
>>>
>>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>>> about 1/4 of the way through.
>>>
>>> This is probably the worst piece of Linux software I have used. But then
>>> it appears to be written in Python, so no surprises there..
>>
>> have some quarrel with python or with using scripting languages
>> for heavy GUI apps in general ?
> Both :-)
>
> But its more that the sort of person who choose python, tends to
> be..ahem..an enthusiastic amateur

Well, I chose Python.

If starting programming in 1964 makes me an amateur...

[toc] | [prev] | [next] | [standalone]

#949

despen@verizon.net wrote:
> The Natural Philosopher <tnp@invalid.invalid> writes:
> 
>> goarilla wrote:
>>> On Wed, 27 Apr 2011 08:22:46 +0100, The Natural Philosopher wrote:
>>>
>>>> despen@verizon.net wrote:
>>>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>>>
>>>>>> despen@verizon.net wrote:
>>>>>>> philo <philo@invalid.not> writes:
>>>>>>>
>>>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>>>
>>>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>>>
>>>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>>>
>>>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>>>>> use k3b for burning iso burning... Unfortunately  many of the other
>>>>>>>> burning apps I've tried just did not it
>>>>>>> devede creates isos, not burn them.
>>>>>>>
>>>>>>> I've had it take a long time but 4 hours is a lot. It does need a lot
>>>>>>> of CPU.
>>>>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>>>>> ISO is 7.3GB!!! WTF is happening?
>>>>> Hard to say.
>>>>>
>>>>> There are 8.5GB DVDs to put the file on.
>>>>>
>>>>> There's an "adjust disk usage" thing that lets you control the ultimate
>>>>> ISO file size.
>>>> The actual tunable turned out to be 'video bit rate' or something.
>>>>
>>>>
>>>> The 'adjust disk image' does nothing, it seems.
>>>>
>>>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>>>> about 1/4 of the way through.
>>>>
>>>> This is probably the worst piece of Linux software I have used. But then
>>>> it appears to be written in Python, so no surprises there..
>>> have some quarrel with python or with using scripting languages
>>> for heavy GUI apps in general ?
>> Both :-)
>>
>> But its more that the sort of person who choose python, tends to
>> be..ahem..an enthusiastic amateur
> 
> Well, I chose Python.
> 
> If starting programming in 1964 makes me an amateur...

says nothing about it.

Depends what you did in between.

[toc] | [prev] | [next] | [standalone]

#953

The Natural Philosopher <tnp@invalid.invalid> writes:

> despen@verizon.net wrote:
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>
>>>> have some quarrel with python or with using scripting languages
>>>> for heavy GUI apps in general ?
>>> Both :-)
>>>
>>> But its more that the sort of person who choose python, tends to
>>> be..ahem..an enthusiastic amateur
>>
>> Well, I chose Python.
>>
>> If starting programming in 1964 makes me an amateur...
>
> says nothing about it.
>
> Depends what you did in between.

I can't figure out where you are coming from.
First you make a wild generalization that you know can't
be true, then you try to defend it.

I can assure you that the term "enthusiastic amateur"
can in no way be applied to me.  I've used Python and
dozens of other languages.  I find very little fault with
Python.  I used, it, it did the job with a minimum of fuss.
I'd use it again.

And of the years from 1964 until today, I spent no more than
one of those years in management.  I didn't like it.  I've been
writing code since 1964 and I still do today and I'm well paid for it.

That's not to say the progress bar couldn't have been handled better
but changing the implementation language wouldn't do a thing to improve
the situation.

[toc] | [prev] | [next] | [standalone]

#944

The Natural Philosopher <tnp@invalid.invalid> writes:

> despen@verizon.net wrote:
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>
>>> despen@verizon.net wrote:
>>>> philo <philo@invalid.not> writes:
>>>>
>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>
>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>
>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>
>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>> I'd stop it and get rid of any temporary file created
>>>>> Personally I use k3b for burning iso burning...
>>>>> Unfortunately  many of the other burning apps I've tried just did not it
>>>> devede creates isos, not burn them.
>>>>
>>>> I've had it take a long time but 4 hours is a lot.
>>>> It does need a lot of CPU.
>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>> ISO is 7.3GB!!! WTF is happening?
>>
>> Hard to say.
>>
>> There are 8.5GB DVDs to put the file on.
>>
>> There's an "adjust disk usage" thing that lets you
>> control the ultimate ISO file size.
>
> The actual tunable turned out to be 'video bit rate' or something.
>
>
> The 'adjust disk image' does nothing, it seems.

I seem to remember it doing something for me.
I had a file that was just over 4.7...

But as long as you found a solution.

> And the telltale that goes from 0-100% is valueless. It goes to 100%
> about 1/4 of the way through.

I'd have to look at the code, but likely the underlying library doesn't
provide good numbers so they are taking a wild guess.  You could see if
there's a place to file a bug report.

> This is probably the worst piece of Linux software I have used. But
> then it appears to be written in Python, so no surprises there..

I  just  rewrote  a large  amount  of  PerlGtk  as  Python Qt4  and  was
pleasantly surprised at Python. I'd still pick Perl first but I couldn't
find PerlQt4. I didn't see any major failings in Python.

[toc] | [prev] | [next] | [standalone]

#946

despen@verizon.net writes:

> The Natural Philosopher <tnp@invalid.invalid> writes:
>
>> despen@verizon.net wrote:
>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>
>>>> despen@verizon.net wrote:
>>>>> philo <philo@invalid.not> writes:
>>>>>
>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>
>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>
>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>
>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>> I'd stop it and get rid of any temporary file created
>>>>>> Personally I use k3b for burning iso burning...
>>>>>> Unfortunately  many of the other burning apps I've tried just did not it
>>>>> devede creates isos, not burn them.
>>>>>
>>>>> I've had it take a long time but 4 hours is a lot.
>>>>> It does need a lot of CPU.
>>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>>> ISO is 7.3GB!!! WTF is happening?
>>>
>>> Hard to say.
>>>
>>> There are 8.5GB DVDs to put the file on.
>>>
>>> There's an "adjust disk usage" thing that lets you
>>> control the ultimate ISO file size.
>>
>> The actual tunable turned out to be 'video bit rate' or something.
>>
>>
>> The 'adjust disk image' does nothing, it seems.
>
> I seem to remember it doing something for me.
> I had a file that was just over 4.7...
>
> But as long as you found a solution.
>
>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>> about 1/4 of the way through.
>
> I'd have to look at the code, but likely the underlying library doesn't
> provide good numbers so they are taking a wild guess.  You could see if
> there's a place to file a bug report.

Follow up.

Progress is calculated off file size.

An approach that is sure to fail.

They should never let the number hit 100%, perhaps a message,
"still running, taking longer than expected..."

[toc] | [prev] | [next] | [standalone]

#948

despen@verizon.net wrote:
> despen@verizon.net writes:
> 
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>
>>> despen@verizon.net wrote:
>>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>>
>>>>> despen@verizon.net wrote:
>>>>>> philo <philo@invalid.not> writes:
>>>>>>
>>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>>
>>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>>
>>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>>
>>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>>> I'd stop it and get rid of any temporary file created
>>>>>>> Personally I use k3b for burning iso burning...
>>>>>>> Unfortunately  many of the other burning apps I've tried just did not it
>>>>>> devede creates isos, not burn them.
>>>>>>
>>>>>> I've had it take a long time but 4 hours is a lot.
>>>>>> It does need a lot of CPU.
>>>>> well its finished BUT it said the size would be 2.3GB. but the actual
>>>>> ISO is 7.3GB!!! WTF is happening?
>>>> Hard to say.
>>>>
>>>> There are 8.5GB DVDs to put the file on.
>>>>
>>>> There's an "adjust disk usage" thing that lets you
>>>> control the ultimate ISO file size.
>>> The actual tunable turned out to be 'video bit rate' or something.
>>>
>>>
>>> The 'adjust disk image' does nothing, it seems.
>> I seem to remember it doing something for me.
>> I had a file that was just over 4.7...
>>
>> But as long as you found a solution.
>>
>>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>>> about 1/4 of the way through.
>> I'd have to look at the code, but likely the underlying library doesn't
>> provide good numbers so they are taking a wild guess.  You could see if
>> there's a place to file a bug report.
> 
> Follow up.
> 
> Progress is calculated off file size.
except it isn't. The file goes on growing well past 100%. amd then it 
sits there for two hours while it concocts the .ISO. :-)


> 
> An approach that is sure to fail.
> 
> They should never let the number hit 100%, perhaps a message,
> "still running, taking longer than expected..."
I bet is not a they, its a he :-0)

[toc] | [prev] | [next] | [standalone]

#960

On Wed, 27 Apr 2011 13:08:35 -0400, despen wrote:

> despen@verizon.net writes:
> 
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>
>>> despen@verizon.net wrote:
>>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>>
>>>>> despen@verizon.net wrote:
>>>>>> philo <philo@invalid.not> writes:
>>>>>>
>>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>>
>>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>>
>>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>>
>>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>>>> use k3b for burning iso burning... Unfortunately  many of the
>>>>>>> other burning apps I've tried just did not it
>>>>>> devede creates isos, not burn them.
>>>>>>
>>>>>> I've had it take a long time but 4 hours is a lot. It does need a
>>>>>> lot of CPU.
>>>>> well its finished BUT it said the size would be 2.3GB. but the
>>>>> actual ISO is 7.3GB!!! WTF is happening?
>>>>
>>>> Hard to say.
>>>>
>>>> There are 8.5GB DVDs to put the file on.
>>>>
>>>> There's an "adjust disk usage" thing that lets you control the
>>>> ultimate ISO file size.
>>>
>>> The actual tunable turned out to be 'video bit rate' or something.
>>>
>>>
>>> The 'adjust disk image' does nothing, it seems.
>>
>> I seem to remember it doing something for me. I had a file that was
>> just over 4.7...
>>
>> But as long as you found a solution.
>>
>>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>>> about 1/4 of the way through.
>>
>> I'd have to look at the code, but likely the underlying library doesn't
>> provide good numbers so they are taking a wild guess.  You could see if
>> there's a place to file a bug report.
> 
> Follow up.
> 
> Progress is calculated off file size.
> 
> An approach that is sure to fail.
> 

out of curiousity how would you design an
accurate progress meter ?

> They should never let the number hit 100%, perhaps a message, "still
> running, taking longer than expected..."

[toc] | [prev] | [next] | [standalone]

#961

goarilla wrote:
> On Wed, 27 Apr 2011 13:08:35 -0400, despen wrote:
> 
>> despen@verizon.net writes:
>>
>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>
>>>> despen@verizon.net wrote:
>>>>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>>>>
>>>>>> despen@verizon.net wrote:
>>>>>>> philo <philo@invalid.not> writes:
>>>>>>>
>>>>>>>> On 04/26/2011 03:43 PM, The Natural Philosopher wrote:
>>>>>>>>> I am trying to make an DVD ISO of a 3.5GB mpeg.
>>>>>>>>>
>>>>>>>>> Devedee is still going 4 hours later saying 1/4 and 100%.
>>>>>>>>>
>>>>>>>>> at least 7 GB of mpg has built up in the temporary directory.
>>>>>>>>>
>>>>>>>>> WTF is happening? will it ever stop? where is the ISO?
>>>>>>>> I'd stop it and get rid of any temporary file created Personally I
>>>>>>>> use k3b for burning iso burning... Unfortunately  many of the
>>>>>>>> other burning apps I've tried just did not it
>>>>>>> devede creates isos, not burn them.
>>>>>>>
>>>>>>> I've had it take a long time but 4 hours is a lot. It does need a
>>>>>>> lot of CPU.
>>>>>> well its finished BUT it said the size would be 2.3GB. but the
>>>>>> actual ISO is 7.3GB!!! WTF is happening?
>>>>> Hard to say.
>>>>>
>>>>> There are 8.5GB DVDs to put the file on.
>>>>>
>>>>> There's an "adjust disk usage" thing that lets you control the
>>>>> ultimate ISO file size.
>>>> The actual tunable turned out to be 'video bit rate' or something.
>>>>
>>>>
>>>> The 'adjust disk image' does nothing, it seems.
>>> I seem to remember it doing something for me. I had a file that was
>>> just over 4.7...
>>>
>>> But as long as you found a solution.
>>>
>>>> And the telltale that goes from 0-100% is valueless. It goes to 100%
>>>> about 1/4 of the way through.
>>> I'd have to look at the code, but likely the underlying library doesn't
>>> provide good numbers so they are taking a wild guess.  You could see if
>>> there's a place to file a bug report.
>> Follow up.
>>
>> Progress is calculated off file size.
>>
>> An approach that is sure to fail.
>>
> 
> out of curiousity how would you design an
> accurate progress meter ?

well you could calculate the real file size..and monitor ITS creation.

But seriously, its a hacked together gui that is pretty feature full, 
but has no sane defaults, very little explanation as to what the 
controls actually do, and a telltale that is so misleading it took me 5 
attempts before I realised the program had not in fact crashed, but was 
still grinding away..

In short I call it 'amateur' because it is designed by one knowledgeable 
person probably, to do what *he* wanted. Not as a program that would 
enable a non-knowledgeable user, to simply do what *they* wanted.

It is so similar in that respect to xsane..

Compare and contrast with gnome apps. Buggy they sometimes are, and 
feature poor maybe, but any idiot who wants to can use them.

[toc] | [prev] | [next] | [standalone]

#962

goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid>
writes:

> On Wed, 27 Apr 2011 13:08:35 -0400, despen wrote:
>
>> despen@verizon.net writes:
>> Follow up.
>> 
>> Progress is calculated off file size.
>> 
>> An approach that is sure to fail.
>
> out of curiousity how would you design an
> accurate progress meter ?

To start with, see next sentence:

>> They should never let the number hit 100%, perhaps a message, "still
>> running, taking longer than expected..."

Accurate would require that the program doing the conversion output
percentage numbers as it runs.  Only that program would know where it is
in the input file.

You can't really infer much from the size of the output file.

[toc] | [prev] | [next] | [standalone]

#965

On Thu, 28 Apr 2011 09:10:24 -0400, despen wrote:

> goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid>
> writes:
> 
>> On Wed, 27 Apr 2011 13:08:35 -0400, despen wrote:
>>
>>> despen@verizon.net writes:
>>> Follow up.
>>> 
>>> Progress is calculated off file size.
>>> 
>>> An approach that is sure to fail.
>>
>> out of curiousity how would you design an accurate progress meter ?
> 
> To start with, see next sentence:
> 
>>> They should never let the number hit 100%, perhaps a message, "still
>>> running, taking longer than expected..."
> 
> Accurate would require that the program doing the conversion output
> percentage numbers as it runs.  Only that program would know where it is
> in the input file.
> 
> You can't really infer much from the size of the output file.

yeah but a lot of times these programs are frontends
for ffmpeg, mencoder, vobcopy, lame, ...

[toc] | [prev] | [next] | [standalone]

#966

On Fri, 29 Apr 2011 08:20:05 +0000, goarilla wrote:

> On Thu, 28 Apr 2011 09:10:24 -0400, despen wrote:
> 
>> goarilla <kevin.paulus@mtm.DOTremove-thisDOT.kuleuven.DOTbe.invalid>
>> writes:
>> 
>>> On Wed, 27 Apr 2011 13:08:35 -0400, despen wrote:
>>>
>>>> despen@verizon.net writes:
>>>> Follow up.
>>>> 
>>>> Progress is calculated off file size.
>>>> 
>>>> An approach that is sure to fail.
>>>
>>> out of curiousity how would you design an accurate progress meter ?
>> 
>> To start with, see next sentence:
>> 
>>>> They should never let the number hit 100%, perhaps a message, "still
>>>> running, taking longer than expected..."
>> 
>> Accurate would require that the program doing the conversion output
>> percentage numbers as it runs.  Only that program would know where it
>> is in the input file.
>> 
>> You can't really infer much from the size of the output file.
> 
> yeah but a lot of times these programs are frontends for ffmpeg,
> mencoder, vobcopy, lame, ...

never mind i misread

[toc] | [prev] | [next] | [standalone]

#976

On Thu, 28 Apr 2011 11:05:07 +0000, goarilla wrote:

> out of curiousity how would you design an accurate progress meter ?

I thought that I had seen something like that on rosettacode, but I just
had a quick look and couldn't find anything, so that is probably a candidate
for a new task.

Mark.

-- 
Mark Hobley
Linux User: #370818  http://markhobley.yi.org/

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.misc

csiph-web