Latest post Tue, Feb 19 2013 6:30 PM by Mike Shaw. 224 replies.
Page 13 of 15 (225 items) « First ... < Previous 11 12 13 14 15 Next >
Sort Posts: Previous Next
  • Wed, Oct 3 2012 3:34 PM In reply to

    • Mike Shaw
    • Top 75 Contributor
    • Joined on Fri, Nov 4 2005
    • Kent, United Kingdom
    • Posts 1,424
    • Points 19,730

    Re: MC 6.0.3/SN 6.0.3 bugs.

    I may be wrong, but I think when I did things that way (using CTRL-Z or CTRL-X to delete a clip), what happened was after deleting the clip filler with cuts were often created all over the place (on other tracks), with the result that after a while, my timelines looked like a brick wall in the filler areas.  I was fortunate to have a BBC editor sit with me (they use AVID MC) for a while on one movie I was doing for him - and he used the 'TXG/TZG ' methods to remove them - the method I now use to remove clips - which doesn't leave cut filler all over the place. 

    Interesting that you can CTRL-X again to rermove the filler/gap (I must try that) - I guess what is happening there is you're removing the filler 'clip' from the scenario - and with no filler, there'd be no gap.

    It sounds very much to me like intended behaviour I'm afraid. 

    Coming from lesser editors, the concept of filler was a bit strange to me.  It may be the way CTRL-X (now) works is something to do with the filler in MC.  If you think of film, then there has to be filler/blank film to act as spacers between seperated clips of course. Take away the filler, and the gap has closed up.

    Just surmising...

    MC6.0.3.2 Gigabyte GA-X58A-UD3R Rev2 MB, Intel i7-950 3.06Ghz, 12GB DDR3 1333Mhz RAM, 1x500GB, 3x1TB HDrives, 2+1TB Network drives, nVidia Quadro FX1800... [view my complete system specs]
  • Wed, Oct 3 2012 3:42 PM In reply to

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Mike Shaw:
    If you think of film, then there has to be filler/blank film to act as spacers between seperated clips of course. Take away the filler, and the gap has closed up.

    As a former classic film editor, I can tell you that is precisely right. And given that Media Composer was deliberately designed to mimic the classic film editing environment, so that feature film makers would be comfortable in the new NLE environment as they made the transition away from physically cutting film, it makes perfect sense. That is indeed the role and the reason for filler in Avid.

    Newscutter Nitris DX 9.5.3.5 * Media Composer 5.5.3.6 (At Home on PC running XP Pro) * Symphony 6.5.2.1 (At home on MacBook Pro3,1 running 10.7.2) * Interplay... [view my complete system specs]

    Larry Rubin

    Senior Editor

    The Pentagon Channel

    www.pentagonchannel.mil

  • Thu, Oct 4 2012 9:35 AM In reply to

    • Vilem
    • Top 75 Contributor
    • Joined on Sat, Apr 10 2010
    • Prague
    • Posts 1,427
    • Points 15,690

    Re: MC 6.0.3/SN 6.0.3 bugs.

    I know it's in the release notes has not been announced, but for info.

    The patch 6.0.3.1, Marque still produces illegal range of colors.


    V.

    AVID MC2020.10, HP Z620 - 2 x Intel Xeon E5-2620, Quadro P2000 - driver 442.50, RAM 48GB - DDR3, BM Intensity Pro 4k - 10.11, W10 - 64bit Professional... [view my complete system specs]
  • Fri, Oct 5 2012 11:04 PM In reply to

    • Sylvain P
    • Top 75 Contributor
    • Joined on Fri, Nov 4 2005
    • Montreal, Quebec, Canada
    • Posts 1,489
    • Points 17,600

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Alt + T (mark clip) doesn't work correctly.

     

    Media Composer 2018.12.2 (Symphony Option), ASUS P8P67 Deluxe, Intel i7 2600k, 16G DDR3-1600, PNY NVIDIA Quadro 2000 (353.82), Windows 10 Pro. Boris Red... [view my complete system specs]

    Sylvain Primeau

    Self-employed worker - Les productions Primeau Medias

    primeaumedias.com

     

    Radio-Canada/CBC news editor

    cbc.ca / ici.radio-canada.ca

  • Mon, Oct 8 2012 7:13 AM In reply to

    • mkj
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Sweden
    • Posts 458
    • Points 6,035

    Re: MC 6.0.3/SN 6.0.3 bugs.

    is anyonoe having problem with exporting a sequence to an XDCAM disc with "Export do device"?

    I get this error msg:

     

    (and this works with MC 5.5.3.4)

  • Tue, Oct 9 2012 4:12 AM In reply to

    • Sylvain P
    • Top 75 Contributor
    • Joined on Fri, Nov 4 2005
    • Montreal, Quebec, Canada
    • Posts 1,489
    • Points 17,600

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Step Forward One Field and Step Backwar One Field doesn't work at all.

     

    Media Composer 2018.12.2 (Symphony Option), ASUS P8P67 Deluxe, Intel i7 2600k, 16G DDR3-1600, PNY NVIDIA Quadro 2000 (353.82), Windows 10 Pro. Boris Red... [view my complete system specs]

    Sylvain Primeau

    Self-employed worker - Les productions Primeau Medias

    primeaumedias.com

     

    Radio-Canada/CBC news editor

    cbc.ca / ici.radio-canada.ca

  • Tue, Oct 9 2012 4:45 AM In reply to

    • mjolnarn
    • Top 10 Contributor
    • Joined on Wed, Feb 8 2006
    • Sweden
    • Posts 13,346
    • Points 159,365

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Sylvain P:

    Step Forward One Filed and Step Backwar One Field doesn't work at all.

    Works great here Sylvain with interlaced projects, are you sure you aren´t in a progressive project .

     

    Mac: 17" Macbook Pro i7 2,66 ghz with 8Gb Ram, 500gb 7200rpm drive___ PC_NEW Win10 Pro Mbo Asus Rampage IV Black CPU Ivy Bridge-E 4960X ( = 12 x 4... [view my complete system specs]

    Tomas 

     

  • Fri, Oct 12 2012 7:25 PM In reply to

    • Sylvain P
    • Top 75 Contributor
    • Joined on Fri, Nov 4 2005
    • Montreal, Quebec, Canada
    • Posts 1,489
    • Points 17,600

    Re: MC 6.0.3/SN 6.0.3 bugs.

    mjolnarn:

    Sylvain P:

    Step Forward One Field and Step Backwar One Field doesn't work at all.

    Works great here Sylvain with interlaced projects, are you sure you aren´t in a progressive project .

     

    Ah yeah, you are right. I'm used to work interlaced at my job and progressive at home.

    So now, in an interlaced project, the Step Forward On Field button works as expected... but Alt + right or left arrow now move 10 frames at a time.

    In MC5, Alt + left/right arrow moved on field.

    Media Composer 2018.12.2 (Symphony Option), ASUS P8P67 Deluxe, Intel i7 2600k, 16G DDR3-1600, PNY NVIDIA Quadro 2000 (353.82), Windows 10 Pro. Boris Red... [view my complete system specs]

    Sylvain Primeau

    Self-employed worker - Les productions Primeau Medias

    primeaumedias.com

     

    Radio-Canada/CBC news editor

    cbc.ca / ici.radio-canada.ca

  • Sat, Oct 13 2012 9:28 AM In reply to

    • DIESELE
    • Top 100 Contributor
    • Joined on Mon, Apr 28 2008
    • Posts 1,184
    • Points 14,655

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Yesterday it again refused to load sequences in the source monitor - could only do it by putting in record monitor and then CTRL+ALT+C.  Its happened 3 times now and a re-boot cures.

    Have there been any further (overdue) fixes for us non 6.5 purchasers yet?

    Symphony 2018.12.10, Blackmagic Intensity Pro 11.1 (unsatisfactory in full res UHD though for client monitor), WIN 10 on 2500Mbps M.2 SSD, Nvidia Quadro K4200, Asus X99-A Mobo, i7 5820K 4.0 GHz Hex core mildly overclocked CPU, 32Gb 2800 Mhz RAM, WD Black 8Tb RAID10 array @ 450Mbs

     

     

  • Sat, Oct 13 2012 9:45 AM In reply to

    Re: MC 6.0.3/SN 6.0.3 bugs.

    DIESELE:
    Have there been any further (overdue) fixes for us non 6.5 purchasers yet?

    Latest is 6.0.3.1 about 10 days ago:

    http://community.avid.com/forums/t/113305.aspx

    Media Composer 2020.10 w/Symphony/SS/PF options, HP Z-Book G6 17", i7-9850H 2.60GHz, 32gb RAM, NVIDIA Quadro RTX 3000, Windows 10 Pro [view my complete system specs]

    "There is hardly anything in the world that some man cannot make a little worse and sell a little cheaper, and the people who only consider the price are this man's lawful prey."  - John Ruskin (1819-1900)

     

    Carl Amoscato | Freelance Film & Video Editor | London, UK

  • Sat, Oct 13 2012 10:02 AM In reply to

    • DIESELE
    • Top 100 Contributor
    • Joined on Mon, Apr 28 2008
    • Posts 1,184
    • Points 14,655

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Thanks Carl. 3 fixes Huh?

     

     

    Symphony 2018.12.10, Blackmagic Intensity Pro 11.1 (unsatisfactory in full res UHD though for client monitor), WIN 10 on 2500Mbps M.2 SSD, Nvidia Quadro K4200, Asus X99-A Mobo, i7 5820K 4.0 GHz Hex core mildly overclocked CPU, 32Gb 2800 Mhz RAM, WD Black 8Tb RAID10 array @ 450Mbs

     

     

  • Thu, Oct 25 2012 8:27 AM In reply to

    • JonnyL
    • Not Ranked
    • Joined on Thu, Oct 13 2005
    • UK
    • Posts 182
    • Points 2,430

    Re: MC 6.0.3/SN 6.0.3 bugs.

    I have listed this bug before but I have a work around:

    Title tool, trying to use different font sizes in the same text block causes the whole block to the new size.  This only happens if you try to move the block immediately after applying the new size.  If you select another block first and then go back to moving the original block and the size change "sticks"

     

    Also: RTAS.  Using the rtas tool, if you minimise the application with the RTAS tool open, then maximise, the RTAS settings are reset to default.  I think this is related to the failure to export a quicktime / Wav with the RTAS audio processing.  Closing the RTAS window solves both problems.

    This was using the compressor / limiter

    Asus X299, i7 7820, Nvidia 2000M 32GB ram, NVME SSD 8.9.1 ( yes its very fast!) [view my complete system specs]
  • Thu, Oct 25 2012 9:07 AM In reply to

    • DIESELE
    • Top 100 Contributor
    • Joined on Mon, Apr 28 2008
    • Posts 1,184
    • Points 14,655

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Gretski:
     Using the rtas tool, if you minimise the application with the RTAS tool open, then maximise, the RTAS settings are reset to default.  

    I get this RTAS 'reset' issue too, but dont bother reporting bugs anymore - patience has worn thin after 12 months of what I hoped was being proactive. Repairing what they broke from V5 seems off the radar compared to headline stuff.

    Thanks for the RTAS tip as I can now workaround this frustrating issue now. Yes

     

    Symphony 2018.12.10, Blackmagic Intensity Pro 11.1 (unsatisfactory in full res UHD though for client monitor), WIN 10 on 2500Mbps M.2 SSD, Nvidia Quadro K4200, Asus X99-A Mobo, i7 5820K 4.0 GHz Hex core mildly overclocked CPU, 32Gb 2800 Mhz RAM, WD Black 8Tb RAID10 array @ 450Mbs

     

     

  • Fri, Nov 9 2012 2:18 AM In reply to

    • Ken Lent
    • Not Ranked
    • Joined on Tue, Dec 18 2007
    • California
    • Posts 129
    • Points 1,375

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Vilem:

    I know it's in the release notes has not been announced, but for info.

    The patch 6.0.3.1, Marque still produces illegal range of colors.


    V.

    Does anyone know whether Marquee still produces illegal colors in 6.0.3.2?  And if so, is there a workaround?

    Core i7 930 PC 2.8GHz / 18GB RAM / Win10 Pro 64bit / nVidia Quadro K2200 (driver 411.95) / MC 2018.12.9 (Symphony/PF/SS) / BCC AVX 10.0.2 / NewBlue Titler... [view my complete system specs]
  • Fri, Nov 9 2012 2:33 AM In reply to

    • Ken Lent
    • Not Ranked
    • Joined on Tue, Dec 18 2007
    • California
    • Posts 129
    • Points 1,375

    Re: MC 6.0.3/SN 6.0.3 bugs.

    Heff:

    I continue to suffer from a littany of bugs in 6.0.3 that were not there in any previous versions, and that are seriously slowing me down.

    1.Random failures to open bins created in 6.01 or 5.5.3 causing " Binary Code" error messages requiring a quit and re-launch,  This is not fixed either by trashing MC state and site settings, or opening the bin again, as previously posted here.

    Does anyone know whether this bug has been fixed in MC 6.0.3.2?

    Core i7 930 PC 2.8GHz / 18GB RAM / Win10 Pro 64bit / nVidia Quadro K2200 (driver 411.95) / MC 2018.12.9 (Symphony/PF/SS) / BCC AVX 10.0.2 / NewBlue Titler... [view my complete system specs]
Page 13 of 15 (225 items) « First ... < Previous 11 12 13 14 15 Next >

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller