Differences

This shows you the differences between two versions of the page.

--- personality:create_r20_from_d4 [2022/05/30 12:11] – icke_siegen
+++ personality:create_r20_from_d4 [2024/08/24 08:19] (current) – icke_siegen
@@ Line 1: / Line 1: @@
 ====== Creating R20 files from d4 personalities ======
-<fs small>**(This is NOT an official documentation but simply based on my personal experiences - it might be not complete or even simply wrong in some aspects. Please give feeback if you find anything that you think should be improved.)**</fs>
+<fs small>**(This is NOT an official documentation but simply based on my personal experiences - it might be not complete or even simply wrong in some aspects. Please give feedback if you find anything that you think should be improved.)**</fs>
 R20 files had been the personalities for the Classic consoles from the Pearl 2000 on. After production of the Classic consoles was stopped, Avolites also ceased to offer free personality service for this system in 2019. You can still download the existing personalities, but no new ones will be created.
@@ Line 11: / Line 11: @@
 Items currently **NOT** covered by this page are
   * conditions in d4 files (need to be stripped for R20 files)
-  * 16bit dimmers
   * [[personality:compatibility attributes|]]
@@ Line 39: / Line 38: @@
 ===== - Identify the correct d4 file =====
-We assume that a d4 personality for your fixture already exists. Luckily they usually have verbose file names - have a look in the personality folder (with the PC suite installed it is ''C:\Program Files (x86)\Avolites\Titan\FixtureLibrary''). If you don't find what you need then search at https://personalities.avolites.com/ or https://www.avolites.de/downloads/d4find for the correct filename. If you still don't find anything then request the personality for Titan or build it yourself (this might be explained on another day).
+We assume that a d4 personality for your fixture already exists. Luckily they usually have verbose file names - have a look in the personality folder (with the PC suite installed it is ''C:\Program Files (x86)\Avolites\Titan\FixtureLibrary''). If you don't find what you need then search at https://personalities.avolites.com/ or https://www.avofixturefinder.com for the correct filename. If you still don't find anything then request the personality for Titan or build it yourself (this might be explained on another day).
 If you have found the correct d4 file copy it to a suitable location, e.g. your desktop, and open it  in the Titan Personality Builder.
@@ Line 112: / Line 111: @@
   * {{ :personality:eqfu2608.r20 |EQFU2608.R20}}
   * {{ :personality:eqfu2617.r20 |EQFU2617.R20}}
