Taperssection.com

Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: rigpimp on November 17, 2016, 11:13:35 PM

Title: File size limit and editor capabilities
Post by: rigpimp on November 17, 2016, 11:13:35 PM
More Wavelab fun.

I have a 2+ hour Stringdusters recording I want to edit.  Wavelab is puking on it after pasting the three files together and then saving it as 24/96.  The saved file is repeatedly less than 10m long in Wavelab despite Windows saying that it is 4.4GB.

Does Audacity play nice with super large files?
Title: Re: File size limit and editor capabilities
Post by: down2earthlandscaper on November 18, 2016, 02:54:20 AM
Hmmm. Not sure about your editing software program specifically, but I run into the same "file too large issues" so lately I've just been editing each file individually but I save the settings I applied as a "preset" so I can apply exactly the same settings to each file. Once I've completed I will paste them together at that point and divide the tracks.

My apologies if this is obvious and you already knew...
Title: Re: File size limit and editor capabilities
Post by: beatkilla on November 18, 2016, 07:14:42 AM
Save as Wav64.There is no file size limit.
Title: Re: File size limit and editor capabilities
Post by: bvaz on November 18, 2016, 07:57:38 AM
this issue is even more of a PITA when doing a matrix.
I used to just find a split where I would track it and use 2 different files.  I would just do the same steps in post on both files.
I've since started to record at 24/48.
Title: Re: File size limit and editor capabilities
Post by: Justy Gyee on November 18, 2016, 11:55:33 AM
Save as Wav64.There is no file size limit.
were is this option in wavelab?
i dont see it
Title: Re: File size limit and editor capabilities
Post by: rigpimp on November 18, 2016, 12:13:41 PM
Save as Wav64.There is no file size limit.
were is this option in wavelab?
i dont see it

"Save As" then the pull list of file types.  It didn't work for me but it is because I have some hidden process that is accessing/locking up the .gpk file again.  I still cannot figure out what it is.