Minirok 2.0 - Minimalist Audio Player for KDE4 Introduction Written in Python, Minirok is a minimalist audio player which ships with a simple and intuitive interface, which kind of resembles the Amarok 1.4 interface, except all the major features were removed. WRITEMONKEY 2.7 FOR WINDOWS Writemonkey is a Windows zenware. writing application with an extremely stripped down user interface, leaving you alone with your thoughts and your words. It is light, fast and free. With an array of innovative tools under the hood and full Markdown. support, it helps you write better. Screenshot 1, Screenshot 2, Screenshot 3, Screenshot 4, Logo/icon.

1. Byword 2 0 3 – Minimalist Typing Interface Free
2. Byword 2 0 3 – Minimalist Typing Interface Tutorial

• INTERFACE
  • Specifying arguments
• DIAGNOSTICS

Getopt::Euclid - Executable Uniform Command-Line Interface Descriptions

Byword is your minimalist typing interface. Byword starts with a clean full-screen interface that lets you start typing right away-no templates to choose, no type settings to tune, no spacing to adjust. Everything is already prepared for you. Features: Full-screen interface; Focus mode to highlight only the few lines nearby the cursor-you will. Even though Markdown itself is not hard, Byword offers assistance to make it even easier with very little configuration required. The UI is minimalistic and un-intrusive, the syntax auto-completion is excellent, and there are multiple small but helpful features that make writing Markdown with Byword a breeze. The best writing apps know what to leave behind when switching from a 21-inch-screen to a 9.7-inch one, and they do it without trampling over any of our individual writing styles and preferences.

This document describes Getopt::Euclid version 0.4.5

Getopt::Euclid uses your program's own POD documentation to create a powerful command-line argument parser. This ensures that your program's documented interface and its actual interface always agree.

The created command-line argument parser includes many features such as argument type checking, required arguments, exclusive arguments, optional arguments with default values, automatic usage message, ...

To use the module, simply write the following at the top of your program:

This will cause Getopt::Euclid to be require'd and its import method will be called. It is important that the import method be allowed to run, so do not invoke Getopt::Euclid in the following manner:

When the module is loaded within a regular Perl program, it will:

1. locate any POD in the same *.pl file or its associated *.pod file.

2. extract information from that POD, most especially from the =head1 REQUIRED ARGUMENTS and =head1 OPTIONS sections,

3. build a parser that parses the arguments and options the POD specifies,

4. remove the command-line arguments from @ARGV and parse them, and

5. put the results in the global %ARGV variable (or into specifically named optional variables, if you request that -- see 'Exporting option variables').

As a special case, if the module is loaded within some other module (i.e. from within a .pm file), it still locates and extracts POD information, but instead of parsing @ARGV immediately, it caches that information and installs an import() subroutine in the caller module. This new import() acts just like Getopt::Euclid's own import, except that it adds the POD from the caller module to the POD of the callee.

All of which just means you can put some or all of your CLI specification in a module, rather than in the application's source file. See 'Module interface' for more details.

Program interface

You write:

and your command-line is parsed automagically.

Module interface

You write:

and your module will then act just like Getopt::Euclid (i.e. you can use your module instead of Getopt::Euclid>, except that your module's POD will also be prepended to the POD of any module that loads yours. In other words, you can use Getopt::Euclid in a module to create a standard set of CLI arguments, which can then be added to any application simply by loading your module.

To accomplish this trick Getopt::Euclid installs an import() subroutine in your module. If your module already has an import() subroutine defined, terrible things happen. So do not do that.

You may also short-circuit the import method within your calling program to have the POD from several modules included for argument parsing.

Alternatively, to parse arguments from a source different from @ARGV, use the process_args() subroutine.

If you want to use the :minimal or :vars mode in this type of scenario, you can pass extra options to process_args():

This is particularly when you plan on processing POD manually.

Similarly, to parse argument specifications from a source different than the current script (and its dependencies), use the process_pods() subroutine.

By default, this method will look for .pod files associated with the given .pl and .pm files and use these .pod files preferentially when available. Set -strict to 1 to only use the given files.

POD interface

This is where all the action is. POD markup can be placed in a .pod file that has the same prefix as the corresponding Perl file. Alternatively, POD can be inserted anywhere in the Perl code, but is typically added either after an __END__ statement (like in the SYNOPSIS), or interspersed in the code:

When Getopt::Euclid is loaded in a non-.pm file, it searches that file for the following POD documentation:

Getopt::Euclid ignores the name specified here. In fact, if you use the standard --help, --usage, --man, --podfile, or --version arguments (see 'Standard arguments'), the module replaces the name specified in this POD section with the actual name by which the program was invoked (i.e. with $0).

Getopt::Euclid ignores the usage line specified here. If you use the standard --help, --usage, --man or --podfile arguments, the module replaces the usage line specified in this POD section with a usage line that reflects the actual interface that the module has constructed.

Getopt::Euclid extracts the current version number from this POD section. To do that it simply takes the first substring that matches <digit>.<digit> or <digit>_<digit>. It also accepts one or more additional trailing .<digit> or _<digit>, allowing for multi-level and 'alpha' version numbers such as:

or:

You may also specify the version number in your code. However, in order for Getopt::Euclid to properly read it, it must be in a BEGIN block:

Euclid stores the version as $Getopt::Euclid::SCRIPT_VERSION.

Getopt::Euclid uses the specifications in this POD section to build a parser for command-line arguments. That parser requires that every one of the specified arguments is present in any command-line invocation. See 'Specifying arguments' for details of the specification syntax.

The actual headings that Getopt::Euclid can recognize here are:

Caveat: Do not put additional subheadings (=headX) inside the REQUIRED ARGUMENTS section.

Getopt::Euclid uses the specifications in this POD section to build a parser for command-line arguments. That parser does not require that any of the specified arguments is actually present in a command-line invocation. Again, see 'Specifying arguments' for details of the specification syntax.

Typically a program will specify both REQUIRED ARGUMENTS and OPTIONS, but there is no requirement that it supply both, or either.

The actual headings that Getopt::Euclid recognizes here are:

Caveat: Do not put additional subheadings (=headX) inside the REQUIRED ARGUMENTS section.

Getopt::Euclid prints this section whenever the standard --version option is specified on the command-line.

The actual heading that Getopt::Euclid recognizes here is any heading containing any of the words 'COPYRIGHT', 'LICENCE', or 'LICENSE'.

Specifying arguments

Each required or optional argument is specified in the POD in the following format:

Argument structure

• Each argument is specified as an =item.

• Any part(s) of the specification that appear in square brackets are treated as optional.

• Any parts that appear in angle brackets are placeholders for actual values that must be specified on the command-line.

• Any placeholder that is immediately followed by ... may be repeated as many times as desired.

• Any whitespace in the structure specifies that any amount of whitespace (including none) is allowed at the same position on the command-line.

• A vertical bar indicates the start of an alternative variant of the argument.

For example, the argument specification:

indicates that any of the following may appear on the command-line:

as well as any other combination of whitespacing.

Any of the above variations would cause all three of:

to be set to the string 'data.txt'.

You could allow the optional = to also be an optional colon by specifying:

Optional components may also be nested, so you could write:

which would allow -i, -in, and -input as synonyms for this argument and would set all three of $ARGV{'-i'}, $ARGV{'-in'}, and $ARGV{'-input'} to the supplied file name.

The point of setting every possible variant within %ARGV is that this allows you to use a single key (say $ARGV{'-input'}, regardless of how the argument is actually specified on the command-line.

Repeatable arguments

Normally Getopt::Euclid only accepts each specified argument once, the first time it appears in @ARGV. However, you can specify that an argument may appear more than once, using the repeatable option:

When an argument is marked repeatable the corresponding entry of %ARGV will not contain a single value, but rather an array reference. If the argument also has 'Multiple placeholders', then the corresponding entry in %ARGV will be an array reference with each array entry being a hash reference.

Boolean arguments

If an argument has no placeholders it is treated as a boolean switch and its entry in %ARGV will be true if the argument appeared in @ARGV.

For a boolean argument, you can also specify variations that are false, if they appear. For example, a common idiom is:

These two arguments are effectively the same argument, just with opposite boolean values. However, as specified above, only one of $ARGV{'--print'} and $ARGV{'--noprint'} will be set.

As an alternative you can specify a single argument that accepts either value and sets both appropriately:

With this specification, if --print appears in @ARGV, then $ARGV{'--print'} will be true and $ARGV{'--noprint'} will be false. On the other hand, if --noprint appears in @ARGV, then $ARGV{'--print'} will be false and $ARGV{'--noprint'} will be true.

The specified false values can follow any convention you wish:

or:

et cetera.

Multiple placeholders

An argument can have two or more placeholders:

The corresponding command line argument would then have to provide two values:

Byword 2 0 3 – Minimalist Typing Interface Free

Multiple placeholders can optionally be separated by literal characters (which must then appear on the command-line). For example:

would then require a command-line of the form:

If an argument has two or more placeholders, the corresponding entry in %ARGV becomes a hash reference, with each of the placeholder names as one key. That is, the above command-line would set both $ARGV{'-size'}{'h'} and $ARGV{'-size'}{'w'}.

Optional placeholders

Placeholders can be specified as optional as well:

This specification then allows either:

or:

on the command-line. If the second placeholder value is not provided, the corresponding $ARGV{'-size'}{'w'} entry is set to undef. See also 'Placeholder defaults'.

Unflagged placeholders

If an argument consists of a single placeholder with no 'flag' marking it:

then the corresponding entry in %ARG will have a key the same as the placeholder (including the surrounding angle brackets):

The same is true for any more-complicated arguments that begin with a placeholder:

The only difference in the more-complex cases is that, if the argument has any additional placeholders, the entire entry in %ARGV becomes a hash:

Note that, as in earlier multi-placeholder examples, the individual second- level placeholder keys do not retain their angle-brackets.

Repeated placeholders

Any placeholder that is immediately followed by ..., like so:

will match at least once, but as many times as possible before encountering the next argument on the command-line. This allows to specify multiple values for an argument, for example:

An unconstrained repeated unflagged placeholder (see 'Placeholder constraints' and 'Unflagged placeholders') will consume the rest of the command-line, and so should be specified last in the POD

and on the command-line:

If a placeholder is repeated, the corresponding entry in %ARGV will then be an array reference, with each individual placeholder match in a separate element. For example:

Placeholder constraints

You can specify that the value provided for a particular placeholder must satisfy a particular set of restrictions by using a =for Euclid block. For example:

specifies that both the <h> and <w> must be given integers. You can also specify an operator expression after the type name:

specifies that <h> has to be given an integer that is greater than zero, and that <w> has to be given a number (not necessarily an integer) that is no more than 100.

These type constraints have two alternative syntaxes:

as shown above, and the more general:

Using the second syntax, you could write the previous constraints as:

In other words, the first syntax is just sugar for the most common case of the second syntax. The expression can be as complex as you wish and can refer to the placeholder as many times as necessary:

Note that the expressions are evaluated in the package main namespace, so it is important to qualify any subroutines that are not in that namespace. Furthermore, any subroutines used must be defined (or loaded from a module) before the use Getopt::Euclid statement.

You can also use constraints that involve variables. You must use the :defer mode and the variables must be globally accessible:

Standard placeholder types

Getopt::Euclid recognizes the following standard placeholder types:

Since regular expressions are supported, you can easily match many more type of strings for placeholders by using the regular expressions available in Regexp::Common. If you do that, you may want to also use custom placeholder error messages (see 'Placeholder type errors') since the messages would otherwise not be very informative to users.

Placeholder type errors

If a command-line argument's placeholder value does not satisify the specified type, an error message is automatically generated. However, you can provide your own message instead, using the .type.error specifier:

Whenever an explicit error message is provided, any occurrence within the message of the placeholder's unbracketed name is replaced by the placeholder's value (just as in the type test itself).

Placeholder defaults

You can also specify a default value for any placeholders that are not given values on the command-line (either because their argument is not provided at all, or because the placeholder is optional within the argument). For example:

This ensures that if no <w> value is supplied:

then $ARGV{'-size'}{'w'} is set to 80. Likewise, of the -size argument is omitted entirely, both $ARGV{'-size'}{'h'} and $ARGV{'-size'}{'w'} are set to their respective default values

However, Getopt::Euclid also supports a second type of default, optional defaults, that apply only to flagged, optional placeholders.

For example:

This ensures that if the option --debug is not specified, then $ARGV{'--debug'} is set to 0, the regular default. But if no <log_level> value is supplied:

then $ARGV{'--debug'} is set to 1, the optional default.

The default value can be any valid Perl compile-time expression:

You can refer to an argument default or optional default value in its POD entry as shown below:

Just like for 'Placeholder constraints', you can also use variables to define default values. You must use the :defer mode and the variables must be globally accessible:

Exclusive placeholders

Some arguments can be mutually exclusive. In this case, it is possible to specify that a placeholder excludes a list of other placeholders, for example:

Specifying both placeholders at the same time on the command-line will generate an error. Note that the error message can be customized, as illustrated above.

When using exclusive arguments that have default values, the default value of the placeholder with the .excludes statement has precedence over any other placeholders.

Argument cuddling

Getopt::Euclid allows any 'flag' argument to be 'cuddled'. A flag argument consists of a single non- alphanumeric character, followed by a single alpha-numeric character:

Cuddling means that two or more such arguments can be concatenated after a single common non-alphanumeric. For example:

Note, however, that only flags with the same leading non-alphanumeric can be cuddled together. Getopt::Euclid would not allow:

This is because cuddling is recognized by progressively removing the second character of the cuddle. In other words:

becomes:

which becomes:

which will fail, unless a z argument has also been specified.

On the other hand, if the argument:

had been specified, the module would accept:

as a cuddled version of:

Exporting option variables

By default, the module only stores arguments into the global %ARGV hash. You can request that options are exported as variables into the calling package using the special ':vars' specifier:

That is, if your program accepts the following arguments:

Then these variables will be exported

For options that have multiple variants, only the longest variant is exported.

The type of variable exported (scalar, hash, or array) is determined by the type of the corresponding value in %ARGV. Command-line flags and arguments that take single values will produce scalars, arguments that take multiple values will produce hashes, and repeatable arguments will produce arrays.

If you do not like the default prefix of 'ARGV_', you can specify your own, such as 'opt_', like this:

The major advantage of using exported variables is that any misspelling of argument variables in your code will be caught at compile-time by use strict.

Standard arguments

Getopt::Euclid automatically provides four standard arguments to any program that uses the module. The behaviours of these arguments are 'hard- wired' and cannot be changed, not even by defining your own arguments of the same name.

The standard arguments are:

The --usage argument causes the program to print a short usage summary and exit. The Getopt::Euclid-usage()> subroutine provides access to the string of this message.

The --help argument causes the program to take a longer usage summary (with a full list of required and optional arguments) provided in POD format by help(), convert it to plaintext, display it and exit. The message is paged using IO::Pager::Page (or IO::Page) if possible.

The --man argument causes the program to take the POD documentation for the program, provided by man(), convert it to plaintext, display it and exit. The message is paged using IO::Pager::Page (or IO::Page) if possible.

The --podfile argument is provided for authors. It causes the program to take the POD manual from man(), write it in a .pod file with the same base name as the program, display the name of the output file and exit. These actions can also be executed by calling the podfile() subroutine.This argument is not really a standard argument, but it is useful if the program's POD is to be passed to a POD converter because, among other things, any default value specified is interpolated and replaced by its value in the .pod file, contrary to in the program's .pl file.

If you want to automate the creation of a POD file during the build process, you can edit you Makefile.PL or Build.PL file and add these lines:

If you use Module::Install to bundle your script, you might be interested in using Module::Install::PodFromEuclid to include the --podfile step into the installation process.

The --version argument causes the program to print the version number of the program (as specified in the =head1 VERSION section of the POD) and any copyright information (as specified in the =head1 COPYRIGHT POD section) and then exit. The Getopt::Euclid-version()> subroutine provides access to the string of this message.

Minimalist keys

By default, the keys of %ARGV will match the program's interface exactly. That is, if your program accepts the following arguments:

Then the keys that appear in %ARGV will be:

In some cases, however, it may be preferable to have Getopt::Euclid set up those hash keys without 'decorations'. That is, to have the keys of %ARGV be simply:

You can arrange this by loading the module with the special ':minimal_keys' specifier:

Note that, in rare cases, using this mode may cause you to lose data (for example, if the interface specifies both a --step and a <step> option). The module throws an exception if this happens.

Deferring argument parsing

In some instances, you may want to avoid the parsing of arguments to take place as soon as your program is executed and Getopt::Euclid is loaded. For example, you may need to examine @ARGV before it is processed (and emptied) by Getopt::Euclid. Or you may intend to pass your own arguments manually only using process_args().

To defer the parsing of arguments, use the specifier ':defer':

Compile-time diagnostics

The following diagnostics are mainly caused by problems in the POD specification of the command-line interface:

Something is horribly wrong. Getopt::Euclid was unable to read your program to extract the POD from it. Check your program's permissions, though it is a mystery how perl was able to run the program in the first place, if it is not readable.

You tried to define an import() subroutine in a module that was also using Getopt::Euclid. Since the whole point of using Getopt::Euclid in a module is to have it build an import() for you, supplying your own import() as well defeats the purpose.

You specified something in a =for Euclid section that Getopt::Euclid did not understand. This is often caused by typos, or by reversing a placeholder.type or placeholder.default specification (that is, writing type.placeholder or default.placeholder instead).

Both these errors mean that you specified a type constraint that Getopt::Euclid did not recognize. This may have been a typo:

or else the module simply does not know about the type you specified:

See 'Standard placeholder types' for a list of types that Getopt::Euclid does recognize.

You specified a type constraint that is not valid Perl. For example:

instead of:

You specified a default value that is not valid Perl. For example:

instead of:

Same as previous diagnostic, but for optional defaults.

You referred to a default value in the description of an argument, but there is no such default. It may be a typo, or you may be referring to the default value for a different argument, e.g.:

instead of:

Same as previous diagnostic, but for optional defaults.

You specified an optional default but the placeholder that it affects is not an optional placeholder. For example:

instead of:

You specified an optional default but the parameter that it affects is unflagged. For example:

instead of:

You specified to exclude a variable that was not seen in the POD. Make sure that this is not a typo.

You attempted to define a .type constraint for a placeholder that did not exist. Typically this is the result of the misspelling of a placeholder name:

or a =for Euclid: that has drifted away from its argument:

You tried to load the module twice in the same program. Getopt::Euclid does not work that way. Load it only once.

The only argument that a use Getopt::Euclid command accepts is ':minimal_keys' (see 'Minimalist keys'). You specified something else instead (or possibly forgot to put a semicolon after use Getopt::Euclid).

Minimalist mode removes certain characters from the keys hat are returned in %ARGV. This can mean that two command-line options (such as --step and <step>) map to the same key (i.e. 'step'). This in turn means that one of the two options has overwritten the other within the %ARGV hash. The program developer should either turn off ':minimal_keys' mode within the program, or else change the name of one of the options so that the two no longer clash.

Run-time diagnostics

The following diagnostics are caused by problems in parsing the command-line

At least one argument specified in the REQUIRED ARGUMENTS POD section was not present on the command-line.

Getopt::Euclid recognized the argument you were trying to specify on the command-line, but the value you gave to one of that argument's placeholders was of the wrong type.

Getopt::Euclid did not recognize an argument you were trying to specify on the command-line. This is often caused by command-line typos or an incomplete interface specification.

Getopt::Euclid requires no configuration files or environment variables.

• version

• Pod::Select

• Pod::PlainText

• File::Basename

• File::Spec::Functions

• List::Util

• Text::Balanced

• IO::Pager::Page (recommended)

Getopt::Euclid may not work properly with POD in Perl files that have been converted into an executable with PerlApp or similar software. A possible workaround may be to move the POD to a __DATA__ section or a separate .pod file.

Please report any bugs or feature requests to bug-getopt-euclid@rt.cpan.org, or through the web interface at https://rt.cpan.org/Public/Dist/Display.html?Name=Getopt-Euclid.

Getopt::Euclid has a development repository on Sourceforge.net at http://sourceforge.net/scm/?type=git&group_id=259291 in which the code is managed by Git. Feel free to clone this repository and push patches! To get started: git clone git://getopt-euclid.git.sourceforge.net/gitroot/getopt-euclid/getopt-euclid) git branch 0.2.x origin/0.2.x git checkout 0.2.x

Damian Conway <DCONWAY@cpan.org>

Florent Angly <florent.angly@gmail.com>

Copyright (c) 2005, Damian Conway <DCONWAY@cpan.org>. All rights reserved.

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE 'AS IS' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

To install Getopt::Euclid, copy and paste the appropriate command in to your terminal.

For more information on module installation, please visit the detailed CPAN module installation guide.

The mission was to achieve perfect symbiosis – an ideal fusion of high end sound with an innovative design concept. MBL’s teams of developers and designers worked hand in hand in engineering the concept and have broken fresh ground. The outcome is now a new range of superb high quality high end audio – the MBL Corona Line. The Corona Line’s minimalist design is a new byword for restrained understatement combined with classical elegance which makes it the perfect match for almost any type of room. The Corona Line takes its name from the 40mm button shaped like the MBL logo and mounted on the upper side in a corona of light. This signature button serves to regulate the brightness of the display. All products in the range have been carefully coordinated to complement one another and when taken together as a single family unit radiate an atmosphere of truly captivating serenity.

The Corona Line hasn’t just broken the mould in design terms alone; technically speaking too this new product line sets new standards. The outer solid aluminium casing contains a second casing of reinforced steel which screens off the electronics in magnetically shielded slots with full electrical isolation of the power supplies units and transformers. The CD player features a state of the art high quality Slot drive and digital RCA and Toslink inputs as well as a native USB dock for CD audio data. A novel intelligent MBL SmartLink network enables the devices to talk to one another. This means that all associated input signals are controlled by the Pre-Amplifi er or Integrated Amplifi er and a simple touch of the button on a device or the remote control is all that you need to put the whole Corona system on standby. The power consumption is then under 1 VA (Green Standby).

The MBL Corona Line is a fully rounded statement of our proven expertise in audio engineering and design – a consummate fusion of perfect acoustics and design. A truly alluring entry to the world of high end audio.

General

Weight
15,5 kg / 34.2 lbs

Dimensions (without cables)
W 45,0 cm / D 44,5 cm / H 14,5 cm
W 17.7 in / D 17.5 in / H 5.7 in

Dimensions with packaging
W 59,0 cm / D 54,0 cm / H 35,5 cm
W 23.2 in / D 21.3 in / H 21.9 in

Line Voltage
230 Vac / 50 Hz or
115 Vac / 50/60 Hz

Power consumption
in stand by < 1 VA
in idle < 20 VA
Maximum 21 VA (during ‘Play’)

Digital Inputs
1 x Toslink

Connection
Snap-In-Type

Wavelength
650 nm

Nominal Input Power
10mW

Working input power range
3mW – 30mW

electrically/galvanically Isolated
optically isolated 1 x S/P-DIF

Connection
RCA

Input Impedance
75 Ohm

Nominal Input-Level
0.5 Vpp

Working Input-Voltage Range
0,2 – 5 Vpp

electrically/galvanically Isolated
galvanically isolated

USB Input

Connection
USB Type B

Sampling Frequency
44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz

Mode
MCMI (Master Clock Mode Interface), Asynchronous USB

electrically/galvanically Isolated
galvanically isolated

Operating System Drivers
Natively supported, without any special driver

Digital Outputs
1 x S/P-DIF

Connection
RCA

Output Impedance
0.5 Vpp

Nominal Output-Level
75 Ohm

electrically/galvanically Isolated
galvanically isolated

Analog Outputs
Maximum Output Level

Unbalanced RCA Out
2 V @ 0 dBFS

Balanced XLR Out
4 V @ 0 dBFS

Output Impedance (RCA / XLR)
100 Ohm / 200 Ohm

Absolute Phase (RCA / XLR)
In-Phase / Pin-2 = In-Phase

Total Harmonic Distortion (THD)
< 0.001% @ 0 dBFS

Byword 2 0 3 – Minimalist Typing Interface Tutorial

Signal to Noise Ratio (RCA / XLR)
> 110 dB (A-Weighted) @ 0 dBFS

Channel Separation
> 100 dB @ 1 kHz

CD Section

CD Mechanism
Slot drive, front loaderSlot drive, front loader

Media
Standard compact disc (Red Book), 12 cm and 8 cm discs

Formats
CD, CDR, CD-RW (Multi-Read)

Book-Type
CD-DA, CD-Extra, Extended CD, CD-Enhanced

Laser type
780 nm (reads black CDR)

Resolution / Sample Rate
16 Bit / 44.1 kHz (CD-Digital-Audio)

CD-Text
Album Title, Album Artist, Track Title, Track Artist

DAC Section

Resolution
24 Bit

Sampling Frequencies
44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz

D/A Converter Type
Multi-Bit Delta Sigma

Digital Oversampling Filter
Psychoacoustic optimized filter of 4/5 Minimum Phase and 1/5 Linear Phase

Analog Output Filter
Group Delay Optimized Bessel Filter @ > 40 kHz