Forum Replies Created

Page 1 of 2
  • Michael j Toffan

    November 26, 2014 at 10:59 am in reply to: Working with MXF Files in Vegas

    Good point Graham, I have not solved that one either.

  • Michael j Toffan

    November 25, 2014 at 11:48 pm in reply to: Working with MXF Files in Vegas

    Graham

    I use VLC media player and SCRATCH to play my MXF files when I am not in Sony Vegas Pro. I hope that helps.

  • Michael j Toffan

    August 22, 2013 at 12:13 am in reply to: JVC White Waterdhield BD-Rs LTH–a bit OT

    Rich, of the two (Ridata and TDK), I certainly have more experience with the Ridata and could at least recommend the Ridata on that basis. So far, the TDK disks also seem to be doing fine, I just need more time with them before I could give them an honest rating.

    So far, no complaints of smearing or water damage from clients.

    I handle the disks carefully right after printing so the ink has a chance to fully dry. I also provide a good snap-in case with the disk (versus a slide in) so that may help as well.

    Like you, I am taking note of other folks positive experiences and may leverage their recommendations as well.

  • Michael j Toffan

    August 20, 2013 at 11:05 pm in reply to: JVC White Waterdhield BD-Rs LTH–a bit OT

    I have not tried the JVC BD-R White Watershed disks you mention. I have used white Inkjet printable BD-R disks from Phillips, RiData and some 50 GB TDK BD-R that I use for backup. All work well for printing; however, I had a lot trouble writing to the Phillips with both an LG BD-R writer and a Pioneer BD-R writer, (most of the Phillips disks were unusable) so I will not be using Phillips disks in the future. I use an Epson Artisan 50 to print graphics and titles on the disks.

    I look forward to hearing what others have used with success.

    I have not tried coating with clear acrylic lacquer.

  • Michael j Toffan

    August 20, 2013 at 10:42 pm in reply to: View Transform ACES RRT (sRGB)

    I put a ticket in on this to Sony a couple of days ago and they indicated it was a know issue that will be addressed in a future update. The work around I found is as exactly as you mentioned to use the video gamma setting versus the linear gamma.

  • Michael j Toffan

    August 7, 2013 at 11:11 pm in reply to: Davinci Resolve Workflow with Sony Vegas Pro

    You’re welcome!

    Unless you are doing Raw or 4K, the lite version should provide most of what you need.

  • Michael j Toffan

    August 7, 2013 at 10:38 pm in reply to: Davinci Resolve Workflow with Sony Vegas Pro

    Hi Thomas

    I have been using Davinci Resolve Lite side by side with Vegas Pro 12 for about 4 or 5 months. I recently did an example where I recolored one of my existing projects using Davinci Resolve. The Vimeo link below provides this example (original and recolored) along with comments on what I did.

    JUN22013 DevouPark RESOLVE GRDG STDY FINAL
    https://vimeo.com/70247970

    What seems to work will for me is to bring my clips into Vegas, do a rough edit (no cross fades or other FX) and render out to Sony MXF file using a “HD422 1080-30p 50mps” custom template I modified to keep it progressive. (note you can use the 24p, 50i or 60i templates as well). The Sony MXF loads right in as a single file and Resolve has a scene detection capability that works very well to split it into the individual clips. On return, after color grading, render back out to one of the three Sony MXF file choices as individual or one clip depending on your desire. The MXF file works very well without loss of fidelity (you can find numerous references to that from John Rofano on this site).

    Once back into Vegas Pro, you can do additional work on it and/or render out to any desired format you wish. I usually render out in 1080-30p mp4.

    Davinci Resolve is very powerful tool, I can certainly say for me, it was well worth the learning curve. I can recommend a couple books and a workshop to come up to speed. The 600+ page manual has all the details; but, for many it can be a difficult read and it is always nice to see a demo.

    Michael T

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Mark, very interesting observations, thanks for sharing.

    Fortunately it has been awhile since I have run into a hang during rendering (knock on wood). When it does happen, I end up bailing out and re-doing the render. I am going to bookmark your comments and try your work around next time I run into that issue.

    Hopefully your observations are also insightful for the Sony Software team.

  • Hi Pedro

    Looking at your system specs, you have a very high end PC, which though slightly different, should have similar performance to mine. I have used your format to describe my system below:

    Vegas Pro 12
    Windows 7, 64bit ultimate
    Intel i7-3930x 3.2Ghz (2011 hex core cpu)
    ASUS P9x79 Premium MB
    64 Gigs of 1600 mhz GSkill RAM
    ASUS nVidia 680 video card (1500 Cuda cores, 2048 MB GDDR5)
    OCZ Vertex 4 SSD HD (for O/S)
    2 – 2TB HD in RAID 0 configuration
    Pioneer Blu-Ray Writer
    Corsair AX1200 Pro Powersupply
    prolimatech megahalems cpu cooler

    My single biggest problem rendering with the GPU enabled was the dynamic RAM preview setting. Once I started setting dynamic RAM preview to zero in the Preferences under Video tab, I have had good success rendering AVCHD to MP4 with GPU rendering set to either OPEN CL or CUDA. I typical use the Internet HD 1080 template under Main Concept AVC/AAC with a customized template set to progressive only and best quality.

    To see if I was having your issue, I took a 15 second slider clip with a nearly blown out window at mid clip that really brought out the glint and added “Sony Glint” plugin set to Sparkle and “Border” plugin set to a .0951 white border. I rendered three cases, one with GPU set to OPEN CL, one set to CUDA and then I deleted the plug-ins and rendered with CUDA.

    I was able to render all three cases without crashing; however, it was very clear from the render time that the Glint and Border plugins are taxing the system. The results:

    Sony Glint and Border GPU set to:OPEN CL Render Time: 3m 48s

    Sony Glint and Border GPU set to:CUDA Render Time: 3m 36s

    Delete Glint and Border GPU set to:CUDA Render Time: 0m 32s

    The glint and border cases clearly are challenging cases and will certainly stress the system. If you have not yet tried setting your Dynamic RAM preview to zero…doing so may help.

    Your system specs are so similar to mine, it seems you should be able to have similar results. My clip is certainly different than yours; so take my results with a grain of salt, hopefully this quick study gives you a reference and maybe some ideas to check.

    Mike

  • Michael j Toffan

    March 28, 2013 at 11:23 pm in reply to: Batch Convert AVCHD to MXF

    Hi Jim, if you place a region over each event in the timeline, then select batch render, your desired codec and the render regions button at the bottom of the batch render template; the batch render will render out separate files for each of the events with a region overlay.

    If you have edited your video in AVCHD, and you have a lot events to put regions on by hand, you can use a plugin like the “VASST MarkerMaker” (about $10) to quickly apply regions to all clips and subclips simultaneously is a real time safer.

    Mike

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy