ここでは、grandMA3 で作業を開始するための簡単な手順について説明します。MA University の MA e-Learning では、さまざまなトレーニングが提供されています。すべての情報は、MA Lighting の Webサイト www.malighting.com からアクセスできます。
起動時に表示される Release Notes から抜けるには、右上隅にある I agree をタップしてください。grandMA3 ソフトウェアのメイン画面が開きます。画面の右側には、定義済みのビューボタンがあります。これをタップすると、画面の表示内容を切り替えられます。
grandMA3 ソフトウェアを初めて起動した場合、まず何台かのフィクスチャをパッチしてみてください。あるいは、ソフトウェアに同梱されているデモショーの1つを読み込んでもかまいません。いずれの場合も、Menu を押します。grandMA3 onPC ソフトウェアを利用している場合は、左上隅に
シンボルがあります。これクリックするのは、卓で Menu を押すことと同じです。
Backup に続けて Load をタップすると、ショーを読み込めるようになります。
まず、タイトルバーの Shows を繰り返しタップして Demo Shows に切り替えてください。そのためには、Demo Shows が表示されるまで Shows を繰り返しタップします。Demo Shows が表示されたら、その中から任意のものを選択できます。デモショーを選択したら、Load をタップしてください。
すでに読み込まれているショーがある場合、新しいものを読み込む前に現在のショーを保存するかどうか尋ねるポップアップが表示されます。最も適切と思われる選択肢を選んでください。
これで、grandMA3 ソフトウェアを使用する準備が整いました。そこには、画面内容を簡単に変更できるビューボタンがあります。下部には、エンコーダバーとコマンドラインがあります。作業を開始するのに必要なのはこれだけです。詳しくは grandMA3 のヘルプを参照してください。卓や onPC でヘルプにアクセスするには、Help と表示されたビューボタンをタップします。あるいは、MA Lighting のサイトの Online Manuals にアクセスしてください。grandMA3 ソフトウェアについて段階的に学びたい場合は、クイックスタートガイド を参照したり、Webサイトにある無料の MA e-Learning に参加したりしてください。
grandMA3 ソフトウェアを楽しく活用してください。
このソフトウェア・バージョンでの改善・変更点については、以下で述べられています。
|
|
ヒント |
| grandMA3 ソフトウェアは、シャットダウン前に動作していたショーファイル(または状態)で起動します。 |
| 説明 |
|---|
| Grouping フィクスチャの一部であるフィクスチャ(トラスなど)を Position Calibration ダイアログでキャリブレーションした場合、Solve をタップした後にフィクスチャの位置がずれていました。 |
| 説明 |
|---|
| エクゼキュータにカスタム・コマンドを設定して実行すると、ソフトウェアがクラッシュする可能性があります。 |
| レシピ内の MAtricks を変更すると、ソフトウェアがクラッシュする可能性があります。 |
| 説明 |
|---|
| Webリモートが接続されたステーションでパッチから抜けると、ソフトウェアがクラッシュする場合があります。 |
| フェーダのタッチ・レスポンスが正しく動作しない場合がありました。 The touch response of the fader was either missing or displayed without the fader being touched. |
| 説明 |
|---|
| 以前のキューで使用された XYZ 値でプリセットを更新すると、現在の出力で XYZ 値ではなく Pan/Tilt 値がアサートされる可能性があります。 |
| Go+ を押した際に、メインのシーケンスが予期せず最初のキューにジャンプすることがまれにあります。 |
| MIBのディレイタイムが1秒未満に設定され、再生がディマー・フェイザーから閉じたディマーにフェードする場合、ディマーが完全に閉じる前までにMIB値が適用されます。 |
Recipe Editor の改善:
Patch メニューの改善:
外部タイムコード信号の小さな変動に対する許容範囲を拡大しました。
| 説明 |
|---|
| It was possible to use the command line to assign object actions to objects, even if these actions were not a part of options in the UI. |
| Turning an empty encoder would execute commands in the command line. |
| If a timecode event was assigned and triggered by an encoder and then Delete was pressed, the software could crash. |
| PSR の後でマクロのハンドルが壊れる可能性がありました。例えば、#[Group 'StartShow Group 1 Linear'] が #[FFFFFFFFFFFFFFFF] になってしまいます。 |
| キューパートがキューと同じアトリビュート値でクックされた後に、Allow Duplicates 列が Yes に設定されている場合、キューパートは自動的に再クックされません。 |
| If you created a recipe with a group that contained subfixtures without a valid ID and applied MAtricks, the MAtricks would not be applied correctly. |
| 一部のMacデバイスでは、grandMA3 onPC アプリケーションが設定に表示されなかったため、サウンド入力が機能しませんでした。 |
| Recipe Editor を用いてレシピを作成し、複数のキューに保存した場合、そのレシピはキューの1つにだけ保存されます。 |
| When cooking recipes it could happen that not all fixtures of the selection used the selected values, even if they were capable to do so. |
| If blocked attributes have been unblocked, the values of unrelated fixtures that were still blocked would be displayed as unblocked in cyan in the track sheet. |
| macOS を用いている場合、onPC ソフトウェアが時々起動しないことがあります。 |
| If presets had Cue Part settings other than the default and you created a recipe with the recipe editor, the presets would not be added to the defined programmer part but in the order they were selected. |
| In some cases, if you executed valid commands using a macro or plugin that for example included /CueOnly, the command line history would falsely display errors. |
| If you executed DumpLog /NoAutoClose while no USB drive was connected, the pop-up would ignore /NoAutoClose and a countdown would appear. |
| Storing recipes in a cue with the same group but a different preset did not store the recipe in a new recipe line. |
| 別のレシピ行を参照する値を含むレシピ行を新しいレシピ行にコピーした場合、Value セルが空のままになります。 |
| ショーファイルを v2.1.1.5 から v2.2 に移行した場合、ソフトウェアがフリーズする可能性があります。 |
| セッション中にMVRファイルをショーにインポートすると、卓がクラッシュする可能性があります。 |
| If Allow Duplicates was disabled and you created a recipe with a preset in a cue and another recipe with a phaser that used the same attribute in a cue part, cooking would not work if the cooking mode was set to Low Priority. |
| シーケンスの Wrap Around が無効になっている場合、シーケンスはアジェンダ・イベントによってトリガーされません。 |
| It was possible to assign a tag to itself by executing an incomplete assign command. |
| Renumbering some cues of a sequence also renumbered cues of the sequence that were not selected. |
| Image プール内の別の画像を移動した直後に画像を移動すると、ソフトウェアがクラッシュする可能性があります。 |
| In certain show files, when you changed the XYZ values to pan tilt in the programmer, the pan and tilt values were incorrect. |
| シーケンスをインポートすると、ほとんどのMIB設定が失われます。 |
| If you migrated a show file to the new software version, in some cases presets would wrongly be selective instead of global. |
| The DoubleSpeed, HalfSpeed, and Speed 1 commands were passed to the speed master assigned to the sequence, but should have only affected the sequence. |
| The software could crash when importing fixtures with custom meshes that used textured materials via Partial Show Read. |
| Rename Show File ポップアップで Rename をタップするとソフトウェアがクラッシュすることがあります。 |
| Changing the speed in sequences that had the same speed master assigned using DoubleSpeed, HalfSpeed or Speed1 would lead to different speeds in the sequences and speed master. |
| 説明 |
|---|
| If a console was disconnected from a session and a fader was moved, the fader position would not be synchronized in the data merge process. This would lead to two different positions of the same fader. |
| If a console was disconnected from a session and a preset or executor configuration was changed, two different versions of the same preset or executor configuration would exist on different devices after merging the session data. |
| If the master console with a higher priority unexpectedly dropped out of a session and a different show file was loaded in the session, the show file of the higher priority master would be used in the session without a warning as soon as it rejoined the session. |
| DMX channels 511 and 512 of an incoming DMX signal were not recognized and the DMX universe displayed no incoming values. |
| If you selected a USB stick in the backup menu, the software could crash. |
| If you had two sessions with the same session index but different software versions, one of them in version 2.2, in the same network, devices in the session would crash. |
| If a session was created with normal priority, then a high priority station was invited and Keep Session's Show File was selected, a processing unit that was additionally invited would not accept the current show file. Instead, it triggered |
| If you were in a session and loaded a different show file on the connected station, the show file would not be loaded on all devices in the session. |
| In some cases, the previously saved show file of a station with a higher priority could falsely be overwritten after inviting a station to a session and keeping the session's show file. |
| If you had a console and an onPC in session, connected via web remote to the console and then started a new show on the onPC, the console could crash. |
| Pressing the sleep button on an external keyboard connected to a console could cause the console to freeze. |
| 説明 |
|---|
| The offsets of DMX channels of fixture types using breaks could be wrong. |
| Patching MArkers and changing their rotation in the patch would not show their rotation values if you reentered the patch. |
| If you changed the size of a target space of a MArker, the XYZ values of fixtures that were spread across the space of that MArker would not be automatically updated. |
| In sessions, it could happen, that X, Y, and Z values would all change if you turned an encoder to change one of the values. |
| When fixtures were copied in the patch, relative pan/tilt values could be lost. |
| Creating multipatch fixtures in the patch could cause the software to crash. |
| Defective fixture types could lead to preset and cue data being lost if you migrated a show file to the new software version. In addition, a notification now informs the user to adjust the invalid fixture types. |
| 説明 |
|---|
| フェイザー・ステップの一部としてキューに保存されていた Dimmer プリセットを更新しても、キュー内のフェイザーに更新された値が適用されませんでした。 |
| If a cue already had reference data of phaser presets in it, and new phaser data was stored in a step of the phaser, this would result in lost phaser data in the cue. |
| Phaser Editor を開いた状態で、最初または2番目のエンコーダを回して 2D Bar から Phaser Bar に変更すると、ソフトウェアがクラッシュする可能性があります。 |
| 説明 |
|---|
| If a running cue was deleted, the cue would still be played back and the sequence would not be stopped. This bug is fixed. Now the sequence will be disabled after the running cue is deleted. |
| A Goto event during encoder movement caused the value to snap or jump to 0. This bug is improved to prevent values from jumping to 0. |
| 説明 |
|---|
| 新しいソフトウェア・バージョンにショーファイルを移行した場合、Plugins プールのプール・アクションは Call ではなく None に設定されていました。 |
| If timecode events were recorded using pool objects, they were displayed as events triggered by DC Remotes in the timeline. |
| Login ポップアップで、Tab キーを押してもパスワード入力欄にカーソルが移動しませんでした。 |
| The label pop-up on screen six and seven would not automatically change to appearance tab if new appearance was created and entered. Instead it stayed on the keyboard tab. |
| The names and numbers of groups that only contained a single fixture were not displayed in Selection of recipe lines. |
| If you recorded a timecode and disabled Setup, the record button would disappear but the timecode recording would still be running. |
| Filtered sheets would not automatically update to include recently added fixtures if the fixtures met the filter criteria. |
| If the At filter was set to exclude Relative, cooking would fail and recipe lines would be displayed in red. |
| シーケンスやエクゼキュータを編集すると、System Monitor で複数のLuaエラーが発生する可能性があります。 |
| 選択したシーケンスを変更すると、Info ウィンドウに Note が表示されないことがあります。 |
| Windows または Mac でソフトウェアを再起動した後、エンコーダバーに一部のフィーチャグループが表示されない場合があります。 |
| In the timecode viewer, rows of track groups would be displayed too big and needed to be opened manually every time, instead of staying opened. |
| Appearances would not be displayed in the load and goto pop-up for sequences when toggling Cue Appearance. |
| If you turned a preset into a recipe, inserted a new recipe line, and opened the value selector, there would be no option to select other recipe lines. |
| If a quickey pool was visible and then the selected data pool was changed, quickeys of the previous data pool would still be triggered, given that empty objects of the new quickey pool of the selected data pool were selected. |
| 現在のキューが Sequence Sheet のタイトルバーに表示されていません。 |
| Adding a group to the selection using the clone dialog would change the original fixture selection order of that group. |
| If you had a session with multiple output stations that were displayed in a layout and one device was dismissed from the session, the color of the layout element only would change if the status of a second station was changed, too. |
| v2.2 でショーファイルを読み込むと、プールに割り当てられたアピアランスが失われます。 |
| Layout Viewer でビューをタップしても、そのビューを呼び出すことができませんでした。 |
| プール内のオブジェクトに対してオブジェクト・アクションを読み込む際、オブジェクトに間違ったアイコンが表示されていました。 |
grandMA3 version 2.2.1.1 の最新リリースでは、照明エクスペリエンスを豊かにするいくつかの機能強化が行われています。皆様から寄せられたご意見をもとに改良を重ね、多くの新機能を搭載しています。以下の簡単な説明を読み、詳しくは関連リンクを参照してください。
このリリースの新機能
新しいタグ機能を用いると、ソフトウェア全体でオブジェクトを整理、リンク、相互参照できます。 また、ライブ的なショーにも最適なツールです。同じタグを持つすべてのオブジェクトを、まとめてトリガーしたり選択したりできます。
Tags プールを開くには、Add Window ダイアログで Pools - Tags に移動します。
オブジェクトにタグを割り当てるには、以下の3つの方法があります。
コマンドラインでタグを使用する方法については、Tag キーワード を参照してください。
プール・オブジェクトにタグが割り当てられると、それに
が表示されます。割り当てられたタグの名前と番号は、プール・オブジェクト設定の Tags に表示されます。
Sequence Editor や Macro Editor などでは、オブジェクトに割り当てられたタグが、タイトルバーとグリッドの間の領域に表示されます。これらのタグは、プール・オブジェクトと同様に編集したり、プール・アクションを実行したりできます。タグに割り当てられたアピアランスの背景色は、エディタに表示されるタグの背景色を定義します。
Tags ポップアップを開くには、以下のようにします。
すでに割り当てられているタグは、それを解除できます。その逆も可能です。ポップアップの左側には、対応するプール・オブジェクトに割り当てられているタグが表示されます。右側には、割り当てられていないタグが表示されます。
ポップアップでは、タグをロック/解除したり、Kill Instant および Kill Delayed (後述を参照)から保護したりすることもできます。
Tags プール内のオブジェクトに対するデフォルト・アクションは ListReference です。
Tag Editor には、タグが割り当てられているオブジェクトの情報が、以下のように表示されています。
Tag Editor の Add New Tag Reference を用いると、複数のオブジェクトを一度にタグに割り当てられます。Add Tag References ポップアップで複数のオブジェクトを選択し、連続して割り当てられます。オブジェクト行を選択し、Assign をタップしてください。
Tag Editor のタイトルバーで Settings を有効にすると、 Name、Scribble、Appearance、Tags、Note、および Tag Type を設定したり、Forward Commands をオン/オフを切り替えられますタグは再帰的であるため、あるタグを別のタグに割り当てることができます。
以下のタグタイプを選択できます。
タグタイプが機能するには、シーケンスをトリガーする前にタグとタグタイプを設定する必要があります。そうでない場合、対応するシーケンスが一度トリガーされるとすぐにタグタイプが機能します。
タグによって再生が開始されると、Off Menu および Running Playbacks ウィンドウの Trigger 列にタグが表示されます。
|
|
ヒント |
| Kill Protect は、タグから実行される Kill Instant や Kill Delayed によってシーケンスが無効化されることからシーケンスを保護するものではありません。Kill Protect については、Sequence Settings および Kill キーワード を参照してください。 |
Forward Commands をオンにすると、タグのすべての参照に対して再生コマンドを実行できます(デフォルトでオン)。
これは、>>>、<<<、Go+、Go-、Goto、Halfspeed、Load、On、Off、Pause、Rate1、Speed1、Toggle、および Top に適用されます。
このリリースでの改善点
Recipe Editor は、レシピの作成と編集のワークフローを改善し、高速化するために導入されました。 ユーザインターフェースを用いて、セレクション(グループ)、値(プリセット、ビットマップ、ジェネレータ)、フィルタ(フィルタ、ワールド)、および MAtricks を定義することで実現されます。レシピは、LTPに基づいて生成された時点でクックされます。Recipe Editor は、Programmer Parts ウィンドウに代わるもので、その機能を引き継いでいます。
Recipe Editor は、Add Window ポップアップの Tools - Recipe Editor にあります。
Recipe Editor を用いてレシピを作成するには、Edit Recipe モードを有効にします。これには、以下の複数の方法があります。
コマンドラインを用いてレシピを編集する方法については、EditRecipe キーワード を参照してください。
Edit Recipe モードを無効にするには、Esc キーを押すか、上述いずれかの方法でモードを切り替えます。Edit Recipe モードが無効になると、すべてのプールは通常通り動作します。
Edit Recipe モードが有効になっている間、Edit と Esc が交互に点滅します。
レシピに使用できる各オブジェクト・タイプには、プール・ウィンドウに緑の
が表示されます。
以下のウィンドウでは、レシピ・インジケータが使用されています。
|
|
ヒント |
| レシピに使用できるように、対応するプールの Pool Action 設定を必ず SelFix/At または At に設定してください。 |
レシピを作成するには、以下のようにします。
|
|
ヒント |
| セレクションと値の記録順序は、レシピの処理方法に影響を与えます。 同じセレクションを持つ複数のレシピ行が同じアトリビュートを参照している場合、最後のレシピ行が出力を決定します。 |
|
|
ヒント |
| 空のグループを持つレシピを作成することは可能です。 |
|
|
ヒント |
| レシピに直接値を入力することはできません。事前にプリセットに保存する必要があります。 プリセットが選択されていない場合、値はプログラマに保存されます。 |
対応する キューまたはプリセット(例: EditRecipe Cue 1、EditRecipe 1、または EditRecipe Preset 2.2)を指定して EditRecipe を実行すると、Recipe Editor 内の特定オブジェクトの編集モードが有効になります。シーケンスとエクゼキュータ(例: EditRecipe Sequence 1, EditRecipe Page 1.204)を指定すると、実行中のキューが編集されます。
タイトルバーの CleanUp をタップすると、同じフィーチャグループの複数プリセットで同じセレクションを用いているすべてのレシピが削除されます。出力を生成する最後のオブジェクトだけが保持されます。例えば、Group 1 + Red + Yellow + Blue を選択して CleanUp をタップすると、Group 1 + Red + Yellow のレシピ行が削除されます。すでに選択されているプリセットをもう一度タップして選択を解除すると、対応するレシピ行も削除されます。CleanUp は、同じフィクスチャが1つのフィーチャグループの複数項目で使用されている場合にのみ有効です。それ以外の場合、ボタンはグレーアウトされます。Edit Recipe が無効になっている場合、このボタンは表示されません。
Off Group ["グループ名" または グループ番号]、Off Preset ["フィーチャグループ名" または フィーチャグループ番号].["プリセット名" または プリセット番号]、または Off にしてグループやプリセットをタップすることでも、対応するレシピ行を削除できます。グループに複数の行がリンクされている場合は、レシピ内のそれらすべてが削除されます。
例えば Group 2 をタップして、異なるセレクションを定義することもできます。プール・オブジェクトの周りの茶色枠は、Group 1 など、以前のセレクションに対する値を示します。もう一度 Group 1 をタップすると、このセレクションに対して以前に定義された値が再び緑色で強調表示されます。
MAtricks オーバーレイを開いて、レシピ行に特定の MAtricks 値を定義します。MAtricks Editor でレシピを編集している間、タイトルバーには "(Recipe)" と緑のポット・アイコンが表示されます。
ウィンドウ設定の Columns タブを用いて、Recipe Editor の列を個別に調整します。
レシピに対するその他の改善点については、後述の レシピの改善 を参照してください。
Updated predefined content:
Carallon フィクスチャ・ライブラリを v19.9 に更新。
レシピの改善:
Sequence Sheet の改善:
キューやシーケンスのプロパティを変更する際の動作を改善:
シーケンスが実行中の場合、CueFade 5 のようなコマンドは実行中のキューを指定します。シーケンスがオフの場合、シーケンス自体を指定します。これはシーケンスとキューのプロパティに適用されます。
For example, the name: Label will address the sequence when the sequence is off, and it will address the running cue when the sequence is on.
Preferences and Timings の改善:
Timing マスターを設定するには、以下のようにします。
This menu allows you to set the default values for actions triggered by Goto, Go-, >>>, and <<<. They can be set to CueTiming, using the timings set in the cue (only for Goto and Go-), a numeric value, or a timing master. CueTiming sets the timing values of the target cue and ignores the timings of other cues. Values that are tracked into the target cue, and therefore do not have a defined timing in that cue, will use the timing of Part 0.
デフォルト値は以下の通りです。
Content Sheet の改善:
Added
a special value to Specials in the attribute calculator called
Deactivate:
コマンドラインで用いる方法については、Deactivate キーワード を参照してください。
レイアウトの改善:
Gel Editor の改善:
Appearance Editor の改善:
Improved the display of selected cells in conjunction with appearances:
Cells that are selected by the user and that display an appearance now also display a thick blue
frame and the appearance in the center.
Scribbles Editor の改善:
Label ダイアログの改善:
Improved Text Input:
画面キーボードに以下の言語を追加:
Notes の改善:
Info ウィンドウの Notes を改善:
Help の改善:
3D Viewer:
PSR の改善:
Clock Viewer の改善:
|
|
ヒント |
| タイトルバーの対応する名前は、選択したスタイルに応じて変わります。例えば、"Digital AM/PM" を選択すると、タイトルバーには正午に "Clock PM" と表示されます。 |
Fixture Sheet の改善:
Universes プールの改善:
ネットワークの改善:
|
|
ヒント |
| マルチキャスト・ベース・アドレスを変更する際は、ネットワーク構造全体に影響を与えるため、注意してください。デバイス間の通信を可能にするには、各 grandMA3 デバイスに同じマルチキャスト・アドレスを設定する必要があります。 |
|
|
ヒント |
| NACKのレートが常に0を超えている場合は、デバイスのネットワーク環境を確認してください。 |
|
|
ヒント |
| 個々の値については、https://www.iana.org/assignments/dscp-registry/dscp-registry.xhtml を参照してください。 |
|
|
制限 |
| grandMA3 onPC for Windows® では、DSCP値がデフォルトの CS0 で上書きされます。 |
|
|
ヒント |
| DSCP、TTL、Data Merge Default Mode、および Data Merge Default Timeout を変更するには、Admin 権限が必要です |
構文: NetworkSpeedTest [デバイスタイプ] ["デバイスタイプ名" または デバイス番号]
詳しくは NetworkSpeedTest キーワード を参照してください。
|
|
ヒント |
| TCP および UDP 速度はパーセントで表示されます。100パーセントは、推奨帯域幅を示します。詳しくは ネットワーク設計 を参照してください。 |
NDI の改善:
Art-Net入力の改善:
MIDIの改善:
Message Center の改善:
Pool Action 設定の改善:
個別の Object Action 設定を追加:
|
|
User name[Fixture]>Assign Temp At Sequence 5 |
Timecode プールの改善:
Window Settings の改善:
ウィンドウのサイズ変更機能を改善:
新規ショーファイルの改善:
Configure Display ポップアップの改善:
新しいオブジェクトを保存する際の構文を改善:
Add Window メニューの改善:
Assign Menu と Executor Configurations ポップアップの Handle タブを改善:
Patch メニーの改善:
Windows 上で動作する grandMA3 onPC のハードウェア検出機能を改善:
Clone ウィンドウの改善:
プリセットプールの改善:
循環参照を含むレシピのプリセットには、プール・オブジェクトの背景に明赤色のアイコン(
)が追加表示されます。
プリセットの自動命名を改善(例: 埋め込みプリセットなど):
このメカニズムは、同じ機能グループの他のプリセット名を使用する前に、使用されている各機能グループの1つのプリセット名を使用します。
プレイバックバーの改善: マスター・インジケータは、エクゼキュータおよび特殊エクゼキュータの右上隅に表示されます。
それらの略称は以下の通りです。
エンコーダバーの選択ボタンを改善:
フィクスチャが Selection Grid の 0/0/0 以外の位置に配置されている場合、ボタンは X、Y、Z ラベルで、フィクスチャがどの軸上に配置されているかを表示します。
Random ジェネレータの改善:
ジェネレータの Speed マスターを設定できるようになりました。
Command Line History の改善:
マクロやキュー・コマンドを通じて実行されるコマンドは、そのコマンドのソースをコマンドの前に表示するようになりました。
例:
| OK : | Call Macro 1 |
| (Macro 1 'Select EncoderBar') OK: Select EncoderBar 1 |
Lua の改善:
Added
the possibility to asynchronously execute remote commands, using the /Async option keyword.
詳しくは /Async オプション・キーワード を参照してください。
Added the possibility to assign an object to multiple targets at the same time:
|
|
User name[Fixture]>Assign Appearance 1 At Sequence 1 + 2 + 3 |
詳しくは CopyCrashLog キーワード を参照してください。
Added the option /Remove as an extended
functionality to the CopyCrashLog keyword. In combination with the CopyCrashLog keyword, the /Remove option keyword deletes crash logs on the device after copying.
/Remove を CopyCrashLog と組み合わせて使用する方法については、/Remove オプション・キーワード を参照してください。
新しいキーワード ListCrashLog を追加。すべてのクラッシュログを Command Line History に一覧表示します。
詳しくは ListCrashLog キーワード を参照してください。
DumpLog キーワードの改善:
/Limit オプションを DumpLog キーワードと組み合わせて使用する方法については、/Limit オプション・キーワード を参照してください。
If コマンドの改善:
CleanUp キーワードの改善:
例:
|
|
User name[Fixture]>CleanUp Sequence 1 Cue 2 Part 0 /Type "Recipe" |
― または ―
|
|
User name[Fixture]>CleanUp Sequence 1 Cue 2 Part 0 /Type "Recipe" /Recipe "NoOutput" |
新しいキーワード HelpKeyword を追加。HelpKeyword は、Command Line History にキーワード一覧を直接表示します。HelpKeyword を実行し、コマンドラインの左側にある
をタップしてください。
|
|
重要 |
| Help + Please を実行して一覧をトリガーすることは引き続き可能ですが、将来のバージョンでは削除される予定です。 |
詳しくは HelpKeyword キーワード を参照してください。
Added the possibility to unassign objects from other objects
(for example Tags from Sequences, or Appearances from Groups) by using commands that combine Assign and Off:
Assign Off [オブジェクト] ["オブジェクト名" または オブジェクト番号] At [オブジェクト] ["オブジェクト名" または オブジェクト番号]
例:
"Spots DS" グループから "Red" というアピアランスの割り当てを解除するには、以下のように入力します。
|
|
User name[Fixture]>Assign Off Appearance "Red" At Group "Spots DS" |
|
|
ヒント |
| For more information about the new keywords, please read the corresponding sections above. |
新しいカラーテーマ項目:
| 説明 |
|---|
|
Pointing beams into the 2D camera lead to visual artifacts.
|
| If the 3D viewer was open and different groups were selected, illegal array values in 3D caused the console to freeze. |
| Incompatible diver versions for AMD RX 5700 XT and RX 570 graphic cards could cause the software to crash when opening the 3D viewer. |
| When using Position Calibration, the calibration points were not displayed in the 3D Viewer window. |
| 説明 |
|---|
|
Pressing and holding Help and then pressing Page+, Page-, or Oops executed the command additionally to opening the help viewer. This bug is now fixed. Now the corresponding topic opens in the help viewer without executing the command. |
| If you edited a macro, the command preview would sometimes be wrong. |
| If you assigned a sequence to an empty sequence, a pop-up would ask whether you wanted to overwrite the new sequence although it was empty. If you pressed Yes, the sequence would be successfully assigned, however, the command line would show an "Illegal Object". |
| If you used the Label keyword to label cues of a selected sequence, the command line would show an "Illegal Object Error". |
| Assigning a sequence to another sequence using the command line without writing "sequence" a second time, for example Assign Sequence 1 at 2, did not work. |
| It was not possible to assign appearances and scribbles to mirrored sequences. |
| Assigning objects to sequences created new and empty sequences in the pool. |
| If you selected fixtures by typing the FIDs connected with a + in the command line, for example 1+2+3, all attributes would be knocked in into all fixtures except for the first fixture. |
|
A pop-up opened by a macro, that required an input which was not a string, only appeared on
the screen that was in focus. This bug is now fixed.
The pop-up now appears on all screens. |
| Oopsing lasso selection in the layout was not possible. Instead the command line was oopsed. |
|
If you copied fixtures from one layout to a different layout that already included the copied
fixtures and tapped on "Create Empty Element" in the appearing pop-up, duplicates of the selected fixtures would be inserted.
|
| It was possible to store and overwrite view buttons after their view has been locked. |
| Assigning a sequence to an empty view button did not delete the screen content. |
| Elements were hidden by default when assigning fixtures to layouts. |
| Keyboard shortcuts Ctrl+Z and Ctrl+Y both triggered Oops. Now only Ctrl+Z triggers Oops. |
| Commands that employ a defined range of objects using handles could fail. |
| If you opened the Off Menu pressing Off twice, one Off would still remain in the command line. This bug was fixed. Now the command line will be cleared after pressing Off twice. |
| It was not possible to use properties of encoder banks in variables. |
| If you tried to delete an object in a layout that was not in setup mode, a pop-up would inform you that this is not possible, but Delete would still be shown in the command line and Delete would still light up. |
| If you created a customized encoder bar and made changes to the patch, this would occasionally break the selector of the encoder bank. |
| MAtricks From/To properties are returned as integers instead of floats, for example, when using Lua "Printf(ObjectList('Cue 1 Part 0.1')[1].FadeFromX)". |
| If you edited a macro line or cue command and pressed Oops, the characters would not be deleted in the expected order. |
| Updating fixtures in other cue parts, except for part 0, could cause them to be moved to part 0 of the cue. |
|
Updating a specific cue with the command line while another cue was running, for example Update Cue 1, did not update the specific cue, but the running one |
| Changes to the device configuration, output configuration and local settings did not trigger a pop-up asking the user to save the show file. |
| If you imported a layout that contained multiple fixtures with the same name, only the first fixture with that name would appear in the imported layout. |
| If you changed the Action setting in a sequence pool to something other than Select and tapped on an empty tile in the pool, an empty sequence would still be created and selected. |
| When a gel was stored and recalled outside the sRGB color space, the stored gel was recalled on the edge of the sRGB color space. |
| The software could crash after deleting a track or a single event in Timecode due to invalid memory access. |
| Cutting and Pasting multiple timecode events while you are in a session, may have caused other stations to drop out of the session. |
| In some cases, timecode events behaved as if Assert previous Events was enabled even if it was not. |
| The software could crash when executing EditSetting for a recipe in a programmer part. |
| The command line, command line history, and system monitor would show an illegal property if you opened the color picker in the Special Dialog window in the Book view and tapped on View or Sort By. |
| Some invalid syntax in the command line, for example Page 1.201 thru 1.203 at 100, created multiple unwanted objects. |
| If you stored a cue using tracking shield, in some cases values from a previously referenced preset would be stored as hard values in the cue without the preset reference. The data output was not altered by this. |
| If you had multiple fixtures with the same name in a layout, copied them and pasted them to a different layout, only the first line would reference a fixture, the other lines would not display the selected fixtures. |
| If you selected a grouping fixture in the fixture sheet, sometimes the software would crash or the GUI would freeze. |
| If you imported pages with playback masters from a show file using PSR, the playback master would be an empty executor object. |
| If you were renumbering cues, the incremental delta used to enumerate cues would not be taken from the first one in the list, but all cues would be processed. |
| Sometimes the selected color of a fixture was bound to the sRGB color space, even if the fixture was capable of having colors outside of this color space. |
| When having a lot of objects in a layout selected and then opening the layout editor the software scrolled through all selected items, and when finished it was not possible to select items. |
|
Layout elements did not have dependencies to their assigned objects. This bug is now
fixed. When exporting and importing layouts or importing layouts using PSR, the dependencies are imported as well. When fixtures are exported as dependency, they need to exist in the destination show file as well. Sequences are not exported as dependencies, as they have usually also a lot of dependencies. |
| The software could crash when overwriting an existing user profile during the import of user profiles. |
| Importing of environmental fixtures via PSR did not import the 3D models correctly. |
| The software could crash after selecting a show file for PSR and initializing the PSR process. |
| When fixing or unfixing a page, the assigned objects did not change their fix indication immediately. |
| The software could crash when storing a preset using DMX as data source while having several programmer parts with duplicate values. |
| If you cloned a large number of unordered fixtures, the cloning could fail and the command line history would only display a green bar instead of the syntax. |
| Importing files with an apostrophe in the name could lead to the name of the file being interpreted as command line input and the file not being imported. |
| If you were in a session and added a note to a cue using the command line, the note would not be visible on the connected stations. |
| Using Dimmer Cue Only would sometimes track the stored dimmer value into the next cue if a fixture had two or more attributes in which dimmer was set in the special column in the attribute definitions. |
| Starting the PSR process could lead to broken handles in commands. |
| In imported layouts that were previously exported, the appearance of some layout elements would sometimes not be imported. |
| Imported sequences that had previously been exported had wrong values for individual timings below 0.1 seconds. |
| If you overwrote an existing cue, the name of the cue would be reset. |
|
If you extracted values from a preset and another preset could be updated with those values,
Update would not light up.
|
|
On some mac devices an error appeared, stating that the hard drive was full. This can
happen if the folder permissions are set up in a way that do not allow a "shows" folder to be created. This has been improved.
A pop-up now informs the user about this and tells to check the folder permissions. |
| Deleting a generator in data pool 2 or higher deleted the entire data pool. |
| When editing Column Sets while being in session, the changes were not immediately transferred to the other stations. |
| When storing to an existing view with an appearance and the screenshot functionality was not used when storing, the appearance was removed from the view. |
| When Color Readout was set to CMY and channel sets of ColorRGB attributes were used, the values were not inverted. |
|
When you loaded a show file where the Layout Element Defaults were renamed, a new
set of Layout Element Defaults would be imported. This bug is now fixed.
It is no longer possible to rename Layout Element Defaults. In v2.2, show files with renamed Layout Element Defaults are corrected when loading the show file. After that renaming is no longer allowed. |
| If you imported a plugin in the show converter and then selected and imported another one, the first plugin would be added to Local a second time. |
|
If you executed a command with IfOutput, all fixtures would be
displayed on grid
position 1/1 in the selection grid. This bug is now fixed.
Now the fixtures are displayed as a linear selection in the selection grid for all except for selective presets. |
| If you changed the FID of a fixture using Lua, the software would crash. |
| If you exported a user profile after enabling Hide Environmental in the PSR Patch and imported it into a show file, the software would crash. |
| If you included an empty group in a command, the command would not be executed. |
| If you created a new page by pressing Page+ and assigned an executor configuration to that page, assigning an appearance to the new page would cause the executor configuration to be lost the first time. |
| Changing values for specific cue parts did not take the corresponding cue part into account. Instead, part 0 was used. |
| Show file names that contained a ' in the file name could not be loaded. |
| The software could freeze when multiple pop-ups were open at the same time and the user tried to close the top one. |
| Assigning a Sequence to a ViewButton created a hidden object on this button. Afterwards it was not possible to move a View onto this ViewButton. |
| The Preset Timings defaults for cues in the Preferences and Timings menu displayed empty buttons when no additional feature groups were existing. |
| The software would sometimes crash when executing ListRef. |
| 説明 |
|---|
| It could happen that a device was displayed twice in the output configuration if you joined and left a session several times and used Remove Absent in between. |
| When the Root Bridge of an RSTP changed, the session did not work anymore. |
| If DMX Remotes In From and In To were inverted (255-0), the resulting fader movements for the assigned object would not be executed. |
| If you left a session with the master device, changed the sACN configuration and then rejoined the session and merged all data, the devices in the session would have different sACN configurations. |
| If you joined a session with a different show file, a Session Data Merge pop-up would appear despite the show files not being compatible. |
| While in a session, a station could drop out of the session if a sequence was deleted. |
| If two devices in a session were receiving two Art-Net or SACN streams input on the same local universe with HTP, the output of the connected station would flicker. |
| PSR import of show file from external USB drive failed with an "PSR input file invalid" error message. |
|
grandMA3 onPC on running on Windows only listed real network interfaces. This bug is
now fixed.
grandMA3 onPC running on Windows also lists virtual network interfaces. |
| When the grandMA3 software sent an RDM packet to an RDM fixture, for example when changing the DMX Personality, it could happen that the RDM packet was sent with the previous value instead of the new one. |
| Sound input was not transferred to other devices in a session. |
| When connecting to a processing unit using an older show state than on the console, an unnecessary Session Data Merge pop up appeared. |
| Inviting or dismissing grandMA3 stations to a session changed the output when the current output was coming from tracked values and playbacks with blocked values in the background were still active. |
| 説明 |
|---|
| If you deleted data in a fixture type in the fixture type editor and then oopsed the deletion, physical descriptions that were linked would not be oopsed. |
| If you changed the pretty name of the dimmer in the attribute definitions tab of the patch, all sheet modes, except for the fixture, would appear blank in the fixture sheet. |
| In some cases, if a station joined a session, there would be no option for the merge of show data. Instead, a pop-up would ask the user to choose between two show files without displaying the affected data. This could for example happen, if a station with a high priority dropped out of a session and rejoined the session after changes were made to preset data that was used as a default in the patch, resulting in patch changes. |
| Alphabetical sorting of the Fixture Type column in the patch did not work. |
|
If you performed a Partial Show Read with Merge PSR after
changing the Attribute Definitions in the Patch, the changes would not be kept in the merged show
file. This bug is now fixed. The Attribute Definitions of the local show file will be used when using Partial Show Read. |
| With Partial Show Read some fixture of the local running show were deleted. |
| If the stages in the local show file had the same name (or default names), the same size and the same orientation, when you performed a Partial Show Read, stages of the local running show other than Stage 1 were deleted and all patched fixtures of the local show were added to Stage 1. |
| PSR did not work with files that were stored on an external USB flash drive. |
| If the mode of a fixture type was changed, for example from "Basic" to "Extended", fixtures of this type would not share previous values of global preset data anymore. Instead, only the first patched fixture would keep values of the global preset data. |
| If fixtures had been exchanged in the patch, recipes of cues containing the exchanged fixtures had to be recooked or merged again. |
| When editing a fixture type and then deleting the DMX Mode rows, conflicts would occur when pressing Oops. |
|
If a mode of a fixture type had conflicting attributes in geometry, for example two different
color mixing systems, the fixture type could not be imported in any mode, even if other modes
did not have any conflicting attributes. This bug is now fixed.
Now in the fixture type editor, conflicting modes and their channels are displayed in red and can be adjusted. Additionally, information about conflicting attributes in geometry are shown in the conflicts information window. All other modes work as expected. |
| Rearranging the order of stages in the patch would hide all fixtures. |
| If a fixture had unused DMX channels, the DMX Footprint shown in the Library in the Patch would be wrong. |
| 説明 |
|---|
| Entering the desk lock while touching the faders kept the faders highlighted after releasing the fingers of the faders. |
| If you oopsed a preset selection for a recipe in the programmer, the value in the programmer would be lost instead of returning to the previously selected preset. |
| Bitmaps and generators in programmer recipes did not generate output. |
| If you used the bitmap generator, switching off the source did not switch off the output. |
| The Zoom fader of the bitmap generator did not refer to the center of the input, but to the center of the canvas. |
| When increasing the value of virtual dimmers by using the relative layer, the color tone of the other ColorRGB channels increased further even if the first ColorRGB channel had already reached 100%. |
|
If a sequence was not running, executing Go- or <<< would always trigger the first cue. This bug is now
fixed.
Now if a sequence is not running and Restart
Mode is set to First Cue, executing Go- or <<< triggers the first cue. If Restart Mode is set to Current Cue or Next Cue it behaves the same way as Go+. |
| When addressing a non-existent cue in a playback command, either the first cue was executed if the sequence was off, or the current cue was executed again if the sequence was on. This bug is now fixed. When addressing a non-existent cue in a playback command, the command line now returns an error. |
| The output for mirrored sequences was not updated immediately. Instead, the sequence had to be restarted to see the changes. |
| 説明 |
|---|
|
The error pop-up "Load show failed." could appear on any screen. This bug is now fixed.
Now the pop-up always appears on all screens. |
| If you changed the width of a column in the sequence sheet, the column editor sometimes would not display all columns. |
| A screenshot that was previously stored on a view button would not disappear if you disabled the screenshot function and stored the view again. |
| Pool window preference settings were not applied directly after saving. This bug is fixed. When storing a pool window on the screen the first preference stored is used in all pool settings except for preset pools. |
| The Edit Columns pop-up in the sequence sheet could be opened several times. |
| Removing fixtures in the selection grid by pressing - did not consider MAtricks positions, so the wrong fixtures were removed. |
| If Setup was enabled in the selection grid, the selection of fixtures would not be cleared after moving them around and then selecting different fixtures. Pressing Clear now sets all fixtures as partly selected. Therefore, the workflow "Select -> Change -> Select" is possible. |
| Symbol and gobo previews were not displayed when imported from the symbols and gobos pool. |
| Properties of sounds were not displayed in the sounds tab of the running playbacks window. |
| If you toggled through the different column sets within the column set editor, the column area would be blank when cycling through the sets the first time. |
|
When the login pop-up appeared, the cursor was set to the Password input field. This bug is now
fixed. The cursor is now set to the User input field. |
| It was not possible to change the display intensity and color theme on xPort nodes and I/O nodes. |
| The indicators for parked and DMX Tester did not analyze fine and ultra channels. |
| If you adjusted the hue value of a color using the color picker after changing the saturation, the saturation would jump to a different value. |
| If you created a square using the shaper dialog and tried to adjust it afterwards, the shapers would sometimes not work as expected and could jump to full or zero. |
| If you resized layout elements in y direction in a layout in setup mode, the snap grid setting would not be respected and the elements could be resized without restriction. |
| If you scrolled in the help using the two-finger gesture, the scrolling of the page would not be in sync with the movement of the fingers. |
| It was not possible to edit a note in the Info Window by tapping anywhere below the last item in the note tab due to a very small text field. Now the text box extends to the bottom of the window and can be easily edited. |
| Recipes were displayed in the Notes tab of the Info window if they were children of cue part 1 or higher. |
| When editing an appearance in the appearance pool, the fader for Background Color showed different values than those entered using the calculator. |
| In the Appearance Pool, it was not possible to select a color from the Color Picker if the RGB values were set to 0%. |
| If you changed values in the HSB color picker and then used the hue encoder within 2 seconds, the color picker unexpectedly jumped to the wrong position. |
| If you changed values in the dimmer encoder bank and then changed the encoder bank, and then pressed Off + tapped the Dimmer encoder bank button, you could not enter the dimmer encoder bank again. |
| Fixtures were deselected when doing a 2 finger scroll gesture in a Layout Viewer window while it had Setup enabled. |
| If you opened the on-screen keyboard for the command line and typed in Help, the help pop-up would not open. |
| If you assigned elements to an Xkey and then tried to edit the Xkey, the Edit overlay would open on the small Screen 7, making it unusable. This is fixed and the Editor now opens on Screen 1. |
| If display 1 was not connected on CRV consoles, windows with encoder bar functions, such as the 3D Viewer window in Setup mode, did not display their encoder bar on the letterbox screen of the console. |
| Help overlay was displayed defective on small screens. |
| When using the virtual keyboard to write a description in the Backup menu, the text was not saved when tapping Please. |
| Entering special characters in notes using the on-screen keyboard resulted in incorrect text being entered in the note. |
| The list of stations in the Software Update menu did not refresh automatically after reboot. |
| Layout elements of fixtures could be displayed at full intensity but the intensity of the fixture was not set to 100%. |
| Changing the mode of a fixture could lead to data from a global preset not being applied to that fixture anymore. |
| If you had a user-defined area that was bigger than the display and had a special dialog window open on the shapers tab, scrolling down would lead to the visual being displayed on top of the command line instead of being hidden by it. |
| If the fixture sheet was in channel mode, in some cases fixtures would be displayed with a red background despite not having active values in the programmer. |
|
In the Generator Editor, the Speed fader did not allow values above 60 BPM. This bug is now
fixed. Now the maximum is 255 BPM with the fader and 3600 BPM with the calculator. |
| In the Info window, if you wrote a note for a sequence, after the fist letter the text would jump to the cue. |
| If Setup was enabled in the Layout Viewer, shutting down and restarting the console would shift the view by 50 px. |
| The ViewMode pop-up of the Agenda window did not display its items with the correct width. |
| If you loaded a new show file and Clock Source was set to Timer, the Clock Window would not display the default stopwatch from the Timers pool. |
| Some editors, for example for macros and MAtricks, would stay open whenever logging in with a different user. |
| If you created a view with a help window and stored it with a changed the zoom factor, the content of the help window would not be zoomed if you recalled the view later. |
| If you wanted to select elements in a window and the lasso was ended outside of the valid area, the selection would not be made. |
| The output layer in the Layout Viewer did not show the output of unpatched fixtures. |
| If you had a grouping fixture that had a multi-instance fixture as a child, in some cases Hide Subfixtures would not hide the subfixtures of the multi-instance fixture. |
|
If Show Title Bar was toggled off in window settings,
it was not possible to tap elements below the MA logo in the lower right corner.
|
| If you opened the network menu in the tab Station Control, it would be possible to operate some elements of the Stations tab if you tapped on the black areas. |
| When activating the Setup mode of the Layout Viewer again, former selected layout elements could be displayed as selected. |
| Reset 1, Reset 2, Reset 3, and Reset 4 in the Encoder Bar of the Shapers Dialog did not work. |
| The Recipe area in the Content Sheet did not display the recipes immediately after starting the sequence. |
|
If you pressed Please in the Label Dialog while having
text in the Notes area selected, the selected text would be deleted and the remaining text
would be applied at once. This bug is now fixed.
Pressing Please in the Label Dialog while having text selected does not delete the selected text anymore, but applies the current state. |
| The software could crash if you switched the Window Mode in the Info window. |
| The Layout Viewer window did not display the information about the selected layout elements so that it was readable. |
| Enabling Transpose in the sequence sheet settings would lead to unnecessary line breaks and text being cut off. |
| When adjusting values in the Special Encoder bar of the Shaper Dialog, it could happen that the shaper jumped or the shapers did not move. |
| AutoCreate for dimmer presets did not work when Dim2, Dim3, ... were used in the show file, and when they had the Special property set to Dimmer in the Attribute Definitions. |
| Recipe icons would display the wrong status in the sequence sheet if recipes in a cue part could not be cooked. |
| Vertical alignment for text did not work for layout elements that had fixtures assigned. The text field was always above the fixture. |
|
|
ヒント |
| 以下の機能は非推奨となり、近日中にソフトウェアから削除されます。以下のセクションを必ず確認し、必要に応じてマクロやプラグインを調整してください。 |
|
|
onPC ステーションに対してネットワーク経由でソフトウェアを更新する場合、インストール先システムでインストール処理中に確認が必要です。 |
|
|
ネットワーク上に複数の GlobalMaster があり、それぞれが同じセッション/ロケーション名を持っている場合、優先度の高いステーションがユーザ入力なしに引き継ぎます。 すべてのステーションの優先度が同じ場合、Online Time が最も長いステーションが、すべてのステーションに対する GlobalMaster になります。 |
|
|
Recast は、Absolute レイヤにプリセット・リンクがある場合にのみ、プリセットをキューにリキャストします。 |
|
|
旧バージョンのショーファイルを読み込むと、プログラマ内容が削除されます。 |