+----
+===== - Finetuning / bugfixing in R20 files =====
+There is a good chance the exported files work and can be used in your Classic console. However sometimes you might need to tweak the R20 files directly. At least now you should have read chapter 14 of the [[https://www.avolites.com/software/downloads/pearl-2008-2010-tiger|Pearl 2008 and Tiger Manual]] to get a coarse idea about what is going on. Then load the file into a text editor (I prefer Notepad++) an edit to your liking.
+{{ :personality:r20_20_16bdim.png|}} One example of where you need to edit the R20 files directly is a very specific issue with the old software and 16bit dimmers: there are fixtures where not only pan, tilt or e.g. the gobo are controlled in 16bit resolution, but also the dimmer is, taking 2 Dmx channels and allowing a very fine controlling. Unfortunately the classic software has problems handling this: you can e.g. set the dimmer to 0 using the channel menu, but as soon as you hit ''Clear'' the dimmer is slightly on again: the ''Dimmer fine'' channel (LSB) resets to 254 instead of 0, effectively bringing the dimmer output to approx. 0.4%.
+The fix is to make the personality with an 8 bit dimmer, and set the Dimmer fine channel to 0. Example here is the Elation Arena Par Zoom v2 15 DMX - you can use the {{ :personality:elation_arena_par_zoom_v2.d4 |Titan Personality}} and export the R20 files as described (hint: references are already in, only two wheels need to be mapped), or you directly check the file {{ :personality:elapzm26.r20 |ELAPZM26.R20}} -- this is mode 5 of this fixture, and the channel assignment is this:
+^ Channel  ^ Function      ^
+| 1        | Red high      |
+| 2        | Red low       |
+| 3        | Green high    |
+| 4        | Green low     |
+| 5        | Blue high     |
+| 6        | Blue low      |
+| 7        | White high    |
+| 8        | White low     |
+| 9        | Colour Macro  |
+| 10       | Dimmer high   |
+| 11       | Dimmer low    |
+| 12       | Shutter       |
+| 13       | Dimmer Speed  |
+| 14       | Zoom high     |
+| 15       | Zoom low      |
+Now in the ELAPZM26.R20 file find the DMX section which looks like this:
+  ;----------------------------------------------------------------------------
+  ; DMX channel description
+  ;
+  ; Column by column description of each DMX channel
+  ; 1. The channels bank number (1..20)
+  ; 2. The upper faders in the bank (1) or the lower faders in the bank (61)
+  ; 3. Channel type (L=LTP, H=HTP, I=Instant LTP, S=16-bit instant LTP,
+  ;    s=16-bit Fadeable LTP
+  ; 4. DMX offset (1..number of DMX channels)
+  ; 5. The output level is proportionally reduced by this level (0..100%)
+  ; 6. The curve number (applicable only to HTP channels), usually set to 1
+  ; 7. Inverted (I) or Normal (N)
+  ; 8. Attribute type (A=Colour Wheel 1, B=Cyan, C=Magenta, D=Yellow,
+  ;         E=Pan, F=Tilt, G=Iris, H=Dimmer, I=Gobo1, J=Gobo2, K=Gobo1 Rotate,
+  ;         L=Focus, M=Gobo2 Rotate, N=Colour Wheel 2, O=Shutter, P=Prism, Q=Zoom,
+  ;         R=Effect Rotate, S=Frost, T=Red, U=Green, V=Blue, 0=uncategorised)
+  ; 9. Checksum channel (Always 1)
+  ;10. Attribute name, must be enclosed in quotes and upto 12 characters allowed
+  ;11. The ON value of this channel (0..255)
+  ;12. The Highlight level of this channel
+  ;13. The Lowlight level of this channel
+  ;
+  DMX
+    1   s    1   100   1N   T   1   "Red"             255   255     0
+     0   L    2   100   1N   T   1   "Red Low"         255   255     0
+   61   s    3   100   1N   U   1   "Green"           255   255     0
+     0   L    4   100   1N   U   1   "Green Low"       255   255     0
+    61   s    5   100   1N   V   1   "Blue"            255     0   230
+     0   L    6   100   1N   V   1   "Blue Low"        255     0   230
+     1   s    7   100   1N   0   1   "White"             0     0     0
+     0   L    8   100   1N   0   1   "White Low"         0     0     0
+     1   I    9   100   1N   A   1   "Colour Macro"      0     0     0
+     1   H   10   100   1N   H   1   "Dimmer"          255     0     0
+     0   s   11   100   1N   H   1   "Dimmer Low"      255     0     0
+    61   L   12   100   1N   O   1   "Shutter"         255     0     0
+     1   L   13   100   1N   0   1   "Dim Spd"           0     0     0
+     1   s   14   100   1N   Q   1   "Zoom"            127     0     0
+     0   L   15   100   1N   Q   1   "Zoom Low"        127     0     0
+  END
+  ;
+  ;----------------------------------------------------------------------------
+You can easily find the two lines for the dimmer channels:
+     1   H   10   100   1N   H   1   "Dimmer"          255     0     0
+     0   s   11   100   1N   H   1   "Dimmer Low"      255     0     0
+While the first line is absolutely okay the second line needs some tweaking: Nick Morris (the personality master) wrote about this
+>> ...just change Dimmer Low channel type to 8bit HTP (H), move Dimmer Low to an empty wheel slot (for example ... 11 1) and set Dimmer Low attribute type to uncategorised (0).
+We change the second line so that it reads
+    1   H   11   100   1N   0   1   "Dimmer Low"      255     0     0
+Now having patched the edited personality the dimmer low channel is unaffected by the main dimmer attribute as it is in another category and on page 2:
+{{:personality:r20_21_8bit_dimmer.png|}}
+(Frankly, when pressing clear, the wheel still shows a dimmer value of 0.3% -- but if you check the DMX output you'll see it is 0. Chalk it up to another issue...)
 ----