JP4897138B2 - Playback apparatus and playback method - Google Patents

Description

【００８７】
ＳＮ１Ｃ＋Ｌ（２バイト）
意味：ＮＭ１−Ｓ領域に書かれるメモリカードの名前（１バイト）の属性を表す
機能：使用する文字コードと言語コードを各１バイトで表す
値：文字コード（Ｃ）は上位１バイトで下記のように文字を区別する
00: 文字コードは設定しない。単なる２進数として扱うこと
01: ASCII(American Standard Code for Information Interchange)
02:ASCII+KANA 03:modifided8859-1
81:MS-JIS 82:KS C 5601-1989 83:GB(Great Britain)2312-80
90:S-JIS(Japanese Industrial Standards)(for Voice)。
【００８８】
言語コード（Ｌ）は下位１バイトで下記のようにEBU Tech 3258 規定に準じて言語を区別する
00: 設定しない 08:German 09:English 0A:Spanish
0F:French 15:Italian 1D:Dutch
65:Korean 69:Japanese 75:Chinese
データが無い場合オールゼロとすること。
【００８９】
ＳＮ２Ｃ＋Ｌ（２バイト）
意味：ＮＭ２−Ｓ領域に書かれるメモリカードの名前（２バイト）の属性を表す
機能：使用する文字コードと言語コードを各１バイトで表す
値：上述したＳＮ１Ｃ＋Ｌと同一
ＳＩＮＦＳＩＺＥ（２バイト）
意味：ＩＮＦ−Ｓ領域に書かれるメモリカード全体に関する付加情報の全てを合計したサイズを表す
機能：データサイズを１６バイト単位の大きさで記述、無い場合は必ずオールゼロとすること
値：サイズは０ｘ０００１から０ｘ３９Ｃ（９２４）
Ｔ−ＴＲＫ（２バイト）
意味：TOTAL TRACK NUMBER
機能：総トラック数
値：１から０ｘ０１９０（最大４００トラック）、データが無い場合はオールゼロとすること
ＶｅｒＮｏ（２バイト）
意味：フォーマットのバージョン番号
機能：上位がメジャーバージョン番号、下位がマイナーバージョン番号

【００９０】
上述したヘッダに続く領域に書かれるデータ（図１３Ｂ）について以下に説明する。
【００９１】
ＮＭ１−Ｓ
意味：メモリカード全体に関する１バイトの名前
機能：１バイトの文字コードで表した可変長の名前データ（最大で２５６）
名前データの終了は、必ず終端コード（０ｘ００）を書き込むこと
サイズはこの終端コードから計算すること、データの無い場合は少なくとも先頭（０ｘ００２０）からヌル（０ｘ００）を１バイト以上記録すること
値：各種文字コード
ＮＭ２−Ｓ
意味：メモリカード全体に関する２バイトの名前
機能：２バイトの文字コードで表した可変長の名前データ（最大で５１２）
名前データの終了は、必ず終端コード（０ｘ００）を書き込むこと
サイズはこの終端コードから計算すること、データの無い場合は少なくとも先頭（０ｘ０１２０）からヌル（０ｘ００）を２バイト以上記録すること
値：各種文字コード。
【００９２】
ＣＯＮＴＥＮＴＳ ＫＥＹ
意味：曲ごとに用意された値でＭＧ（Ｍ）で保護されてから保存される。ここでは、１曲目に付けられるＣＯＮＴＥＮＴＳ ＫＥＹと同じ値
機能：Ｓ−ＹＭＤｈｍｓのＭＡＣの計算に必要となる鍵となる
値：０から０ｘＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦまで
ＭＡＣ
意味：著作権情報改ざんチェック値
機能：Ｓ−ＹＭＤｈｍｓの内容とＣＯＮＴＥＮＴＳ ＫＥＹから作成される値
値：０から０ｘＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦまで。
【００９３】
ＴＲＫ−ｎｎｎ
意味：再生するＡＴＲＡＣ３データファイルのＳＱＮ（シーケンス）番号
機能：ＴＲＫＩＮＦの中のＦＮｏを記述する
値：１から４００（０ｘ１９０）
トラックが存在しない時はオールゼロとすること
ＩＮＦ−Ｓ
意味：メモリカード全体に関する付加情報データ（例えば写真、歌詞、解説等の情報）
機能：ヘッダを伴った可変長の付加情報データ
複数の異なる付加情報が並べられることがある。それぞれにＩＤとデータサイズが付けられている。個々のヘッダを含む付加情報データは最小１６バイト以上で４バイトの整数倍の単位で構成される。
その詳細については、後述する値：付加情報データ構成を参照
Ｓ−ＹＭＤｈｍｓ（４バイト）（Ｏｐｔｉｏｎ）
意味：信頼できる時計を持つ機器で記録した年・月・日・時・分・秒
機能：最終記録日時を識別するための値、ＥＭＤの時は必須

【００９４】
再生管理ファイルの最後のスロットとして、ヘッダ内のものと同一のＢＬＫＩＤ−ＴＬ０と、ＭＣｏｄｅと、ＲＥＶＩＳＩＯＮとが書かれる。
【００９５】
民生用オーディオ機器として、メモリカードが記録中に抜かれたり、電源が切れることがあり、復活した時にこれらの異常の発生を検出することが必要とされる。上述したように、ＲＥＶＩＳＩＯＮをブロックの先頭と末尾に書き込み、この値を書き換える度に＋１インクリメントするようにしている。若し、ブロックの途中で異常終了が発生すると、先頭と末尾のＲＥＶＩＳＩＯＮの値が一致せず、異常終了を検出することができる。ＲＥＶＩＳＩＯＮが２個存在するので、高い確率で異常終了を検出することができる。異常終了の検出時には、エラーメッセージの表示等の警告が発生する。
【００９６】
また、１ブロック（１６ＫＢ）の先頭部分に固定値ＢＬＫＩＤ−ＴＬ０を挿入しているので、ＦＡＴが壊れた場合の修復の目安に固定値を使用できる。すなわち、各ブロックの先頭の固定値を見れば、ファイルの種類を判別することが可能である。しかも、この固定値ＢＬＫＩＤ−ＴＬ０は、ブロックのヘッダおよびブロックの終端部分に二重に記述するので、その信頼性のチェックを行うことができる。なお、再生管理ファイルＰＢＬＩＳＴの同一のものを二重に記録しても良い。
【００９７】
ＡＴＲＡＣ３データファイルは、トラック情報管理ファイルと比較して、相当大きなデータ量であり、ＡＴＲＡＣ３データファイルに関しては、後述するように、ブロック番号ＢＬＯＣＫ ＳＥＲＩＡＬが付けられている。但し、ＡＴＲＡＣ３データファイルは、通常複数のファイルがメモリカード上に存在するので、ＣＯＮＮＵＭ０でコンテンツの区別を付けた上で、ＢＬＯＣＫ ＳＥＲＩＡＬを付けないと、重複が発生し、ＦＡＴが壊れた場合のファイルの復旧が困難となる。換言すると単一のＡＴＲＡＣ３データファイルは、複数のＢＬＯＣＫで構成されると共に、離散して配置される可能性があるので、同一ＡＴＲＡＣ３データファイルを構成するＢＬＯＣＫを判別するためにＣＯＮＮＵＭ０を用いると共に、同一ＡＴＲＡＣ３データファイル内の昇降順をブロック番号ＢＬＯＣＫ ＳＥＲＩＡＬで決定する。
【００９８】
同様に、ＦＡＴの破壊までにはいたらないが、論理を間違ってファイルとして不都合のあるような場合に、書き込んだメーカーの機種が特定できるように、メーカーコード（ＭＣｏｄｅ）がブロックの先頭と末尾に記録されている。
【００９９】
図１２Ｃは、付加情報データの構成を示す。付加情報の先頭に下記のヘッダが書かれる。ヘッダ以降に可変長のデータが書かれる。
【０１００】
ＩＮＦ
意味：FIELD ID
機能：付加情報データの先頭を示す固定値
値：０ｘ６９
ＩＤ
意味：付加情報キーコード
機能：付加情報の分類を示す
値：０から０ｘＦＦ
ＳＩＺＥ
意味：個別の付加情報の大きさ
機能：データサイズは自由であるが、必ず４バイトの整数倍でなければならない。また、最小１６バイト以上のこと。データの終わりより余りがでる場合はヌル（０ｘ００）で埋めておくこと
値：１６から１４７８４（０ｘ３９Ｃ０）
ＭＣｏｄｅ
意味：MAKER CODE
機能：記録した機器の、メーカー、モデルを識別するコード
値：上位１０ビット（メーカーコード） 下位６ビット（機種コード）
Ｃ＋Ｌ
意味：先頭から１２バイト目からのデータ領域に書かれる文字の属性を表す
機能：使用する文字コードと言語コードを各１バイトで表す
値：前述のＳＮＣ＋Ｌと同じ
ＤＡＴＡ
意味：個別の付加情報データ
機能：可変長データで表す。実データの先頭は常に１２バイト目より始まり、長さ（サイズ）は最小４バイト以上、常に４バイトの整数倍でなければならない。データの最後から余りがある場合はヌル（０ｘ００）で埋めること
値：内容により個別に定義される。
【０１０１】
図１３は、付加情報キーコードの値（０〜６３）と、付加情報の種類の対応の一例を示す。キーコードの値（０〜３１）が音楽に関する文字情報に対して割り当てられ、その（３２〜６３）がＵＲＬ(Uniform Resource Locator)（Ｗｅｂ関係）に対して割り当てられている。アルバムタイトル、アーティスト名、ＣＭ等の文字情報が付加情報として記録される。
【０１０２】
図１４は、付加情報キーコードの値（６４〜１２７）と、付加情報の種類の対応の一例を示す。キーコードの値（６４〜９５）がパス／その他に対して割り当てられ、その（９６〜１２７）が制御／数値・データ関係に対して割り当てられている。例えば（ＩＤ＝９８）の場合では、付加情報がＴＯＣ（Table of Content）−ＩＤとされる。ＴＯＣ−ＩＤは、ＣＤ（コンパクトディスク）のＴＯＣ情報に基づいて、最初の曲番号、最後の曲番号、その曲番号、総演奏時間、その曲演奏時間を示すものである。
【０１０３】
図１５は、付加情報キーコードの値（１２８〜１５９）と、付加情報の種類の対応の一例を示す。キーコードの値（１２８〜１５９）が同期再生関係に対して割り当てられている。図１５中のＥＭＤ(Electronic Music Distribution) は、電子音楽配信の意味である。
【０１０４】
図１６を参照して付加情報のデータの具体例について説明する。図１６Ａは、図１２Ｃと同様に、付加情報のデータ構成を示す。図１６Ｂは、キーコードＩＤ＝３とされる、付加情報がアーティスト名の例である。ＳＩＺＥ＝０ｘ１Ｃ（２８バイト）とされ、ヘッダを含むこの付加情報のデータ長が２８バイトであることが示される。また、Ｃ＋Ｌが文字コードＣ＝０ｘ０１とされ、言語コードＬ＝０ｘ０９とされる。この値は、前述した規定によって、ＡＳＣＩＩの文字コードで、英語の言語であることを示す。そして、先頭から１２バイト目から１バイトデータでもって、「ＳＩＭＯＮ＆ＧＲＡＦＵＮＫＥＬ」のアーティスト名のデータが書かれる。付加情報のサイズは、４バイトの整数倍と決められているので、１バイトの余りが（０ｘ００）とされる。
【０１０５】
図１６Ｃは、キーコードＩＤ＝９７とされる、付加情報がＩＳＲＣ(International Standard Recording Code：著作権コード) の例である。ＳＩＺＥ＝０ｘ１４（２０バイト）とされ、この付加情報のデータ長が２０バイトであることが示される。また、Ｃ＋ＬがＣ＝０ｘ００、Ｌ＝０ｘ００とされ、文字、言語の設定が無いこと、すなわち、データが２進数であることが示される。そして、データとして８バイトのＩＳＲＣのコードが書かれる。ＩＳＲＣは、著作権情報（国、所有者、録音年、シリアル番号）を示すものである。
【０１０６】
図１６Ｄは、キーコードＩＤ＝９７とされる、付加情報が録音日時の例である。ＳＩＺＥ＝０ｘ１０（１６バイト）とされ、この付加情報のデータ長が１６バイトであることが示される。また、Ｃ＋ＬがＣ＝０ｘ００、Ｌ＝０ｘ００とされ、文字、言語の設定が無いことが示される。そして、データとして４バイト（３２ビット）のコードが書かれ、録音日時（年、月、日、時、分、秒）が表される。
【０１０７】
図１６Ｅは、キーコードＩＤ＝１０７とされる、付加情報が再生ログの例である。ＳＩＺＥ＝０ｘ１０（１６バイト）とされ、この付加情報のデータ長が１６バイトであることが示される。また、Ｃ＋ＬがＣ＝０ｘ００、Ｌ＝０ｘ００とされ、文字、言語の設定が無いことが示される。そして、データとして４バイト（３２ビット）のコードが書かれ、再生ログ（年、月、日、時、分、秒）が表される。再生ログ機能を持つものは、１回の再生毎に１６バイトのデータを記録する。
【０１０８】
図１７は、１ＳＵがＮバイト（例えばＮ＝３８４バイト）の場合のＡＴＲＡＣ３データファイルＡ３Ｄｎｎｎｎのデータ配列を示す。図１７には、データファイルの属性ヘッダ（１ブロック）と、音楽データファイル（１ブロック）とが示されている。図１７では、この２ブロック（１６×２＝３２Ｋバイト）の各スロットの先頭のバイト（０ｘ００００〜０ｘ７ＦＦ０）が示されている。図１８に分離して示すように、属性ヘッダの先頭から３２バイトがヘッダであり、２５６バイトが曲名領域ＮＭ１（２５６バイト）であり、５１２バイトが曲名領域ＮＭ２（５１２バイト）である。属性ヘッダのヘッダには、下記のデータが書かれる。
【０１０９】
ＢＬＫＩＤ−ＨＤ０（４バイト）
意味：BLOCKID FILE ID
機能：ＡＴＲＡＣ３データファイルの先頭であることを識別するための値
値：固定値＝”ＨＤ＝０”（例えば０ｘ４８４４２Ｄ３０）
ＭＣｏｄｅ（２バイト）
意味：MAKER CODE
機能：記録した機器の、メーカー、モデルを識別するコード
値：上位１０ビット（メーカーコード） 下位６ビット（機種コード）
ＢＬＯＣＫ ＳＥＲＩＡＬ（４バイト）
意味：トラック毎に付けられた連続番号
機能：ブロックの先頭は０から始まり次のブロックは＋１づつインクリメント
編集されても値を変化させない
値：０より始まり０ｘＦＦＦＦＦＦＦＦまで。
【０１１０】
Ｎ１Ｃ＋Ｌ（２バイト）
意味：トラック（曲名）データ（ＮＭ１）の属性を表す
機能：ＮＭ１に使用される文字コードと言語コードを各１バイトで表す
値：ＳＮ１Ｃ＋Ｌと同一
Ｎ２Ｃ＋Ｌ（２バイト）
意味：トラック（曲名）データ（ＮＭ２）の属性を表す
機能：ＮＭ２に使用される文字コードと言語コードを各１バイトで表す
値：ＳＮ１Ｃ＋Ｌと同一
ＩＮＦＳＩＺＥ（２バイト）
意味：トラックに関する付加情報の全てを合計したサイズを表す
機能：データサイズを１６バイト単位の大きさで記述、無い場合は必ずオールゼロとすること
値：サイズは０ｘ００００から０ｘ３Ｃ６（９６６）
Ｔ−ＰＲＴ（２バイト）
意味：トータルパーツ数
機能：トラックを構成するパーツ数を表す。通常は１
値：１から０ｘ２８５（６４５dec ）
Ｔ−ＳＵ（４バイト）
意味：トータルＳＵ数
機能：１トラック中の実際の総ＳＵ数を表す。曲の演奏時間に相当する
値：０ｘ０１から０ｘ００１ＦＦＦＦＦ
ＩＮＸ（２バイト）（Ｏｐｔｉｏｎ）
意味：INDEX の相対場所
機能：曲のさびの部分（特徴的な部分）の先頭を示すポインタ。曲の先頭からの位置をＳＵの個数を１／４した数で指定する。これは、通常のＳＵの４倍の長さの時間（約９３ｍ秒）に相当する
値：０から０ｘＦＦＦＦ（最大、約６０８４秒）
ＸＴ（２バイト）（Ｏｐｔｉｏｎ）
意味：INDEX の再生時間
機能：ＩＮＸ-nnnで指定された先頭から再生すべき時間のＳＵの個数を１／４した数で指定する。これは、通常のＳＵの４倍の長さの時間（約９３ｍ秒）に相当する
値：０ｘ００００：無設定 ０ｘ０１から０ｘＦＦＦＥ（最大６０８４秒）
０ｘＦＦＦＦ：曲の終わりまで。
【０１１１】
次に曲名領域ＮＭ１およびＮＭ２について説明する。
【０１１２】
ＮＭ１
意味：曲名を表す文字列
機能：１バイトの文字コードで表した可変長の曲名（最大で２５６）
名前データの終了は、必ず終端コード（０ｘ００）を書き込むこと
サイズはこの終端コードから計算すること、データの無い場合は少なくとも先頭（０ｘ００２０）からヌル（０ｘ００）を１バイト以上記録すること
値：各種文字コード
ＮＭ２
意味：曲名を表す文字列
機能：２バイトの文字コードで表した可変長の名前データ（最大で５１２）
名前データの終了は、必ず終端コード（０ｘ００）を書き込むこと
サイズはこの終端コードから計算すること、データの無い場合は少なくとも先頭（０ｘ０１２０）からヌル（０ｘ００）を２バイト以上記録すること
値：各種文字コード。
【０１１３】
属性ヘッダの固定位置（０ｘ３２０）から始まる、８０バイトのデータをトラック情報領域ＴＲＫＩＮＦと呼び、主としてセキュリティ関係、コピー制御関係の情報を一括して管理する。図１９にＴＲＫＩＮＦの部分を示す。ＴＲＫＩＮＦ内のデータについて、配置順序に従って以下に説明する。
【０１１４】
ＣＯＮＴＥＮＴＳ ＫＥＹ（８バイト）
意味：曲毎に用意された値で、メモリカードのセキュリティブロックで保護されてから保存される
機能：曲を再生する時、まず必要となる最初の鍵となる。ＭＡＣ計算時に使用される
値：０から０ｘＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦまで
ＭＡＣ（８バイト）
意味：著作権情報改ざんチェック値
機能：コンテンツ累積番号を含む複数のＴＲＫＩＮＦの内容と隠しシーケンス番号から作成される値
隠しシーケンス番号とは、メモリカードの隠し領域に記録されているシーケンス番号のことである。著作権対応でないレコーダは、隠し領域を読むことができない。また、著作権対応の専用のレコーダ、またはメモリカードを読むことを可能とするアプリケーションを搭載したパーソナルコンピュータは、隠し領域をアクセスすることができる。
【０１１５】
Ａ（１バイト）
意味：パーツの属性
機能：パーツ内の圧縮モード等の情報を示す
値：図２０を参照して以下に説明する
ただし、Ｎ＝０，１のモノラルは、ｂｉｔ７が１でサブ信号を０、メイン信号（Ｌ＋Ｒ）のみの特別なＪｏｉｎｔモードをモノラルとして規定する。ｂｉｔ２，１の情報は通常の再生機は無視しても構わない。
【０１１６】
Ａのビット０は、エンファシスのオン／オフの情報を形成し、ビット１は、再生ＳＫＩＰか、通常再生かの情報を形成し、ビット２は、データ区分、例えばオーディオデータか、ＦＡＸ等の他のデータかの情報を形成する。ビット３は、未定義である。ビット４、５、６を組み合わせることによって、図示のように、ＡＴＲＡＣ３のモード情報が規定される。すなわち、Ｎは、この３ビットで表されるモードの値であり、モノ（Ｎ＝０，１）、ＬＰ（Ｎ＝２）、ＳＰ（Ｎ＝４）、ＨＸ（Ｎ＝５）、ＨＱ（Ｎ＝７）の５種類のモードについて、記録時間（６４ＭＢのメモリカードの場合）、データ転送レート、１ブロック内のＳＵ数がそれぞれ示されている。１ＳＵのバイト数は、（モノ：１３６バイト、ＬＰ：１９２バイト、ＳＰ：３０４バイト、ＥＸ：３８４バイト、ＨＱ：５１２バイト）である。さらに、ビット７によって、ＡＴＲＡＣ３のモード（０：Dual １：J0int ）が示される。
【０１１７】
一例として、６４ＭＢのメモリカードを使用し、ＳＰモードの場合について説明する。６４ＭＢのメモリカードには、３９６８ブロックがある。ＳＰモードでは、１ＳＵが３０４バイトであるので、１ブロックに５３ＳＵが存在する。１ＳＵは、（１０２４／４４１００）秒に相当する。従って、１ブロックは、
（１０２４／４４１００）×５３×（３９６８−１６）＝４８６３秒＝８１分
転送レートは、
（４４１００／１０２４）×３０４×８＝１０４７３７ bps
となる。
【０１１８】
ＬＴ（１バイト）
意味：再生制限フラグ（ビット７およびビット６）とセキュリティバージョン
（ビット５〜ビット０）
機能：このトラックに関して制限事項があることを表す

