Forum Replies Created

Page 94 of 449
  • Graham Bernard

    January 13, 2018 at 9:11 am in reply to: V13 can’t get “arm for record” to light

    Well? Silence? I can’t hear you . . . ?

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 7:18 am in reply to: V13 can’t get “arm for record” to light

    Erm? Where is your Mic plugged in? Is your Mic on front or rear port?

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 7:09 am in reply to: V13 can’t get “arm for record” to light

    [Rob Lindsay] “Getting closer tho!”Yeah . . . . How did you activate that Driver?

    OK, let me see your Track Header. Expand its width.

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 6:59 am in reply to: V13 can’t get “arm for record” to light

    Here’s mine showing that the INPUT is Live for DSSM:

    I believe, I can’t see all your Track Header, but here’s yours greyed-out, I think (?):

    Bottom line here, that Primary Driver option needs to be activated – yeah?

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 6:44 am in reply to: V13 can’t get “arm for record” to light

    Lol, and yes it had been lit, but in making the screen grab and stopping recording it had switched off! – Don’t be confused.

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 6:42 am in reply to: V13 can’t get “arm for record” to light

    Ah-hah!

    I went back and compared both of our Direct Sound Surround Mapper. Do you spot the difference?:

    Yours:

    And now mine:

    You’re missing that “Primary Sound Capture Drive” option, which I believe has to be part of the selection you can make from my previous thread.

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 13, 2018 at 6:19 am in reply to: V13 can’t get “arm for record” to light

    [Rob Lindsay] “All help is appreciated!”

    I’ll try.

    Although I’m running W7 not W10 it’s has to be similar, here’s my VP13 and VP15 recording onto Timeline. Make sure you have the Mic Icons lit on the Track Header!:

    VP13

    VP15

    Two questions:

    1] What is that ASIO Realtek Device for and I’m asking ‘cos VP and ASIO don’t play nicely, but as it is there why wouldn’t you use it? My external Presonus AudioBox uses ASIO and it works:

    2] What are the selections you’ve made in Audio Devices? Here’s mine for recording:

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 11, 2018 at 5:33 am in reply to: Wedding DVD burning file size Vegas Render

    [John Rofrano] “It all depends on the source video.”

    Agreed John. I posted this “hours” earlier And eventually all the FXing produces some major heavy-lifting for the encode and a requirement for greater BitRates and consequently larger files.

    Rule One: Capture with the best lighting you can. I have several kit bags of lighting. A set of LED Panels; top lights; fill and LED spots. I’ve also rigged an anonymous floor standing standard lamp I rigged with a controllable incandescent. I like that one!

    Rule Two: Use a heavy or at least a “stiff” Tripod. I have a 10 year old MILLER with carbon fibre legs which I use rigged to a Dolly.

    .
    .
    .
    .

    Rule 1000: Optimise Encode appropriate/suitable for platform.

    But hey, these rules are only guidelines. Personally I’d swap R1 for R2 ????

    And again Derek, do take up John’s suggestion of a DI. This DI then becomes THE file to encode from. For me this gives me a cleanly QA media created the best way I can output. And then I can encode knowing what I’m dealing with. Also the encode times are massively reduced.

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 9, 2018 at 8:46 am in reply to: Wedding DVD burning file size Vegas Render

    Don’t know what happened to my reply…. I’ll try it again:

    [Derek Charles] “I’m starting to understand”

    Good. Derek, you need to be more consistent and forensic with your analysis. I write this stuff down. Leaping all over the place will get all of us disconfabulated! Well, me at least. And, yes I did

    [Derek Charles] “perhaps you can chime in on my issue with Neat Video in this thread”

    where I read a bit more of your wrangling with Mercalli and NeatVideo. I can only garner that your original footage is both wobbly and noisy/grainy? Yes? In which case you’re starting off with a bit more of a problem than just BitRates and streaming – comparing others quality output. I also read there you’re using both Merc and NV chained together. This implies you’re giving the renderer/encoder the maths task of doing both sets of wrangling at the same time? Yes? Well, and in which case, don’t! Do one and then do the other. My preference would be for firstly NV, this’ll get you nicely FLAT images and THEN Mercalli. But, try reversing the order. You’ll soon enough find out.

    Derek, we’re starting to understand the pickle you’ve got yourself into. Hopefully you can see it through and be happy with the outcomes. Oh yeah, any chance you can upload a small sample so I can view the issues? At the moment I’m thinking I’m second guessing just what it is we’re up against – yes?

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

  • Graham Bernard

    January 9, 2018 at 8:35 am in reply to: Wedding DVD burning file size Vegas Render

    [Derek Charles] “I’m starting to understand”

    Good. Derek, you need to be more consistent and forensic with your analysis. I write this stuff down. Leaping all over place will get all of us disconfabulated! Well, me at least. And, yes I did

    [Derek Charles] “perhaps you can chime in on my issue with Neat Video in this thread”

    where I read a bit more of your wrangling with Mercalli and NeatVideo. I can only garner that your original footage is both wobbly and noisy/grainy? Yes? In which case you’re starting off with a bit more of a problem than just BitRates and streaming – comparing others quality output. I also read there you’re using both Merc and NV chained together. This implies you’re giving the renderer/encoder the maths task of doing both sets of wrangling at the same time? Yes? Well, and in which case, don’t! Do one and then do the other. My preference would be for firstly NV, this’ll get you nicely FLAT images and THEN Mercalli. But, try reversing the order. You’ll soon enough find out.

    Derek, we’re starting to understand the pickle you’ve got yourself into. Hopefully you can see it through and be happy with the outcomes. Oh yeah, any chance you can upload a small sample so I can view the issues? At the moment I’m thinking I’m second guessing just what it is we’re up against – yes?

    * Grazie

    Video Content Creator and Potter
    PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
    Cameras: Canon XF300 + PowerShot SX50HS Bridge

Page 94 of 449

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