I'm using APro w/ my Artcessories phono box... a USB Audio CODEC - compatible thing, used it for years with Audacity with no problem.
Alas-
I've noticed that, with the latest APro 2.0.x I am getting recordings that basically seem to 'go back in time'. The elapsed time counter will increment for a while, then bounce back a few seconds/minutes... the resulting recordings are all chopped up.
A quick look at the console gives me a veritable butt-ton of
6/30/12 1:38:30.967 PM Amadeus Pro[168]: buffer overrun...
messages. I've tweaked the buffer size around in the preferences panel, apparently to no avail. Also I seem to remember giving the app more memory (such weird memories of pre-Mac-OS-X days...) in the preferences also.
Thoughts?
NB- probably not related- but I also get to see plenty of:
6/30/12 2:20:55.870 PM Amadeus Pro[207]: No front doc....
(
"<HSSoundDocument>"
)
in there too.
Amadeus Pro[168]: buffer overrun...
Moderator: Martin Hairer
- flipphillips
- Posts: 9
- Joined: Sat Jun 30, 2012 5:44 pm
<Bump>
I've updated the Retina MBP to the final Mountain Lion. I've messed with buffer settings/memory settings, etc.
I can't actually digitize anything with APro via my USB Audio CODEC supported box because I get:
7/26/12 8:17:02.466 PM Amadeus Pro[1996]: buffer overrun...
and packets get dropped, sound is choppy, etc.
I get thousands of these in my syslog.
Any clues here at all? Some debugging I can turn on to check some things?
I've updated the Retina MBP to the final Mountain Lion. I've messed with buffer settings/memory settings, etc.
I can't actually digitize anything with APro via my USB Audio CODEC supported box because I get:
7/26/12 8:17:02.466 PM Amadeus Pro[1996]: buffer overrun...
and packets get dropped, sound is choppy, etc.
I get thousands of these in my syslog.
Any clues here at all? Some debugging I can turn on to check some things?