ＦＮｏ（２バイト）
意味：ファイル番号
機能：最初に記録された時のトラック番号、且つこの値は、メモリカード内の隠し領域に記録されたＭＡＣ計算用の値の位置を特定する
値：１から０ｘ１９０（４００）
ＭＧ（Ｄ）ＳＥＲＩＡＬ−ｎｎｎ（１６バイト）
意味：記録機器のセキュリティブロック（セキュリティＩＣ２０）のシリアル番号
機能：記録機器ごとに全て異なる固有の値
値：０から0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ＣＯＮＮＵＭ（４バイト）
意味：コンテンツ累積番号
機能：曲毎に累積されていく固有の値で記録機器のセキュリティブロックによって管理される。２の３２乗、４２億曲分用意されており、記録した曲の識別に使用する
値：０から０ｘＦＦＦＦＦＦＦＦ。
【０１１９】
ＹＭＤｈｍｓ−Ｓ（４バイト）（Ｏｐｔｉｏｎ）
意味：再生制限付きのトラックの再生開始日時
機能：ＥＭＤで指定する再生開始を許可する日時
値：上述した日時の表記と同じ
ＹＭＤｈｍｓ−Ｅ（４バイト）（Ｏｐｔｉｏｎ）
意味：再生制限付きのトラックの再生終了日時
機能：ＥＭＤで指定する再生許可を終了する日時
値：上述した日時の表記と同じ
ＭＴ（１バイト）（Ｏｐｔｉｏｎ）
意味：再生許可回数の最大値
機能：ＥＭＤで指定される最大の再生回数
値：１から０ｘＦＦ 未使用の時は、０ｘ００
ＬＴのｂｉｔ７の値が０の場合はＭＴの値は００とすること
ＣＴ（１バイト）（Ｏｐｔｉｏｎ）
意味：再生回数
機能：再生許可された回数の内で、実際に再生できる回数。再生の度にデクリメントする
値：０ｘ００〜０ｘＦＦ 未使用の時は、０ｘ００である
ＬＴのｂｉｔ７が１でＣＴの値が００の場合は再生を禁止すること。
【０１２０】
ＣＣ（１バイト）
意味：COPY CONTROL
機能：コピー制御
値：図２１に示すように、ビット６および７によってコピー制御情報を表し、ビット４および５によって高速ディジタルコピーに関するコピー制御情報を表し、ビット２および３によってセキュリティブロック認証レベルを表す。ビット０および１は、未定義
ＣＣの例：（ｂｉｔ７，６）１１：無制限のコピーを許可、０１：コピー禁止、００：１回のコピーを許可
（ｂｉｔ３，２）００：アナログないしディジタルインからの録音、ＭＧ認証レベルは０とする
ＣＤからのディジタル録音では（ｂｉｔ７，６）は００、（ｂｉｔ３，２）は１０となる
ＣＮ（１バイト）（Ｏｐｔｉｏｎ）
意味：高速ディジタルコピーＨＳＣＭＳ(High speed Serial Copy ManagementSystem) におけるコピー許可回数
機能：コピー１回か、コピーフリーかの区別を拡張し、回数で指定する。コピー第１世代の場合にのみ有効であり、コピーごとに減算する
値：００：コピー禁止、０１から０ｘＦＥ：回数、０ｘＦＦ：回数無制限。
【０１２１】
上述したトラック情報領域ＴＲＫＩＮＦに続いて、０ｘ０３７０から始まる２４バイトのデータをパーツ管理用のパーツ情報領域ＰＲＴＩＮＦと呼び、１つのトラックを複数のパーツで構成する場合に、時間軸の順番にＰＲＴＩＮＦを並べていく。図２２にＰＲＴＩＮＦの部分を示す。ＰＲＴＩＮＦ内のデータについて、配置順序に従って以下に説明する。
【０１２２】
ＰＲＴＳＩＺＥ（４バイト）
意味：パーツサイズ
機能：パーツの大きさを表す。クラスタ：２バイト（最上位）、開始ＳＵ：１バイト（上位）、終了ＳＵ：１バイト（最下位）
値：クラスタ：１から０ｘ１Ｆ４０（８０００）、開始ＳＵ：０から０ｘＡ０（１６０）、終了ＳＵ：０から０ｘＡ０（１６０）（但し、ＳＵの数え方は、０，１，２，と０から開始する）
ＰＲＴＫＥＹ（８バイト）
意味：パーツを暗号化するための値
機能：初期値＝０、編集時は編集の規則に従うこと
値：０から０ｘＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦ
ＣＯＮＮＵＭ０（４バイト）
意味：最初に作られたコンテンツ累積番号キー
機能：コンテンツをユニークにするためのＩＤの役割
値：コンテンツ累積番号初期値キーと同じ値とされる。
【０１２３】
ＡＴＲＡＣ３データファイルの属性ヘッダ中には、図１７に示すように、付加情報ＩＮＦが含まれる。この付加情報は、開始位置が固定化されていない点を除いて、再生管理ファイル中の付加情報ＩＮＦ−Ｓ（図１１および図１２Ｂ参照）と同一である。１つまたは複数のパーツの最後のバイト部分（４バイト単位）の次を開始位置として付加情報ＩＮＦのデータが開始する。
【０１２４】
ＩＮＦ
意味：トラックに関する付加情報データ
機能：ヘッダを伴った可変長の付加情報データ。複数の異なる付加情報が並べられることがある。それぞれにＩＤとデータサイズが付加されている。個々のヘッダを含む付加情報データは、最小１６バイト以上で４バイトの整数倍の単位
値：再生管理ファイル中の付加情報ＩＮＦ−Ｓと同じである。
【０１２５】
上述した属性ヘッダに対して、ＡＴＲＡＣ３データファイルの各ブロックのデータが続く。図２３に示すように、ブロック毎にヘッダが付加される。各ブロックのデータについて以下に説明する。
【０１２６】
ＢＬＫＩＤ−Ａ３Ｄ（４バイト）
意味：BLOCKID FILE ID
機能：ＡＴＲＡＣ３データの先頭であることを識別するための値
値：固定値＝”Ａ３Ｄ”（例えば０ｘ４１３３４４２０）
ＭＣｏｄｅ（２バイト）
意味：MAKER CODE
機能：記録した機器の、メーカー、モデルを識別するコード
値：上位１０ビット（メーカーコード） 下位６ビット（機種コード）
ＣＯＮＮＵＭ０（４バイト）
意味：最初に作られたコンテンツ累積番号
機能：コンテンツをユニークにするためのＩＤの役割、編集されても値は変化させない
値：コンテンツ累積番号初期値キーと同じ値とされる
ＢＬＯＣＫ ＳＥＲＩＡＬ（４バイト）
意味：トラック毎に付けられた連続番号
機能：ブロックの先頭は０から始まり次のブロックは＋１づつインクリメント
編集されても値を変化させない
値：０より始まり０ｘＦＦＦＦＦＦＦＦまで
ＢＬＯＣＫ−ＳＥＥＤ（８バイト）
意味：１ブロックを暗号化するための１つの鍵
機能：ブロックの先頭は、記録機器のセキュリティブロックで乱数を生成、続くブロックは、＋１インクリメントされた値、この値が失われると、１ブロックに相当する約１秒間、音が出せないために、ヘッダとブロック末尾に同じものが二重に書かれる。編集されても値を変化させない
値：初期は８バイトの乱数
ＩＮＩＴＩＡＬＩＺＡＴＩＯＮ ＶＥＣＴＯＲ（８バイト）
意味：ブロック毎にＡＴＲＡＣ３データを暗号化、復号化する時に必要な初期値
機能：ブロックの先頭は０から始まり、次のブロックは最後のＳＵの最後の暗号化された８バイトの値。デバイドされたブロックの途中からの場合は開始ＳＵの直前の最後の８バイトを用いる。編集されても値を変化させない
値：０から０ｘＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦＦ
ＳＵ−ｎｎｎ
意味：サウンドユニットのデータ
機能：１０２４サンプルから圧縮されたデータ、圧縮モードにより出力されるバイト数が異なる。編集されても値を変化させない（一例として、ＳＰモード
の時では、Ｎ＝３８４バイト）
値：ＡＴＲＡＣ３のデータ値。
【０１２７】
図１７では、Ｎ＝３８４であるので、１ブロックに４２ＳＵが書かれる。また、１ブロックの先頭の２つのスロット（４バイト）がヘッダとされ、最後の１スロット（２バイト）にＢＬＫＩＤ−Ａ３Ｄ、ＭＣｏｄｅ、ＣＯＮＮＵＭ０、ＢＬＯＣＫ ＳＥＲＩＡＬが二重に書かれる。従って、１ブロックの余りの領域Ｍバイトは、（１６，３８４−３８４×４２−１６×３＝２０８（バイト）となる。
この中に上述したように、８バイトのＢＬＯＣＫ ＳＥＥＤが二重に記録される。
【０１２８】
以下、この発明を上述したディジタルオーディオレコーダに適用した一実施形態について図面を参照して説明する。図２４は、この発明の一実施形態の要部の構成を示す。図２４において７０で示されるのがオーディオシステム内に設けられたＣＰＵであり、このＣＰＵ７０がバスインターフェースおよびバスを介して前述したＤＳＰ３０に接続される。また、ＣＰＵ７０には、操作部８０が接続されている。
【０１２９】
図２４に示すように操作部８０には、ボタン群８１〜８６等が配設されている。具体的には、８１で示されるのが録音／再生位置の後戻しボタンであり、８４で示されるのが録音／再生位置の先送りボタンであり、８２で示されるのが録音ボタンであり、８５で示されるのが再生ボタンであり、８３で示されるのが停止ボタンであり、８６で示されるのが一時停止ボタンである。
【０１３０】
操作部８０のボタン群８１〜８６の中の一つが押されると、そのボタンの押されたタイミングでその押されたボタンに応じた検出情報が操作部８０において生成され、この検出情報がＣＰＵ７０に供給される。ＣＰＵ７０は、操作部８０からの検出情報により操作部８０の操作状態を監視し、所定のボタンに対して所定操作がなされたと判定される場合には、その操作ボタンに応じた制御情報を生成し、制御情報を各部に供給することで各種動作を実行する。
【０１３１】
例えば、録音ボタン８２が押された場合には、録音動作が開始される。つまり、選択された所定の入力ソースから生成したオーディオデータがメモリカード４０の所定領域に順次書き込まれる。また、再生ボタン８５が押された場合には、再生動作が開始される。つまり、メモリカード４０の所定領域に書き込まれているオーディオデータが順次読み出され、読み出されたオーディオデータに基づいてアナログオーディオ信号が生成されてライン出力端子１９から取り出される。
【０１３２】
また、再生状態において、さらに再生ボタン８５が押されて使用者により所定時間以上押され続けた場合には、再生動作に並行してインデックス管理情報書き込み処理に移行し、使用者によって任意の再生区間が設定される。具体的には、インデックス管理情報書き込み処理では、再生ボタン８５の押されたタイミングで規定されるインデックス情報の開始位置を示す情報と、再生ボタン８５の押され続けた時間を示す情報とがＣＰＵ７０において生成され、これら情報が再生区間を示す情報としてメモリカード４０の所定領域に書き込まれる。
【０１３３】
つまり、再生されている楽曲等において使用者の気に入った特徴的な部分や、所謂ダイジェスト部分が使用者により指定され、その再生区間を示す情報がメモリカード４０の所定領域に書き込まれる。なお、再生ボタン８５の押されたタイミングで規定されるインデックス情報の開始位置を示す情報は、例えば、前述したＡＴＲＡＣ３オーディオファイルＡ３ＤＤｎｎｎｎの属性ヘッダ中のＩＮＸに格納され、再生ボタン８５の押され続けた時間を示す情報は、ＸＴに格納される。ＩＮＸによって、最大約６０８４秒まで指定することが可能であり、ＸＴによって、６０８４秒程度まで指定することが可能とされている。
【０１３４】
一度、このように使用者の気に入った特徴的な部分や、所謂ダイジェスト部分を特定し、その再生区間を示す情報をメモリカード４０の所定領域に書き込んでおけば、次回からの再生動作に先立って、容易に曲の検索を行うことが可能となり、また、特徴的な部分のみを取りまとめて再生することも可能となる。
【０１３５】
上述したこの発明の一実施形態について、図２６および図２７を参照してより詳細に説明する。上述したデータフォーマットでは、ＩＮＸおよびＸＴの値としてＳＵの個数を１／４にした数を使用している。但し、以下の説明では、簡単のため、ＳＵの個数を１／４としない例で説明する。最初に、メモリカードをレコーダに挿入し、再生ボタン８５を押すことによって、再生動作を開始する（ステップＳ１）。ステップＳ２では、トラックの先頭かどうかが判定される。トラックの先頭であると判定されると、ＳＵの個数のカウントが開始され、ステップＳ３に移行する。
【０１３６】
そして、ステップＳ３において、さらに再生ボタン８５が押されたかどうかが判定される。再生ボタン８５が押されたと判定される場合においてのみステップＳ４に移行する。ステップＳ４においては、再生ボタン８５が４秒以上押され続けたかどうかが判定される。再生ボタン８５が４秒以上押され続けた場合においてのみステップＳ５に移行し、再生動作に並行してインデックス管理情報書き込み状態になる。インデックス管理情報書き込み状態においては、先ず、トラックの先頭から再生ボタン８５の押されたタイミングまでのＳＵの個数のカウント値がＩＮＸに書き込まれる。具体的には、図２７に示すように再生ボタン８５がｔ１のタイミングで押され、４秒間押され続けてタイミングｔ２に到達すると、タイミングｔ２から４秒遡ってトラックの先頭からタイミングｔ１までのＳＵの個数のカウント値Ｐ１がＩＮＸに書き込まれる。このステップＳ５の処理によりインデックス情報の開始位置が規定される。
【０１３７】
ステップＳ５の処理が完了すると、ステップＳ６において、再生ボタン８５が押されなくなったかどうかが判定される。再生ボタン８５から指が離れ、再生ボタン８５がオフされた場合においてのみステップＳ７に移行し、ステップＳ７において、再生ボタン８５の押され続けた時間に応じたＳＵの個数のカウント値がＸＴに書き込まれる。具体的には、図２７に示すように再生ボタン８５がｔ３のタイミングでオフされたとすると、再生ボタン８５の押され続けた時間（ｔ３−ｔ１）に応じたＳＵの個数のカウント値（Ｐ３−Ｐ１）がＸＴに書き込まれる。このステップＳ７の処理により指定される再生区間の長さが規定される。ステップＳ７の処理が完了すると、再生動作に並行したインデックス管理情報書き込み処理が終了する。
【０１３８】
なお、上述した一実施形態の説明においては、再生ボタン８５を兼用して４秒以上再生ボタン８５が押され続けた場合にインデックス管理情報書き込み処理に移行する場合について説明したが、他のボタンを兼用して押されたタイミングのみならずボタンがオフされるタイミングをも監視して所定時間以上押され続けた場合にインデックス管理情報書き込み処理に移行するようにしても良い。つまり、通常の操作部の監視処理では、配設されたボタンの押されたタイミングのみが各種制御情報を生成するために利用されるが、この発明では、ボタンがオフされるタイミングをも利用し、４秒間以上押されたかどうかの判定処理を用いることにより通常の動作とインデックス管理情報書き込み処理とを区別して操作ボタンの兼用を可能としている。従って、通常の動作とインデックス管理情報書き込み処理とを区別する判定時間は、４秒に限定されるものでなく、誤動作を防止できれば４秒以上でも４秒以下でも良い。
【０１３９】
図２５は、他の実施形態における操作部８０の構成を示す。他の実施形態においては、通常動作用のボタン群８１〜８６以外に専用のインデックスボタン８７が配設されており、このインデックスボタン８７を用いることによりインデックス管理情報の書き込みがなされる。なお、操作部８０においてその操作状態に応じて発生する検出情報は、前述した一実施形態と同様にＣＰＵ７０に供給される。
【０１４０】
例えば、録音ボタン８２が押された場合には、録音動作が開始される。つまり、選択された所定の入力ソースから生成したオーディオデータがメモリカード４０の所定領域に順次書き込まれる。また、再生ボタン８５が押された場合には、再生動作が開始される。つまり、メモリカード４０の所定領域に書き込まれているオーディオデータが順次読み出され、読み出されたオーディオデータに基づいてアナログオーディオ信号が生成されてライン出力端子１９から取り出される。
【０１４１】
また、再生状態において、インデックスボタン８７が押されて使用者により所定時間以上押され続けた場合には、再生動作に並行してインデックス管理情報書き込み処理に移行し、使用者によって任意の再生区間が設定される。具体的には、インデックス管理情報書き込み処理では、インデックスボタン８７の押されたタイミングで規定されるインデックス情報の開始位置を示す情報と、インデックスボタン８７の押され続けた時間を示す情報とがＣＰＵ７０において生成され、これら情報が再生区間を示す情報としてメモリカード４０の所定領域に書き込まれる。
【０１４２】
つまり、再生されている楽曲等において使用者の気に入った特徴的な部分や、所謂ダイジェスト部分が使用者により指定され、その再生区間を示す情報がメモリカード４０の所定領域に書き込まれる。なお、インデックスボタン８７の押されたタイミングで規定されるインデックス情報の開始位置を示す情報は、前述した一実施形態と同様に前述したＡＴＲＡＣ３データファイルＡ３Ｄ−ｎｎｎのＩＮＸに格納され、再生ボタン８５の押され続けた時間を示す情報は、ＸＴに格納される。
【０１４３】
一度、このように使用者の気に入った特徴的な部分や、所謂ダイジェスト部分を特定し、その再生区間を示す情報をメモリカード４０の所定領域に書き込んでおけば、次回からの再生動作に先立って、容易に曲の検索を行うことが可能となり、また、特徴的な部分のみを取りまとめて再生することも可能となる。
【０１４４】
上述したこの発明の他の実施形態について、図２７および図２８を参照してより詳細に説明する。最初に、メモリカードをレコーダに挿入し、再生ボタン８５を押すことによって、再生動作を開始する（ステップＳ１１）。ステップＳ１２では、トラックの先頭かどうかが判定される。トラックの先頭であると判定されると、ＳＵの個数のカウントが開始され、ステップＳ１３に移行する。
【０１４５】
そして、ステップＳ１３において、インデックスボタン８７が押されたかどうかが判定される。インデックスボタン８７が押されたと判定される場合においてのみステップＳ１４に移行する。ステップＳ１４においては、インデックスボタン８７が４秒以上押され続けたかどうかが判定される。インデックスボタン８７が４秒以上押され続けた場合においてのみステップＳ１５に移行し、再生動作に並行してインデックス管理情報書き込み状態になる。インデックス管理情報書き込み状態においては、先ず、トラックの先頭からインデックスボタンボタン８７の押されたタイミングまでのＳＵの個数のカウント値がＩＮＸに書き込まれる。具体的には、図２７に示すようにインデックスボタン８７がｔ１のタイミングで押され、４秒間押され続けてタイミングｔ２に到達すると、タイミングｔ２から４秒遡ってトラックの先頭からタイミングｔ１までのＳＵの個数のカウント値Ｐ１がＩＮＸに書き込まれる。このステップＳ１５の処理によりインデックス情報の開始位置が規定される。
【０１４６】
ステップＳ１５の処理が完了すると、ステップＳ１６において、インデックスボタン８７が押されなくなったかどうかが判定される。インデックスボタン８７から指が離れ、インデックスボタン８７がオフされた場合においてのみステップＳ１７に移行し、ステップＳ１７において、インデックスボタン８７の押され続けた時間に応じたＳＵの個数のカウント値がＸＴに書き込まれる。具体的には、図２７に示すようにインデックスボタン８７がｔ３のタイミングでオフされたとすると、インデックスボタン８７の押され続けた時間（ｔ３−ｔ１）に応じたＳＵの個数のカウント値（Ｐ３−Ｐ１）がＸＴに書き込まれる。このステップＳ１７の処理により指定される再生区間の長さが規定される。ステップＳ１７の処理が完了すると、再生動作に並行したインデックス管理情報書き込み処理が終了する。
【０１４７】
なお、上述した他の実施形態の説明においては、専用のインデックスボタン８７を用い、４秒以上インデックスボタン８７が押され続けた場合にインデックス管理情報書き込み処理に移行する場合について説明したが、配設されたインデックスボタン８７の押されたタイミングのみを利用してインデックス管理情報の書き込みを行うようにしても良い。
【０１４８】
図２９は、インデックスボタン８７の押されたタイミングのみを利用してインデックス管理情報の書き込みを行う場合の処理手順を示す。図２９および図２７を参照して他の実施形態の変形例についてより詳細に説明する。最初に、メモリカードをレコーダに挿入し、再生ボタン８５を押すことによって、再生動作を開始する（ステップＳ２１）。ステップＳ２２では、トラックの先頭かどうかが判定される。トラックの先頭であると判定されると、ＳＵの個数のカウントが開始され、ステップＳ２３に移行する。
【０１４９】
そして、ステップＳ２３において、インデックスボタン８７が０．２秒以上押されたかどうかが判定される。インデックスボタン８７が押されたと判定される場合においてのみステップＳ２４に移行する。ステップＳ２４においては、再びインデックスボタン８７が０．２秒以上押されたかどうかが判定される。なお、ステップＳ２３およびステップＳ２４において、インデックスボタン８７が押されたかどうかを判定するために０．２秒間の判定基準を設けているのは、インデックスボタン８７に対して意図的な操作がなされたかどうかを識別するためで、ただ単に押されたかどうかを判定するようにしても良い。インデックスボタン８７が押されたと判定される場合においてのみステップＳ２５に移行し、再生動作に並行してインデックス管理情報書き込み状態になる。インデックス管理情報書き込み状態においては、先ず、トラックの先頭から最初にインデックスボタンボタン８７の押されたタイミングまでのＳＵの個数のカウント値がＩＮＸに書き込まれる。具体的には、図２７に示すようにインデックスボタン８７がｔ１のタイミングで押され、０．２秒間押され続けてタイミングｔ４に到達すると、タイミングｔ４から０．２秒遡ってトラックの先頭からタイミングｔ１までのＳＵの個数のカウント値Ｐ１がＩＮＸに書き込まれる。このステップＳ２５の処理によりインデックス情報の開始位置が規定される。
【０１５０】
そして、ステップＳ２５の処理が完了すると、ステップＳ２６において、最初のインデックスボタン８７の押されたタイミングから二回目のインデックスボタン８７の押されたタイミングまでの時間に応じたＳＵの個数のカウント値がＸＴに書き込まれる。このステップＳ２６の処理により指定される再生区間の長さが規定される。具体的には、図２７に示すようにインデックスボタン８７がｔ３のタイミングで押され、０．２秒間押され続けてタイミングｔ５に到達すると、タイミングｔ５から０．２秒遡って再生区間の終端のタイミングが規定され、最初のインデックスボタン８７の押されたタイミングから二回目のインデックスボタン８７の押されたタイミングまでの時間（ｔ３−ｔ１）に応じたＳＵの個数のカウント値（Ｐ３−Ｐ１）がＸＴに書き込まれる。ステップＳ２６の処理が完了すると、再生動作に並行したインデックス管理情報書き込み処理が終了する。
【０１５１】
なお、上述した一実施形態および他の実施形態の説明においては、再生ボタン８５が押された再生状態において、所定の操作部材に対して所定操作を行った時にインデックス管理情報の書き込み処理に移行する場合について説明したが、録音ボタン８２が押された録音状態においても、所定の操作部材に対して所定操作がなされた場合に録音動作と並行して、インデックス管理情報の書き込み処理を行うことも可能である。
【０１５２】
この発明では、更に第２０図に示すようにＬＰモードにおいては１２８分の記記録可能時間を設定することができ、例えば４０分のＣＤなら３枚を１枚のメモリカードに収録することができる。このように、１枚のメモリカードに複数枚のアルバムを収録する場合に、各アルバムの代表曲をダイジェスト部分として再生できれば検索に便利である。上記アルバムの代表曲はアルバムからシングルカットされた曲の更にダイジェスト部分であるのが望ましい。
【０１５３】
上記アルバムのダイジェスト部分は例えば図１１に示す再生管理ファイル（ＰＢＬＩＳＴ）の0x0647以降のＩＮＦ- Ｓに記録される。この発明では、図１４に示すようにＩＤ＝７７にアルバムダイジェストが可変長で指定されている。上記再生管理ファイル( ＰＢＬＩＳＴ) に複数枚のアルバムに対して各々ダイジェストポイントを設定する場合には図１４のＩＤ＝１１７を参照して１枚のメモリカードに収録された総アルバム数( 即ち総セット数) を参照してＩＤ＝７７に設定するアルバムダイジェスト数を決定する。既に所定のアルバムに収録されている全曲に対してダイジェスト( ＩＮＸ, ＸＹ) が設定されている場合には、上記アルバムの中から代表曲の曲番号を上記ＩＤ＝７７に設定をしておく。
【０１５４】
アルバムのダイジェスト部分の再生時には上記再生管理ファイル( ＰＢＬＩＳＴ) の0x0647番地以降のＩＮＦ- Ｓを参照してＩＤ＝７７を検索し、そこに設定されているアルバム番号および曲番号を参照することで代表曲を再生する。また、直接ＩＤ＝７７にアルバムの代表曲に対応するダイジェスト情報（ＩＮＸ，ＸＴ）を記録してもよい。
【０１５５】
また、上述した一実施形態および他の実施形態の説明では、インデックス管理情報書き込み状態において、インデックス情報の開始位置を規定する情報としてトラックの先頭からのＳＵの個数のカウント値を用いる場合について説明したが、他の再生位置や再生タイミングを示す情報をＩＮＸに書き込むようにしても良い。また、再生区間の長さを規定する情報として、所定のタイミングの間のＳＵの個数のカウント値を用いる場合について説明したが、他の再生位置や再生タイミングを示す情報をＸＴに書き込むようにしても良い。さらに、インデックス管理情報をＩＮＸおよびＸＴに書き込む場合について説明したが、他の所定の領域にインデックス管理情報を書き込むようにしても良い。
【０１５６】
なお、上述した説明では、オーディオデータの処理に対してこの発明を適用しているが、オーディオデータとビデオデータの両者からなるコンテンツ、またはビデオデータのみからなるコンテンツに対してもこの発明を適用することができる。
【０１５７】
【発明の効果】
この発明では、所定の操作部材に対して所定操作がなされると、再生動作に並行してインデックス管理情報書き込み処理に移行し、使用者によって任意の再生区間を設定することが可能となる。具体的には、インデックス管理情報書き込み処理において、使用者によって再生ボタンの押されたタイミングで規定されるインデックス情報の開始位置を示す情報と、再生ボタンの押され続けた時間を示す情報とが制御部において生成され、これら情報が再生区間を示す情報として半導体メモリの所定領域に書き込まれる。このことにより、再生されている楽曲等において使用者の気に入った特徴的な部分や、所謂ダイジェスト部分を特定することが可能となる。従って、この発明に依れば、曲のインデックス情報をユーザ自身が指定することができ、また、これを用いて容易に検索することができる。このため、記録再生装置の利便性を向上させることができると共に、使い勝手を向上させることができる。
【図面の簡単な説明】
【図１】この発明の不揮発性メモリカードを使用したデジタルオーディオレコーダ／プレーヤーに関するブロック図である。
【図２】この発明に適応されるＤＳＰの内部ブロック図を示す。
【図３】この発明に適応されるメモリカードの内部ブロック図を示す。
【図４】この発明に適応されるメモリカードを記憶媒体とするファイル管理構造を示す模式図である。
【図５】この発明に適応されるメモリカード内のフラッシュメモリのデータの物理的構造を示す。
【図６】この発明に適応されるメモリカード内のデータ構造を示す、
【図７】メモリカード内に記憶されるファイル構造を示す枝図面である。
【図８】メモリカード内に記憶されるサブディレクトリである再生管理ファイルＰＢＬＩＳＴ. ＭＳＦのデータ構造を示す。
【図９】連続した１つのＡＴＲＡＣ３データファイルを所定単位長ごとに分割するとともに属性ファイルを付加した場合のデータ構造図である。
【図１０】この発明のコンバイン編集処理および分割編集処理を説明するための構造図である。
【図１１】再生管理ファイルＰＢＬＩＳＴのデータ構造図を示す。
【図１２】再生管理ファイルＰＢＬＩＳＴのデータ構造図を示す。
【図１３】上記付加情報データの種類の対応表を示す。
【図１４】上記付加情報データの種類の対応表を示す。
【図１５】上記付加情報データの種類の対応表を示す。
【図１６】付加情報データのデータ構造を示す。
【図１７】ＡＴＲＡＣ３データファイルの詳細なデータ構造図である。
【図１８】ＡＴＲＡＣ３データファイルを構成する属性ヘッダーの上段のデータ構造図である。
【図１９】ＡＴＲＡＣ３データファイルを構成する属性ヘッダーの中段のデータ構造図である。
【図２０】録音モードの種類と各録音モードにおける録音時間等を示す表である。
【図２１】コピー制御状態を示す表である。
【図２２】ＡＴＲＡＣ３データファイルを構成する属性ヘッダーの下段のデータ構造図である。
【図２３】ＡＴＲＡＣ３データファイルのデータブロックのヘッダーのデータ構造図である。
【図２４】この発明の一実施形態における操作部近傍部の略線図である。
【図２５】この発明の他の実施形態における操作部近傍部の略線図である。
【図２６】この発明の一実施形態におけるダイジェスト部指定の手順を示すフローチャートである。
【図２７】この発明の一実施形態および他の実施形態におけるダイジェスト部の指定に関するタイミングチャートである。
【図２８】この発明の他の実施形態におけるダイジェスト部指定の手順を示すフローチャートである。
【図２９】この発明の他の実施形態におけるダイジェスト部指定の手順を示すフローチャートである。
【符号の説明】
１０・・・オーディオエンコーダ／デコーダＩＣ、２０・・・セキュリティＩＣ、３０・・・ＤＳＰ、４０・・・メモリカード、４２・・・フラッシュメモリ、５２・・・セキュリティブロック、７０・・・ＣＰＵ、８０・・・操作部、８５・・・再生ボタン、８７・・・インデックスボタン、ＴＲＫＬＩＳＴ．ＭＳＦ・・・トラック情報管理ファイル、ＩＮＦＬＩＳＴ．ＭＳＦ・・・付加情報管理ファイル、Ａ３Ｄｎｎｎ．ＭＳＡ・・・オーディオデータファイル[0001]
BACKGROUND OF THE INVENTION
This invention is a digest related to a program / album. Part It is specified by the user, and the position and period of the specified digest part are recorded in the management area. Regeneration Equipment and regeneration Method About.
[0002]
[Prior art]
An electrically rewritable non-volatile memory called EEPROM (Electrically Erasable Programmable ROM) is composed of two transistors, so it occupies a large area per bit and is limited in increasing the degree of integration. was there. In order to solve this problem, a flash memory capable of realizing one bit with one transistor by the all-bit batch erasing method has been developed. A flash memory is expected to replace a recording medium such as a magnetic disk or an optical disk.
[0003]
There is also known a memory card in which a flash memory is configured to be detachable from a device. If this memory card is used, a digital audio recording / reproducing apparatus using the memory card can be realized in place of a conventional disc-shaped medium such as a CD (compact disc) or an MD (mini disc).
[0004]
In a conventional digital audio recording / reproducing apparatus such as a CD (compact disc) player, the first part (for example, 10 seconds) of each song is automatically reproduced one after another so that the contents recorded on the CD can be immediately grasped. , Intro scan, music scan, etc. However, such a function reproduces only the head portion, and the user may not be able to grasp the contents or characteristics of the song.
[0005]
Conventionally, a playback device has been proposed for specifying the digest portion of a song on a video CD. However, since a video CD cannot be recorded on a playback-only disc, it has been decided in advance by the producer (content holder or record company). The digest part was recorded, and it was impossible for the user to install an arbitrary place of their preference.
[0006]
As another method, it is also conceivable to record a digest portion of a song for each disc designated by the user in a nonvolatile memory built in the disc playback apparatus main body. In this case, the digest portion of the song is associated with the disc identifier and stored in a table, stored in the non-volatile memory, and referred to the disc identifier mounted in the playback device and the table identifier. When the same identifier is determined, the corresponding digest part can be reproduced.
[0007]
[Problems to be solved by the invention]
However, since the digest information is not recorded on the disc, it has to be referred to the table in the main body of the reproducing apparatus one by one, and the processing in the microcomputer is difficult, and it takes time to reproduce. Further, conventionally, digest information for each song has been recorded, but digest information for each album has not been recorded.
[0008]
Therefore, an object of the present invention is to record the digest information of the song specified by the user in the nonvolatile memory. Regeneration Equipment and regeneration Method Is to provide.
[0009]
Another object of the present invention is to record the digest part of a plurality of albums recorded in one non-volatile memory. Regeneration Equipment and regeneration Method Is to provide.
[0010]
[Means for Solving the Problems]
In order to solve the above-described problem, the invention of claim 1 is a reproduction means for reproducing a program from a nonvolatile memory in which the program is recorded,
In parallel with program playback by playback means, It is a characteristic part Index management information that identifies the start and end positions of the digest part By key operation Index management information generating means for generating;
Index management information in nonvolatile memory Management area Recording means for recording against,
Instruction means for instructing reproduction of the digest portion of the program;
When an instruction to play the digest part is input by the instruction means, Each of multiple programs The digest part specified by the index management information Sequentially Control means for controlling the reproduction means to reproduce;
Is a playback device.
[0011]
Claim 4 The invention of Depending on the playback means, A reproduction step of reproducing the program from the nonvolatile memory in which the program is recorded;
In parallel with the playback of the program in the playback step, It is a characteristic part Index management information that identifies the start and end positions of the digest part By key operation An index management information generation step to be generated;
By recording means Index management information in nonvolatile memory Management area Recording steps to record against,
By instruction means An instruction step for instructing playback of the digest portion of the program;
Instructions means When an instruction to play the digest part is input by Each of the multiple programs is controlled by the control unit. The digest part specified by the index management information Sequentially A control step for controlling the reproducing means to reproduce;
Is a playback method.
[0013]
In this invention, since the start address and period of a digest part are set based on a user's input, a user can designate a digest part. Moreover, since the information of the digest part is recorded in the nonvolatile memory, the process of reproducing the digest part can be simplified. Furthermore, digest information of each of a plurality of albums recorded in one nonvolatile memory can be recorded.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described. FIG. 1 shows the overall configuration of a digital audio recorder / player using a memory card according to an embodiment of the present invention. This embodiment is a digital audio signal recording and reproducing device using a removable memory card as a recording medium. More specifically, this recorder / player constitutes an audio system together with an amplifier device, a speaker, a CD player, an MD recorder, a tuner and the like. The present invention can be applied to other audio recorders. That is, the present invention can also be applied to a portable recording / reproducing apparatus. The present invention can also be applied to a set top box for recording digital audio signals distributed via data communication using satellite, digital broadcasting, the Internet, or the like. Furthermore, the present invention can be applied to recording / reproduction of moving image data, still image data, etc. in addition to digital audio signals. In one embodiment, additional information such as images and characters other than digital audio signals can be recorded / reproduced.
[0015]
The recording / reproducing apparatus includes an audio encoder / decoder IC 10, a security IC 20, and a DSP (Digital Signal Processor) 30 each configured by a one-chip IC. Further, a memory card 40 that is detachable from the recording / reproducing apparatus main body is provided. In the memory card 40, a security block including a flash memory (nonvolatile memory), a memory control block, and a DES (Data Encryption Standard) encryption circuit is integrated on a single chip. In this embodiment, the DSP 30 is used, but a microcomputer may be used.
[0016]
The audio encoder / decoder IC 10 includes an audio interface 11 and an encoder / decoder block 12. The encoder / decoder block 12 performs high-efficiency encoding for writing a digital audio signal to the memory card 40 and decodes data read from the memory card 40. As a high-efficiency encoding method, ATRAC3 improved from ATRAC (Adaptive Transform Acoustic Coding) adopted in the mini-disc is used.
[0017]
In the above-described ATRAC3, audio data having a quantization bit of 16 bits sampled at a sampling frequency of 44.1 kHz is subjected to a high-efficiency encoding process. The minimum data unit when processing audio data with ATRAC3 is a sound unit SU. One SU is 1024 samples (1024 × 16 bits × 2 channels) compressed to several hundred bytes, and is about 23 milliseconds in time. Audio data is compressed to about 1/10 by the high-efficiency encoding process described above. Similar to ATRAC1 applied to the mini-disc, in the ATRAC3 system, there is little deterioration in sound quality due to compression / decompression processing of the signal-processed audio signal.
[0018]
The line input selector 13 selectively supplies MD reproduction output, tuner output, and tape reproduction output to the A / D converter 14. The A / D converter 14 converts the input line input signal into a digital audio signal having a sampling frequency = 44.1 kHz and a quantization bit = 16 bits. The digital input selector 16 selectively supplies the digital output of MD, CD, CS (satellite digital broadcast) to the digital input receiver 17. The above digital input is transmitted via an optical cable, for example. The output of the digital input receiver 17 is supplied to the sampling rate converter 15 and converted into a digital audio signal having a sampling frequency of 44.1 kHz and a quantization bit of 16 bits.
[0019]
The encoded data from the encoder / decoder block 12 of the audio encoder / decoder IC 10 is supplied to the DES encryption circuit 22 via the interface 21 of the security IC 20. The DES encryption circuit 22 has a FIFO 23. The DES encryption circuit 22 is provided to protect the copyright of the content. The memory card 40 also incorporates a DES encryption circuit. The DES encryption circuit 22 of the recording / reproducing apparatus has a plurality of master keys and a unique storage key for each device. Further, the DES encryption circuit 22 has a random number generation circuit and can share an authentication and session key with a memory card incorporating the DES encryption circuit. Furthermore, the DES encryption circuit 22 can re-key with the storage key through the DES encryption circuit.
[0020]
The encrypted audio data from the DES encryption circuit 22 is supplied to a DSP (Digital Signal Processor) 30. The DSP 30 communicates with the memory card 40 mounted on the attachment / detachment mechanism (not shown) via the memory interface, and writes the encrypted data in the flash memory. Serial communication is performed between the DSP 30 and the memory card 40. In addition, an external SRAM (Static Random Access Memory) 31 is connected to the DSP 30 in order to secure a memory capacity necessary for controlling the memory card.
[0021]
Further, a bus interface 32 is connected to the DSP 30, and data from an external controller (not shown) is supplied to the DSP 30 via the bus 33. The external controller controls the operation of the entire audio system and gives data such as a recording command and a playback command generated in response to a user operation from the operation unit to the DSP 30 via the bus interface 32. Further, additional information data such as image information and character information is also supplied to the DSP 30 via the bus interface 32. The bus 33 is a bidirectional communication path, and additional information data, control signals, and the like read from the memory card 40 are taken into an external controller via the DSP 30, the bus interface 32, and the bus 33. Specifically, the external controller is included in another device such as an amplifier device included in the audio system. Furthermore, the display for displaying additional information, the operating state of the recorder, and the like is controlled by an external controller. The display unit is shared by the entire audio system. Here, since the data transmitted / received via the bus 33 is not a copyrighted work, it is not encrypted.
[0022]
The encrypted audio data read from the memory card 40 by the DSP 30 is decrypted by the security IC 20 and subjected to the ATRAC3 decryption process by the audio encoder / decoder IC 10. The output of the audio encoder / decoder 10 is supplied to the D / A converter 18 and converted into an analog audio signal. Then, an analog audio signal is taken out to the line output terminal 19.
[0023]
The line output is transmitted to an amplifier device (not shown) and reproduced by a speaker or headphones. A muting signal is supplied to the D / A converter 18 from an external controller. When the muting signal indicates that muting is on, audio output from the line output terminal 19 is prohibited.
[0024]
FIG. 2 shows the internal configuration of the DSP 30. The DSP 30 includes a core 34, a flash memory 35, an SRAM 36, a bus interface 37, a memory card interface 38, and a bus and a bridge between the buses. The DSP 30 has the same function as the microcomputer, and the core 34 corresponds to the CPU. A program for processing of the DSP 30 is stored in the flash memory 35. The SRAM 36 and the external SRAM 31 are used as the RAM.
[0025]
In response to an operation signal such as a recording command received via the bus interfaces 32 and 37, the DSP 30 writes predetermined encrypted audio data and predetermined additional information data to the memory card 40. The process of reading the data from the memory card 40 is controlled. In other words, the DSP 30 is located between the application software of the entire audio system for recording / reproducing audio data and additional information and the memory card 40, and the DSP 30 is operated by software such as access to the memory card 40 and a file system. To do.
[0026]
For the file management on the memory card 40 in the DSP 30, a FAT system used in an existing personal computer is used. In addition to this file system, in one embodiment, a management file having a data structure as described later is used. The management file manages data files recorded on the memory card 40. The management file as the first file management information manages audio data files. The FAT as the second file management information manages the entire file on the flash memory of the memory card 40 including the audio data file and the management file. The management file is recorded on the memory card 40. The FAT is written in the flash memory at the time of shipment together with the root directory and the like. Details of the FAT will be described later.
[0027]
In one embodiment, audio data compressed by ATRAC3 is encrypted in order to protect copyright. On the other hand, the management file is not encrypted because copyright protection is not necessary. In addition, the memory card may be one having an encryption function and one having no encryption function. As in one embodiment, a memory card that supports a recorder that records audio data as a work is only a memory card having an encryption function. A voice recorded by an individual or a recorded image is recorded on the memory card not having the encryption function.
[0028]
FIG. 3 shows the configuration of the memory card 40. The memory card 40 has a control block 41 and a flash memory 42 configured as a one-chip IC. The bidirectional serial interface between the DSP 30 of the player / recorder and the memory card 40 consists of 10 lines. The four main lines are a clock line SCK for transmitting a clock during data transmission, a status line SBS for transmitting status, a data line DIO for transmitting data, and an interrupt line INT. In addition, two GND lines and two VCC lines are provided as power supply lines. Two lines Reserv are undefined lines.
[0029]
The clock line SCK is a line for transmitting a clock synchronized with data.
The status line SBS is a line for transmitting a signal representing the status of the memory card 40. The data line DIO is a line for inputting and outputting commands and encrypted audio data. The interrupt line INT is a line for transmitting an interrupt signal for requesting an interrupt from the memory card 40 to the DSP 30 of the player / recorder. An interrupt signal is generated when the memory card 40 is inserted. However, in this embodiment, since the interrupt signal is transmitted through the data line DIO, the interrupt line INT is grounded.
[0030]
A serial / parallel conversion / parallel / serial conversion / interface block (hereinafter abbreviated as S / P / P / S / IF block) 43 of the control block 41 is connected to the DSP 30 of the recorder connected via the above-described plurality of lines. This is an interface with the control block 41. The S / P / P / S / IF block 43 converts the serial data received from the DSP 30 of the player / recorder into parallel data, imports it into the control block 41, and converts the parallel data from the control block 41 into serial data. It is sent to the DSP 30 of the player / recorder. Further, the S / P / P / S / IF block 43, when receiving a command and data transmitted via the data line DIO, encrypts the command and data for normal access to the flash memory 42, and encryption. Separate necessary commands and data.
[0031]
In the format transmitted via the data line DIO, a command is transmitted first, and then data is transmitted. The S / P / P / S / IF block 43 detects the command code and determines whether the command and data are necessary for normal access or the command and data necessary for encryption. In accordance with the determination result, a command necessary for normal access is stored in the command register 44 and data is stored in the page buffer 45 and the write register 46. An error correction encoding circuit 47 is provided in association with the write register 46. For the data temporarily stored in the page buffer 45, the error correction encoding circuit 47 generates a redundant code of the error correction code.
[0032]
The output data of the command register 44, page buffer 45, write register 46, and error correction coding circuit 47 is supplied to a flash memory interface and sequencer (hereinafter abbreviated as memory I / F / sequencer) 51. The memory IF / sequencer 51 is an interface between the control block 41 and the flash memory 42 and controls data exchange between them. Data is written into the flash memory 42 via the memory IF / sequencer 51.
[0033]
Audio data compressed by ATRAC3 written in the flash memory 42 (hereinafter referred to as ATRAC3 data) is encrypted by the security IC 20 of the player / recorder and the security block 52 of the memory card 40 for copyright protection. It has been done. The security block 52 includes a buffer memory 53, a DES encryption circuit 54, and a nonvolatile memory 55.
[0034]
The security block 52 of the memory card 40 has a plurality of authentication keys and a unique storage key for each memory card. The nonvolatile memory 55 stores a key necessary for encryption, and has a structure that cannot be analyzed even if chip analysis is performed. In this embodiment, for example, a storage key is stored in the nonvolatile memory 55. Furthermore, it has a random number generation circuit, can authenticate with a compatible player / recorder, and can share a session key. The content key is rekeyed with the storage key through the DES encryption circuit 54.
[0035]
For example, mutual authentication is performed when the memory card 40 is attached to a player / recorder. Authentication is performed by the security IC 20 of the player / recorder and the security block 52 of the memory card 40. When the player / recorder authenticates that the installed memory card 40 is a compatible memory card, and authenticates that the other player / recorder is compatible, the player / recorder This means that the authentication process was successful. When authentication is performed, the player / recorder and the memory card 40 each generate a session key and share the session key. A session key is generated for each authentication.
[0036]
When writing content to the memory card 40, the player / recorder encrypts the content key with the session key and passes it to the memory card 40. In the memory card 40, the content key is decrypted with the session key, encrypted with the storage key, and passed to the player / recorder. The storage key is a unique key for each memory card 40. When the player / recorder receives the encrypted content key, the storage key performs a formatting process, and the encrypted content key and the encrypted content key are encrypted. The content is written into the memory card 40
[0037]
The write processing for the memory card 40 has been described above. Hereinafter, the read processing from the memory card 40 will be described. Data read from the flash memory 42 is supplied to the page buffer 45, the read register 48, and the error correction circuit 49 via the memory IF / sequencer 51. Data stored in the page buffer 45 is error-corrected by the error correction circuit 49. The error-corrected page buffer 45 output and read register 48 output are supplied to the S / P / P / S / IF block 43 and supplied to the DSP 30 of the player / recorder via the serial interface described above.
[0038]
At the time of reading, the content key encrypted with the storage key and the content encrypted with the block key are read from the flash memory 42. The security block 52 decrypts the content key with the storage key. The decrypted content key is re-encrypted with the session key and transmitted to the player / recorder side. The player / recorder decrypts the content key with the received session key. The player / recorder generates a block key with the decrypted content key. Using this block key, the encrypted ATRAC3 data is sequentially decrypted.
[0039]
The ConfigROM 50 is a memory that stores version information of the memory card 40, various attribute information, and the like. Further, the memory card 40 is provided with an erroneous erasure prevention switch 60 that can be operated by the user as needed. When the switch 60 is in the erase prohibition connection state, even if a command for instructing to erase the flash memory 42 is sent from the recorder side, the erase of the flash memory 42 is prohibited. Further, OSC Cont. 61 is an oscillator that generates a clock that is a timing reference for processing of the memory card 40.
[0040]
FIG. 4 shows a file system processing hierarchy of a computer system using a memory card as a storage medium. As the file system processing hierarchy, the application processing layer is the highest level, and below this, a file management processing layer, a logical address management layer, a physical address management layer, and a flash memory access are sequentially stacked. In the above hierarchical structure, the file management processing layer is a FAT system. The physical address is assigned to each block of the flash memory, and the correspondence between the block and the physical address is unchanged. The logical address is an address logically handled by the file management processing layer.
[0041]
FIG. 5 shows an example of a physical configuration of data in the flash memory 42 in the memory card 40. In the flash memory 42, a data unit called a segment is divided into a predetermined number of blocks (fixed length), and one block is divided into a predetermined number of pages (fixed length). In the flash memory 42, erasing is collectively performed in units of blocks, and writing and reading are performed in units of pages. Each block and each page have the same size, and one block is composed of page 0 to page m. One block has a capacity of, for example, 8 KB (K bytes) bytes or 16 KB, and one page has a capacity of 512 B. The entire flash memory 42 has 4 MB (512 blocks) and 8 MB (1024 blocks) when 1 block = 8 KB, and 16 MB (1024 blocks), 32 MB (2048 blocks), 64 MB (1 block = 16 KB). 4096 blocks).
[0042]
One page consists of a 512-byte data part and a 16-byte redundant part. The first 3 bytes of the redundant portion are an overwrite portion that is rewritten in accordance with the data update. The block status, page status, and update status are recorded in each of the 3 bytes in order from the top. The contents of the remaining 13 bytes of the redundant part are basically fixed according to the contents of the data part. 13 bytes are composed of a management flag (1 byte), a logical address (2 bytes), a format reserve area (5 bytes), distributed information ECC (2 bytes), and data ECC (3 bytes). The distributed information ECC is redundant data for error correction with respect to the management flag, logical address, and format reserve, and the data ECC is redundant data for error correction with respect to 512-byte data.
[0043]
As a management flag, a system flag (its value is 1: user block, 0: boot block), conversion table flag (1: invalid, 0: table block), copy prohibition designation (1: OK, 0: NG), access permission Each flag (1: free, 0: read protect) is recorded.
[0044]
The first two blocks 0 and 1 are boot blocks. Block 1 is for backup in which the same data as block 0 is written. The boot block is a head block of valid blocks in the card, and is a block that is first accessed when a memory card is loaded into the device. The remaining blocks are user blocks. A header, system entry, and boot & attribute information are stored in the first page 0 of the boot block. Page 1 stores use-prohibited block data. Page 2 stores CIS (Card Information Structure) / IDI (Identify Drive Information).
[0045]
In the boot block header, a boot block ID and the number of valid entries in the boot block are recorded. In the system entry, the start position of the prohibited block data, its data size, data type, CIS / IDI data start position, its data size, and data type are recorded. Boot & attribute information includes memory card type (read only, readable and writable, hybrid of both types, etc.), block size, number of blocks, total number of blocks, security support, and data related to card manufacturing. (Production date, etc.) are recorded.
[0046]
In the flash memory, the data is rewritten, the insulating film is deteriorated, and the number of rewrites is limited. Therefore, it is necessary to prevent repeated and concentrated access to a certain storage area (block). Therefore, when rewriting the data of a certain logical address stored at a certain physical address, the flash memory file system does not rewrite the updated data to the same block, but rewrites the unused block. The updated data is written. As a result, the correspondence between the logical address and the physical address before the data update changes after the update. By performing the swap process, it is possible to prevent the same block from being repeatedly accessed intensively and to extend the life of the flash memory.
[0047]
Since the logical address is attached to the data once written to the block, even if the block in which the pre-update data and the post-update data are moved moves, the same address can be seen from the FAT. Subsequent access can be performed appropriately. Since the correspondence relationship between the logical address and the physical address is changed by the swap processing, a logical-physical address conversion table indicating the correspondence between the two is required. By referring to this table, the physical address corresponding to the logical address specified by the FAT is specified, and the block indicated by the specified physical address can be accessed.
[0048]
The logical-physical address conversion table is stored on the SRAM by the DSP 30. If the RAM capacity is small, it can be stored in the flash memory. This table is generally a table in which physical addresses (2 bytes) are associated with logical addresses (2 bytes) arranged in ascending order. Since the maximum capacity of the flash memory is 128 MB (8192 blocks), 8192 addresses can be represented by 2 bytes. The logical-physical address conversion table is managed for each segment, and its size increases according to the capacity of the flash memory. For example, when the capacity of the flash memory is 8 MB (2 segments), two pages are used for the logical-physical address conversion table for each of the two segments. When the logical-physical address conversion table is stored in the flash memory, whether or not the block is a block in which the logical-physical address conversion table is stored according to a predetermined 1 bit of the management flag in the redundant portion of each page described above. Is instructed.
[0049]
The above-mentioned memory card can be used by a FAT system of a personal computer as well as a disk-shaped recording medium. Although not shown in FIG. 5, an IPL area, a FAT area, and a root directory area are provided on the flash memory. In the IPL area, an address where a program to be loaded into the memory of the recorder first is written and various information of the memory are written. In the FAT area, related items of blocks (clusters) are written. The FAT defines values indicating an unused block, the next block number, a bad block, and the last block. Furthermore, directory entries (file attributes, update date, start cluster, file size, etc.) are written in the root directory area.
[0050]
FIG. 6 illustrates a management method based on FAT management. FIG. 6 shows a schematic diagram in the memory. From the top, the partition table portion, free space, boot sector, FAT region, FAT copy region, Root Directory region, Sub
A directory area and a data area are stacked. The memory map is a memory map after conversion from a logical address to a physical address based on a logical-physical address conversion table.
[0051]
The boot sector, the FAT area, the FAT copy area, the root directory area, the sub directory area, and the data area are collectively referred to as a FAT partition area.
[0052]
In the partition table section described above, the start and end addresses of the FAT partition area are recorded. The FAT normally used for floppy disks does not have a partition table section. The first track has an empty area because nothing other than the partition table is placed.
[0053]
Next, in the boot sector, the size of the FAT structure, the cluster size, and the size of each area are recorded according to either the 12-bit FAT or the 16-bit FAT. The FAT manages file positions recorded in the data area. The FAT copy area is a FAT backup area. In the root directory part, a file name, a head cluster address, and various attributes are recorded, and 32 bytes are used for each file.
[0054]
The subdirectory portion exists as a file having a file attribute called a directory. In the embodiment of FIG. MSF, CAT. MSA, DOG. There are four files, MSA and MAN. In this subdirectory part, file names and recording positions on the FAT are managed. That is, in FIG. An address on the FAT of “5” is managed in the slot in which the file name of MSA is recorded. In the slot in which the file name MSA is recorded, an address on the FAT of “10” is managed.
[0055]
The cluster 2 and later are actual data areas. In this embodiment, audio data compressed by ATRAC3 is recorded in this data area. Furthermore, a FAT address “110” is managed in the slot in which the file name “MAN.MSA” is recorded.
[0056]
In the embodiment of the present invention, CAT. Audio data compressed by ATRAC3 having a file name of MSA is recorded, and DOG. Audio data in which DOG-1 which is the first half part of the file name MSA is compressed by ATRAC3 is recorded, and DOG. Audio data in which DOG-2, which is the latter half part of the file name MSA, is compressed by ATRAC3 is recorded. Further, MAN. Audio data compressed by ATRAC3 having a file name of MSA is recorded.
[0057]
In this embodiment, an example is shown in which a single file is divided into two and recorded discretely. An area labeled Empty on the data area is a recordable area.
[0058]
The cluster 200 and subsequent areas are areas for managing file names. A file called MSA is stored in the cluster 201 at DOG. A file called MSA is stored in the cluster 202 as MAN. A file called MSA is recorded. When rearranging the file order, the rearrangement may be performed after the cluster 200.
[0059]
When the memory card of this embodiment is inserted for the first time, the start and end addresses of the FAT partition area are recorded with reference to the head partition table section. After the boot sector part is reproduced, the root directory and sub directory parts are reproduced. Then, the playback management information PBLIST. Recorded in the Sub Directory part is recorded. The slot in which the MSF is recorded is searched and PBLIST. Reference is made to the address of the end of the slot in which the MSF is recorded.
[0060]
In this embodiment, PBLIST. Since the address “200” is recorded at the end of the slot in which the MSF is recorded, the cluster 200 is referred to. The cluster 200 and later are areas for managing file names and managing the playback order of files. In this embodiment, a file called CAT.MSA is the first song, and DOG. The file MSA is the second song, and MAN. The file called MSA is the third song.
[0061]
Here, when all of the clusters 200 and thereafter are referred to, the process moves to the subdirectory section, and CAT. MSA, DOG. MSA and MAN. Refer to the slot that matches the file name MSA. In FIG. 6, CAT. An address “5” is recorded at the end of the slot in which the file name MSA is recorded, and an address “10” is recorded at the end of the slot in which the file DOG.MSA is recorded. An address 110 is recorded at the end of the slot in which the file MSA is recorded.
[0062]
CAT. Based on the address “5” recorded at the end of the slot in which the file name MSA is recorded, the entry address on the FAT is searched. In the entry address 5, the cluster address “6” is entered. When the entry address “6” is referred to, the cluster address “7” is entered, and when the entry address “7” is referenced, “8” is entered. ”Is entered, and when the entry address“ 8 ”is referenced, a code indicating the end of“ FFF ”is recorded.
[0063]
Therefore, CAT. The file MSA uses the cluster areas of clusters 5, 6, 7, and 8. By referring to the clusters 5, 6, 7, and 8 of the data area, the CAT. An area where ATRAC3 data called MSA is actually recorded can be accessed.
[0064]
Next, a method of searching for a file called DOG.MSA recorded discretely will be described below. An address “10” is recorded at the end of the slot in which the file name “DOG.MSA” is recorded. Here, the entry address on the FAT is searched based on the address “10”. In the entry address 10, a cluster address “11” is entered. When an entry address “11” is referred to, a cluster address “12” is entered. When an entry address “12” is referenced, “100” is entered. ”Is entered. Further, when referring to the entry address “100”, a cluster address “101” is entered, and when referring to the entry address “101”, a code indicating the end of FFF is recorded.
[0065]
Therefore, DOG. The file MSA uses the cluster areas of clusters 10, 11, 12, and 10101. By referring to the clusters 10, 11, and 12 of the data area, DOG. An area in which ATRAC3 data corresponding to the first half part of the file called MSA is actually recorded can be accessed. Further, by referring to the clusters 100 and 101 in the data area, DOG. An area in which ATRAC3 data corresponding to the latter half part of the file called MSA is actually recorded can be accessed.
[0066]
Furthermore, MAN. The entry address on the FAT is searched based on the address “110” recorded at the end of the slot in which the file name MSA is recorded. In the entry address 110, a cluster address “111” is entered, and when an entry address “111” is referred to, a code indicating the end point “FFF” is recorded.
[0067]
Therefore, MAN. The file MSA uses the cluster areas 110 and 111. By referring to the clusters 110 and 111 in the data area, the MAN. An area where ATRAC3 data called MSA is actually recorded can be accessed.
[0068]
As described above, the data files recorded discretely on the flash memory can be linked and reproduced sequentially.
[0069]
In this embodiment, separately from the file management system defined by the format of the memory card 40 described above, a management file for managing each track and the parts constituting each track is provided for the music file. I am doing so. This management file is recorded on the flash memory 42 using the user block of the memory card 40. As a result, as will be described later, even if the FAT on the memory card 40 is broken, the file can be restored.
[0070]
This management file is created by the DSP 30. For example, when the power is turned on for the first time, it is determined whether or not the memory card 40 is attached. When the memory card is attached, authentication is performed. When the authentication confirms that the memory card is a regular memory card, the boot block of the flash memory 42 is read into the DSP 30. Then, the logical-physical address conversion table is read. The read data is stored in the SRAM. Even for a memory card that the user purchases for the first time, FAT and a root directory are written in the flash memory 42 at the time of shipment. The management file is created when recording is performed.
[0071]
That is, a recording command generated by a user's remote control or the like is given from the external controller to the DSP 30 via the bus and the bus interface 32. The received audio data is compressed by the encoder / decoder IC 10, and ATRAC3 data from the encoder / decoder IC 10 is encrypted by the security IC 20. The DSP 30 records the encrypted ATRAC3 data in the flash memory 42 of the memory card 40. After this recording, the FAT and management file are updated. Each time the file is updated, specifically, the recording of the audio data is started and the recording of the FAT and the management file is rewritten on the SRAMs 31 and 36 each time the recording is finished. When the memory card 40 is removed or the power is turned off, the final FAT and management file are stored in the flash memory 42 of the memory card 40 from the SRAMs 31 and 36. In this case, the FAT and management file on the flash memory 42 may be rewritten each time recording of audio data is started and recording is ended. Even when editing is performed, the contents of the management file are updated.
[0072]
Further, in the data configuration of this embodiment, additional information is also created and updated in the management file and recorded on the flash memory 42. In another data structure of the management file, the additional information management file is created separately from the management file for track management. The additional information is given from the external controller to the DSP 30 via the bus and the bus interface 32. The additional information received by the DSP 30 is recorded on the flash memory 42 of the memory card 40. The additional information is not encrypted because it does not pass through the security IC 20. The additional information is written from the SRAM of the DSP 30 to the flash memory 42 when the memory card 40 is removed or the power is turned off.
[0073]
FIG. 7 shows the overall file structure of the memory card 40. There are still image directories, moving image directories, Voice directories, control directories, and music (HIFI) directories. Since this embodiment performs recording / reproduction of music, the music directory will be described below. Two types of files are placed in the music directory. One of them is the reproduction management file PBLIST. MSF (hereinafter simply referred to as PBLIST), and the other is an ATRAC3 data file A3Dnnnn. MSA (hereinafter simply referred to as A3Dnnn). The maximum number of ATRAC3 data files is specified up to 400. In other words, up to 400 songs can be recorded. The ATRAC3 data file is arbitrarily created by the device after being registered in the reproduction management file.
[0074]
FIG. 8 shows the structure of a reproduction management file, and FIG. 9 shows the structure of an ATRAC3 data file of 1 FILE (one song). The reproduction management file is a 16 KB fixed length file. The ATRAC3 data file is composed of a leading attribute header followed by actual encrypted music data in units of music. The attribute header also has a fixed length of 16 KB and has a configuration similar to that of the reproduction management file.
[0075]
The playback management file shown in FIG. 8 includes a header, a 1-byte code memory card name NM1-S, a 2-byte code memory card name NM2-S, a song order playback table TRKTBL, and additional information INF- of the entire memory card. S. The attribute header at the head of the data file shown in FIG. 9 includes a header, a 1-byte code song name NM1, a 2-byte code song name NM2, track key information such as track information TRKINF, parts information PRTINF, and track additional information INF. Consists of. The header includes information on the total number of parts, name attributes, size of additional information, and the like.
[0076]
The ATRAC3 music data follows the attribute header. The music data is divided into 16 KB blocks, and a header is added to the head of each block. The header includes an initial value for decrypting the encryption. Note that only the music data in the ATRAC3 data file is subjected to the encryption process, and the other reproduction management file, header data, etc. are not encrypted.
[0077]
With reference to FIG. 10, the relationship between a song and an ATRAC3 data file will be described. One track means one song. One song is composed of one ATRAC3 data file (see FIG. 9). The ATRAC3 data file is audio data compressed by ATRAC3. The memory card 40 is recorded in units called clusters. One cluster has a capacity of 16 KB, for example. Multiple files are not mixed in one cluster. The minimum unit for erasing the flash memory 42 is one block. In the case of the memory card 40 used for recording music data, a block and a cluster are synonyms, and 1 cluster = 1 sector is defined.
[0078]
One song is basically composed of one part, but if editing is performed, one song may be composed of a plurality of parts. A part means a unit of data recorded within a continuous time from the start of recording to the stop thereof, and usually one track is composed of one part. The connection of the parts in the music is managed by the part information PRTINF in the attribute header of each music. That is, the part size is represented by 4-byte data called the part size PRTSIZE in PRTINF. The first 2 bytes of the part size PRTSIZE indicate the total number of clusters held by the part, and each subsequent 1 byte indicates the position of the start sound unit (hereinafter abbreviated as SU) and the position of the end SU in the first and last clusters. . By having such a part description method, it is possible to eliminate the movement of a large amount of music data that is normally required when editing music data. If the editing is limited to the block unit, the movement of the music data can be similarly avoided, but the editing unit is too large for the block unit compared to the SU unit.
[0079]
SU is the minimum unit of parts, and is the minimum data unit when audio data is compressed by ATRAC3. The SU is data of several hundred bytes obtained by compressing audio data of 1024 samples (1024 × 16 bits × 2 channels) obtained at a sampling frequency of 44.1 kHz to about 1/10. One SU is about 23 milliseconds in terms of time. Usually, one part is composed of thousands of SUs. When one cluster is composed of 42 SUs, a sound of about 1 second can be represented by one cluster. The number of parts constituting one track is affected by the additional information size. Since the number of parts is determined by the number of headers, music titles, additional information data, etc. removed from one block, a state where there is no additional information is a condition for using the maximum number (645) of parts.
[0080]
FIG. 10A shows a file structure in the case where two pieces of audio data from a CD or the like are recorded continuously. The first song (file 1) is composed of, for example, 5 clusters. Between the first song and the second song (file 2), two files cannot be mixed in one cluster, so file 2 is created from the beginning of the next cluster. Therefore, the end of the part 1 corresponding to the file 1 (end of the first music piece) is located in the middle of the cluster, and no data exists in the remaining part of the cluster. The second song (file 2) is similarly composed of one part. In the case of file 1, the part size is 5, the start cluster SU is 0, and the end cluster is 4.
[0081]
As editing operations, four types of operations are defined: divide, combine, erase, and move. Divide is to divide one track into two. When the divide is performed, the total number of tracks increases by one. The divider divides one file on the file system into two files, and updates the reproduction management file and the FAT. Combine is to combine two tracks into one. When combined, the total number of tracks decreases by one. Combine combines two files on the file system into one file, and updates the playback management file and FAT. Erase is to erase a track. The track number after deletion is reduced by one. Move is to change the track order. As described above, the reproduction management file and the FAT are also updated for the erase and move processes.
[0082]
The result of combining the two songs (file 1 and file 2) shown in FIG. 10A is shown in FIG. 10B. The combined result is a single file, which consists of two parts. FIG. 10C shows the result of dividing one song (file 1) in the middle of cluster 2. Due to the divide, a file 1 consisting of clusters 0 and 1 and the front side of cluster 2 and a file 2 consisting of the rear side of cluster 2 and clusters 3 and 4 are generated.
[0083]
As described above, in this embodiment, since there is a description method regarding parts, in FIG. 10B which is a result of the combination, the start position of part 1, the end position of part 1, the start position of part 2, and the end of part 2 Each position can be defined in SU units. As a result, it is not necessary to move the music data of part 2 in order to close the gap between the joint results. In addition, since there is a description method related to parts, it is not necessary to move data so as to fill the empty space at the top of file 2 in FIG.
[0084]
FIG. 11 shows a more detailed data structure of the reproduction management file PBLIST, and FIGS. 12A and 12B show a header and other parts constituting the reproduction management file PBLIST. The reproduction management file PBLIST has a size of one cluster (1 block = 16 KB). The header shown in FIG. 12A consists of 32 bytes. 12B includes a name NM1-S (256 bytes), a name NM2-S (512 bytes), CONTENTSKEY, MAC, and S-YMDhms for the entire memory card, and a table TRKTBL (800 for managing the playback order) Bytes), additional information INF-S (14720 bytes) for the entire memory card, and finally a part of the information in the header is recorded again. The head of each of these different types of data groups is defined to be a predetermined position in the reproduction management file.
[0085]
The playback management file has a header of 32 bytes from the beginning represented by (0x0000) and (0x0010) shown in FIG. 12A. A unit divided by 16 bytes from the beginning in the file is called a slot. In the headers arranged in the first and second slots of the file, data having the following meanings, functions, and values are arranged in order from the top. Note that the data described as Reserved represents undefined data. Normally, null (0x00) is written, but the Reserved data is ignored no matter what is written. There may be changes in future versions. Also, writing to this part is prohibited. When the part written as Option is not used, it is all handled in the same manner as Reserved.
[0086]
BLKID-TL0 (4 bytes)
Meaning: BLOCKID FILE ID
Function: Value used to identify the beginning of the playback management file
Value: Fixed value = “TL = 0” (for example, 0x544C2D30)
MCode (2 bytes)
Meaning: MAKER CODE
Function: A code that identifies the manufacturer and model of the recorded device
Value: Upper 10 bits (maker code) Lower 6 bits (model code)
REVISION (4 bytes)
Meaning: Number of rewrites of PBLIST
Function: Incremented each time the playback management file is rewritten
Value: Starts from 0 and increases by +1
S-YMDhms (4 bytes) (Option)
Meaning: Year, month, day, hour, minute, second recorded on a device with a reliable clock
Function: Value for identifying the last recording date

