Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE (Read 30835 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #100
Except when it doesn't.

And even when it does work, it modifies the audio to meet the limitations of the Red Book standard.
What exact modifications does it perform? Other than padding to finish on CD frame?

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #101
Just the padding, if the bit depth and sample rate is already correct. But I thought you wanted to archive your audio? Any modification is counter to that goal.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #102
Just the padding, if the bit depth and sample rate is already correct. But I thought you wanted to archive your audio? Any modification is counter to that goal.

Achive a digital download with EAC? I wanted to get the end result as with my usual workflow generating files for daily use, I archive bandcamp downloads as the zip it came in on external memory storage units. The only instance I use EAC for archiving is ripping CDs and especially CD-Rs to image+cue in case the CD-R rots and that can happen immidiately. I once got a fresh release from the band, replicated in by a renowned company and it had read errors from the start.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #103
Then... what are you doing with EAC when the bandcamp download is already split into separate tracks? Transcoding? You can do that with a script. And the script will work with tracks ripped from CDs and DVDs and BDs too!

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #104
Then... what are you doing with EAC when the bandcamp download is already split into separate tracks? Transcoding? You can do that with a script. And the script will work with tracks ripped from CDs and DVDs and BDs too!

Processing them as if it was a CD to get the same result and workflow as with physical CDs finished with a log.
DVDae already comes with tools to provide me with desired end product.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #105
Processing them as if it was a CD to get the same result and workflow as with physical CDs finished with a log.
And.. what is the result you want? Writing a script that spits out a log with the audio checksums is easy enough; just about everything else EAC logs is irrelevant to converting files between formats.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #106
Processing them as if it was a CD to get the same result and workflow as with physical CDs finished with a log.
And.. what is the result you want? Writing a script that spits out a log with the audio checksums is easy enough; just about everything else EAC logs is irrelevant to converting files between formats.

The result I want is the same result I would get from ripping a physical CD with EAC including the stuff irrelevant to you.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #107
The result I want is the same result I would get from ripping a physical CD with EAC including the stuff irrelevant to you.
I meant, like, which codec and what kind of tags and stuff. But please, explain to me how each of the items in the EAC log are relevant to you.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #108
The result I want is the same result I would get from ripping a physical CD with EAC including the stuff irrelevant to you.
I meant, like, which codec and what kind of tags and stuff. But please, explain to me how each of the items in the EAC log are relevant to you.

The codec is irrelevant, the tags are updated in the player of my choosing after wards anyway including the subdirectory structure.
They are relevant to me, because I preffer them there to mimic the EAC log for a physical disc.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #109
The codec is irrelevant,
It sounds like the codec is the only part that matters, since you're only using EAC to convert the audio to that codec and generate a log file.

They are relevant to me, because I preffer them there to mimic the EAC log for a physical disc.
Yes, but what in the log do you actually look for when checking to see if everything was done correctly?

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #110
The codec is irrelevant,
It sounds like the codec is the only part that matters, since you're only using EAC to convert the audio to that codec and generate a log file.

They are relevant to me, because I preffer them there to mimic the EAC log for a physical disc.
Yes, but what in the log do you actually look for when checking to see if everything was done correctly?

That is irrelevant to this discussion, the codec can be sbstituted with any codec and any settings.

The presence of informations that are traditionally in the EAC log without errors reported.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #111
Yes, but what in the log do you actually look for when checking to see if everything was done correctly?
The presence of informations that are traditionally in the EAC log without errors reported.

?

That was not an answer. But anyawy, you would get:

* EAC version. Don't know why you need that, you don't use EAC to obtain the data.
* Date. Don't know why you need that, it is going to be wrong.
* Drive. Don't know why you need that, it is going to be wrong.
* Drive settings. Don't know why you need that, they are going to be wrong.
* Output format. Don't know why you need that, you know it already from the filetype.
* TOC. Don't know why you need that, it is going to be wrong.
What else? AccurateRip information that isn't applicable? CRCs that verify that if you read the same file twice it will still be the same file?

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #112
Yes.








MOD Edit: Removed multiple instances of quoted text

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #113
So, what you really "need" is a random EAC log and then a text processing script that takes the .cue and writes into the file
* the TOC table with rounded-off times or maybe even with long enough fractions of a second to be correct
* some bogus track information with arbitrary CRCs (say, 000000)
?

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #114
So, what you really "need" is a random EAC log and then a text processing script that takes the .cue and writes into the file
* the TOC table with rounded-off times or maybe even with long enough fractions of a second to be correct
* some bogus track information with arbitrary CRCs (say, 000000)
?
Ideally I need EAC, or CueTools to process the files in the firta place, or software to perform similar taskthat will output EAC like logs with as many informations similar to EAC as are used in the settings for said program.



Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #117
The point is that since
* it is not going to be correct
* you are not going to use it for anything, at least not for anything that needs it to be correct
then you can just generate a faux log by a text manipulation tool. It is going to include wrong statements that you are not going to use, so why care?
If you even insist on the audio CRCs, you can employ https://github.com/leo-bogert/eac-crc .

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #118
The point is that since
* it is not going to be correct
* you are not going to use it for anything, at least not for anything that needs it to be correct
then you can just generate a faux log by a text manipulation tool. It is going to include wrong statements that you are not going to use, so why care?
If you even insist on the audio CRCs, you can employ https://github.com/leo-bogert/eac-crc .

Why do people collect sealed and graded baseball cards? BEcause the want to. Same here.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #119
Why do people collect sealed and graded baseball cards? BEcause the want to. Same here.
Incorrect comparison. All physical objects have value on their own. Even trash has value, because it can be recycled into something useful. Unlike text file with meaninglesss useless data, which has absolutely no value.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #120
Why do people collect sealed and graded baseball cards? BEcause the want to. Same here.
Incorrect comparison. All physical objects have value on their own. Even trash has value, because it can be recycled into something useful. Unlike text file with meaninglesss useless data, which has absolutely no value.

I do realize that files have no inherent value and yet they do have worth, otherwise people wouldn't be charging money for downloads i the first place, be it stock images on getty, music files on bandcamp, software, or ppv videos.
So while I appreciate your insights, they are less than relevant to my original inquiry, so if you sticked to the topic, or provide a solution I would appreciate it even more.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #121
The point is that since
* it is not going to be correct
* you are not going to use it for anything, at least not for anything that needs it to be correct
then you can just generate a faux log by a text manipulation tool. It is going to include wrong statements that you are not going to use, so why care?
If you even insist on the audio CRCs, you can employ https://github.com/leo-bogert/eac-crc .

Why do people collect sealed and graded baseball cards? BEcause the want to. Same here.

I think it would be more fair to compare this to special baseball cards in a larger-than-usual size, custom printed in one copy at your order.
And the "error", as you prefer to call it, being that you cannot get those without paying to get them customized.

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #122
That is irrelevant to this discussion, the codec can be sbstituted with any codec and any settings.
Now I'm really curious why you insist on keeping your preferred codec and settings a secret. But you're right, the codec itself isn't too important.

The presence of informations that are traditionally in the EAC log without errors reported.
So it's perfectly fine for the information to be wrong as long as it's there? Why bother having that information in the first place, then? If you only care about whether any errors that occurred, it's pretty easy to add error handling to a format conversion script.

 

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #123
So while I appreciate your insights, they are less than relevant to my original inquiry, so if you sticked to the topic, or provide a solution I would appreciate it even more.

But this is just beating around the bush. You got your answer multiple times, you decided you didn't like it so this convo goes on and on. Please, end the topic, stop responding. No software know to us will do what you want it to do for simple reason: the thing you want to do is not done the way you want it be done. Like cutting wood with kitchen knife, you can do it, yeah, but there are better tools for that for more than one reason, and there are reasons why we don't do it with kitchen knives.
TAPE LOADING ERROR

Re: EAC Unhandled exception at ASPI32.4152 -> ASSIGN-RANGE

Reply #124
That is irrelevant to this discussion, the codec can be sbstituted with any codec and any settings.
Now I'm really curious why you insist on keeping your preferred codec and settings a secret. But you're right, the codec itself isn't too important.

The presence of informations that are traditionally in the EAC log without errors reported.
So it's perfectly fine for the information to be wrong as long as it's there? Why bother having that information in the first place, then? If you only care about whether any errors that occurred, it's pretty easy to add error handling to a format conversion script.

The encoder and settings are not relevant to the inqiury, it can be swapped at any time for another encoder.
How will the information be wrong, if those will be the settings used.

So while I appreciate your insights, they are less than relevant to my original inquiry, so if you sticked to the topic, or provide a solution I would appreciate it even more.

But this is just beating around the bush. You got your answer multiple times, you decided you didn't like it so this convo goes on and on. Please, end the topic, stop responding. No software know to us will do what you want it to do for simple reason: the thing you want to do is not done the way you want it be done. Like cutting wood with kitchen knife, you can do it, yeah, but there are better tools for that for more than one reason, and there are reasons why we don't do it with kitchen knives.

Suggesting I don't do something, or use different software does not answer my inquiry, which was specifically "how to get rid of the error and have the specific software I'm using to carry on, without compromising the structure of the cue, or any other part of my workflow". I'm not interested in any toold you deem to be better. CueTools 1.9.1 processed the entire cue to tracks, so this is doable, which means it can be programmed into newer CueTools releases, which means somewhere along the updates the specific setting got capped to not allow more than certain amount, currently reported as ~140 minutes. So if there is no software known to you that can achieve what I need, then you don't know the answer to inquiry, therefore all yout input is offtopic, so please stop responding with sentences completely irrelevant to my inquiry, it's a waste of your time then.