Ticket #8 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

Waveform display triggers crash while working with big filese

Reported by: avneesh-singh Owned by: julien-quint
Priority: major Milestone: Obi Beta 2
Component: Application Version:
Keywords: display Cc: avneesh-singh
Blocked By: Blocking:
Time planned: 1d Time remaining: 1d
Time spent: 1d Estimated Number of Hours:
Add Hours to Ticket: Billable?:
Total Hours:

Description

Exception is thrown if a large size audio file is used. It happened with atleast following operations

  • Import file
  • move keyboard focus to file
  • try to split this file.

Steps for one of these cases:

  1. open a project.
  2. create a section.
  3. while keyboard focus is on this section in contents view import this

large file.

Result: exception is thrown. debugger takes to line 179 of class waveform which says if (mBitmap != null) pe.Graphics.DrawImage?(mBitmap, new Point(0, 0));

size of file used for test Failed file: 1 hr, 2 min in time and 329 MB in size. File which passed test: 32 min in time and about 157 MB in size.

Not yet able to check exact threshold size above which crash is triggered but rough sizes are listed above.

Sender: julienq Logged In: YES user_id=1313300 Originator: NO

I gave up trying to open a 1-hour file; possibly my virtual machine is the main problem here. A generic solution for working with large files could be to chunk large files into smaller blocks, e.g. anything longer than 5 minutes (selectable by a preference; and while doing import) could be auto-split into 5 minutes chunks which would improve performance and navigation. Note that it is not phrase detection, we just cut at the 5-minute mark regardless of audio content. We can even add a custom class to easily recognize blocks that have been chunked in this way.


Date: 2008-05-15 15:24 Sender: julienq Logged In: YES user_id=1313300 Originator: NO

I gave up trying to open a 1-hour file; possibly my virtual machine is the main problem here. A generic solution for working with large files could be to chunk large files into smaller blocks, e.g. anything longer than 5 minutes (selectable by a preference; and while doing import) could be auto-split into 5 minutes chunks which would improve performance and navigation. Note that it is not phrase detection, we just cut at the 5-minute mark regardless of audio content. We can even add a custom class to easily recognize blocks that have been chunked in this way.

Change History

comment:1 Changed 11 years ago by avneesh-singh

  • Cc avneesh-singh added
  • Owner changed from somebody to julien-quint

comment:1 Changed 11 years ago by avneesh-singh

  • Milestone changed from Obi Beta 2 candidate to Obi Beta 2

comment:1 Changed 11 years ago by avneesh-singh

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.