- Status Closed
- Percent Complete
- Task Type Bugs
- Category Recording
- Assigned To No-one
- Operating System Iriver H100 series
- Severity High
- Priority Very Low
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#6061 - Recording 48kHz via Optical
If you record 48kHz with optical, the recording screen shows you 48kHz. But if you listen to the file, it is played in 44.1kHz, pitch is too low and speed is too slow. If you play it on the computer, its still too slow, because of that I think something with the recorded file is wrong.
Funny is, that if you monitor the recording, I think you listen to the right pitch/speed.
This is for Wave and for MP3 recording. I didn’t test other formats. I can supply example files, if needed.
Closed by MikeS
2006-11-07 00:35
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
2006-11-07 00:35
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Guess I was a week late :D
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
It seems the dev who recently implemented the encoding framework assumed frequency is always 44100 :(
Just had a quick look and this won’t be so easy to fix.
This is addressed in the next recording update and will be fixed hopefully Monday or Tuesday Oct. 30th or 31st. :)