paulo
Thanks Brando for sticking with me.
 
Same hardware and settings (WDM not ASIO FWIW). The test scenario was a new Plat project with only one synth and no other plug-ins at all, so it isn't fx bin related. Msorrels duplicated the test (post #5) and had the same result, so it's not just me. As I said, I did exactly the same test today in X3 and it doesn't happen.

Not exactly - unless I am missing something. Look at where the clip actually is in MSorrel's frozen clip example - 8.01.
I know the inspector says 7.04 as it did for me as well, but the actual clip is still at 8.01

paulo

...wicked
Well that's what, one tick of time? I'd try zooming in and see if there's any audio there. The clip might have a 1-tick lead in before signal actually occurs.

As far as I can tell from zooming in there is no lead in.

This seems to vary with synth...

Brando

paulo
Thanks Brando for sticking with me.
 
Same hardware and settings (WDM not ASIO FWIW). The test scenario was a new Plat project with only one synth and no other plug-ins at all, so it isn't fx bin related. Msorrels duplicated the test (post #5) and had the same result, so it's not just me. As I said, I did exactly the same test today in X3 and it doesn't happen.

Not exactly - unless I am missing something. Look at where the clip actually is in MSorrel's frozen clip example - 8.01.
I know the inspector says 7.04 as it did for me as well, but the actual clip is still at 8.01

I don't think you can really tell from that pic he posted. Mine looks like it's ok and the inspector is wrong until I really zoom in very close and then you can see that actually the inspector is reporting correctly and the clip does in fact start slightly before the mark

The clip does start before the mark.  I've stripped the project down to just the track itself.  I'd think any version of SONAR should be able to read it (since TTS-1 comes with SONAR).  Load it up, hit the freeze button on the track and select the audio and look at it in the inspector.
 
https://drive.google.com/open?id=0B6PJ_vzx_2PaMEY3bzlvbHhORGc
 

I'm not actually sure it's "wrong" audiowise though. 
 
I don't think it should have anything to do with your audio interface/settings though, since it doesn't render to the sound card. 
 
It does have something to do with the synth, since each synth tells SONAR what its latency is.  Perhaps freeze uses that to decide where to start the audio on the timeline incorrectly? 
 
As I said I think the results bring up a good question, since it's not what I think it should be.  But I'm not 100% sure it's a bug/failure though.  Perhaps someone from Cakewalk could shed some light on it.
 

paulo

Brando

paulo
Thanks Brando for sticking with me.
 
Same hardware and settings (WDM not ASIO FWIW). The test scenario was a new Plat project with only one synth and no other plug-ins at all, so it isn't fx bin related. Msorrels duplicated the test (post #5) and had the same result, so it's not just me. As I said, I did exactly the same test today in X3 and it doesn't happen.

Not exactly - unless I am missing something. Look at where the clip actually is in MSorrel's frozen clip example - 8.01.
I know the inspector says 7.04 as it did for me as well, but the actual clip is still at 8.01

I don't think you can really tell from that pic he posted. Mine looks like it's ok and the inspector is wrong until I really zoom in very close and then you can see that actually the inspector is reporting correctly and the clip does in fact start slightly before the mark

Hi Paulo - Unfortunately I am not at my DAW. Will take a closer look when I get to it and can take a closer look.

This happens to me sometimes.  If I unfreeze and refreeze, it's usually OK.
 
For me, the clip is always late and not early.
 
Just for the record, I often freeze and instrument, drag the audio to a new track, and then delete the virtual instrument to save resources.  I would not do this with a critical, foundational instrument, but if I have a percussion sound, or short instrument line, etc., I don't mind deleting the instrument since it would always be easy to redo it if I needed to.

paulo

Brando

paulo
Thanks Brando for sticking with me.
 
Same hardware and settings (WDM not ASIO FWIW). The test scenario was a new Plat project with only one synth and no other plug-ins at all, so it isn't fx bin related. Msorrels duplicated the test (post #5) and had the same result, so it's not just me. As I said, I did exactly the same test today in X3 and it doesn't happen.

Not exactly - unless I am missing something. Look at where the clip actually is in MSorrel's frozen clip example - 8.01.
I know the inspector says 7.04 as it did for me as well, but the actual clip is still at 8.01

I don't think you can really tell from that pic he posted. Mine looks like it's ok and the inspector is wrong until I really zoom in very close and then you can see that actually the inspector is reporting correctly and the clip does in fact start slightly before the mark

That's not the behaviour I get here. (Again using Synth1 rather than TTS-1 which is crashing here). I just did a repeat (sorry for the delay in posting back) and I can zoom in farther than I ever normally would. The MIDI note that I placed at 8.01 is exactly at 8.01 when frozen, and then again when unfrozen again.
 

Using Rapture Session and the A Room Piano, the Inspector shows the 7:04:959 and when you zoom in you can see the waveform starts before the 8:01:000 (where the play head is in this screen shot).
 

It does it with Synth1 for me as well (I had to download and install it, deleted it years ago).  With Synth1 the clip starts at 7:04:959 and if you zoom in enough you can see it really does start there.