Weird Trouble exporting one vocal track on DP24

[sagetunes]

Here's one that's beguiling me bigtime; I cannot export one particular track, a vocal track. Every other track exports. I have cloned this track to another track---still 'export failed". I have altered the track slightly, erasing little sections, etc, still failure. I have to clue what's going on with this. Thoughts?

 

[Phil Tipping]

Before doing anything, make sure you back up the card.
Try doing a 'delete unused' operation on that song. Sometimes the track fragments (the 'zz' files in the Song folder and the sys file which catalogues them all) can get corrupted and cause problems. There can be several causes: out-of-date firmware, incompatible card, operator error, etc.
If this doesn't work, have a look at the zz files using a computer and see if there are any with a zero size. If so, delete them.
There's also a procedure from @Mark Richards in the sticky posts for recovering the sys file in some circumstances.
Good luck.

 

[sagetunes]

Thanks Phil. I did delete unused, and all other tracks on this song do export successfully. Is there a possibility the actual content on the track is prohibiting it from export? I dropped in/punched at least 50 times on this vocal track. I ask because I did clone the track and that coned track failed as well.

 

[-mjk-]

I suggest that you run the track at unity gain and record it to mixdown and then import that file. You could also try a live bounce. Either way as long as it plays back you can record it without any loss.

 

[sagetunes]

Thanks---I did the live bounce, then exported, no problem. I'll never know how it came to this, but hey, who cares, it worked....that's why I love virtual tracks, and this forum is great. Thanks to all!

 

[Phil Tipping]

I did clone the track and that coned track failed as well.

From my understanding, cloning does not actually copy any audio (much like all the other Track Edit functions). I believe it just sets up another pointer to the same audio files (the zz files in the song folder), so if they are corrupted, the clone will also appear corrupted.

 

[sagetunes]

Yes--looks like that is the case. Thanks!

 

[-mjk-]

From my understanding, cloning does not actually copy any audio (much like all the other Track Edit functions). I believe it just sets up another pointer to the same audio files (the zz files in the song folder), so if they are corrupted, the clone will also appear corrupted.

The failure would support that contention, Phil.

 

[-mjk-]

Thanks---I did the live bounce, then exported, no problem. I'll never know how it came to this, but hey, who cares, it worked....that's why I love virtual tracks, and this forum is great. Thanks to all!

During my career, I learned that no one cares how you "engineered" the solution, i.e. you took the machine apart, troubleshooted and repaired it, etc.. They only care that you got it up and running as quickly as possible. That technique you used is just as valid as actually finding the cause and fixing it. I am very glad that worked out.

Now get back in the studio young man, and make some hit records! lol

 

[shredd]

track fragments (the 'zz' files in the Song folder and the sys file which catalogues them all) can get corrupted and cause problems

I'll second that - the "oodles of zz segments" theory...
I also habitually punch in & out of tracks countless times, and/or do a lot of editing...resulting in this absurd number of "zz" segments the DP uses to constitute a single track.
I haven't had the export issues the OP did...BUT I also never get parking tickets!

In the interest of avoiding this problem, I have learned (in addition to devotedly adhering to the invaluable mantra "Back Up Your Work"!!!) to, once I've got a track/V-track more or less in the 'shape' I want it, do bounces (NOT clones) where the dozens-of-zz-segments track are "run off" to a new track, the full recording-lenth, all as one zz file. They seem to be a lot less problematic then. As the smart guyz noted, lots of tracks with oodles of zz segments can trip up the unit's proprietary operating system, trying to 'orgainize it all...and the problem gets worse when you throw in old firmware, bad/inadequate SD cards, etc.