Bizarre tracking issue

[cleamon]

Anyone seen this? (DP 8.06) It's only happened to me this one time. The only way to "fix" it was to create a new project and "load" this sequence into it.

The basic issue is that when I was recording (rendering a MIDI track to audio), the displayed soundbite out paced the timeline. The longer I recorded, the farther ahead it got. When I stopped recording, the (displayed) soundbite was significantly shorter than the actual data. If I played it, it played through to the end of the recording (but beyond the soundbite edge) as expected. If I tried to edge-edit the soundbite so I could see it, I got the circle-slash cursor. If I switched to the trim tool, it acted even more bizarre.
I've written a tech-link on it FWIW.

[MIDI Life Crisis]

Never saw that but I'd toggle punch-guard and try again. It's the first thing that comes to mind. No, it's not supposed to work that way and probably isn't the cause, but it does effect how DP 8 treats recording time. Worth a shot.

[Shooshie]

Haven't seen that one. Sorry.

Would you let us know what MOTU says?

Shooshie

[Shooshie]

Out of curiosity, could you tell us what the following settings are for that soundbite?

1) sample rate
2) bit resolution
3) file type (WAV, AIFF, etc.)

If you look in the soundbites window, can you see if there are multiple sample rates in the list, or multiples of any of the other settings? Usually, they should all be the same for one project, though it's possible to have others. DP usually handles all that without error.

Shoosh

[MIDI Life Crisis]

Knowing your machine and hardware, RAM, etc., would be... helpful.

[cleamon]

Out of curiosity, could you tell us what the following settings are for that soundbite?

1) sample rate
2) bit resolution
3) file type (WAV, AIFF, etc.)

If you look in the soundbites window, can you see if there are multiple sample rates in the list, or multiples of any of the other settings? Usually, they should all be the same for one project, though it's possible to have others. DP usually handles all that without error.

Shoosh

I wasn't really wanting to troubleshoot this, as I've only seen it once and have moved on. I was curious though if anyone else had seen it.
But since you asked:
The project has about a dozen MIDI tracks (output to external devices), no audio tracks. I was in the process of rendering the MIDI tracks, one by one, to audio. This was the first one. The project is using internal clock, 44.1kHz, 24 bits, WAV.
I blame it on a corrupt project file. I created a new project with the same defaults, Loaded that sequence into it and record worked fine on all tracks.

Thanks.

[Shooshie]

Yeah, you're probably right; just a corrupted file.
Cosmic waves.
Quantum zombies

Shooshie