Forum Replies Created

Page 8 of 29
  • Petros Kolyvas

    March 18, 2013 at 4:04 pm in reply to: 4bay FW800 Raid5 system

    I’m guessing that you need it for archival storage and not for speed as FW800 will top out at a theoretical max of around 92MB/s and then in-practice somewhat less.

    We have a SAS version of this: https://www.newegg.ca/Product/Product.aspx?Item=N82E16816215292&Tpk=GAGE104U40SL&IsVirtualParent=1

    Made by these guys: https://www.istarusa.com/raidage/products.php?model=GAGE104U40SL-SAUF#.UUc0CqV30to

    It’s sold by other brands under different product names: https://eshop.macsales.com/shop/hard-drives/RAID/Rack_Mount/

    I dug around OEM sites to find it becuase I was sure OWC wasn’t actually manufacturing the thing and they wouldn’t sell me one without disks. However, like all solutions in this price-range you get what you pay for. There will be no customer service to turn to.

    Also, the SAS version I have doesn’t have an on-board RAID controller, instead using my R680 which I trust and, I would suggest if you’re upgrading that you look around and see what kind of alternative, reliable RAID-5 solutions you need. Sonnet has proven to be one of the better companies (even though my experience hasn’t been fantastic) and if you’re not pleased with them it’s going to take a significant step up in cost to find a company providing better service and products.

    This is all, just, my opinion of course!


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    February 20, 2013 at 3:28 pm in reply to: PP CS6 on a MAC with Matrox MXO2LE loves to crash

    I have found Premiere to still be a little more crash happy than FCP. However in almost every case it’s due to third-party plugins and connections.

    In fact the worst was the Matrox MXO2. I had one in an edit suite and it was so crash happy I sold it for an AJA card and since then, the crashes dropped dramatically (more or less back into the realm of FCP) and seem to be unrelated to the AJA card.

    I’ve found the general speed of the system to make up for some of these shortcomings. That said, I think it needs some more “bolstering” in the stability department (not to mention media management – which remains terribly poor) as well, but I’m still quite happy with it now that my MXO2 is out of the picture.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • So here’s what happened.

    In the case of all the “Projects that won’t open on the Mac Pro” – they all used a 64-bit VST effect on the output buss of the Audio Mixer. The plugin has since seen a minor x.01 point update from the manufacturer since the project was last known-good.

    Opening the project on a machine that does not have the plugin installed/available marks the single plugin on the master buss “offline.”

    Here’s the buggy/catchy bit.

    If I select “none” from the plugin drop down. It does not hold. Even though the plugin appears to be removed, it is, in fact, not. If I open another timeline/sequence in the same project and then return to the one in question, “Offline” appears again on the master buss.

    You/I/One must actually select another plugin (preferably one of the ones that ships with Premiere) and then select “none” to ensure the removal.

    If the plugin is removed in this way (again highlighting a bug somewhere in there), then the project will open on the original machine (the one WITH the plugin in question to begin with.)

    This is the first time I’ve been truly, deeply, disappointed with Premiere Pro CS6. I’ve had in-use crashes with iLok authenticated plugins before, but never a project that wouldn’t open on a source machine with the very plugin (authorized and all) that was causing the crash.

    I’m going to suggest Digital Rebellion add “remove audio plugins” from their Project File Repair utility as a result of this discovery.

    Good luck editors!

    PK


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • If you can find out what kind of interface your array uses, it’s entirely possible you could use a non-Dulce solution.

    However, (and this is just an example), many quality SAS RAID cards (even older 3Gb ones) are still selling from reliable parties at around $1000/pop – at the prices you’re being quoted, I’d have a hard time believing it’s anything but.

    Having said that it might be time to look at the longer-term picture and pickup a new card for future higher-speed expansion requirements – but wait and see what you need first.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    January 25, 2013 at 3:29 pm in reply to: Wacom tablets and Premiere don’t mix???

    We have one at two out of three stations – and even contract editors who balk at first, quickly turn around.

    Having a discreetly mapped interface makes using muscle memory for certain interface elements speed up workflow dramatically!


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    January 21, 2013 at 8:01 pm in reply to: Wacom tablets and Premiere don’t mix???

    In fact, with all the evidence indicating a serious bug, why not just take the time to contact Wacom on behalf of your users? I can provide you with a direct Wacom support contact if you need. I can even provide a case number.

    I know Adobe has watched my video (almost a year ago) on Vimeo and Wacom is sure it was Premiere Pro change since the tablets work fine on CS5 and earlier.

    Even Walter Biscardi blogged about the issue: https://www.biscardicreative.com/blog/2012/12/workflow-update-imac-adobe-and-the-x-factor/

    “Hey Adobe there’s a bug!”
    “File a bug report”
    “We did”
    “File more bug reports”
    “We did”
    “File more bug reports”
    ….. error – feedback loop. 😉


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    January 21, 2013 at 7:52 pm in reply to: Wacom tablets and Premiere don’t mix???

    Done it for this issue so many times I’m giving up (fed up). Wacom claimed to have contacted the Adobe team directly and got no resolution either so I would tell people to save their time since it doesn’t seem like a priority.

    *can you tell I’m annoyed by it?!* 😉


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    January 20, 2013 at 5:53 pm in reply to: Wacom tablets and Premiere don’t mix???

    No, it’s a known issue that Adobe seems to be mum on fixing. The Wacom support team noted there was an in-Premiere behaviour change at some point causing keyframe and general jumping.

    I made a video about it: https://vimeo.com/46319803

    And there’s a big thread (and other little threads) about it: https://forums.creativecow.net/readpost/3/925015

    I submitted feedback to Adobe and Wacom many months ago. It’s a shame really; the pen (and keyboard) is mightier than the mouse (and keyboard).


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

    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.

  • Perhaps I was a little misleading (not intentionally sorry!) in my aggregation howto/info.

    Aggregation will not double your point to point bandwidth. IE you wont be able to start receiving data at 2Gbps. It should increase your point to multi-point bandwidth. Think of it a bit like train tracks with each connected station being a train. You can’t have one train occupy both tracks at once, but you can send two trains at the same time.

    That is to say that you can send more data out to two stations at once, not 2Gbps to a single station. Activity monitor will report twice the data going out on an aggregate link in a station-to-station test but that’s just because it’s sending copies of the data over both ports.

    There’s also the control protocol overhead and other bottlenecks to think of, but you’re right in wondering what you’re seeing, the tools can provide what are seemingly impossible results at a glance and performance is never really doubled in practice – just increased over the single-port option.

    And in our case, all of the hardware was already in place (Mac Pros with their two ports, and a 3com switch with LACP support).

    Our setup here has one primary station sending out to three other edit stations, all on GbE. It’s certainly still a low-cost solution to a performance problem better solved by having the primary station on a 10GbE uplink, but, like others we can’t afford that yet. At the same time I don’t think investing in new GbE tech is wise unless it’s absolutely mandatory as 10GbE will and is, becoming more affordable all the time.

    You might find some increase in performance by making sure you’re using Jumbo frames but it will be modest (even minor) at best. I don’t think a newer switch will make a difference though I could be wrong – switches have internal throughput limits based on their own processor and design and it would depend how good (or bad) your current switch is, but one or two connections shouldn’t push the limits of even the lowliest switch.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Petros Kolyvas

    November 30, 2012 at 6:37 pm in reply to: Premiere sound when finish render

    If you queue the export in Media Encoder (instead of using Premiere directly) it will provide audio feedback on success/fail of exports or the export queue if you’ve queued up multiple sequences.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

Page 8 of 29

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