Dll FULL_TOC_ENTRY_RAW query

osbick · **Joined:** Thu Dec 07, 2006 3:55 pm **Posts:** 3

In using the StarBurn dll to get ID and TOC from a CD, I was working from someone else's code and they had used the TOC_INFORMATION structure's FULL_TOC_ENTRY_RAW PMIN, PSEC, PFRAME values. I followed suit and couldn't get it to work as I always calculated really strange values.
Eventually I swapped and started using the TOC_ENTRY startingMSF array instead (using array members 0=min, 1=sec, 2=frames). This worked much better. Comparing the two, it seemed to me that the TOC_ENTRY MSF didn't map to the FULL_TOC_ENTRY_RAW's PMIN, PSEC, PFRAME as I would have expected. Using the TOC_ENTRY seems to be fine and give the results I need, but I just wondered had anyone else come across this or could they explain to me the correspondence between the two structures?

Thanks.

anton (staff) · **Posted:** Fri Dec 15, 2006 8:42 pm

Can you provide a sample run log for what you say?

osbick wrote:

In using the StarBurn dll to get ID and TOC from a CD, I was working from someone else's code and they had used the TOC_INFORMATION structure's FULL_TOC_ENTRY_RAW PMIN, PSEC, PFRAME values. I followed suit and couldn't get it to work as I always calculated really strange values.
Eventually I swapped and started using the TOC_ENTRY startingMSF array instead (using array members 0=min, 1=sec, 2=frames). This worked much better. Comparing the two, it seemed to me that the TOC_ENTRY MSF didn't map to the FULL_TOC_ENTRY_RAW's PMIN, PSEC, PFRAME as I would have expected. Using the TOC_ENTRY seems to be fine and give the results I need, but I just wondered had anyone else come across this or could they explain to me the correspondence between the two structures?

Thanks.

#1 Burning Software

Dll FULL_TOC_ENTRY_RAW query

Who is online