Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
109 user(s) are online (60 user(s) are browsing Forums)

Members: 1
Guests: 108

TheMagicSN, more...

Headlines

 
  Register To Post  

Cannot allocate more than 100MB but have 1.5GB free
Quite a regular
Quite a regular


See User information
I came across an annoying problem.

I need to edit an audio sample that is 170MB large. I use SampleManager because it is the best (on a machine where AudioMaster doesn't work). But the program says it cannot allocate more than 100MB (of presumably continuous memory), but I have a freshly started system with 1.5GB memory free, which means there should be at least 1GB continous available.

Is this an annoying limitation of OS4 memory management, to simply forbid allocations above 100MB, or at least report no more than 100MB when asked about the largest available chunk?

X1000. OS4.1 FEU2
I have swapping off, since I have 2GB physical RAM.

Do I have to hack this program to remove this check or what? Patch/hack exec perhaps...

Go to top
Re: Cannot allocate more than 100MB but have 1.5GB free
Just can't stay away
Just can't stay away


See User information
@Deniil

Try AmiSoundEd, it has a different memory management model. It doesn't allocate memory for the sample as one block but, rather, as a linked series of buffers.

Go to top
Re: Cannot allocate more than 100MB but have 1.5GB free
Quite a regular
Quite a regular


See User information
@trixie

Thanks!
I'll try it.

Turns out OS4 does return 1.6GB as largest available, but SampleManager doesn't believe it. It has some internal limit of 100MB. Patched exec->AvailMem to force it to return more than 100MB, only to find out that it returns 1,6GB and SampleManager says 100MB no matter what... ;)

Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project