Wavosaur

SammeyTiger · Joined: 16 May 2008 Posts: 6

I remember reading that the current version of Wavosaur.
Can't read big files.
What is the max file size (in time, and file size) that it can reliably read?

Wavosaur Main Developer · Site Admin Joined: 30 Sep 2006 Posts: 507 Location: France

It's difficult to answer you, it depends of the memory (RAM) installed on your system.
For all my own project I never had problem. But with huge file >1 hour for example, you could have memory allocation error.

I hope it helps.
_________________
~~~~~~~~~~~~~~~~~~
Wavosaur Main Developer
~~~~~~~~~~~~~~~~~~
http://www.wavosaur.com

SammeyTiger · Joined: 16 May 2008 Posts: 6

Thank you,
at least now I have an estimate if nothing else.
And that is more then I had before.

maxb · Joined: 29 Jul 2008 Posts: 13

That was a problem I had before at work with only 512 MB ram. Now I got 1024 MB ram and Wavosaur is working better on a little longer recordings.

Dandruff · Joined: 16 Dec 2006 Posts: 58

Yeah, we really need diskstreaming!

http://www.wavosaur.com/forum/unable-to-load-large-mp3-1-0-0-8000-t293.html

Wavosaur Main Developer · Site Admin Joined: 30 Sep 2006 Posts: 507 Location: France

I know, me too I need this!

We are analysing new Wavosaur architecture (a sort of v2). For the moment I don't have the visibilty to answer you about the schedule.
It should be better with 4 times more "human" resource...
_________________
~~~~~~~~~~~~~~~~~~
Wavosaur Main Developer
~~~~~~~~~~~~~~~~~~
http://www.wavosaur.com

Dandruff · Joined: 16 Dec 2006 Posts: 58

Wavosaur Main Developer · Site Admin Joined: 30 Sep 2006 Posts: 507 Location: France

Ohhh yes!
It's just a big piece of code. We need to study a good and efficient architecture (on paper unfortunately). And after we will code. It takes time.

Next release (1.0.3) will have very interresting new feature. After this release I will study CPU usage (one other heavy job on GUI, and for me, yeahh...).
At the end of this year we think to have a good idea of the v2 architecture and its feasibility.
_________________
~~~~~~~~~~~~~~~~~~
Wavosaur Main Developer
~~~~~~~~~~~~~~~~~~
http://www.wavosaur.com

Dandruff · Joined: 16 Dec 2006 Posts: 58

Cool

lcubed · Joined: 15 Aug 2009 Posts: 1

Hello and thanks!

I understand the the current system doesn't use disk streaming techniques to deal with memory limitations on system. I understand that this limits the file size that Wavosaur can deal with reasonably.

That said, can I do something with the "File | New" feature to interactively determine what the largest file size that wavosaur will open and edit on my system?

I've got 2MB of RAM currently.

If this isn't a good approach to take, please provide an alternative method other that brute force create a wav file of a certain size and test, close the file, make another file and test, etc... Or, if there's a easy automated tool for creating these test files, that would kickstart this method that would help too.

:::::What prompted this question:::::
I'm trying to edit a lame decoded mp3 (to wav) file that is 1h43m22s long.
Wavosaur loads, but only displays approx 1m55s of the beginning of the file. I've tried to make sure that some other problem isn't causing the shortening/splitting of the file at import time, and don't see any error that I'm making as yet.

I tried creating a new file with the "File | New" feature and input 6222s for the file length and get varying results. Sometimes it creates a shorter file and sometimes I get a memory allocation error.

Big thanks in advance, love what you guys do...

-lcubed