Jump to content

All Activity

This stream auto-updates

  1. Last week
  2. Earlier
  3. thanks, I have tried but, no... I guess something is wrong ...
  4. Hi Ignacio did you try to move the pivot in comp 3D to the head in you Background? when the pivot is in the center of the area you want to track than all the tracking attributes are correct. Rotation and X and Y should work correctly. hope it helps Yoav
  5. I'm trying to move a graphic over a video following the head movement of a person,,, the graphic is a image which is smaller than the background video and I compose it with a Comp3d The problem is that when I track the head on the video and I apply it to the image, it didn't work well, first because the position of the image is reset to 0 (but I can fix moving the curves) but the issue is that only works with position X and Y if I try to apply rotation or size it doesn't match at all any idea??
  6. Hi everyone, A new pre-release of Mistika Workflows is now available. This latest upgrade introduces many new and improved functionalities, additional task and input nodes and several other exciting enhancements throughout the software. What is New in Mistika Workflows 10.2.1? Here is the complete list of new features, and improvements made to this new version: Complex media delivery packages (“Megapacks”) New support for Panasonic 8KP2 media packs, including import/export from/to P2 and 8KP2 cards, XML metadata modification, P2 serial number assignment, and copying to multiple (x5) 8KP2 cards according to the 8KP2 standard. Also with capabilities for joining media packs and the option for generating tapeName from Panasonic user bit data. Creation of ADI v1.1 and ADI v3.1 (SkyADI) media delivery packages (client customizable nodes) Support for Sony XDROOT as an input node. New codec support Panasonic AVC intra: Import / Export MXF XAVC: Import / Export BRAW: Blackmagic RAW files Import .ts and .m2t import Flow control New Auto Trigger node: A periodic timer to trigger the execution of pending workflows via definable time interval. New Serialize inputs node: To send multiple input nodes to a single task node, avoiding the need of duplicating the whole pipeline. “Add Root” property added to the Watcher node (active by default). When active, it permits to keep the original folder tree structure of the incoming files, passing the full paths to the next nodes. Not otherwise. “Delete after processing” property added to the Watcher node, for automatic deletion of input files once the workflow has been completed. Render Logs are now created on separate files, including the date/time of creation in their names. Name Convention Highly improved Name Convention, with support for additional syntax fields extracted from media metadata (Tape Name, Color Space, …) Now a different Name Convention can be applied to each workflow. Encoding nodes now include the addTimeStamp option within the properties panel. Name Convention can be also defined on Input nodes. File transfer nodes FTP: New properties “Delete After Transfer” (and “Are You Sure”), “Include / Exclude”, “New Files Only”. Also a RenameFileList for automatic renaming options. Aspera Client: New targetRate property, allowing the user to define how much bandwidth he wants to dedicate to Aspera file transfers. There is also a new SSL Certificate login property, and a new RenameFileList property for automatic renaming. RAW extraction from camera formats Camera RAW nodes (ARRI/R3D/Canon/Sony..) now have a Debayer (From file/ Custom) property, to select between using default debayering extraction or custom settings. Transcoding nodes The interlaced property now also supports “From Input” Transcoding nodes are now able to overwrite clip’s TC. All transcoding nodes now allow changing the Tape Name in the Properties panel. “Drop Frame/Non Drop Frame/Auto” property added to transcoding nodes. Common resolution presets added to transcoding nodes. Miscellaneous New display filter “Watermark'' easy to customize at workflow execution time, either by using a .CSV file (pyCSVtoDFILT node) or by filling the Header/Body/Footer text properties (pyWatermarkCfg node). Python source code is provided to serve as an example about how to modify display filters. ConcatXLS: Merges various XLS files in one. XLS is a popular format for asset management but usually comes in multiple .xls files, and this node permits to concat all of them. Retimer added to transcoders unlocking three new ways of the frame rate modification and conversion.
  7. Hi curly, sorry but at the moment there is no integration with Wf and render farms. That is something we are considering to add. but we have no roadmap for that, and it will definitively not happen before V10.5 cheers
  8. Hi All, I would like to ask if it is possible the make use of Mistika Workflow and setup a H.264/265 transcoding farm which means I can make use of multiple workstations to do batch jobs? Regards, Curly
  9. Hi, Thanks a lot for reaching out. Sorry for the inconvenience, but the trial version of PTGui obfuscates the projects and makes them unreadable. You can try the feather and optical flow, but without seeing the stocking I don't know what is happening to it. So you can contacting us. So, you can contact us through a ticket and share with us the media, so from the support portal we can help you to create a customized preset. Best regards. Daniel
  10. I think i got it. When I start Mistika the Mosaic (M) is activated for some reason. So, if you drop in your video files and just import the stichting, you won´t see any change. Took me a while to find out. After several tries that did not work, it suddenly worked. I was very confused until it hit the Mosaic Button. It works now as promised with Hugin (no matter which version) It works with PTGui IF it´s not the trial. PTGui 12.7 Trial is not working. With PTGui 10.something (no Trial) the import of the stitching works also. But... we are ffed anyway, cause Hugin has no option for a horizontal picture angle but only one for the verrtical angle. So the picture looks like this in mistika: okayisch here, yaiks there
  11. Hey there, we have some captured "cameras" from a realtime simulation from a fulldome setting (5 beamer, 5 computer). Unfortunately i get absolutely no reaction from Mistika from the imported Hugin or PTGui projects to the workarounds shown in these tutorials: "Seamless Stitching using PTGui and Mistika VR" and "Hugin Integration in Mistika VR" from your YouTube channel. Mistika 10.3.1 (Trial) Hugin 2020.0.0.2f576e5d5b4 PtGui Pro 12.7 (Trial!) Yes, i have seen this post: If i load any of the saved projects, Mistika is doing.... nothing at all. No stichting, no failure popup. Nothing. Any idea what i am doing wrong? All of the programs have definetely other versions than in the tut videos, starting at the import/export dialogue in Mistika.
  12. Thank you for your reply.
  13. Yeah! There are many guides available on Google. You can ask your query there. There is another method of hiding task bar. Restart Windows explorer to fix taskbar malfunctioning.
  14. Can you provide me any step by step guide to it?
  15. It's quite easy. Simply Right Click on it And it will move you to setting and there you can do it easily.
  16. Can anyone help me? Task bar is not getting hidden in my PC. I am using Windows 10 Operating System. Can you please tell me how Can I hide task bar? Thanks in advance
  17. This example is the same as but this time, we will create the workflow during the execution of another workflow with a python node. Please Note you will need Wf Version 10.4.1 or later to execute this code The behaviour will be very silimar to the previous example, but in this case, 3 properties are added to the node to parametrize them; wfName: to store the name to use when creating the new workflows inputFile: to set the input file path ftpDst: to set the final ftp destination the node will also check that the inputFile exists before allowing you to execute the workflow So, with those changes, the python node would look like this: import Mistika from Mistika.classes import CbaseItem from Mistika.classes import Cconnector from Mistika.QtCore import QPointF def init(self): self.addProperty("wfName","My Test") self.addProperty("inputFile","G:/MATERIAL/formatos/EXR/CU_BIC_FX008_BICHA_V3_0035.exr") self.addProperty("ftpDst","ftp://ftp.sgo.es/") return True def isReady(self): if len(self.inputFile)==0: #no empty file supported return self.critical("myTest:isReady:len","input file can not be empty") return True def process(self): #create the example workflow wf=Mistika.workflows.addWorkflow(self.wfName) # creates a workflow file=wf.importFile(self.inputFile,True) #automatically create a node from a file (the node created depends on the file type (It is similar to droping a file into the workflow editor. The second parameter says if the file comes from a sequence print file file.pos=QPointF(0,0) prores=wf.addNode("ProRes",CbaseItem.NODETYPE_TASK) # add a prores file (From the Tasks group. this helps to diferenciate nodes that appear in more than one group (such us FTP) print prores prores.pos=QPointF(300,0) # reposition the prores node (just for clarity) ftp=wf.addNode("FTP",CbaseItem.NODETYPE_OUTPUT) # add an ftp output node print ftp ftp.pos=QPointF(600,0) # reposition the prores node (just for clarity) file.getFirstConnectorByName("VideoOut").link(prores.getFirstConnectorByName("VideoIn")) # connect the nodes prores.getFirstConnectorByName("VideoOut").link(ftp.getFirstConnectorByName("File")) # connect the nodes #populate node properties file.gamma="Linear" # define source color space file.gamut="ACES (AP1)" prores.colorSpace="Rec2020" # define destination Color Space prores.resolution="HD 1080 (1920x1080)" # define destination resolution prores.displayFilter="watermark" # set a display filter called watermark ftp.url=self.ftpDst # set the destination ftp address wf.giveBackAffinity() # this function will be needed in versions >= 10.4.0 to give the management of the created workflow back to the system return True To create the node with the code above you can paste the node in the script editor, and using Right Mouse Button->Save In ibrary, and call it "myExample". that will create a myExample.py in the SGOAppData/shared/workflowsLibrary directory and a myexample.xsd in the SGOAppData/shared/config/schemas directory. the myexample.xsd needs to be edited in order to add the properties defined in the python script. here you have an example of a myexample.xsd file with the properties added <xsd:schema xmlns:sgo="http://www.sgo.es/2017/sgo.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element sgo:categoryType="categoryCollapsible" name="myExample" sgo:visibility="0" sgo:sortOrder="0"> <xsd:complexType> <xsd:sequence> <xsd:element name="objectName" type="xsd:string" sgo:visibility="0" sgo:sortOrder="0"/> <xsd:element name="color" type="color" sgo:visibility="0" sgo:sortOrder="1"/> <xsd:element name="wfName" type="xsd:string" sgo:visibility="0" sgo:sortOrder="10"/> <xsd:element name="inputFile" type="universalPath" sgo:properties="readOnly|urlVisibleButtonBrowser|pathNameFilters('All Files (*.*)')|fileDialogWindowTitle('Select a File')" sgo:visibility="0" sgo:sortOrder="11"/> <xsd:element name="ftpDst" type="xsd:string" sgo:visibility="0" sgo:sortOrder="12"/> <xsd:element name="code" type="textEditor" sgo:visibility="0" sgo:sortOrder="51"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> As soon as you write this xsd file in the schemas folder you will see the new properties appearing in the properties editor, like this:
  18. Hi all, Here you have a small example to illustrate how to create workflows using Py scripting In this example, the created workflow will look like this: Code: # imports used in the example import Mistika from Mistika.classes import CbaseItem from Mistika.classes import Cconnector from Mistika.QtCore import QPointF #create the example workflow wf=Mistika.workflows.addWorkflow("My Test") # creates a workflow file=wf.importFile("G:/MATERIAL/formatos/EXR/CU_BIC_FX008_BICHA_V3_0035.exr",True) #automatically create a node from a file (the node created depends on the file type (It is similar to droping a file into the workflow editor. The second parameter says if the file comes from a sequence file.pos=QPointF(0,0) prores=wf.addNode("ProRes",CbaseItem.NODETYPE_TASK) # add a prores file (From the Tasks group. this helps to diferenciate nodes that appear in more than one group (such us FTP) prores.pos=QPointF(300,0) # reposition the prores node (just for clarity) ftp=wf.addNode("FTP",CbaseItem.NODETYPE_OUTPUT) # add an ftp output node ftp.pos=QPointF(600,0) # reposition the prores node (just for clarity) file.getFirstConnectorByName("VideoOut").link(prores.getFirstConnectorByName("VideoIn")) # connect file->prores prores.getFirstConnectorByName("VideoOut").link(ftp.getFirstConnectorByName("File")) # connect prores->ftp #populate node properties file.gamma="Linear" # define source color space file.gamut="ACES (AP1)" prores.colorSpace="Rec2020" # define destination Color Space prores.resolution="HD 1080 (1920x1080)" # define destination resolution prores.displayFilter="watermark" # set a display filter called watermark ftp.url="ftp://ftp.sgo.es/" # set the destination ftp address once you have this kind of script, you can add it into a GUI menu button using the following steps: 1.- Write the script in your own myExample.py file There is a default location in SGO AppData/shared/scripts but you can write the script in any other directory 2.- Add it to the menu using the the bindPyFile command: i.e. lets suppose my py script is "c:/tmp/myExample/py"example and I want to create a command called "My Example" in the "menu bar->My Scripts" submenu I can use the following command: Mistika.app.bindPyFile("menuBar->My Scripts","My Example","c:/tmp/myExample/py",10) If "My Scripts" menu does not exist. it will be created as well. The number 10 represents the load priority, and it can be used to order the items in the menu (from lower to higher values ) This command will create a bind in the "SGO AppData/workflows/codeBinds" folder linking the menu and the created py file. to delete the menu, delete the bind file from that folder (the change is applied the next time the sw starts).
  19. Hi everyone, An upgraded version of Mistika Boutique is now available with Dual Output for Dolby Vision FX, a new “Switch to second video track” option added to Macros... and so much more! Here is the complete list of new features, and improvements made to this new version: New features Dual Output for Dolby Vision FX enabling the Dolby Vision FX to be applied in only one monitor with original media being displayed in the other one. A new “Switch to second video track” option added to Macros, displaying the video tracks that are hidden in some cameras, such as Qoocam or Vuze for example. Fixes Fixed “TC Rules”/Timeline TC in the output tab. Improved behaviour of the qualifier. R3D folder structure is now recognized correctly, so the Media Browser can be used accordingly to import R3D files. (Tangent) Shapes are now being displayed in the correct vector. Audio parameters can now be propagated correctly between clips. Shapes are no longer being eliminated when deleting a parameter. Shape points can now be moved individually when the tracking is complete. Alexa Mini mxf files can now be read correctly. Fixed focus behaviour when copy/paste in Color grade. Fixed rendering of the Mainconcept AVC Intra 200 P2 codec. TC in audio clip is now being kept correctly when audio and video are separated by A/V break. The Timeline TC is now correctly refreshed when navigating by using the shortcuts Next/Prev Edit. The default option of the embedded Scope in Color grade is now correctly set to input. The selector to change the LUT is now always visible in the Time editor. Fixed behaviour of the Precision color control panel when performing tracking and navigating to Fixed Vectors. Fixed behaviour of the Precision panel when using the ring to modify the Hexagon values. Cache color indicator is now being refreshed in a cached clip when the color grade is modified. EDL files containing characters with accents now work properly. Fixed re-analysis functionality in Dolby Vision FX. Fixed an issue related to a split in the SDI output when a P2 file was displayed. Fixed Copy/Paste functionality: users are now able to correctly copy and paste shapes and grades between shots. French accents are now correctly displayed in EDL files. Fixed moving around the Timespace’s tracker tab to proceed one frame only. The cursor in Qualifier is now displayed properly. Fixed rendering of DNxHR 444 format. Mistika can now read .ts and .m2t files properly. The list of loaded LUTs in the color grade is now correctly saved. The default result size is not affecting the cache behavior anymore. The “Undo” command now works correctly in “Offset” and “Contrast” mode. The Keyframe Graph is not affected anymore by zoom-ing in when the visual editor is zoomed by the arrow keys. Fixed behaviour of the Zoom-in functionality in Visual Editor when the Keyframe Graph is open. Non Drop frames in Phantom formats are now properly recognized.
  20. Hi everyone! We have released an upgraded version of Mistika VR. You can download now this new version from your Online SGO Account. New features KanDao 60 fps resolutions: 5616x2012 and 6016x2012 support Fixes Fixed move interface between different resolution monitors.
  21. Hi, I'm evaluating a trial of Mistika Boutique 10.2.0 on my 2019 MacPro. Everything is working great, but I can not get Arri Raw to play back at all. This includes .ari and mxf wrapped from the Amira. The app just sits there and I get a spinning ball until I hit stop on my tangent panel. I have watched the "Performance Setting Tutorial" on YouTube, but nothing I set seems to help with the Arri files. Maybe I'm missing a setting, can anyone recommend an optimal config setting? These are my specs: 2019-Mac Pro with 3.5Ghz 8-Core Intel XeonW, MacOS Big Sur 11.4 288GB RAM, Single AMD Radeon W5700X Directly attached TB3 SSD Raid. FWIW, I can play back the same files in realtime on this system with other software packages , so I don't believe I have a hardware bottleneck. Thanks in Advance! Michael
  22. Hi! Thanks a lot for reaching out! In which software need to create the Keyframes? Mistika VR or Mistika Boutique/Ultima? Here you have the explanation about the keyframes in Mistika VR, however, I can explain you how to create in Mistika Boutique/Ultima: To animate any parameter, just right-click on the parameter and click on add keyframe (In the edge points case, select the Yaw or pitch in the Edge points tab, it will keyframing both parameters). You´ll notice that the parameter turns blue. (It indicates that it´s animated). The keyframes are painted as a little arrow in your timeline. When you have more than one (the parameter is animated) you´ll notice a blue line that connects the keyframes. To navigate between the keyframes just "Shift+right" or "shift+left" or by clicking: To delete it, just navigate to your keyframe (The parameter turns green). Right-click and select "Remove keyframe": I hope it´s useful!! Cheers! Carlos
  23. I often see the footages where subjects stay on different stitching borderlines at different times. So, I have to adjust edge points, but I wish I can keyframe edge points so that subjects staying on stitching borderlines can be perfectly stitched. It seems like there's no way to keyframe edge points on Mistika at this point. Any solution for this?
  24. Hi everyone, An upgraded version of the industry’s favourite VR stitching solution Mistika VR is now available, adding PTGui 12 integration and support of Kandao’s latest camera, the Obsidian Pro. This latest release is now available to all existing Mistika VR users at no additional cost and can be downloaded from their Online SGO Account. New features Support for KanDao Obsidian Pro Integration and support for PTGui Fixes Fixed “Source Name” option when rendering ZCam media.
  25. A preset for the DJI Mavic 2 Zoom (25 stills panorama) now available. As the drone is not entirely precise while pointing in the 25 directions, every shot needs to be individually adjusted. To use the preset, -Drag the folder containing the 25 stills into MistikaVR Choose "Import files as individual images". -Apply the attached preset -Toggle the "proxy" mode (rightmost button of the tools bar) for faster calibration: We are using a lot of high resolution images here! -Use the "Improve Angles" tool. Do not use "improve offsets", as all the shots are actually made by the same rotating camera and the lens center offset should not differ from each other. This may be relatively slow, 10 or more seconds. You could use the "Improve Angles" more than once if the images did not yet align well. -Switch the "Proxy" off for full resolution. -Switch the Options->"Optical Flow" on. Thanks to Błażej Krajczewski for the calibration samples. Dji_Mavic2Zoom_25ShotsPano_4000x3000.grp
  26. Hi! Thanks a lot for reaching out! This circle likely is the part of the 360º sphere that the lenses couldn´t capture. In some cameras, the fisheye lenses can´t cover the entire 180º in top and bottom, so, when you do the stitching, this lack is shared by the rest of the lens and causes the black circle on top and bottom. To make sure, you can send me the media that causes these black circles. Please, open a ticket in our support portal: https://support.sgo.es In this way, we can be sure that this is the reason or there is another reason. Have a nice day Carlos
  27. My questions is simply as the title. Sometimes I see them in a video, and sometimes I don't. What causes black hole in a video? My guess is that black hole is made because there's no repetitive pattern on the top and bottom. I'm not sure though. Please, share your expertise if you know why. Thank you!
  1. Load more activity
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.