[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51217] @audioplayer/play and playblocking beh
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #51217] @audioplayer/play and playblocking behave differently from document |
Date: |
Sat, 10 Jun 2017 07:16:14 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
URL:
<http://savannah.gnu.org/bugs/?51217>
Summary: @audioplayer/play and playblocking behave
differently from document
Project: GNU Octave
Submitted by: None
Submitted on: Sat 10 Jun 2017 11:16:12 AM UTC
Category: Documentation
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Documentation
Status: None
Assigned to: None
Originator Name:
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.1
Operating System: GNU/Linux
_______________________________________________________
Details:
The document of these two methods says that the unit of parameter START or
LIMITS is "seconds":
Given optional argument start, begin playing at START seconds in
the recording. Given a two-element vector LIMITS, begin and end
playing at the number of seconds specified by the elements of the
vector.
But the behavior shows that the unit of them is "sample numbers".
For example, If FS=44100, in order to begin playing at 3 seconds, I have to
use play(player,3*44100), not play(player,3).
Which is correct? the document or the behavior?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51217>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51217] @audioplayer/play and playblocking behave differently from document,
anonymous <=