Jump to content

Rakesh Malik

  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Rakesh Malik

  1. Tech support got me back up and running pretty quickly (as usual).

    I'm discovering that the Kandao camera that I have doesn't apparently record metadata with the video clips, so that part I'm still not sure how to get around.

    Where should I be looking for the camera presets in Mistika Boutique? Am I going about the stitching the wrong way?

    My approach was to load the six clips for a single shot into the time space, and then add a VR stitch on top of them. Then I added a VR view on top of that. 


  2. Thanks for the pointer. I'll take a look at the video. I had to file a ticket with support yet again (seems it's been every other month for as long as I've been a subscriber) for the defective license server refusing to let me start Mistika though, so I'm dead in the water for the moment ?


  3. I'm working on stitching some VR footage captured using a Kandao Obsidian Go, and being new to doing this, struggling a bit. It seems like the Go doesn't store metadata in its video files, and the Kandao Studio app is also having trouble getting the stitches right. Its stitches have some huge gaps in them, like they're dropping one camera angle or something. That part I pinged Kandao about, but in the mean time does anyone have any advice on getting started with the stitching?


  4. That was it, I was working on a new timeline, but not a new project. The raw params are back ?

    I must have misunderstood, I though the floating windows could be moved off of the desktop. But now that I have the raw parameters figured out and some coffee perking me up I can spend some time today getting familiar with the new color corrector.

    • Like 2
  5. Where are the raw parameters? I'm not seeing them anywhere for my Redcode clips.

    Is there a way to move the scopes to another monitor? It's not letting me drag them off of the main editor window to my 2nd screen.

  6. On 3/5/2020 at 6:58 AM, jan1 said:

    That sounds weird. Are you on a Mac or PC for that?

    In theory the Tangent Elements and Wave 2 should be quite similar in that regard as they go through same mapper. I've had no problems with it.

    You do mention Resolve connecting to it in the interim causing issues. I had some cases lately where Resolve doesn't completely die. Even though it looks like the app is closed, if you look in the task manager there is still a process hanging around that I have to kill. So maybe that is your issue - that some other app still is attached to it, and that's what the reboot clears out? I think the Tangent Mapper you can also see if an app is still attached, can't you?

    You've seen my posts on LGG... you should know I haven't been wasting money on fruit machines ?

    Does Resolve even use the Tangent mapper? I was under the impression that it didn't, which prevented anyone from updating the mediocre Resolve implementation.

    I haven't verified yet, but I think that you might be right with that theory. Resolve likes to fake exit, but if I don't go looking for it, I don't see it floating around in the task manager. And while I've had a couple of cases where I spun up Mistika and had to restart it to get it to connect to my panel, that's been rare -- unless I'm going back and forth between Mistika and Resolve. And I haven't run into anything like this bouncing between Mistika and Scratch. It makes Scratch and Mistka a nice pair; Scratch is great for dailies, which Mistika isn't, and I haven't figured out how to automate what I do in Scratch using Workflows yet.


  7. To update... I've found that if I have the Tangent mapper running, Mistika usually connects to the Wave2 on startup... unless I let Resolve connect to the panel in the interim; after that the only thing I've found that enables Mistika to connect to it again is to reboot the computer. Sigh... 

    Scratch and Mistika both work well with the Tangent panel, and I've always thought that Scratch's mapping was quite good... until I got it working with Mistika. Now the Scratch mapping, as deep as it is, feels a lot less elegant ?


    • Like 2
  8. Selecting it in mconfig didn't work; the Tangent mapper didn't show Mistika connected to the panel. I followed the steps on that page, but didn't have any better success; assuming that is that I have the right Tangent driver kit installed. Tangent's page doesn't show anything in the application support section for Mistika Boutique, so I just download the Tangent Hub installer and tried that. I've tried with the Use Synapse/Arc option on and off, same result. 

    Any ideas?





  9. R3d isn't done on the Afterburner card. It's implemented via Metal to get GPU acceleration. 

    I wouldn't be surprised to start seeing Agilex cards elsewhere, not just under the Afterburner brand. Intel is most likely going to be happy to sell it to others... especially with AMD's repeated drubbings. ?

    I'm using both Scratch and Mistika right now. Both do some things extremely well that I wish could be combined into a single application sometimes.

    In general, I prefer Scratch's UI, but Mistika is a wonderful compositing application, and I love how easy it is to simply roll your own delta keyer using channel booleans and the clean plate node. I honestly have no idea how to go about setting that up within the timeline itself, but it's nice and easy in the node graph (which is why I couldn't set it up in the timeline -- I didn't try to ? ).

    Speed... Scratch. Nothing comes close. Mistika finally got into the ballpark with the new Red SDK update, and I suspect that Resolve will be close now also. 

    The visual grading tools are very nice in Scratch. Being able to click on a point in the image and manipulate is rather pleasant, even though you can easily mangle the whole thing.

    Conforming in Mistika is kind of a pain. That has actually been the main impediment for me in using it on more projects. The tools are all there, but they're clunky as all hell, so generally I don't much like conforming in Mistika. There's no elegant way to view the reference video along side or over the raw video, and there doesn't appear to be a particularly straightforward way to simply replace a clip. In Scratch, you select the replace mode, hunt down the clip you want to replace the erroneous clip with, and drop it in place. Then you just type the right timecode into the "in" field for the clip, and Bob's your uncle. I wish it were that easy in Mistika. Hopefully there's a nifty trick there that I don't know about yet... 

    Most of the time however I can get a pretty clean conform from Resolve using AAF, so for dicey conforms I sometimes just do the tedious part of it in Resolve which has by far the best editing toolkit of the three (no surprise) and export an AAF. That's usually almost 100% spot on, and saves a lot of work, though I think it's a bit comical to be using Resolve as a conforming tool ?

    The Red SDK update with Mistika 8.8.10 made a big difference. It's a LOT faster now, to the point where it wasn't usable without a monster machine similar to Jan's, to now I can use Mistika on my ZenBook Pro Duo. I can't really get much use out from the 2nd monitor on my machine in Scratch or Mistika. In Mistika, not at all. In Scratch I can only use it as the second monitor in dual head configuration, which mirrors the AJA output.


    • Like 1
  10. I have a laptop with a built-in second monitor, and no way to make use of it with Mistika. Being able to drag the scopes onto the 2nd monitor would be nice, but also being able to put the node tree there would be useful, particularly since it's a half-height 4K monitor...


  11. I have a shoot coming up this weekend, with a small budget, which means that we probably will not have a DIT... so I'm thinking that it would be nice to set up a workflow to help with this.

    What I'm hoping to do with the workflow is as follows. It doesn't have to be triggered automatically, and that might actually be a bit awkward to do with a watch folder due to the windows driver letter business anyway, which is outside your control. Hence the awkward part.

    So my ideal would be:

    Plug in the Red minimag reader and the SD card reader

    Copy the audio + video to two drives

    Load the video, sync the audio by time code

    Embed the scene + take from the audio files into the camera metadata

    Render ProRes proxies with production audio


    I'd be fine with setting up the source and destination folders, and starting it manually, but it would be very helpful to have the rest automated.


  12. I just received a couple of edits to grade, and I'm planning to use Mistika for at least one of them, which means I'll be doing some of this soon... 

    On 9/19/2019 at 5:21 AM, cbolanos@sgo.es said:

    However, I'd say that if you only want your grade to be propagated to the cuts that belong to the same shot, there's no need to use the linearize effect, just using the Match and Paste effect selecting the "Match Reelname" property will propagate the grade.

    Nice trick to know!

    For this sort of situation I'm really fond of gangs. I like being able to to click through the timeline and add clips to a gang, and then just pick one and grade it. If one needs a power window or something that won't work across the shots, I add a color node to that one clip.  

    On 9/19/2019 at 7:54 AM, jan1 said:

    With that said, there is something to the A/C mode (sort of storyboard), because it keeps me in the flow. Once I have some initial grading done, I like to just progress through the story board and copy grade to other clips and make adjustments. Having to duplicate and run macros forces to switch back and forth between what's going on in the timeline and what I'm doing in the visual editor. Once I'm grading it's very nice to just stay in the visual editor as context and go back and forth.

    Keeping in mind that I keep my UI configured to a single monitor (I do have two but due to their arrangements I find it easier to use just one). So switching between the timeline and the visual editor is more of context switch for me. I think this is an area where Mistika will find as you go more to Boutique and a more diverse hardware setup, that you cannot make assumptions on how people work, and you see them preferring different ways than would be natural in the traditional setup.

    I'm in sort of the same situation with the setup I'm using now. I have an internal 4K monitor and an external 4K monitor... but the external monitor is also my (interim) reference monitor (it's a Sony AF9 OLED tv). Since that's my ref it's also the monitor my AJA I/O 4K+ is hooked up to. So I have one output on my computer connected directly for Resolve since my current Decklink device can't do 4K (or HDR), and I use the AJA box for Scratch and Mistika. 

    But that means that in Mistika I'm working on a single screen also. For compositing I greatly prefer working with nodes, so I also find myself bouncing back and forth between the visual editor and the timeline quite a bit. 


    • Like 1
  13. Agreed -- they're very fast, on top of being very good. They were very nicely in Scratch, but there are several rather nice ones that are mostly unusable there because Scratch doesn't have a proper node interface, obviously not a limitation in Mistika... ?


    • Like 1
  14. Christobal, thanks for referring me to that tutorial. I'll peruse it shortly.

    What I found unintuitive is that when I set the mode for the shape before drawing the shape, it got reset. Once I realized that I had to reset it, it made sense.

    The eval stack takes some getting used to, but I agree that it's very powerful, but it's the transparent way that you can go back and forth between the eval stack and the node tree that appeals to me when it comes to compositing. 

    I'm still getting used to how to manipulate and export (maybe not the right word) alpha channels from the color node. I used the green screen effect because it worked so well though... Mistika's keyers are very nice to work with.


    • Like 2
  15. Thanks! That had what I was looking for, but I was searching the wrong playlist.

    The shape behavior is also very unintuitive. Set the shape's mode to "intersect" and create a shape, it pops back to add, which isn't correct. It makes you think it's broken, when in reality it's just being obnoxious.

    And if you have, say, the Comp3D node active, select the green screen and add a shape, the shape ends up making no sense whatsoever. You have to make sure that you have the green screen (in this case) node active when you add the shape, then transforming that clip with the transform widget on the Comp3D node works as expected. That part makes perfect sense once you get used to the active vs selected node thing in the eval tree.

    Now to figure out how to use the edge build node to add a little bit of light wrapping, then figure out how to clean up the dark line around the foreground element... ?

    Making progress!


    • Like 2
  • 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.