C-King:

In my case, it's a G-Speed Studio XL 8-bay Thunderbolt RAID. Thunderbolt only!

 

Chyld

Directly to a thunderbolt port or via something like a Sonnet or similar?

Might pay to just fill in your system specs..

Mine is connected via a OWC hub without issues. It seems really odd that you can choose it as a transcoding destination but you can't import to it. That points to corrupt Avid settings somewhere.  I would do all the normal stuff - new user, new settings, new site settings etc. (probably done that already right?) 

What do your media creation settings say? Can you choose it as a destination there?

 

 

My G-Raid striped pair is connected directly via Thunderbolt to my MacBook Pro. No adapters. Last time I saw the problem, I could link to media on the drive but it did not show up as available in Media Creation and I could not render or transcode to it.

The G-SPEED Studio XL 48TB RAID (Level 6) is connected directly via Thunderbolt to the MacPro. As suggested by Avid Support, updated to MC 8.7.2 (also updated to MacOS 12.2 and the newest AMA plugins) without success…

 

I'd like to add that this problem occurs with our SNS EVO ethernet connected drives as well. We've been trying all of the solutions/options mentioned above, without any succes.

Any help, insights, solutions or ideas are greatly appreciated!

I had the same problem some time ago. After trying various things, I gave up and transcoded the media in davinci. I wrote about that case here: https://community.avid.com/forums/p/182138/851128.aspx#851128
(didn't find this tread back then)

Last week the same problem occurred to a student of mine. The issue was resolved in restarting Avid.

I've seen this issue with various kinds of hard disks. All of them connected with USB 3.0 though. Sometimes on laptops, sometimes on Mac Pros (trashcan). I feel like smaller 2.5" discs are more affected, however this is only a guess.

bas3000:

I'd like to add that this problem occurs with our SNS EVO ethernet connected drives as well. We've been trying all of the solutions/options mentioned above, without any succes.

Any help, insights, solutions or ideas are greatly appreciated!

Did you type "alldrives" in the Console to allow MC to use network drives?

I've tried "alldrives" several times with no results.

Lately it has been intermittent; sometimes it will see drives, let me import, change media creation settings, etc.

Most of the time, no luck and it won't see any attached drives as media drives, and the drive selection in media creation is blank under all tabs. It also defaults to DNxHD 115 when it loses track of my drives, though it continues to render, leaving me with a mixture of render resolutions. I have been unable to determine a pattern so far.

Has anyone had any luck with this? Trying 8.9.4...

 

C King

Avid have been trying to reproduce this in house for quite a while now, but so far we haven't had any luck. And without being able to reproduce it, makes it very hard to figure out why this is happening.

Moving out the content of AMA Managment seems to fix it temporarily.

But for some reason it can go back. Quesiton is if it's corrupt Project Settings, or User settings.

Could you check in the console if you have an old outdated AMA plugins?
You have the complete list of AMA plugins in the Info tab.

Hi Freddy-

I'm having the problem on a fresh install of 8.10. with only the included AMA plugins, on a new 12 TB G-RAID TB3 connected drive. Drive was reformatted before use, permissions set to all can edit.

With my current project-- all AMA media, brought over from another machine and reconnected on this one-- I cannot import, and it does not like even creating dissolves in the timeline-- telling me the media file source drive is unavailable--  or transcoding. .

All drive filtering is off.

The drive does show up and allow me to designate it in Media Creation settings-- all looks normal there.

With a new user and new project I am unable to import-- it tells me no media drives available, I can only import shot logs. 

Deleting media databases has no effect

alldrives 1 has no effect

unmounting/remounting the G-RAID has no effect

removing AMA Management *does* allow me to import in this test project, with a test user.

removing AMA Management *does* allow me to import media with my existing Avid User settings.

removing AMA Management *does not* allow me to import in my actual project with the test user.

removing AMA Management *does not* allow me to import in my actual project with my existing user settings.

Interestingly, I *can* import media from the source browser without difficulty, but from the flle menu or drag and drop to the bin. I didn't try this before deleting AMA management so I don't know whether it's a change.

 

So it does appear to be connected to the project. I have not yet tested bringing my bins into a new project. 

 

I'm now having this problem on two systems with different types of G-RAID media drives. If there is anything I can do to help you reproduce and solve this, please let me know! I would dearly love to stop having to work around this.

 

Thank you for your help!

 

Chyld King

These are the things I would try.

Let's start with the easy ones some of which you've already tried (try these step by step):

1. Create a brand new user profile on your Mac with Administrative privileges
2. check permissions - create specific read and write permissions on the target drive for your new user, not just everyone.
3. Uninstall Avid, delete all user and site settings and re-install
4. Replace thunderbolt cables (Thunderbolt is good but the cables are very easy to damage if hot plugged). In my experience though they either work or they don't so the cable seems unlikely but an easy one to test.

Now for the less palatable. 

1. Back up system, reformat the system drive and completely re-install MacOS and AMC (nothing else initially)
2. Make sure you install and run Avid under the Administrator profile.

Also of course the most obvious thing - ensure your G-RAID is formatted correctly with HFS+ and check that the OS version and AMC version are compatible.

Hi Mondo-

Thanks for the suggestions.

I'm curious whether you have had experience with this specific problem (drives, especially G-RAID drives, not being recognized as media drives), as these steps are a sort of compendium of general Media Composer troubleshooting going from the minor to the extreme.

Have you taken these steps and solved this particular problem? Since I see it on different systems with different projects, users, OS versions, and MC versions, I'm inclined to think it's a software bug, not a configuration or corruption problem.

If you have had, and solved, this specific problem through these steps, please let me know.

Thanks,

C-King

Again a stupid avid problem, never solved for such a long time.

Yesterdeay I was frustrated about PremierePro for beeing such a instable software,

But today suddenly my always so stable avid, does not let me import or render any files on a big documentary anymore !!

WAAAAAAAAA

Two days ago I could import and see my Thundebold 30TB Drive and suddenly - no rendering and no drives

only linking and transcoding .....

WTF

I am editing on avid for now 15 years and suddenly this ......

A fresh install on this machine is NO option... 8.9.3 here OSX 10.11.6

So I typed all drives...

and after a restart... it tells me that the MEDIA INDEXER is not healthy (???)

I continue and then it tells my that my Shared Medias will not be available and it has no connection to interplay (???)

I continue...

And suddenly my Mediadrives are available......What is happening here

 

Scary

Sly

I would onnect with support and get a case started so they can look at this for you...  drives and media are nothing to plsy with here.

marianna

Hi! 

 

I also have problems with Avid not recognizing my external harddrive, when wanting to transcode the AMA-linked material in my project. No target drive.

The harddrive has read and write access and is Mac OS extended (journal) formatted, the media creation settings has the harddrive. 

It`s just no hard drives exposed in the transcoding window!! 

What other tips do you guys have?