Dbug wrote: ↑
Wed Jan 29, 2020 5:37 pm
Well yes, there was parity errors, and no, the process is not complicated, it's just very slow, requiring you to record, check parity problem, adjust, record, check, adjust record checkkkkkkk kdkdddsfgdsjgølkjsdafgkldsjfglødsajfgløsdfjglsdfgdfg... I've some patience for interesting stuff, but that's just boring
Acutally when there are no errors (and not 13543 parts), it can be rather fast once you've practiced a few times. You can even group wavclean + wav2tap into a single BAT file if you don't want to play with parameters.
But I 100% agree that, when problems start to occur, it can quickly be hell (that's actually partly why I wrote Load Vader).
That being said with multiple tries, I enjoy having each recording (WAV) with its results archived.
I think "live" would be cool to adjust things to get a correct sound, but to solve lighly-damaged tape problems, WAVs will be easier in an investigation / correction / test process.
I could try Load Vader, but there's a certain difference between loading on an oric and recording from a sound card, so no matter what, the input volume would be different, or things would have to be adjusted, no?
Well to be honest I haven't loaded a tape directly on a real Oric for maybe 10 or 15 years now
I'm always recording them into WAV files now, to make TAPs of them, or to toy with the WAV, trying to make it better for the Oric to load.
Now there's indeed a difference between loading on an Oric (based on tape input + ROM real-time code) and using wavclean/wav2tap (based on counting WAV samples). Oric seems sometimes a bit more "cool", but you can't be sure the loading was reliable (hence Load Vader). And sometimes, wavclean/wav2tap will be more cool. Black magic indeed.
I forgot that Progress v1.3, the tape loading progress bar, also displays parity errors live. But Atmos only.