[0087]
SN1C + L (2 bytes)
Meaning: Indicates the attribute of the name (1 byte) of the memory card written in the NM1-S area
Function: Each character code and language code to be used is represented by 1 byte.
Value: Character code (C) is the upper 1 byte and distinguishes characters as follows
00: No character code is set. Treat as a simple binary number
01: ASCII (American Standard Code for Information Interchange)
02: ASCII + KANA 03: modifided8859-1
81: MS-JIS 82: KS C 5601-1989 83: GB (Great Britain) 2312-80
90: S-JIS (Japanese Industrial Standards) (for Voice).
[0088]
The language code (L) is the low-order byte and distinguishes languages according to the EBU Tech 3258 standard as shown below.
00: Not set 08: German 09: English 0A: Spanish
0F: French 15: Italian 1D: Dutch
65: Korean 69: Japanese 75: Chinese
Set to zero when there is no data.
[0089]
SN2C + L (2 bytes)
Meaning: Indicates the attribute of the name (2 bytes) of the memory card written in the NM2-S area
Function: Each character code and language code to be used is represented by 1 byte.
Value: Same as SN1C + L mentioned above
SINFSIZE (2 bytes)
Meaning: Indicates the total size of all the additional information related to the entire memory card written in the INF-S area.
Function: Describes the data size in units of 16 bytes. If there is no data size, be sure to set it to all zeros.
Value: Size is from 0x0001 to 0x39C (924)
T-TRK (2 bytes)
Meaning: TOTAL TRACK NUMBER
Function: Total number of tracks
Value: 1 to 0x0190 (maximum 400 tracks), all zeros if there is no data
VerNo (2 bytes)
Meaning: Format version number
Function: Major version number at the top, minor version number at the bottom

