(2021-02-11, 01:43 AM)zoidberg Wrote: When you say render out what does that mean? I've only ever worked with the saved capture obtained when stopping recording (I usually rename it at the same time otherwise you get a date/time named file). Once it's saved I clear the timeline and carry on

This must be where I'm going wrong, never used Reaper before so just followed some YT videos that suggested the 'render' option under File. I get the option to save the track once I press stop on the recording but where do they go? It doesn't give me an option to save to a location and I can't see them in the Reaper folder.

Thanks for the help guys!

(2021-02-11, 12:50 PM)alexpeden2000 Wrote:

(2021-02-11, 01:43 AM)zoidberg Wrote: When you say render out what does that mean? I've only ever worked with the saved capture obtained when stopping recording (I usually rename it at the same time otherwise you get a date/time named file). Once it's saved I clear the timeline and carry on

This must be where I'm going wrong, never used Reaper before so just followed some YT videos that suggested the 'render' option under File. I get the option to save the track once I press stop on the recording but where do they go? It doesn't give me an option to save to a location and I can't see them in the Reaper folder.

Thanks for the help guys!

No, render is correct. Definitely remembering to save to 16- rather than 24-bit and forcing WAV rather than WAVEX header etc.?

(2021-02-11, 02:25 PM)pipefan413 Wrote: No, render is correct. Definitely remembering to save to 16- rather than 24-bit and forcing WAV rather than WAVEX header etc.?

Yeah did both of those things, are there any other settings that could trip it up?

I've tried both consumer & proressional modes on the ESI and got the same result.

(2021-02-11, 02:55 PM)alexpeden2000 Wrote:

(2021-02-11, 02:25 PM)pipefan413 Wrote: No, render is correct. Definitely remembering to save to 16- rather than 24-bit and forcing WAV rather than WAVEX header etc.?

Yeah did both of those things, are there any other settings that could trip it up?

I've tried both consumer & proressional modes on the ESI and got the same result.

I can't think just now. Hmm. Both you and @captainsolo seem to be having similar/same problem.

As I mentioned to him before, I'm happy to try looking at one of your captures to see what happens when I decode it through a couple of different tools just in case that's all it is, but it probably isn't

I had forgotten just how cursed this process is to get set up. Once I got a verified bit-perfect capture I never changed any settings ever again save for between 44.1/48 for PCM/AC-3.

Can you send me the raw capture so I can take a look?

(2021-02-11, 03:55 PM)zoidberg Wrote: I had forgotten just how cursed this process is to get set up. Once I got a verified bit-perfect capture I never changed any settings ever again save for between 44.1/48 for PCM/AC-3.

Can you send me the raw capture so I can take a look?

Hahaha exactly. Frustrating until it's working and then once it's working it's difficult to think what might be causing issues. But I agree, it would be good to send one or both of us some captures to check it isn't just the decoding part that's going wrong (it might be that the caps are bit perfect but there's some issue with DTS Parser or something, but probably unlikely).

At least we know that it probably isn't being resampled since both are reporting a solid data block, that's definitely a good start. But it could still be chopping a chunk off the start somehow which is preventing decode.

Ah you’ve got me thinking, when I’m recording in Reaper there’s a few seconds of silence at the start and end of the capture, would that be an issue? Could trimming the start and end of the capture make a difference?

I’ll send you both a capture later on anyway.

(2021-02-11, 04:15 PM)alexpeden2000 Wrote: Ah you’ve got me thinking, when I’m recording in Reaper there’s a few seconds of silence at the start and end of the capture, would that be an issue? Could trimming the start and end of the capture make a difference?

I’ll send you both a capture later on anyway.

Theoretically shouldn't matter, no. But aye I'll look at it when I can!

The weak link here is definitely DTS Parser. It's a black box and inconsistent at best, even when I was testing this package out I had a lot of trouble. I'm thinking we can replace it with a custom app that will generate you a reference WAV (for instance, a 10 second clip of random bits, ie. noise) to burn to CD, then record it and use the app to match against the reference.

I now have a working app to try out. Unfortunately, my LD player has been busted so I can't fully check it myself, but I've tried adding silence and messing with the generated file via Sound Forge and all combinations seem good.

Edit: See first post for download and information.