Home Page › Forums › Cymatic Audio Forum › uTrack-X32 › Forgot to stop recording before powering down the X32
- This topic has 12 replies, 3 voices, and was last updated 5 years, 9 months ago by
Phil Boorman.
- AuthorPosts
- 28th May 2017 at 12:08 #28417
Phil Boorman
ParticipantI used the uTrack-X32 last night to record my son’s EP launch gig, which was amazing, but like a fool, I forgot to stop the recording on the device before powering down the desk.
The Take folder contains all of the individual WAV 1.99Gb files that make up the recording, but does not contain the .SET playlist file that informs uTool 2 of the recording resolution etc.
Is there any way that I can recover these recordings?
It looks like I could perhaps copy a SET file from another recording and edit the settings in notepad. I shall try this, and will report further.
I would be very grateful for your help.28th May 2017 at 15:26 #28418Richard Yeoman-Clark
ParticipantYou should be able to just copy the .wav files across to a PC and load them straight into a suitable DAW. There you should be able to join them all together, edit them and/or split the multichannel files into individual audio files.
29th May 2017 at 08:51 #28422Laszlo
KeymasterHi
If you are using uTool 2.0.055 this version should detect the song properly even if the settings file is missing.
29th May 2017 at 15:32 #28426ParticipantThank you for your comments.
I am using v2.0.055, but it is reporting that each of the 21 .WAV files are not correctly formatted audio files. (see screenshot).
I copied the .SET file from TAKE0004, and editted the details to list 19 of the 21 files, as I could be fairly confident of getting the numbers right for these, as each of the first 19 files were exactly the same size, whereas the last two were of different sizes, and it is not easy to establish the exact number of samples in each.
UTOOL2 did now allow me to select the take for import, but it is not picking up on the sample rate and resolution etc., and also shows the length as -14.8, which is naturally incorrect.
Any further suggestions would be very helpful.Attachments:29th May 2017 at 15:41 #28428ParticipantI have just tried to copy the TAKE0005 folder to another location, and windows throws up an error, saying that the file or directory is corrupted and unreadable, (see screenshot).
Attachments:29th May 2017 at 16:06 #28429ParticipantI have tried to open the files in VLC Player, but it reports “Bad Fie Descriptor”.
Audacity does offer the ability to import raw data, but only has the capacity for 16 tracks, not 32, plus I would need to know certain details, such as the Encoding used, the Byte order, and the start offset.
Is anyone aware of some software, or even a professional service that could repair these files?29th May 2017 at 16:17 #28430KeymasterInside of the TAKE0005 folder you can see several wav files like Take0005(0001).wav; Take0005(0002).wav; Take0005(0003).wav
Each of them contains 32 channel wav files and it’s around 10minutes data.
I suggest you to copy each single file to your local drive using standard file explorer.
Open the files in Cubase, Audacity, Reaper etc to merge them together. I assume you’ll not able to read the last one or two files but at least you’ll have the rest of the recording30th May 2017 at 05:07 #28432ParticipantI have spent most of the day trying to fix this.
TAKE0005 was made up of 21 individual WAV files, but only 9 out of these 21 files were actually valid, the rest were corrupt.
When trying to import TAKE0005 into uTool2, the corrupt files were preventing the process from completing.
I then created individual take folders for each of the 21 files, and tried to import them into uTool2 one at a time, which worked for the 9 good files.
I have tried several audio utilities to try and open and edit the header information for the corrupt files, but to no avail.
I am beginning to think that the problem was nothing to do with me forgetting to stop the recording, as the corrupt files were not logically arranged. The good files were 5-02, 5-07, 5-09, 5-10, 5-11, 5-16, 5-17 and 5-19.
Other than the first and the last two files, all of the corrupt files are the same length as the good files, so I am hopeful that the data would still be available if only the header information could be corrected.
Can I send these files to you for further investigation, or is there a tool that you could recommend?
30th May 2017 at 05:24 #28433ParticipantI have just realised that the system must have crashed prematurely, as there are not enough individual 8.29 seconds chunks to make up the duration of the gig.
even if all of the 21 WAV files were the correct length, this gives a total of 174 minutes, (almost three hours), whereas the gig lasted for four hours, and I didn’t power down the X32 for some time after the end of the performance.
Is this a behaviour that has already been identified?
30th May 2017 at 11:38 #28434KeymasterHi,
I sent you a Drobox invitation to shared folder. Please upload the content there. (Preferably zipped).
30th May 2017 at 13:58 #28435ParticipantHi Lazlo,
Dropbox was not happy with the corrupt file, so I have had to email one of the corrupt files to you via wetransfer.com
Many thanks
30th May 2017 at 16:04 #28436KeymasterThat is a SSD or HDD?
What is the firmware version on your uTrack-X32
30th May 2017 at 16:19 #28437ParticipantIt is an HDD.
The X32 is still buried in the van, so I wont be able to confirm the firmware version for a while.
It was straight out of the box and into the mixer, and I think I did a firmware upgrade from my Android tablet, but can’t be 100% sure. - AuthorPosts
- You must be logged in to reply to this topic.