[0090]
Data (FIG. 13B) written in the area following the header described above will be described below.
[0091]
NM1-S
Meaning: 1-byte name for the entire memory card
Function: Variable length name data expressed in 1-byte character code (256 at maximum)
The end code (0x00) must be written at the end of the name data.
The size should be calculated from this end code. If there is no data, record at least 1 byte of null (0x00) from the beginning (0x0020).
Value: Various character codes
NM2-S
Meaning: 2-byte name for the entire memory card
Function: Variable-length name data expressed in 2-byte character code (maximum 512)
The end code (0x00) must be written at the end of the name data.
The size should be calculated from this end code. If there is no data, record at least 2 bytes of null (0x00) from the beginning (0x0120).
Value: Various character codes.
[0092]
CONTENTS KEY
Meaning: The value prepared for each song is protected by MG (M) and stored. Here, the same value as CONTENTS KEY attached to the first song
Function: A key required for MAC calculation of S-YMDhms
Value: From 0 to 0xFFFFFFFFFFFFFFFF
MAC
Meaning: Copyright information alteration check value
Function: Value created from S-YMDhms content and CONTENTS KEY
Value: from 0 to 0xFFFFFFFFFFFFFFFF.
[0093]
TRK-nnn
Meaning: SQN (sequence) number of the ATRAC3 data file to be played
Function: Describes FNo in TRKINF
Value: 1 to 400 (0x190)
Set to zero when there is no track
INF-S
Meaning: Additional information data related to the entire memory card (eg information such as photos, lyrics, commentary, etc.)
Function: Additional information data of variable length with header
A plurality of different additional information may be arranged. Each is assigned an ID and a data size. Additional information data including individual headers is composed of a minimum of 16 bytes and an integer multiple of 4 bytes.
For details, see Value: Additional information data structure described later.
S-YMDhms (4 bytes) (Option)
Meaning: Year, month, day, hour, minute, second recorded on a device with a reliable clock
Function: Value for identifying the last recording date and time, mandatory for EMD

