Javier Moreno

Sorry I think I was missing a key point of your previous message: >> Is there an apply button at the bottom that I can not see ? Yes, there is an "Apply" button at the bottom of the File->Options panel. If you can not even access that area, you can edit this configuration file manually: C:\Users\Your_user_name\SGO AppData\VR\localPReferences.xml Edit that file (for example with the Notepad) and change the scaleForScreens setting to 1.10: <scaleForScreens>1.10</scaleForScreens> Then save it and open Mistika VR Hope it helps Javier

That setting requires to restart the application. When you reopen Mistika, are those settings showing your last custom values or are they reset to the original values ?

Sounds like it didn't autoconfigure correctly. Go to File-Preferences and just switch off the GUI rescaling option (or set an specific value different than 1 to avoid autoconfigurationi, for example set 1.1)

Hola, De momento no es posible insertar metadata externa en los códecs. Solo se propaga la metadata standard de edición (timecodes, frame rate, etc). En el futuro si que está previsto incluir capacidades de manipulación de metadata. Saludos Javier

Hi David! Thanks for the feedback, it was very useful and we have found what it is. We expect to solve it in the next maintence release Cheers, Javier

Hi David, We are trying to reproduce the problem, but unfortunately it is not happening in our systems. We just fixed a bug with the Move node than confused us a bit, but it is not in the Copy node and we can't reproduce it. If not yet, please could you try the same Workflow having both folders in the system disk? (just to discard that it is not related with potential filesystem or network refresh latencies ) Any other detail you could think to reproduce the problem? Cheers, Javier

Well this particular case clearly involves a creative process, and to be honest I'm an engineer and not an artist. So I can't anticipate how many iterations will be needed. I guess it will take "until the client likes it".

Do you mean the render speed? If it is HD it should render in a few seconds, or at 4k less than one minute. But I suppose you may want to do some intermediate renders and adjustment iterations , as judging the optimal speed for something like "sparkles" appearing and disappearing sounds to require realtime playbacks to evaluate it properly. It is not a case of applyng the effects and forget . Basically you will need to go trough several "try and refine " iterations, rendering a realtime preview each time.

I would recommend to experiment with a Noise and Glint effects. Animate the noise parameters, use a color grade to adjust contrast and pass the result to the Glint effect. Also compose with the original image. But each software is going to produce a different result, if you like kiraKira I would recommend to use it and then compose the results in Mistika.

Hi Rakesh. Thanks for oyur honest review, it is very valuable feedback for us. About the clip replacement in Mistika, I am wondering if you could use this technique: 1 - Hunt the replacement clip wherever it is. If you select it in the media browser it will appear in the Source Monitor, or if you prefer to select it in the Tiemeline then press Ctrl+C (Copy) to send it to the clipboard, which in Mistika just is the Source Monitor) 2 - Put the Record Monitor (red bar) in the head of the clip to be replaced (or in any other in point you want it). Alternatively type the timecode for it directly. 3 - Press SourceMonitor->Overwrite (the icon with a red clip going down into a green clip). Or directly use its hotkey (B) while having the pointer in the Source Monitor (hotkeys like this affect the marks of the panel where you have the pointer at that moment). Whe you do that, the new clip will we placed at the record monitor position while also overwriting whatever was in there. The other icons near Overwrite are to insert (making space) or paste on top (similar result to a replace but you don't lose the original clip). In all cases you can also use the yellow marks in the source monitor ( "i" and "o" hotkeys ) to define which part of the incoming clip you want to insert. Or just type its In / Out timecodes in there as you seem to prefer. Regarding the interface, we are working in new capabilities to make it more scalable (for example to better support 4K GUI monitors). For example I think you could use a new scaling feature to mach the bottom screen of your laptop to the bottom part of the Mistika interface (menu panels in general), an let the upper screen for a clean view of the Timeline and Visual editor images. This scaling feature is still in development, but I belive a raugh version is already operative in your Mistika version (i suppose you have 8.10, the one in our website ). It would work as follows: 1 - In Windows, define a single continuous desktop with one screen on top of the other 2 - While in MistikaConfig-> General->AdvancedOptions, select the Interface->Use Scaling button, and for Mon-1 select the scaling factor as neccesary to fit the Mistika botton panel in the bottom display of the laptop (But do not activate "Two Monitors", as this proposal is a for a single (but elongated) monitor. This scaling feature is in development, in your version it can still have some refresh issues and some low res and aliasing at non integer scale factors in some widgets, but we hope to solve all this for next version 8.11. Please let me know if it works, I am curious. Sadly I do not have such wonderful laptop to try by myself. That dual screen laptop seems to be a nice one! Javier

For performance reasons some information like VectorPaint strokes, titles, morph, and data from 3rd party plugins are not saved in the .env file (which is a text file) but in the PRIVATE folder of the project as binary data (which is faster). If you copy a project to other system you need to copy the whole project folder, not just the .env file.

That's an interesting test, thanks for the feedback. BTW for that particular format, a key parameter is the Codecs-GPU frames. In general it should be 1 for GeForce and 2 for the Quadro. (you could also try with 3, but I am afraid it could be a waste of memory)

Well, it also depends on each client. The one case where Quadro is mostly preferred is for client attended sessions, as in those cases it is very desirable to have as much realtime playback performance and stability as possible.

In a case like this you should reduce the memory related parameters ( Max cache memory, ring buffer, pipe units, render units, encode threads ). That will free a lot of memory for other applications. I totally agree, that memory curve is typical of memory leaks. Otherwise it should look like a staircae . What is the exact date of your Boutique version? First thing I would recommend to render the source images to other format and test , as this test will show if the memory leak comes from the decoder or from one of the effects (in that case you would need to remove effects one by one to see which one is causing it) Please if you don't mind open a support case about the memory leak so developers can investigate it, in that way it is much more efficient for them

In all those examples the bottleneck is the effect processing, not the upload and download of images to/from GPU. So the full duplex can not help on them because at such low FPS speeds the PCie bus is infrautilized anyway. To take advantage of it you would need to build an example that is close to realtime, for example a more simpler stack that can deliver speeds close to UHD 60p. In that scenery is where having the Quadro can make the difference between realtime and non realtime. Also, if your storage is fast enough I would recommend to use uncompressed images like Mistika js format , exr raw or dpx. This is to avoid dependence on 3rd party codecs like Arri in a benchmark that is supposed to be about GPUs. Apart from this, one difference that should already be noticeable in your exanple is the advantage of the double amount of GPU memory in the Quadro, as you said that using all of it. Even with that the GeForce has a much better performance / price ratio and it is more than enough in may cases, there is no doubt about it.