[Craig Ricker]

Hi Jeff,

I am most interested in hearing the details of how its been going. As this is our first step into the MAM space, I am very much in need of real peoples experiences with the software, and the limitations they have experienced, as well as the strengths they have found.

So how does it go with axle on that level? What have you found are its strengths and weaknesses, and what is the general workflow that you use it within?

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Bringing this thread back to life. Our company is just starting to look into MAM’s and I have been looking at Cantemo Portal, and stumbled onto this thread. We are based in Australia and UK but would only need 5 editors to have access to material at any 1 time. Scaling in the future is something we want to have in mind. Cantemo Portal 2.0 looks to have some excellent integration with Premiere.

How have you been finding axle. What has been its weaknesses and strengths across the period you’ve been using it? Has there been adequate development over the year to the software?

Any information will be most useful to myself and others i’m sure.

Regards
Craig

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Hey Michael,

Essentially you use the threshold to set the point at which compression will start occuring.

You then set the ratio, to determine how sharp the knee of the compression will occur. The higher the ratio, the sharper the knee (harsher) the lower the ratio the gentler the curve of the knee.

Say you noticed your audio was moving from a range of -20db to -3db on a VO (that’d be quite strange to start with as if you had your mic setup right, and the VO artist was giving a fairly consistent performance you wouldn’t really see this much change in volume)
But for examples sake, lets say thats how much you had.

One of the uses of compression is to reduce the range of the signal so that you can increase the overall loudness.

So for our example you would wish to say set your threshold at say -10db and have your ratio set to say 3:1. Then at worst when your audio’s original volume was at -3db, which is say 7db higher than the set threshold, it would compress it down by 3:1. So thats a 1/3rd of what it was orginally, so rather than 7db higher it would only be 2.3db higher, which would put it at -7.8db final output. SO its more of a ratio thingy rather than an absolute range. Absolute ranges can be achieved but you will get a much harsher knee, and basically you end up with a limiter, where if the signal goes to -10db, it aint going to go over, and the limiter harshly reduces the volume quickly.

Does that help?

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Hi Merlin,

Sorry to see that you received no response. I’m actually curious to hear what setup you went with in the end. Did you find that using a decklink card and seperate audio interface device such as the 2i2 created an out of sync audio and vision issue? Or are they nicely in time, i thought maybe the decklink would delay the vision a bit as its doing some of its work converting to the uncompressed signal.

Be great if you could let us know.

Regards
Craig

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Heck, that is perfect! How easy it is to get frustrated at the small things when they are just staring you in the face! Thankyou!

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Just make a text file that states, what you renamed from and too, and tell your secure storage facility to hang onto it. That way they can always rename their files if need be.

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Not sure about you guys. But the problem has now cleared, since Apple released 10.10.2 combined with the latest cuda driver 6.5.46

I no longer have any crashes or graphics glitching and its been this way now for over 2 weeks.

Hope the rest of you have as much luck

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Have 3 Mac Pro’s at work, upgraded them all to yosemite just before the Christmas break. Come back to work, and we are all experiencing constant freezing and crashing of our Mac Pro’s, which causes a complete freeze, followed by a restart, and a pop up saying ‘Graphics problem detected’.

Most often happens when were using the GPU in premiere pro, or during a render/export from either after effects or premiere.

I have glitches on my screen all the time as well, especially when using hot spaces.

There is clearly some serious bug in yosemite in regards to GPU.

Very painful, and seriously considering now restoring the Mac’s back to snow leopard, where we were completely glitch free, and I could boast the reliability of our Mac’s….

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Appears the latest firmware has not changed anything in this regard. Seeing on the atomos forums again, people mentioning they believe Panasonic will release a firmware fix for this in mid november.

But its such a risk for me, to invest in 4 of these cameras hoping a firmware’s gonna come out…..

I’m gonna have to go and hire one, to see what its doing plugged into a BMD 4K switcher. Maybe its just the external recorders that are picking up a interlaced signal in 25p, but to me that means its putting one out.

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670

[Craig Ricker]

Any chance you can confirm what Atomos is saying, that the GH4 is only outputting the 1080p25 10bit signal at 50i? I really need to do green screen work on a live broadcast (virtual set) and require 1080p25 or at even 1080p50 at 10bit.

There isnt any one commenting on this besides atomos as saying its only capable of 10bit 1080i50.

Can you check with your own recorder?

Be so helpful!

Mac Pro 2.4Ghz 8 core, 24GB RAM, GTX 670