Ok, I power cycled everything this morning. Workstations and Unity. Where the workstations are finding the media has gone back to the way I am use to it working. Very strange. But it still won't scan the folders with names that extend past the SysName.# pattern. Having that missing is going to be a real drag. I wonder it that's a function of the new client version of Unity or if it's something in MC6 that may get fixed. Well, I guess I'll have to start using some sort of table to keep track of which directory has what data in it.
Jay
On Feb 3, 2012, at 11:58 PM, Jay Mahavier wrote:
> The local drive is fine. It's not the system drive. It's an extra internal. I can import QTs and create media to it. I have tried new project. I've tried new user. I've tried it on a second system. The only thing I have not been able to try is rebooting the Unity system. Time to give up and move on. I'll deal with it more on Monday.
>
> Jay
>
> On Feb 3, 2012, at 11:02 PM, johnrobmoore wrote:
>
>> Maybe take the existing AvidMediaFiles folder and put into another folder like "stuffed media" Then let Avid create the whole folder again at the root level and then move your .mxf file into that folder. Everything you've said makes sense and should work from my experience but if it rebuilds and you can't access the media something is funky which is why I think creating an entire new folder wouldn't hurt. Oh I just had a thought, is there any way the Avid is set up in media creations to not access media on the boot drives or system drives in media creations? If it's rebuilding the database I don't think that's the issue but worth a peek. Also is the Avid looking at the local drive set to "Alldrives" in the console so it treats all drives as potential media drives? Just guessing while I'm rotoing my little heart out.
>>
>> --- In Avid-L2@yahoogroups.com, Jay Mahavier <jay_mahavier@...> wrote:
>>>
>>> The folder structure pre-existed on the local drive. I just put the media into the 1 folder. It did build the databases. I can tell, because I deleted the ones there and the timestamp on the ones it built is correct.
>>>
>>> Jay
>>>
>>> On Feb 3, 2012, at 10:24 PM, johnrobmoore wrote:
>>>
>>>> Or the old standard, create a title or something to the local drive and let Avid create an new AvidMediaFiles folder. Drag you copied media in the "1" folder inside the mxf folder etc.... I'd be surprised if it didn't rebuild the database. I work with a hybrid unity and SanMP and we have to manually rename the "1" folder to Edit.07.01, .02 etc... so other bays don't try to rebuild the databases on the SanMP volumes. I never added a discriptor after the last digit with . in front of it. I'm surprise that worked but then I'm surprised I remembered to tie my shoes this morning. Learn new tricks every day. I've never worked in a Lion environment but have been playing with V6 on OS 10.6.8 for now and it seems to work for my basic tests with the Artist Color Panel and Resolve roundtripping.
>>>>
>>>> --- In Avid-L2@yahoogroups.com, "Dom Q. Silverio" <domqsilverio@> wrote:
>>>>>
>>>>> The Avid bin will always reflect the last known location of the media.
>>>>>
>>>>> We never tried modifying the media folder name by adding anything after .#
>>>>>
>>>>> Did you try it with a Snow Leopard system?
>>>>> When you moved it to the local drive did you reconfigure the folder
>>>>> structure to reflect a local drive structure (aka move the media out of
>>>>> "computer name.1" folder)?
>>>>>
>>>>>
>>>>>
>>>>> On 2/3/2012 10:56 PM, Jay Mahavier wrote:
>>>>>> And even more messed up. I can't try the Unity reboot until later, so in the mean time I tried unlinking the files and relinking. Oh, they relinked. Relinked to the Unity volume. And the media isn't even on there. Buggy.
>>>>>>
>>>>>> Jay
>>>>>>
>>>>>> On Feb 3, 2012, at 9:18 PM, Jay Mahavier wrote:
>>>>>>
>>>>>>> Ok, so recently upgraded to MCv6 on Lion. We have a Unity 5 system in house. I'm use to being able to organize my media into folders and rename them and have the media be online and be able to rebuild the databases. As an example, if my system is named Avid01, the default folder in the MXF directory is Avid01.1. All my new media goes in there. But in the past, I could make other folders with names like Avid01.1_Prod_01, Avid01.1_VFX_01, etc. and it would rebuild the databases when I added media to them. But now it's stopped working. Only folders named like Avid01.2, Avid01.3, etc are being scanned. Am I the only one having this problem? Because it sucks.
>>>>>>>
>>>>>>> Sorry for sounding so upset, but I'm really starting to hate Unity after many years of thinking it was awesome. And with the cost to move to ISIS I'm thinking that if and when we are done with this Unity system that I'll be done with Avid storage all together.
>>>>>>>
>>>>>>> Jay
>>>>>>>
>>>>>>> ------------------------------------
>>>>>>>
>>>>>>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>>>>>>> Yahoo! Groups Links
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------
>>>>>>
>>>>>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>>>>>> Yahoo! Groups Links
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------
>>>>
>>>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>>>> Yahoo! Groups Links
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>> ------------------------------------
>>
>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>> Yahoo! Groups Links
>>
>>
>>
>
>
>
> ------------------------------------
>
> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
> Yahoo! Groups Links
>
>
>
No comments:
Post a Comment