Best way to load only what needs to be for the header information only.

[joshuapaulanderson]

The problem

I am wondering the best way to only load what needs to be for performance.
For example we dont want to load a 100 MB file just to modify the header info.
Does ATLDOTNET already do this? If so what is the best way? By using a stream?

Is there a way though code to see where the header info begins and ends?

Environment

• ATL version (or git revision) that exhibits the issue:
• Last ATL version that did not exhibit the issue (if applicable):
• OS/version used to run ATL

Details

If necessary, describe the problem you have been experiencing in more detail.

Don't forget to include ATL.Logging.Log and/or console output

Code To Reproduce Issue [ Good To Have ]

Please remember that with sample code it's easier to reproduce the bug and it's much faster to fix it.

[Zeugma440]

Hello and thanks for your feedback.

I have the feeling that you're getting a little too technical too soon. Could you please explain what is the problem you're trying to solve?

[joshuapaulanderson]

Thank you for your response. We have a web application where user will be uploading file which includes MP3’s. We are wanting to do this as efficiently as possible by only loading what is necessary for reading the tags. I do see that information can sometimes be located not in the beginning of the file. We just want to send up until the information can be read rather than loading the entire file if possible. Does this help make it clearer? I appreciate your response. From: Zeugma440 ***@***.***> Sent: Tuesday, December 10, 2024 8:42 AM To: Zeugma440/atldotnet ***@***.***> Cc: joshuapaulanderson ***@***.***>; Author ***@***.***> Subject: Re: [Zeugma440/atldotnet] Best way to load only what needs to be for the header information only. (Issue #294) Hello and thanks for your feedback. I have the feeling that you're getting a little too technical too soon. Could you please explain what is the problem you're trying to solve? — Reply to this email directly, view it on GitHub<#294 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6IZADGSGHTKS2CQAX7JDSD2E34TNAVCNFSM6AAAAABTLG5PFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZRHAZDKNZUGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[Zeugma440]

For most audio formats including MP3s, ATL can read metadata from the very first bytes without having to read the entire file.

You can simulate it by asking the library to read an MP3 file you've manually truncated. If the metadata is located at the beginning of the file, ATL will read it as expected. However, if the metadata is located at the end (e.g. APEtag), you'll need the entire file.

If so what is the best way? By using a stream?

There's no "best way" per se; it depends on how your app is designed and how you want to process the data you're acquiring.

As far as I'm concerned, the pseudocode I'd use would be :

BEGIN WHILE LOOP : listen to the data my user is uploading until upload is complete
- Feed the data I have so far to ATL
- If ATL gives back metadata, stop uploading and break out of the loop
END WHILE LOOP

[Zeugma440]

No feedback from the OP for one entire month => Issue closed