Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Post Production > Post - Surround - Video
Register FAQ Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-27-2015, 01:28 PM
viaspiaggia viaspiaggia is offline
Member
 
Join Date: Apr 2003
Location: Colchester, CT
Posts: 402
Default Could not complete the import tracks command because basic_string::at

a search is turning up nothing at all on this, so here goes.

Starting a feature so I'm getting AAFs out of his Premiere project. He has it in a bunch of reels (11!) and sent them each separately. Reels 2-11 imported perfectly, reel 1 is giving the error
Could not complete the import tracks command because basic_string::at
every time.

I've had him strip automation, remove fades, remove effects, etc, to no avail. He even just made me an AAF per track and those are still throwing the error. Which seems to indicate something outside of a file problem, since 2 of the tracks are only a few music clips (according to him).

This guy is a novice to say the least, what can I suggest to try and trouble shoot this? I don't know Premiere much at all...

thanks for any thoughts!
__________________
Mac mini 2018 i7
ProTools Ultimate Native
Focusrite Scarlett 18i20
Atmos 7.1.2
hugmonstersound.com / unheardof.world
Reply With Quote
  #2  
Old 04-27-2015, 06:09 PM
Chief Technician Chief Technician is offline
Member
 
Join Date: Dec 2001
Location: NYC
Posts: 6,981
Question Re: Could not complete the import tracks command because basic_string::at

Quote:
Originally Posted by viaspiaggia View Post
what can I suggest to try and trouble shoot this?
In the days of yore, when we worked with OMFs, Pro Tools would have a fit if there were mixed bit depths or mixed sample rates (or both). Is this person certain that everything is the same bit depth and sample rate?
__________________
Jonathan S. Abrams, CEA, CEV, CBNT
Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10)
Reply With Quote
  #3  
Old 04-28-2015, 10:22 AM
smurfyou smurfyou is offline
Member
 
Join Date: Oct 2006
Location: Charlotte, NC
Posts: 1,737
Default Re: Could not complete the import tracks command because basic_string::at

Have him try OMF. Embedded and referenced OMF's work in Premiere now. Just to see if it makes a difference.

Have him check for any effects or transitions that are suspect. In fact I'd remove any and try again. Ensure all the media is online, and that it is the same format and no lingering MP3's or such. Mixed bit rates should not be a problem.

When you say he's trying one track at a time, is he just selecting one track or actually duplicating the sequence and deleting every track but one? That is the way to do it if it comes down to one at a time.
__________________
~Will
Reply With Quote
  #4  
Old 04-28-2015, 10:23 AM
smurfyou smurfyou is offline
Member
 
Join Date: Oct 2006
Location: Charlotte, NC
Posts: 1,737
Default Re: Could not complete the import tracks command because basic_string::at

Also if he's got the whole Adobe suite, he can "Send to Audition", open it up in Audition then export from there. Usually straightens things up.
__________________
~Will
Reply With Quote
  #5  
Old 04-28-2015, 02:00 PM
philper philper is offline
Member
 
Join Date: Dec 1969
Location: ALbany CA USA
Posts: 982
Default Re: Could not complete the import tracks command because basic_string::at

+1 re a clip at wrong SR or a corrupted clip. If the export doesn't work in AAF it isn't likely to work in OMF either.
Reply With Quote
  #6  
Old 04-29-2015, 06:18 PM
viaspiaggia viaspiaggia is offline
Member
 
Join Date: Apr 2003
Location: Colchester, CT
Posts: 402
Default Re: Could not complete the import tracks command because basic_string::at

Thanks all

He did a render and replace with the audio and then exported, but still no love. Wouldn't that fix any sample rate or corrupt audio issues?

Going to have him try the OMF and the Audition route.
__________________
Mac mini 2018 i7
ProTools Ultimate Native
Focusrite Scarlett 18i20
Atmos 7.1.2
hugmonstersound.com / unheardof.world
Reply With Quote
  #7  
Old 04-30-2015, 06:05 AM
Postman Postman is offline
Member
 
Join Date: Dec 1999
Location: where land meets sky
Posts: 2,375
Default Re: Could not complete the import tracks command because basic_string::at

Hi Adam,

Have you tried opening PT10 and PT11? They are different and neither has proven reliable here. We've regularly opened omf and aaf files on both and sometimes on MC as well, in an effort to get the audio we're supposed to have.

Last edited by Postman; 04-30-2015 at 06:06 AM. Reason: edit: this is a primary reason I won't install PT12 yet
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
"Could not complete your request because basic_string..." audiofreak11 Pro Tools 10 1 08-22-2013 11:14 AM
Could not complete the open recent session command because while translating tracks Peter Manganay Windows 3 12-04-2011 03:41 PM
Could not complete the Import Tracks command matchoo0 Post - Surround - Video 5 07-20-2011 09:32 AM
Could not complete the Import Audio command because magic ID does not match ronfinch 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 0 02-21-2010 02:32 PM


All times are GMT -7. The time now is 11:50 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com