Recording timing with AMS 5+

I encountered an issue with AMS that looks like a bug to me.

Previously I had been using FMS 4 with no problem.

Here is what happens---

1. I connect a publisher to the server. But don't start publishing data.
2. I start a recording on the server.
3. Five seconds later I start publishing.

I then use /opt/adobe/ams/tools/flvcheck -v to look at the FLV. I see a tag:

stream-absolute ==> 5

This is correct. Since the data didn't start for 5 seconds after I clicked record.

I am using <AssumeAbsoluteTime>false</AssumeAbsoluteTime> in this application.

This works fine on AMS 4 and AMS 5.

---

Here is what worked on AMS 4 but now doesn't work on 5:

1. I connect a publisher to the server. I start publishing.
2. I stop publishing.
3. I start recording on the server.
4. Five seconds later I start publishing again.

I then use /opt/adobe/ams/tools/flvcheck -v to look at the FLV. I see a tag:

stream-absolute ==> 0.001
or
stream-absolute ==> 0

This isn't correct. Because the published data started 5 seconds after the recording.

I saw some notes in release notes about AdjustForRecordingRollover

I tried setting that to true and false but it didn't look like it was making any difference.

I also saw a reference to AdjustForZeroTimeStampMessages

But I couldn't find any documentation about that and what possible values could be set.

Do you know of any work-arounds for this? Or have any more info on how to use AdjustForRecordingRollover and/or AdjustForZeroTimeStampMessages?