Spotted files not turning up on PT timeline

[DF]

SM v4.3v61
PT 10.3
10.7.2

I've seen this a handful of times, and haven't pinned down the cause.  Has anyone else seen it, and know of a solution?

For some unexpected reason when attempting to spot to the PT timeline, SM will transfer a file to the correct Finder location, but it will not turn up on the PT timeline.

If I repeatedly spot, eventually it will turn up on the timeline, but then I have transferred multiple copies at the Finder level, which clearly I don't want to do.

DAW App is correctly set to Pro Tools.

Rebooting the entire Mac doesn't fix it.  Occasionally opening up another session and going back to the original session seems to set things right, but not always.

I sure would like to know what's going on and how to fix it.  Some people have suggested its that I might have a "Search" active in Pro Tools, but even if I'm showing all (Command Shift D), and showing everything like "Auto-created clips", the problem persists.

Ideas?

[DF]

Additional info:

- spotted files (attempts) that are transferred at the Finder level, that fail to show up on the timeline, also do not show up in the clip list.
- Libritron (another database that does spot to the timeline) spots correctly when SM doesn't.
- Snapper also will spot to the timeline when SM won't.

I've reinstalled my OS (10.7.2) over the old system, repaired permissions, and run Cocktail to clean up as many potential OS issues as possible, with no change in the SM spotting performance.

The Libtritron and Snapper spotting successfully, points more to a SM issue than PT.

The intermittent nature of this is quite scary.  This popped up again today, in the middle of working on a session (was working fine this morning before that), and now I can't get SM to spot at all.  I'm glad the director isn't sitting with me today, but it sure is slowing me down.

[steve pecile]

David

We're not aware of any such intermittent issues.  Although it being 'intermittent' could mean it may just not have happened in the other apps(maybe not spotting as frequently).  I'm assuming you have a filenaming scheme that resolves as an incorrect filenaming scheme will adversely affect a copy and spot.

Do you have a specific example for us to test that does spot in other apps but does not in SM? Is there a reproducible case?  

We do have a new beta to combat the know issues in Mountain Lion and reported Apple events bug.  Anyone wishing access can contact me directly.

--
You received this message because you are subscribed to the Google Groups "Soundminer Users Collective" group.
To view this discussion on the web visit https://groups.google.com/d/msg/soundminerforum/-/cgvYzfaimGsJ.
To post to this group, send email to soundmi...@googlegroups.com.
To unsubscribe from this group, send email to soundminerfor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/soundminerforum?hl=en.

[DF]

On Saturday, November 24, 2012 3:21:49 AM UTC+13, stevep wrote:

David

We're not aware of any such intermittent issues.  Although it being 'intermittent' could mean it may just not have happened in the other apps(maybe not spotting as frequently).

I've traced it to a single session where SM fails 100% of the time and other spotting apps work 100% of the time.

 

 I'm assuming you have a filenaming scheme that resolves as an incorrect filenaming scheme will adversely affect a copy and spot.

No.  If I switch to another session and spot from SM it works spotting the exact same selection from SM.  It's session and SM specific.
 

Do you have a specific example for us to test that does spot in other apps but does not in SM? Is there a reproducible case?  

Possibly.  The session I'd have to send you would have to be cleared out as it contains info that I can't reveal due to NDA's.  I've been in transit and still can't get to Pro Tools at home yet to see if I can send it to you but I'll take a look as soon as I can.  If I can clear it and it still fails I'll send it on.

I've not been able to trace why this session fails, but the same session used to work fine and then something broke it.  I've heard that having a search active can screw it up but that's not the case here as I've checked all the clip bin options and verified they're set to the same as sessions that do work.  I can usually get to the bottom of these thing's as far as causes, but so far no luck.

At least I'm done with that reel now so don't have to deal with it since other sessions do still work.

Cheers,

- Dave




 

[KMcK]

I'm having this same issue, but it is not session specific, it happens with all sessions. At first I thought it was intermittent, but eventually I realized it's related to whether or not Soundminer has been launched since the last restart. 

In other words, a full computer restart will fix the problem... until I quit Soundminer and then re-open it. Basically I get one use of SM per restart. If I quit SM and then open it again, it will fail to spot to session (the file will transfer in the finder, but SM will go into spinning beachball crash and the file never shows up in PT session). Restart computer, launch SM and PT again and it works... until I quit SM and try to re-open. Rinse and repeat. 

Running Pro Tools HD 10.3.2 on OS 10.8.2 on 2010 Mac Pro.

km

[DF]

Mine is not improved by a Mac restart, and is still session-specific.  I just tried the same session that was giving me trouble in NZ and it's behaving the same way now that I'm home, on a different machine.  I cleared the session of everything on the timeline andand now SM will spot to it correctly.  Of course that wouldn't have helped me when I was working in it, but it should help in tracking down the error.

I'll have to do some more tests to see if I can figure out exactly what stage of the clearing allowed SM to spot, but here was the clearing procedure I used.

1) Show All tracks
2) Select all tracks and Marker "Track"
3) <Return> to go to session start, then <Option Shift Return> to select to the end of the session.
4) <DELETE> (In SLIP Mode)

Then SM would spot.  Something is definitely amuck.

- Dave

[JD]

Hi KM, yes we're aware of that one.  It was an Apple 10.8.2 bug.  We have a version that a few people are testing for v4Pro that works around it.  Contact techsupport (at) soundminer.com if you want to try it(and own v4pro)

[JD]

If the files are offline is the session still busted?  Are there descriptions in the region/filenames that are sensitive?