|
|
|
Ptle & Osx Error -35 ?, Bounce to movie Command error? HelpPls! |
|
|
|
Thu 8 Feb 2007, 10:10
|
Rookie
Group: Members
Posts: 33
Joined: 02-Oct 06
Member No.: 83,805
|
Hi all,
I've been watching this forum for a while and it seems there are a good few people on here!
I posted what's below to the DUC forums but am getting minimal relies without much help - Can anyone here give there knowledge and help me out please?
I wrote:
After a week of bouncing to movie and no issues. Today (the day of all days) I am trying to bounce again and getting the "Volume not found error-35" message.
I had some Foley made which I supervised last week. The Foley studio uses TDM vers. 6.9 - I've never had or heard of issues opening (or adding to) sessions with a later version. Could it possibly be a problem now for the latest LE release?
The picture cuts started out as .MP4 - I converted them to .MOV I have also made a new session in PT - changed the name of the original and imported a new mmovie as you suggested.
I have trashed the prefs. and the database, restarted...
I have tried to bounce the file in different locations on internal and external drives.
Please help ASAP as I'm really stuck.
Thanks very much in advance!
Lee Grainge
G5 ppc 1.8Dual 5GB RAM OSX 10.4.8 PT 7.3.1 LE MBOX1 DV Tool Kit II
DIGI at DUC wrote:
What kind of drives are you using and where, exactly, are you choosing for your bounce location?
This error is an OS error, not Pro Tools. It's indicating the the drive you're selecting for the bounce is not being found by the OS for one reason or another.
Have you tried bouncing to a different location?
Is it only this particular session having the problem? If so, is there anything specific or different about the video file in the session that may be contributing to the problem? What format is the video in and what type of compression does it use? Which drive is the video file on?
You could try creating a new session and use 'Import Session Data' to import all the tracks from this session, except for the video track, then recreate the video track and try the bounce again. If the session is corrupted somehow, this may get around that.
Someone else also has the same issue as me.
I have tried all of DIGI tech thoughts on this but to no avail! I can however edit the pic to the stem I made, but that's a pain when you've got a deadline!
Your help will be most forthcoming!
Best,
Lee Grainge
G5 ppc 1.8Dual 5GB RAM OSX 10.4.8 PT 7.3.1 LE MBOX1 DV Tool Kit II
|
|
|
|
|
Fri 9 Feb 2007, 17:48
|
Rookie
Group: Members
Posts: 33
Joined: 02-Oct 06
Member No.: 83,805
|
QUOTE (Jim Hoyland @ Fri 9 Feb 2007, 14:08) This sounds like an error caused by moving from one system to another. The "Digidesign Database" folders that PT creates all over the shop are detailed records of drives used over the history of the application's use and changes in your set-up can upset the little bugger.
The first thing to try would be to go into the "Windows > Workspace" area and make sure that the drive you're bouncing to is set to "R" for both audio and video. If it won't let you do this, you may have to re-install PT as there could be an issue with these databases. For example, I've recently had this problem when restoring a drive.
On a wider note though, its been my experience that the movies created by ProTools from a "Bounce to Movie" operation are extremely unstable, and are likely to cause problems during playback. If you can, I would simply bounce out a stereo audio file and then use QuickTime Pro to stick the audio and video nack together (of course FCP is good for this too).
Not sure why there should be a problem with movies from PT, but we do a lot of this kind of thing at the Uni where I work, and I've found the QT route much more reliable. Hey Jim, Thanks for your thoughts! I have already checked to make sure my workspace drives for Audio+Video are all set to 'r' You say unstable, but I've never had this issue in 7 years, even when I started with the free version this never occured. To not have the database issue I rebuild my computer after every job, I was told this by a peer of mine. Would you agree? The QT Pro way is the way I have been doing it but it's a time thing that annoys me. PT have made a excellent upgrade but I feel there are many faults in the programming. That said the QT option is my only... I also found that if you do use QT Pro for this then it's always improtant to make sure you copy picture to audio rather than the other way around. Reason being (and I'm sure most will know this) is that the compression of the video source will make your audio sound like a 4 bit file. It's nice to get some feedback here as the DUC digi tech seem to of gone on holiday. Best Regards, Lee
|
|
|
|
|
Mon 12 Feb 2007, 10:08
|
Rookie
Group: Members
Posts: 33
Joined: 02-Oct 06
Member No.: 83,805
|
QUOTE (Jim Hoyland @ Sat 10 Feb 2007, 14:24) Hmm.. Got me stumped then.
But, if you "Add to movie"/"Save As" in QTPro, there should be no conversion of the audio file, no matter what Video codec you use (unless its something that needs to be muxed, but no-one does that anymore, do they?).
Sorry, but that's the end of my inspiration! Hey Jim, I always find that simply adding the movie to audio using "Add to movie and scale" works. If you just add to movie doesn't it add w/e on the end? rather than scaling... As for my original thread - I'm hoping that Digi come up with a update that resolves this and the 'other' issues that are consistant within 7.3.1 Cheers, Lee P:S muxed - wasn't that last used when the Dodo was still around?
This post has been edited by leegrainge: Mon 12 Feb 2007, 10:09
|
|
|
|
|
Tue 10 Jul 2007, 15:54
|
Newbie
Group: Members
Posts: 5
Joined: 10-Jul 07
From: Orlando - US
Member No.: 92,875
|
Was this 'bounce'... volume not found' issue ever resolved ?. We have the same problem in our shop. also using LE 7.3.1 and Digi 002
|
|
|
|
|
Fri 27 Jul 2007, 17:26
|
Rookie
Group: Members
Posts: 33
Joined: 02-Oct 06
Member No.: 83,805
|
QUOTE (tskolits @ Tue 10 Jul 2007, 15:54) Was this 'bounce'... volume not found' issue ever resolved ?. We have the same problem in our shop. also using LE 7.3.1 and Digi 002 Hi, No it wasn't ever resolved. Even the DUC forums didn't know what it was. I did try and delete all of my database folders that PT sends over ever HD I've got and had some success but within hours of bouncing to movie again I got the same error code. Must be a bug PT/Digi don't care about enough to do anything with. Anyway I found another (tedious) way. I had to bounce my stems/tracks then apply them to movie in QT. If you find any other way to resolve this issue please let me know.
|
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
|