maximum file size supported

LadyMarmalady wrote on 6/19/2020, 10:13 AM

Hi there. Does anyone know if ACID Pro 8 (64 bit) has a maximum file size? If so, is there a way around it? ACID Pro 7 freaked out when I passed 2GB and wouldn't let me open files after saving although there was no warning I was reaching a critical point, therefore I lost work. I'm currently making a soundscape using ACID Pro 8 (8.0.10 build 20) and the size is heading upwards. I already use 'Remove Unused Clips' before saving to keep the size down. Thanks 😀

Comments

Former user wrote on 6/19/2020, 11:09 AM

I don't think since AP went to 64bit that it has project size limit. I for one have never encountered any size limits. Best of Luck

LadyMarmalady wrote on 6/19/2020, 12:21 PM

Thanks Maxtheschu. It's a bit unnerving to be heading towards the 2GB size with plenty still to do, so your comment is helping confidence 😁

sheppo wrote on 6/21/2020, 5:52 PM

These are the memory limits of windows, and I think they are the same as the per-application limits.

Windows 10

  • Pro 2 TB
  • Home 128 GB

Windows 8

  • Pro 51 GB
  • Home 128 GB

Windows 7

  • Pro 192 GB
  • Home Premium 16 GB
  • Home Basic 8 GB

source https://docs.microsoft.com/en-us/windows/win32/memory/memory-limits-for-windows-releases#physical-memory-limits-windows-10

LadyMarmalady wrote on 6/22/2020, 2:37 AM

This is very useful, sheppo, thanks. I'll look further into this 🙂 I can see on your link graphics cards affect memory too.

sheppo wrote on 6/22/2020, 8:09 AM

Assuming you're not on Windows 7 you'd be hard pressed to max out the 64bit per-application limit... but you know, never say never :)

LadyMarmalady wrote on 6/22/2020, 11:26 AM

Never indeed! I'll be back on here if limits are hit 😁 In the meantime, I'll keep on keeping on and racking up the KBs on Windows 10.

 

Former user wrote on 6/23/2020, 9:28 AM

Hi LadyM & Sheppo, I think there is a misunderstanding here.😀 The memory limits in Windows 10 is the amount of memory the OS can use. In other words, W10 64bit has a memory limit of 2 TB. If you installed 3 TB in your computer W10 can only use 2TB of that 3TB you installed. W10 32bit has 3GB memory limit (as do all 32bit computers) Years ago I installed 6GB in a 32GB computer and of course it would only recognize 3GB (I didn't know about the 32bit limitations) We do learn things the hard, don't we (me) 😁 So the memory limits should not effect the size of your project. However the size of the drive you put it on will. Do you have the file for your project stored on a storage drive or on the OS drive? As to video cards, if you have a computer with an integrated video card then it (the video card) is using the memory installed in the computer, if you have a stand alone video card with it's own memory then it won't access your computers memory. .

All the Best

Max

 

LadyMarmalady wrote on 6/23/2020, 10:17 AM

Hey both, thanks for taking an interest in this. You're so right, Maxtheschu, about learning the hard way - so many bits and pieces only become known about after a mishap! I'm using Windows 10 Pro, 64 bit, which is an update since I worked on the project where I lost work. The project is stored on a 2TB external hard drive, also an update. The video card is currently an integrated one, but I'm updating once I can get my tower to the maintenance guy. So I think I'm understanding this correctly, and everything is in place to enable me to create sound work without worries about hitting a limit again. Mega Good! Thanks again 😄

sheppo wrote on 6/25/2020, 6:30 AM

Looking at the original question, it could be you actually meant the size of the file being rendered from Acid?

2GB WAV file is a limit that many other DAWs suffer from to this very day, I know versions earlier than 7 had this limit, but not so sure about 7 - I have some rendered projects from AP7/AMS10 that are over 2GB.

Additionally there was a ~4GB file size limit for all file types on FAT32 formatted drives, which you may also have been hitting on your older PC.

However, Acid 64bit definitely doesn't have this restriction, since it supports a extensions to the WAV format which allow larger file outputs. If you have a new 64bit PC, and a newly formatted drive - which is likely formatted NTFS by default - you're very unlikely to hit extended file size limits when rendering.

LadyMarmalady wrote on 6/25/2020, 11:15 AM

No sheppo, not when rendering and creating a wav file. This limit was met when saving the work on ACID Pro 7 at the end of the day. I reached 1.96 GB on ACID Pro 7 at the end of one day, and the following day's work pushed it over 2 GB. Nothing seemed amiss during the saving process, and it was only the following day I found the file wouldn't open.

I tested the limit theory by making a test file. It also saved and opened below 2 GB but saved and wouldn't open when the size increased.

I got around the problem by splitting the file and then putting it back together after rendering in sections (bit fiddly but solved the problem!) as well as discovering the Remove Unused Clips button. All grist to the mill.

But I'm now confident this is something in the past for me, thanks to the help here. Maybe this thread will help someone else as I couldn't find anything mentioning this when I was ripping my hair out 😅

Many thanks!

LadyMarmalady wrote on 11/1/2020, 3:01 PM

Hi there

Back with the same issue again - a file over 2GB won't open. I thankfully didn't reach the limit on my last project so it never became an issue. I'm working with the same equipment and specs as I haven't had chance to change anything. Today the project I'm working on reached 188,6164 KB despite using the Remove Unused Clips tool each time I save. I have plenty more work to do, so I deliberately added large files to test pushing the size up, and sure enough once it passed 2GB it refused to open despite apparently saving with no problem and no warning that a limit was being reached. When I try to open it all that appears is a new Untitled ACID file.

I have 735 GB of free RAM space, and work using an external hard drive which also has masses of space.

Has anyone else encountered this and found a way around it apart from the fiddly splitting of the file?

Also, how does the Remove Unused Clips button work? Do I have to do anything more than press it before each save? I've always assumed it takes out everything that's been deleted but I'm not so sure any more.

Thanks