[0094]
As the last slot of the reproduction management file, the same BLKID-TL0, MCode, and REVISION as those in the header are written.
[0095]
As a consumer audio device, a memory card may be removed during recording or the power may be cut off, and it is necessary to detect the occurrence of these abnormalities when the memory card is restored. As described above, REVISION is written at the beginning and end of the block, and each time this value is rewritten, it is incremented by +1. If an abnormal end occurs in the middle of a block, the values of the REVISION at the beginning and end do not match, and the abnormal end can be detected. Since there are two REVISIONs, abnormal termination can be detected with high probability. When an abnormal end is detected, a warning such as an error message is generated.
[0096]
In addition, since the fixed value BLKID-TL0 is inserted at the beginning of one block (16 KB), the fixed value can be used as a guideline for restoration when the FAT is broken. That is, the file type can be determined by looking at the fixed value at the beginning of each block. Moreover, since the fixed value BLKID-TL0 is described twice in the header of the block and the end portion of the block, the reliability of the fixed value BLKID-TL0 can be checked. Note that the same reproduction management file PBLIST may be recorded twice.
[0097]
The ATRAC3 data file has a considerably larger data amount than the track information management file, and the ATRAC3 data file is assigned a block number BLOCK SERIAL as will be described later. However, since the ATRAC3 data file normally has multiple files on the memory card, if the contents are differentiated with CONNUM0 and BLOCK SERIAL is not attached, duplication occurs and the FAT is broken. Recovery becomes difficult. In other words, a single ATRAC3 data file is composed of a plurality of BLOCKs and may be arranged in a discrete manner. Therefore, CONNUM0 is used to discriminate BLOCKs constituting the same ATRAC3 data file and the same. The ascending / descending order in the ATRAC3 data file is determined by the block number BLOCK SERIAL.
[0098]
Similarly, if the FAT is not destroyed, but the logic is inadvertently inconvenient as a file, the manufacturer code (MCode) is placed at the beginning and end of the block so that the manufacturer's model can be specified. It is recorded.
[0099]
FIG. 12C shows the configuration of additional information data. The following header is written at the head of the additional information. Variable length data is written after the header.
[0100]
INF
Meaning: FIELD ID
Function: Fixed value indicating the beginning of additional information data
Value: 0x69
ID
Meaning: Additional information key code
Function: Indicates the classification of additional information
Value: 0 to 0xFF
SIZE
Meaning: Size of individual additional information
Function: The data size is free, but it must be an integer multiple of 4 bytes. It must be at least 16 bytes. If there is a remainder from the end of the data, fill it with null (0x00)
Value: 16 to 14784 (0x39C0)
MCode
Meaning: MAKER CODE
Function: A code that identifies the manufacturer and model of the recorded device
Value: Upper 10 bits (maker code) Lower 6 bits (model code)
C + L
Meaning: Indicates the attribute of the character written in the data area from the 12th byte from the beginning.
Function: Each character code and language code to be used is represented by 1 byte.
Value: Same as above SNC + L
DATA
Meaning: Individual additional information data
Function: Represents variable length data. The head of the actual data always starts from the 12th byte, and the length (size) must be at least 4 bytes and always an integer multiple of 4 bytes. If there is a remainder from the end of the data, fill it with null (0x00)
Value: Defined individually by content.
[0101]
FIG. 13 shows an example of the correspondence between the additional information key code value (0 to 63) and the type of additional information. A key code value (0 to 31) is assigned to character information related to music, and (32 to 63) is assigned to a URL (Uniform Resource Locator) (Web related). Character information such as album title, artist name, and CM is recorded as additional information.
[0102]
FIG. 14 shows an example of correspondence between additional information key code values (64 to 127) and additional information types. Key code values (64 to 95) are assigned to paths / others, and (96 to 127) are assigned to control / numerical value / data relationships. For example, in the case of (ID = 98), the additional information is TOC (Table of Content) -ID. The TOC-ID indicates the first song number, the last song number, the song number, the total performance time, and the song performance time based on the TOC information of the CD (compact disc).
[0103]
FIG. 15 shows an example of correspondence between additional information key code values (128 to 159) and types of additional information. Key code values (128 to 159) are assigned to the synchronous reproduction relationship. EMD (Electronic Music Distribution) in FIG. 15 means electronic music distribution.
[0104]
A specific example of additional information data will be described with reference to FIG. FIG. 16A shows the data structure of additional information, as in FIG. 12C. FIG. 16B shows an example in which the key code ID = 3 and the additional information is the artist name. SIZE = 0x1C (28 bytes), indicating that the data length of this additional information including the header is 28 bytes. Further, C + L is set to character code C = 0x01, and language code L = 0x09. This value indicates an ASCII language in ASCII code according to the above-mentioned rules. Then, the artist name data “SIMON & GRAFUNKEL” is written with 1 byte data from the 12th byte from the top. Since the size of the additional information is determined to be an integral multiple of 4 bytes, the remainder of 1 byte is (0x00).
[0105]
FIG. 16C shows an example in which the key code ID = 97 and the additional information is ISRC (International Standard Recording Code). SIZE = 0x14 (20 bytes), indicating that the data length of this additional information is 20 bytes. In addition, C + L is set to C = 0x00 and L = 0x00, which indicates that there is no character or language setting, that is, that the data is binary. Then, an 8-byte ISRC code is written as data. ISRC indicates copyright information (country, owner, recording year, serial number).
[0106]
FIG. 16D shows an example in which the key code ID = 97 and the additional information is the recording date and time. SIZE = 0x10 (16 bytes), indicating that the data length of this additional information is 16 bytes. Also, C + L is set to C = 0x00 and L = 0x00, which indicates that no character or language is set. Then, a 4-byte (32-bit) code is written as data, and the recording date and time (year, month, day, hour, minute, second) is expressed.
[0107]
FIG. 16E is an example in which the additional information with the key code ID = 107 is the reproduction log. SIZE = 0x10 (16 bytes), indicating that the data length of this additional information is 16 bytes. Also, C + L is set to C = 0x00 and L = 0x00, which indicates that no character or language is set. A 4-byte (32-bit) code is written as data, and a reproduction log (year, month, day, hour, minute, second) is represented. Those having a reproduction log function record 16 bytes of data for each reproduction.
[0108]
FIG. 17 shows a data array of the ATRAC3 data file A3Dnnnn when 1 SU is N bytes (for example, N = 384 bytes). FIG. 17 shows a data file attribute header (1 block) and a music data file (1 block). In FIG. 17, the first byte (0x0000 to 0x7FF0) of each slot of the two blocks (16 × 2 = 32 Kbytes) is shown. As shown separately in FIG. 18, the first 32 bytes of the attribute header are the header, 256 bytes are the song title area NM1 (256 bytes), and 512 bytes are the song title area NM2 (512 bytes). The following data is written in the header of the attribute header.
[0109]
BLKID-HD0 (4 bytes)
Meaning: BLOCKID FILE ID
Function: Value for identifying the beginning of an ATRAC3 data file
Value: Fixed value = “HD = 0” (for example, 0x48442D30)
MCode (2 bytes)
Meaning: MAKER CODE
Function: A code that identifies the manufacturer and model of the recorded device
Value: Upper 10 bits (maker code) Lower 6 bits (model code)
BLOCK SERIAL (4 bytes)
Meaning: Serial number assigned to each track
Function: The beginning of the block starts at 0 and the next block is incremented by +1
Does not change value when edited
Value: Start from 0 to 0xFFFFFFFF.
[0110]
N1C + L (2 bytes)
Meaning: Indicates the attribute of track (song title) data (NM1)
Function: Character code and language code used for NM1 are represented by 1 byte each.
Value: Same as SN1C + L
N2C + L (2 bytes)
Meaning: Indicates the attribute of track (song title) data (NM2)
Function: Character code and language code used for NM2 are represented by 1 byte each.
Value: Same as SN1C + L
INFSIZE (2 bytes)
Meaning: Indicates the total size of all additional information about the track
Function: Describes the data size in units of 16 bytes. If there is no data size, be sure to set it to all zeros.
Value: Size is from 0x0000 to 0x3C6 (966)
T-PRT (2 bytes)
Meaning: Total number of parts
Function: Indicates the number of parts that make up the track. Usually 1
Value: 1 to 0x285 (645dec)
T-SU (4 bytes)
Meaning: Total number of SU
Function: Represents the actual total number of SUs in a track. Equivalent to the performance time of a song
Value: 0x01 to 0x001FFFFF
INX (2 bytes) (Option)
Meaning: INDEX relative location
Function: Pointer that indicates the beginning of the rust part (characteristic part) of the song. The position from the beginning of the song is specified by a number that is 1/4 of the number of SUs. This is equivalent to 4 times longer than normal SU (approximately 93 ms).
Value: 0 to 0xFFFF (maximum, approximately 6084 seconds)
XT (2 bytes) (Option)
Meaning: INDEX playback time
Function: Designates the number of SUs for the time to be reproduced from the head designated by INX-nnn by a quarter. This is equivalent to 4 times longer than normal SU (approximately 93 ms).
Value: 0x0000: No setting 0x01 to 0xFFFE (maximum 6084 seconds)
0xFFFF: Until the end of the song.
[0111]
Next, the song title areas NM1 and NM2 will be described.
[0112]
NM1
Meaning: Character string representing the song title
Function: Variable-length song name expressed in 1-byte character code (256 at maximum)
The end code (0x00) must be written at the end of the name data.
The size should be calculated from this end code. If there is no data, record at least 1 byte of null (0x00) from the beginning (0x0020).
Value: Various character codes
NM2
Meaning: Character string representing the song title
Function: Variable-length name data expressed in 2-byte character code (maximum 512)
The end code (0x00) must be written at the end of the name data.
The size should be calculated from this end code. If there is no data, record at least 2 bytes of null (0x00) from the beginning (0x0120).
Value: Various character codes.
[0113]
The 80-byte data starting from the fixed position (0x320) of the attribute header is called a track information area TRKINF, and mainly manages information related to security and copy control. FIG. 19 shows the TRKINF part. Data in TRKINF will be described below according to the arrangement order.
[0114]
CONTENTS KEY (8 bytes)
Meaning: A value prepared for each song, which is protected after being protected by the security block of the memory card.
Function: The first key you need when playing a song. Used during MAC calculation
Value: From 0 to 0xFFFFFFFFFFFFFFFF
MAC (8 bytes)
Meaning: Copyright information alteration check value
Function: Value created from the contents of multiple TRKINF including the content accumulation number and the hidden sequence number
The hidden sequence number is a sequence number recorded in a hidden area of the memory card. A recorder that does not support copyright cannot read the hidden area. Also, a copyright-compatible dedicated recorder or a personal computer equipped with an application that can read a memory card can access the hidden area.
[0115]
A (1 byte)
Meaning: Part attributes
Function: Shows information such as compression mode in the part
Value: described below with reference to FIG.
However, N = 0, 1 monaural defines bit 7 as 1, sub signal 0, and special joint mode of main signal (L + R) only as monaural. The information of bits 2 and 1 may be ignored by a normal player.
[0116]
Bit 0 of A forms emphasis on / off information, bit 1 forms information of reproduction SKIP or normal reproduction, and bit 2 other than data section, for example, audio data, FAX, etc. The information of the data is formed. Bit 3 is undefined. By combining the bits 4, 5, and 6, the mode information of ATRAC3 is defined as shown. That is, N is the value of the mode represented by these 3 bits, and is mono (N = 0, 1), LP (N = 2), SP (N = 4), HX (N = 5), HQ ( The recording time (in the case of a 64 MB memory card), the data transfer rate, and the number of SUs in one block are shown for five types of modes (N = 7). The number of bytes of 1 SU is (mono: 136 bytes, LP: 192 bytes, SP: 304 bytes, EX: 384 bytes, HQ: 512 bytes). Further, bit 7 indicates the mode of ATRAC3 (0: Dual 1: J0int).
[0117]
As an example, the case of the SP mode using a 64 MB memory card will be described. A 64 MB memory card has 3968 blocks. In the SP mode, since 1 SU is 304 bytes, 53 SUs exist in one block. One SU corresponds to (1024/44100) seconds. Therefore, one block is
(1024/44100) × 53 × (3968-16) = 4863 seconds = 81 minutes
The transfer rate is
(44100/1024) × 304 × 8 = 104737 bps
It becomes.
[0118]
LT (1 byte)
Meaning: Playback restriction flag (bits 7 and 6) and security version
(Bit 5 to bit 0)
Function: Indicates that there are restrictions on this track

FNo (2 bytes)
Meaning: File number
Function: Track number when first recorded, and this value specifies the position of the MAC calculation value recorded in the hidden area in the memory card
Value: 1 to 0x190 (400)
MG (D) SERIAL-nnn (16 bytes)
Meaning: Serial number of security block (security IC 20) of recording device
Function: A unique value that is different for each recording device
Value: 0 to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
CONNUM (4 bytes)
Meaning: Content accumulation number
Function: A unique value accumulated for each song and managed by the security block of the recording device. 2 to the 32nd power and 4.2 billion songs are prepared and used to identify the recorded songs
Value: 0 to 0xFFFFFFFF.
[0119]
YMDhms-S (4 bytes) (Option)
Meaning: Playback start date and time of tracks with playback restrictions
Function: Date and time allowed to start playback specified by EMD
Value: Same as date / time notation above
YMDhms-E (4 bytes) (Option)
Meaning: Playback end date and time of tracks with playback restrictions
Function: Date and time when playback permission specified by EMD ends
Value: Same as date / time notation above
MT (1 byte) (Option)
Meaning: Maximum number of permitted playbacks
Function: Maximum number of playbacks specified by EMD
Value: 1 to 0xFF 0x00 when not used
When LT bit7 is 0, MT should be 00
CT (1 byte) (Option)
Meaning: Number of views
Function: The number of times that playback can actually be performed within the permitted number of playbacks. Decrement every playback
Value: 0x00 to 0xFF 0x00 when not used
When LT bit7 is 1 and CT value is 00, playback is prohibited.
[0120]
CC (1 byte)
Meaning: COPY CONTROL
Function: Copy control
Value: As shown in FIG. 21, bits 6 and 7 represent copy control information, bits 4 and 5 represent copy control information relating to high-speed digital copying, and bits 2 and 3 represent security block authentication levels. Bits 0 and 1 are undefined
Example of CC: (bit7, 6) 11: Permit unlimited copy, 01: Prohibit copy, 00: Permit one copy
(Bit 3, 2) 00: Recording from analog or digital in, MG authentication level is 0
In digital recording from a CD, (bit 7, 6) is 00, and (bit 3, 2) is 10.
CN (1 byte) (Option)
Meaning: Number of permitted copies in high-speed digital copy HSCMS (High speed Serial Copy Management System)
Function: Extends the distinction between copying once and copying free, and specifies the number of times. Valid only for copy 1st generation, subtract for each copy
Value: 00: copy prohibited, 01 to 0xFE: number of times, 0xFF: unlimited number of times.
[0121]
Subsequent to the track information area TRKINF described above, 24-byte data starting from 0x0370 is called a parts management area information PRTINF for parts management. Go. FIG. 22 shows the PRTINF portion. The data in PRTINF will be described below according to the arrangement order.
[0122]
PRTSIZE (4 bytes)
Meaning: Part size
Function: Indicates the size of the part. Cluster: 2 bytes (most significant), start SU: 1 byte (upper), end SU: 1 byte (lowest)
Value: Cluster: 1 to 0x1F40 (8000), start SU: 0 to 0xA0 (160), end SU: 0 to 0xA0 (160) (however, SU counting starts from 0, 1, 2, and 0) )
PRTKEY (8 bytes)
Meaning: Value to encrypt the part
Function: Initial value = 0, follow editing rules when editing
Value: 0 to 0xFFFFFFFFFFFFFFFF
CONNUM0 (4 bytes)
Meaning: First created content cumulative number key
Function: Role of ID to make content unique
Value: The same value as the content cumulative number initial value key.
[0123]
The attribute header of the ATRAC3 data file includes additional information INF as shown in FIG. This additional information is the same as the additional information INF-S (see FIGS. 11 and 12B) in the reproduction management file, except that the start position is not fixed. The data of the additional information INF starts with the next position after the last byte part (in units of 4 bytes) of one or more parts as a start position.
[0124]
INF
Meaning: Additional information data about the track
Function: Additional information data of variable length with header. A plurality of different additional information may be arranged. An ID and a data size are added to each. Additional information data including individual headers is a minimum of 16 bytes and an integer multiple of 4 bytes
Value: the same as the additional information INF-S in the reproduction management file.
[0125]
The data of each block of the ATRAC3 data file follows the attribute header described above. As shown in FIG. 23, a header is added for each block. The data of each block will be described below.
[0126]
BLKID-A3D (4 bytes)
Meaning: BLOCKID FILE ID
Function: Value for identifying the beginning of ATRAC3 data
Value: Fixed value = “A3D” (for example, 0x41334420)
MCode (2 bytes)
Meaning: MAKER CODE
Function: A code that identifies the manufacturer and model of the recorded device
Value: Upper 10 bits (maker code) Lower 6 bits (model code)
CONNUM0 (4 bytes)
Meaning: Cumulative number of content created first
Function: Role of ID to make content unique, value does not change even if edited
Value: The same value as the content accumulation number initial value key
BLOCK SERIAL (4 bytes)
Meaning: Serial number assigned to each track
Function: The beginning of the block starts at 0 and the next block is incremented by +1
Does not change value when edited
Value: start from 0 to 0xFFFFFFFF
BLOCK-SEED (8 bytes)
Meaning: one key to encrypt one block
Function: The beginning of the block generates a random number in the security block of the recording device, the following block is a value incremented by +1, and if this value is lost, no sound can be produced for about 1 second corresponding to one block. The same thing is written twice in the header and the end of the block. Does not change value when edited
Value: Initially 8 bytes random number
INITIALIZATION VECTOR (8 bytes)
Meaning: Initial value required to encrypt and decrypt ATRAC3 data for each block
Function: The beginning of the block starts at 0, the next block is the last encrypted 8-byte value of the last SU. In the middle of the divide block, the last 8 bytes immediately before the start SU are used. Does not change value when edited
Value: 0 to 0xFFFFFFFFFFFFFFFF
SU-nnn
Meaning: Sound unit data
Function: Data compressed from 1024 samples, the number of bytes output varies depending on the compression mode. Even if edited, the value does not change (for example, SP mode
(In case of N = 384 bytes)
Value: ATRAC3 data value.
[0127]
In FIG. 17, since N = 384, 42 SU is written in one block. In addition, the first two slots (4 bytes) of one block are used as headers, and BLKID-A3D, MCode, CONNUM0, and BLOCK SERIAL are written twice in the last slot (2 bytes). Therefore, the remaining area M bytes of one block is (16,384-384 × 42−16 × 3 = 208 (bytes).
In this, as described above, 8-byte BLOCK SEED is recorded twice.
[0128]
Hereinafter, an embodiment in which the present invention is applied to the above-described digital audio recorder will be described with reference to the drawings. FIG. 24 shows a configuration of a main part of one embodiment of the present invention. In FIG. 24, reference numeral 70 denotes a CPU provided in the audio system, and this CPU 70 is connected to the DSP 30 described above via a bus interface and a bus. An operation unit 80 is connected to the CPU 70.
[0129]
As shown in FIG. 24, the operation unit 80 is provided with button groups 81 to 86 and the like. Specifically, reference numeral 81 denotes a back button for recording / playback position, 84 denotes a forward button for recording / playback position, 82 denotes a recording button, 85 Is a play button, 83 is a stop button, and 86 is a pause button.
[0130]
When one of the button groups 81 to 86 of the operation unit 80 is pressed, detection information corresponding to the pressed button is generated in the operation unit 80 when the button is pressed, and this detection information is sent to the CPU 70. Supplied. The CPU 70 monitors the operation state of the operation unit 80 based on the detection information from the operation unit 80, and generates control information corresponding to the operation button when it is determined that the predetermined operation has been performed on the predetermined button. Various operations are executed by supplying control information to each unit.
[0131]
For example, when the recording button 82 is pressed, the recording operation is started. That is, the audio data generated from the selected predetermined input source is sequentially written in the predetermined area of the memory card 40. When the playback button 85 is pressed, the playback operation is started. That is, the audio data written in the predetermined area of the memory card 40 is sequentially read, and an analog audio signal is generated based on the read audio data and taken out from the line output terminal 19.
[0132]
Further, in the playback state, when the playback button 85 is further pressed and kept pressed by the user for a predetermined time or more, the process proceeds to the index management information writing process in parallel with the playback operation, and the user selects an arbitrary playback section. Is set. Specifically, in the index management information writing process, information indicating the start position of index information defined by the timing when the playback button 85 is pressed and information indicating the time during which the playback button 85 has been pressed are stored in the CPU 70. The information is generated and written in a predetermined area of the memory card 40 as information indicating the playback section.
[0133]
That is, the user's favorite characteristic part or so-called digest part of the reproduced music or the like is designated by the user, and information indicating the reproduction section is written in a predetermined area of the memory card 40. The information indicating the start position of the index information defined by the timing when the playback button 85 is pressed is stored in, for example, INX in the attribute header of the ATRAC3 audio file A3DDnnnn described above, and the playback button 85 is kept pressed. Information indicating the time is stored in XT. A maximum of about 6084 seconds can be specified by INX, and a maximum of about 6084 seconds can be specified by XT.
[0134]
Once the characteristic part that the user likes or the so-called digest part is specified in this way and information indicating the playback section is written in a predetermined area of the memory card 40, prior to the next playback operation. Thus, it is possible to easily search for songs, and it is also possible to collect and play back only characteristic parts.
[0135]
One embodiment of the present invention described above will be described in more detail with reference to FIGS. In the data format described above, the number of SUs is ¼ as the values of INX and XT. However, in the following description, for simplicity, an example in which the number of SUs is not set to ¼ will be described. First, the memory card is inserted into the recorder and the playback button 85 is pressed to start the playback operation (step S1). In step S2, it is determined whether or not it is the head of the track. When it is determined that the track is at the head, counting of the number of SUs is started, and the process proceeds to step S3.
[0136]
Then, in step S3, it is determined whether or not the playback button 85 has been pressed. Only when it is determined that the playback button 85 has been pressed, the process proceeds to step S4. In step S4, it is determined whether or not the playback button 85 has been pressed for 4 seconds or more. Only when the reproduction button 85 is kept pressed for 4 seconds or more, the process proceeds to step S5, and the index management information writing state is entered in parallel with the reproduction operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing when the playback button 85 is pressed is written in INX. Specifically, as shown in FIG. 27, when the playback button 85 is pressed at the timing of t1 and continues to be pressed for 4 seconds to reach the timing t2, the SU from the beginning of the track to the timing t1 goes back 4 seconds from the timing t2. The count value P1 of the number is written in INX. The start position of the index information is defined by the process of step S5.
[0137]
When the process of step S5 is completed, it is determined in step S6 whether or not the playback button 85 has been pressed. Only when the play button 85 is released and the play button 85 is turned off, the process proceeds to step S7. In step S7, the count value of the number of SUs corresponding to the time during which the play button 85 is kept pressed is written in XT. It is. Specifically, as shown in FIG. 27, if the playback button 85 is turned off at the timing of t3, the count value of the number of SUs according to the time (t3-t1) that the playback button 85 has been pressed (P3-T1). P1) is written to XT. The length of the playback section specified by the process in step S7 is defined. When the process of step S7 is completed, the index management information writing process in parallel with the reproduction operation is completed.
[0138]
In the above description of the embodiment, the case where the playback button 85 continues to be pressed for 4 seconds or more while also using the playback button 85 has been described, but the process proceeds to the index management information writing process. It is also possible to monitor not only the timing when the button is pressed concurrently but also the timing when the button is turned off, and when the button is continuously pressed for a predetermined time or longer, the process may be shifted to the index management information writing process. In other words, in the normal monitoring process of the operation unit, only the timing when the arranged button is pressed is used to generate various control information, but the present invention also uses the timing when the button is turned off. By using a process for determining whether or not the button has been pressed for 4 seconds or more, the normal operation and the index management information writing process can be distinguished from each other so that the operation button can be shared. Therefore, the determination time for distinguishing between the normal operation and the index management information writing process is not limited to 4 seconds, and may be 4 seconds or more and 4 seconds or less as long as malfunction can be prevented.
[0139]
FIG. 25 shows a configuration of the operation unit 80 in another embodiment. In another embodiment, a dedicated index button 87 is provided in addition to the normal operation button groups 81 to 86, and index management information is written by using the index button 87. In addition, the detection information generated according to the operation state in the operation unit 80 is supplied to the CPU 70 as in the above-described embodiment.
[0140]
For example, when the recording button 82 is pressed, the recording operation is started. That is, the audio data generated from the selected predetermined input source is sequentially written in the predetermined area of the memory card 40. When the playback button 85 is pressed, the playback operation is started. That is, the audio data written in the predetermined area of the memory card 40 is sequentially read, and an analog audio signal is generated based on the read audio data and taken out from the line output terminal 19.
[0141]
In the playback state, when the index button 87 is pressed and kept pressed by the user for a predetermined time or longer, the process proceeds to the index management information writing process in parallel with the playback operation, and an arbitrary playback section is set by the user. Is set. Specifically, in the index management information writing process, information indicating the start position of index information defined by the timing when the index button 87 is pressed and information indicating the time during which the index button 87 has been pressed are stored in the CPU 70. The information is generated and written in a predetermined area of the memory card 40 as information indicating the playback section.
[0142]
That is, the user's favorite characteristic part or so-called digest part of the reproduced music or the like is designated by the user, and information indicating the reproduction section is written in a predetermined area of the memory card 40. Note that the information indicating the start position of the index information defined by the timing at which the index button 87 is pressed is stored in the INX of the ATRAC3 data file A3D-nnn as in the above-described embodiment, and the playback button 85 Information indicating the time of pressing is stored in XT.
[0143]
Once the characteristic part that the user likes or the so-called digest part is specified in this way and information indicating the playback section is written in a predetermined area of the memory card 40, prior to the next playback operation. Thus, it is possible to easily search for songs, and it is also possible to collect and play back only characteristic parts.
[0144]
Another embodiment of the present invention described above will be described in more detail with reference to FIGS. First, the memory card is inserted into the recorder and the playback button 85 is pressed to start the playback operation (step S11). In step S12, it is determined whether or not it is the head of the track. When it is determined that the track is at the head, counting of the number of SUs is started, and the process proceeds to step S13.
[0145]
In step S13, it is determined whether or not the index button 87 has been pressed. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S14. In step S14, it is determined whether or not the index button 87 has been pressed for 4 seconds or more. Only when the index button 87 is kept pressed for 4 seconds or more, the process proceeds to step S15, and the index management information writing state is set in parallel with the reproduction operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing when the index button button 87 is pressed is written into INX. Specifically, as shown in FIG. 27, when the index button 87 is pressed at the timing of t1 and continues to be pressed for 4 seconds to reach the timing t2, the SU from the beginning of the track to the timing t1 is traced back 4 seconds from the timing t2. The count value P1 of the number is written in INX. The start position of the index information is defined by the process of step S15.
[0146]
When the process of step S15 is completed, it is determined in step S16 whether or not the index button 87 has been pressed. Only when the index button 87 is released and the index button 87 is turned off, the process proceeds to step S17. In step S17, the count value of the number of SUs corresponding to the time during which the index button 87 is kept pressed is written in XT. It is. Specifically, as shown in FIG. 27, if the index button 87 is turned off at the timing of t3, the count value of the number of SUs according to the time (t3-t1) that the index button 87 is kept pressed (P3- P1) is written to XT. The length of the playback section specified by the process in step S17 is defined. When the process of step S17 is completed, the index management information writing process in parallel with the reproduction operation is completed.
[0147]
In the description of the other embodiments described above, the case where the dedicated index button 87 is used and the process proceeds to the index management information writing process when the index button 87 is continuously pressed for 4 seconds or more has been described. The index management information may be written using only the pressed timing of the index button 87.
[0148]
FIG. 29 shows a processing procedure when writing index management information using only the timing at which the index button 87 is pressed. With reference to FIG. 29 and FIG. 27, the modification of other embodiment is demonstrated in detail. First, the memory card is inserted into the recorder and the playback button 85 is pressed to start the playback operation (step S21). In step S22, it is determined whether or not it is the head of the track. When it is determined that the track is at the head, counting of the number of SUs is started, and the process proceeds to step S23.
[0149]
In step S23, it is determined whether or not the index button 87 has been pressed for 0.2 seconds or more. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S24. In step S24, it is determined again whether or not the index button 87 has been pressed for 0.2 seconds or more. In step S23 and step S24, a determination criterion of 0.2 seconds is provided to determine whether or not the index button 87 has been pressed. Whether or not an intentional operation has been performed on the index button 87. Therefore, it may be determined whether or not it is simply pressed. Only when it is determined that the index button 87 has been pressed, the process proceeds to step S25, and the index management information writing state is entered in parallel with the reproduction operation. In the index management information writing state, first, the count value of the number of SUs from the beginning of the track to the timing when the index button button 87 is first pressed is written in INX. Specifically, as shown in FIG. 27, when the index button 87 is pressed at the timing of t1 and continues to be pressed for 0.2 seconds to reach the timing t4, the timing starts from the beginning of the track by 0.2 seconds from the timing t4. The count value P1 of the number of SUs up to t1 is written in INX. The start position of the index information is defined by the process of step S25.
[0150]
When the process of step S25 is completed, in step S26, the count value of the number of SUs corresponding to the time from the timing of pressing the first index button 87 to the timing of pressing the second index button 87 is XT. Is written to. The length of the playback section designated by the processing in step S26 is defined. Specifically, as shown in FIG. 27, when the index button 87 is pressed at the timing t3 and continues to be pressed for 0.2 seconds and reaches the timing t5, the end of the playback section is traced back 0.2 seconds from the timing t5. The timing is defined, and the count value (P3-P1) of the number of SUs corresponding to the time (t3-t1) from the timing when the first index button 87 is pressed to the timing when the second index button 87 is pressed is Written to XT. When the process of step S26 is completed, the index management information writing process in parallel with the reproduction operation ends.
[0151]
In the description of one embodiment and the other embodiments described above, when a predetermined operation is performed on a predetermined operation member in a reproduction state in which the reproduction button 85 is pressed, the process proceeds to the index management information writing process. As described above, even in a recording state in which the recording button 82 is pressed, the index management information can be written in parallel with the recording operation when a predetermined operation is performed on a predetermined operation member. It is.
[0152]
In the present invention, as shown in FIG. 20, a recordable time of 128 minutes can be set in the LP mode. For example, if a CD is 40 minutes, 3 sheets can be recorded on one memory card. . Thus, when a plurality of albums are recorded on a single memory card, it is convenient for searching if the representative music of each album can be reproduced as a digest part. The representative song of the album is preferably a digest portion of the song that has been single-cut from the album.
[0153]
The digest portion of the album is recorded in, for example, INF-S after 0x0647 of the playback management file (PBLIST) shown in FIG. In the present invention, as shown in FIG. 14, an album digest is designated with a variable length at ID = 77. When digest points are set for a plurality of albums in the playback management file (PBLIST), the total number of albums (that is, the total set) recorded on one memory card with reference to ID = 117 in FIG. The number of album digests to be set to ID = 77 is determined with reference to (Number). If digests (INX, XY) are set for all the songs already recorded in a predetermined album, the ID number of the representative song is set to ID = 77 from the album.
[0154]
When playing the digest part of an album, ID = 77 is searched with reference to the INF-S after address 0x0647 of the playback management file (PBLIST), and the album number and song number set there are referred to. Play a song. Further, the digest information (INX, XT) corresponding to the representative song of the album may be recorded directly at ID = 77.
[0155]
In the description of one embodiment and the other embodiments described above, the case where the count value of the number of SUs from the head of the track is used as information defining the start position of the index information in the index management information writing state has been described. However, information indicating other reproduction position and reproduction timing may be written in INX. Further, the case where the count value of the number of SUs during a predetermined timing is used as the information defining the length of the playback section has been described. However, information indicating other playback position and playback timing is written in XT. Also good. Furthermore, although the case where the index management information is written in INX and XT has been described, the index management information may be written in another predetermined area.
[0156]
In the above description, the present invention is applied to audio data processing. However, the present invention is also applied to content composed of both audio data and video data, or content composed only of video data. be able to.
[0157]
【Effect of the invention】
In the present invention, when a predetermined operation is performed on a predetermined operation member, the process proceeds to the index management information writing process in parallel with the reproduction operation, and an arbitrary reproduction section can be set by the user. Specifically, in the index management information writing process, information indicating the start position of index information defined by the timing when the user presses the play button and information indicating the time for which the play button has been pressed are controlled. The information is generated in the memory and written in a predetermined area of the semiconductor memory as information indicating the playback section. Thus, it is possible to specify a characteristic part that the user likes in the reproduced music or the like, or a so-called digest part. Therefore, according to the present invention, the user himself / herself can specify the index information of the music, and can easily search using this. For this reason, the convenience of the recording / reproducing apparatus can be improved and the usability can be improved.
[Brief description of the drawings]
FIG. 1 is a block diagram relating to a digital audio recorder / player using a nonvolatile memory card of the present invention.
FIG. 2 shows an internal block diagram of a DSP adapted to the present invention.
FIG. 3 shows an internal block diagram of a memory card applied to the present invention.
FIG. 4 is a schematic diagram showing a file management structure using a memory card applicable to the present invention as a storage medium.
FIG. 5 shows a physical structure of data in a flash memory in a memory card applied to the present invention.
FIG. 6 shows a data structure in a memory card applied to the present invention;
FIG. 7 is a branch diagram showing a file structure stored in a memory card.
FIG. 8 shows a data structure of a reproduction management file PBLIST.MSF which is a subdirectory stored in the memory card.
FIG. 9 is a data structure diagram in the case where one continuous ATRAC3 data file is divided into predetermined unit lengths and an attribute file is added.
FIG. 10 is a structural diagram for explaining combine editing processing and divided editing processing according to the present invention;
FIG. 11 shows a data structure diagram of a reproduction management file PBLIST.
FIG. 12 shows a data structure diagram of a reproduction management file PBLIST.
FIG. 13 shows a correspondence table of types of the additional information data.
FIG. 14 shows a correspondence table of types of the additional information data.
FIG. 15 shows a correspondence table of the types of additional information data.
FIG. 16 shows a data structure of additional information data.
FIG. 17 is a detailed data structure diagram of an ATRAC3 data file.
FIG. 18 is a data structure diagram of an upper part of an attribute header constituting an ATRAC3 data file.
FIG. 19 is a data structure diagram of the middle stage of the attribute header constituting the ATRAC3 data file.
FIG. 20 is a table showing the types of recording modes and the recording time in each recording mode.
FIG. 21 is a table showing a copy control state.
FIG. 22 is a data structure diagram of the lower part of the attribute header constituting the ATRAC3 data file.
FIG. 23 is a data structure diagram of a header of a data block of an ATRAC3 data file.
FIG. 24 is a schematic diagram of the vicinity of the operation unit according to the embodiment of the present invention.
FIG. 25 is a schematic diagram of the vicinity of an operation unit according to another embodiment of the present invention.
FIG. 26 is a flowchart showing a digest part designation procedure according to the embodiment of the present invention.
FIG. 27 is a timing chart relating to the designation of a digest part in one embodiment and another embodiment of the present invention.
FIG. 28 is a flowchart showing a digest part designation procedure according to another embodiment of the present invention.
FIG. 29 is a flowchart showing a digest part designation procedure according to another embodiment of the present invention.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 10 ... Audio encoder / decoder IC, 20 ... Security IC, 30 ... DSP, 40 ... Memory card, 42 ... Flash memory, 52 ... Security block, 70 ... CPU, 80 ... operation unit, 85 ... play button, 87 ... index button, TRKLIST. MSF: Track information management file, INFLIST. MSF: Additional information management file, A3Dnnn. MSA audio data file

Claims (6)

Reproducing means for reproducing the program from a nonvolatile memory in which the program is recorded,
In parallel with the reproduction of the program by the reproduction means, index management information generation means for generating, by key operation, index management information for specifying the start position and end position of the digest part which is a characteristic part of the reproduced program ,
Recording means for recording the index management information in the management area of the nonvolatile memory;
Instruction means for instructing reproduction of the digest part of the program;
Control means for controlling the reproduction means to sequentially reproduce the digest part specified by the index management information of each of the plurality of programs when an instruction to reproduce the digest part is input by the instruction means; A playback device comprising:   2. The reproduction according to claim 1, wherein the program is divided into a plurality of blocks, one of the divided blocks is used as a management area, and the index management information is recorded in the management area. apparatus. When the program recorded in the non-volatile memory is categorized into a plurality of albums, the digest management information for each album is recorded, and an instruction to reproduce the digest portion is input by the instruction means, the digest portion The playback device according to claim 1 or 2, wherein only the player is played back. A reproducing step of reproducing the program from a nonvolatile memory in which the program is recorded by a reproducing means ;
In parallel with the reproduction of the program by the reproduction step, an index management information generation step for generating index management information for specifying a start position and an end position of a digest part which is a characteristic part of the reproduced program by a key operation ; ,
A recording step of recording the index management information in a management area of the nonvolatile memory by a recording means ;
An instruction step for instructing reproduction of the digest part of the program by an instruction means ;
When an instruction to reproduce the digest portion is inputted by the instruction means, the control unit controls the playback unit to sequentially play the digest portion specified by each of the index management information of a plurality of the program A playback method comprising: a control step. 5. The reproduction according to claim 4, wherein the program is divided into a plurality of blocks, one of the divided blocks is used as a management area, and the index management information is recorded in the management area. Method. When the program recorded in the non-volatile memory is categorized into a plurality of albums, the digest management information for each album is recorded, and an instruction to reproduce the digest part is input in the instruction step, the digest part The reproduction method according to claim 4 or 5 , wherein only the image is reproduced.

Images