!!INSTALL!! Swap Magic 3.6 CD DVD (para PS2).zip
Brandi Baylon
PL Mount Modification Kit (Blackmagic Pocket Cinema Camera 6K / 6K G2 / 6K Pro) allows users to convert their BMPCC 6K, 6K G2, or 6K Pro camera to a PL Mount through a short modification process. All necessary tools are included in the kit. The PL Mount is made of stainless steel and aircraft grade aluminum and includes the PL port cap. Shims are provided with the kit for adjusting back focus and the appropriate shims are installed prior to shipping. Further adjustment should not be needed but can be checked using a wide angle lens and a focus chart. The BMPCC6K's own EF Mount screws are used to attach the PL Mount to the camera.
The modification process can be reversed. If you choose to go back to EF mount in the future, you can do it by reversing steps in the process, however, switching back and forth will eventually strip the plastic in your camera as the sensor block is made of a composite plastic material (it is strong but still plastic).
With this kit, the modification is performed by the user. Optional WC installation service for an extra $250. Email in...@woodencamera.com for more info.
Important Note: The majority of modern, s35mm lenses are compatible, but lenses with a rear protrusion longer than 40mm, measured from the PL flange, are not compatible and other lenses may not fit due to the shape of the original Blackmagic 6K body design. Please review the diagram below to measure the protrusion requirements for fitting your lens into a modified BMPCC6K. If you are still unsure, you can check the BMPCC6K Compatible PL Lens Chart here.
* Others
Fixed programming issues when using encoder to reach zero while operation mode is absolute (jumping to full)
Fixed group mask filter
Fixed loading specific show files
Fixed touching a patch command in the "Commands" popup also being applied to the underlying grid cell (unintentionally preparing another command)
Fixed cue-only issues when using selected filter
Color temperature rendering fixes and improvements
Selection state in Playback button view is now stored with the view
Fixed USB-DMX PCBs losing configuration
Fixed hidden subnet mask setting
Fixed SNAP+TOGGLE locking to cue 0 when global rate is on
Fixed control surface communication issues when 24 fader module is connected
Fixed value windows not reflecting channel group assignment changes until restart
Fixed REL ALL EXCEPT cue macro feedback
Fixed RECORD SCREEN on external display
Improved support for touch right-click by holding
Fixed load issues for specific older show files
Fixed storage of cloned fixtures into fixture groups
Fixed cues fades pulsing non-RGB color emitters when override is on
Fixed first GO after UPDATE CUE re-executing the updated cue instead of moving to the next one (when "reset to first cue" option is disabled)
Fixed SWAP FIXTURE losing DMX addressing (even with identical DMX footprint)
Fixed DELAY/FADE command requiring additional "@" key press
Fixed recording/assigning submaster banks 101-500
Added configurable default setting for showing custom object colors
Updated SQL server for pending security protocol compliance
Fixed cue macros (including SET CL VALUE, MIDI notes) not working
Fixed loss of preset value for last logical channel after show file upgrade (typically visible in defaults preset): consider loading your pre-4.6 show again!
Fixed installer aborting due to IIS installation (which triggers installation of RDM report pages)
Fixed missing options due to duplicate names in direct access to parameter
Improved Web control sizing (like Art-Net node management)
Scroll wheel can now also be used for personalities in the fixture type library browser
So you might think why do I need SwapMagic when I can just use any game for that?
Well, swap magic makes the rotation stop first so you can easily change to the disc you want without harming the drive. Once swapped you can then simply press x to continue without any hurry.
Additionally you won't need to tape your PS2 to trick it to spin the disc when opened.
Once you've burned your DVD-R with the ISO data, you need to boot a PC to the CD/DVD drive. With Ubuntu, you are given the choice to use the LiveDVD, which runs the Ubuntu operating system from the DVD-R in real time, or install to disk. We want to install. Once you select that option, make sure you do a custom install. That way we can be sure we are installing to the flash drive, and not the hard drive (that would be bad). Pay close attention to the drive descriptions. I recommend removing and recreating the partition on the flash drive using the EXT4 file system. Also, skip adding the swap file. Normally, it's highly recommended, but in a case like this, a swap file would slow down the read-write processes on the flash drive as well as take up valuable space that could be used for programs.
Subscriptions are the lifeblood of LWN.net. If you appreciate this content and would like to see more of it, your subscription will help to ensure that LWN continues to thrive. Please visit this page to join up and keep LWN on the net. By Jonathan Corbet
September 16, 2008 LWN's 2008 Kernel Summit coverageInitramfs is a useful tool; it allows a filesystem (in cpio format) to betacked on to the end of the kernel executable image. When the kernelboots, it unpacks the filesystem into RAM and mounts it as the initial rootfilesystem. Therein will be found enough bootstrap code to get the systemproperly initialized and running from the real root filesystem. It ispossible to boot a system without an initramfs, but essentially alldistributors make use of this facility.Dave Jones, the Fedora kernel maintainer, made the claim that the initramfscode is one of the most boring parts of any distribution. Even so, alldistributors still roll their own initramfs code. It is a pain, and itdoesn't make any sense. So Dave looked into what's going on in this codeto see if the situation could be made any better.The Red Hat initramfs image, used in Fedora, is the product of many years'worth of heritage and workarounds. Whenever the developers have run intoan early bootstrap problem, they have thrown another hack into theinitramfs code to make things work again. This code is ugly, but nobodywants to switch to anybody else's version. They fear that a differentinitramfs will lack all those hard-earned workarounds, and, besides,everybody feels that their particular solution is the best.So what does the initramfs code do? Its job is to load any necessarystorage drivers, then wait for the storage devices to settle. The swapsystem needs to be enabled. If the swap partition contains a hibernationsignature, a resume from disk operation is begun. Otherwise the initramfscode must find the root filesystem (an operation which may require settingup the device mapper or getting networking going), mount it, then switchover to the real operating system. Red Hat's version has to support a widevariety of root filesystems, and contains a lot of crufty code. The situation is pretty much the same with the other distributors. Wherethings differ, it often has to do with differing kernel configurations,and, in particular, differences of opinion over whether specific codeshould be built into the kernel or built as a module.Differences between initramfs setups can create some annoying problems. Sometimes these differences are enough to cause some kernel configurationsto fail on one distribution. It would make life easier for everybody if amore uniform set of tools were used for early system initialization. Thiscode could be part of the kernel tree, and it could change, when needed, inresponse to kernel changes. In the end, things would just work.There's a few details that would have to be dealt with. Some distributionsuse the in-kernel hibernation (suspend-to-disk) code, while others areusing TuxOnIce. It seems like maybeit's time for everybody to standardize on one hibernation solution. Whilemost distributions have long since switched over to the parallel ATAdrivers, some are still using the older IDE subsystem. Not everybodysupports root filesystems on iSCSI devices. And so on. But these areproblems whichshould be amenable to a solution.Dave is going to start by adding a "make mkinitrd" option to the kernelbuild system; it will create a version of the Fedora mkinitrd for now.Others will be encouraged to join in and help make it work for everybody.Beyond that, Dave suggested that the developers could start to build a setof reference boot scripts in the kernel. Once again, this is an area wheredistributors tend to roll their own code; they could benefit from bits ofcode showing the best way to initialize parts of the system. Al Viropointed out that there will be problems coming from the fact that differentdistributors use different shells in their early boot code. That led to anextended discussion of the evils of nash and the celebrations which willensue upon its eagerly-awaited demise.There was some brief discussion of klibc - a small version of the C libraryintended for use in initramfs code. That project has been stalled for sometime due to lack of interest; it could probably be restarted without toomuch trouble. The problem is that, despite all their wishes, distributionsoften end up having to use glibc in their initramfs filesystems. Thebiggest driver here appears to be internationalization, which is notproperly handled by the various stripped-down libc implementations outthere.Getting back to the concept of a uniform set of initramfs tools, Linussuggested that the process could start with some baby steps. The kernelcould include some bits of code which are automatically added into whateverinitramfs image the distributor provides. There are challenges to makingthat work too, of course. The best way, perhaps, is just to dumpeverybody's initramfs and start over with a new, clean version. Thatproject may get underway before too long. (Log in to post comments) KS2008: Bootstrap code Posted Sep 16, 2008 9:23 UTC (Tue) by nix (subscriber, #2304) [Link]