HS-4000
Release Notes
4
TASCAM HS-4000
Maintenance items
V2.13 fixes
•
After adding a take by FTP to a session other than the
current session, when that session was loaded, the
added take would not be shown and could not be
played without rebuilding. This has been fixed
.
•
On the
ADJUST ENTRY
screen in playlist mode, if the
PREVIEW
button was
ON
and rehearsal playback was
started, the repeat operation of each playlist entry was
ignored during rehearsal playback. This has been fixed.
•
When keys on the RC-HS32PD were operated quickly,
sometimes flash playback startup was delayed. This has
been fixed.
•
Operation stability has been improved.
V2.12 fixes
•
In timeline mode, on a CF card immediately after
recording, when the defaultAES.adl AES31 FILE was
read on a BE-200 , sometimes regions were not shown
on the BE-200. This has been fixed.
•
In timeline mode, when recording was conducted with
TIMELINE Rec Tracks set to 4tr, audio files that were
not POLY files were created on rare occasions. This has
been fixed.
•
In playlist mode, playback sometimes would not occur
correctly at the set timer playback time. This has been
fixed.
•
In take mode, after copying a take to an empty session
using the BROWSE function, the take name would not
appear on the Home Screen. This has been fixed.
V2.11 fixes
•
Using the WAV LOCK function (paid option), you can
now enable and unlock password locking for takes that
have been set as read-only.
•
The monitoring level setting on the
MONITOR MIXER
page of the
MIXER SETUP
screen has been changed
from a project setting to a unit setting. As a result,
loading a project will no longer change the monitoring
level setting.
•
In dual playlist mode, after removing a CF card from
the current slot, changing the PAGE on the right side of
the Home Screen would cause the RC-HS32PD flash key
to light even though playback would not be possible.
This has been fixed.
•
After loading a CF card that had been archived using a
BE-200 or TASCAM HS Editor into the unselected slot,
setting that CF card to the current media would result
in the media not being recognized. This has been fixed.
•
When a CF card that had been read or written using a
Mac was loaded in this unit, the management folder
created automatically on the CF card by the Mac would
not be shown by this unit. This has been fixed.
•
When the timeline mode TIMELINE Rec Tracks setting
was "2trx2 POLY", if an AES31 file output using EXPORT
AES31 was loaded after executing IMPORT ALL TAKES,
the 3/4ch timeline information would disappear. This
has been fixed.
•
If the
EXT CTRL
item on the
LOCK SETUP
screen was
set to
LOCK
, locking would not be possible even when
the
REMOTE
item was set to
LOCK
. This has been fixed.
•
Even if set to
User Word
on the
NEXT TAKE NAME
screen, the folder name would be recorded in the iXML
<SCENE> tag. This is been fixed so that the name set on
the
NEXT TAKE NAME
screen is recorded. In addition,
an iXML <TAPE> tag has been added, and the session
name is recorded for this tag.
•
When a take name is changed, the take iXML data is
now also changed.
•
When PLAY and RECORD signals were both input
through the parallel connector at the same time and
recording was started, timecode would not be output
on rare occasions. This has been fixed.
•
Operation stability has been improved.
V2.00 fixes
•
When switching the
ON AIR
button from ON to OFF,
the resulting transport position and mode have been
changed.
•
In on air mode, when the
ON AIR
button was switched
on and off, the Home Screen time display mode would
change. This has been fixed.
•
Dedicated
FADER MODE
,
FADER Start MODE
and
FADER Stop MODE
settings have been added for on
air mode.
•
When loading a playlist, or when loading a session in
timeline mode, a message will now appear when there
is an entry or region that has a problem.
•
When upgrading from V1.52 or V1.53 to V1.60, the
BWF-J Tally
setting on the
PARALLEL
page of the
REMOTE SETUP
screen would change in on air mode.
This has been fixed.
•
On the character input screen in V1.60, touching the “@”
button would input “2” instead. This has been fixed.