Cant Bounce.. Need some help here.

[Relic]

PT 6.4
I have had this problem on and off, but now for some reason I cant make it work..
I go though and have the track ready to bounce and do so ..
Stereo interlieved
convert during bounce
16 bit
save under a file name (have both clicked "save" and mashed eneter

It goes through the whole "song" and looks normal , but when I go to pull up the wav file there is nothing there.

When I tried to save as a multi mono it gave me an error message relating to a line 33

Otherwise everything still records and is normal.

I have defragged and blew out dust, turned it off and on, prayed and all that.
Anybody have an idea?
Thanks!

[Kontents]

What have you tried to do differently besides the mono?.. Have you tried bouncing without converting during?

[LDB]

U may have to just reinstall Pro Tools and turn off things that are going on in the background when you're bouncing down. I use to have that problem with 6.4 sometimes. Anything interfering with the process i.e background stuff, can cause this. It's like when burning a cd, if your system hiccups the burn process won't complete.

[Relic]

mmmmm, reinstalling would be hella bad, as this aint the "official" version if you get my drift, or actually it may be, but the guy who installed it is awol like a mofo..
Something about owing me an ass load of money for a d8b can keep a guy mia...

Kontents I think I did try that, in fact I tried about everything I could think of including superstitious types of things lol just to try and get it to work.
I will try again today and write down that error message, it was something about unable to create file.

grrrrrrrrr.

[7thangel]

record to disk. print the mix into pt via aux into a stereo track (with any final fx on a master channel not on the recording track). then export it. i don't know the key command but the option is there and sill the best and safest method compared to bounce to disk in pt. if you have a program that can change bit rate and dither, export out at 24 if that's what your using if not export at 16 bits

[LDB]

mmmmm, reinstalling would be hella bad, as this aint the "official" version if you get my drift, or actually it may be, but the guy who installed it is awol like a mofo..
Something about owing me an ass load of money for a d8b can keep a guy mia...

Kontents I think I did try that, in fact I tried about everything I could think of including superstitious types of things lol just to try and get it to work.
I will try again today and write down that error message, it was something about unable to create file.

grrrrrrrrr.

You should move up to 7.4. If you need it I got it!

[Relic]

^^^ doesnt that require an upgrade in hardware?


Ima check that 7thAngel...

[7thangel]

? before this problem, did you ever check to see if your 'version' will open in another persons pt?

[thedreampolice]

No you dont need new hardware. Try hitting select all and then doing a bounce. Or setting your selection markers to the song. Let me know what happens.

[LDB]

^^^ doesnt that require an upgrade in hardware?


Ima check that 7thAngel...

Nope....you can use your digi001. I use it with my M-Audio Fast Track Pro. There's no dedicated hardware for that version.

[Relic]

here's the message I get when I select convert after bounce:

Could not complete the "Bounce to Disk..." command because: Assertion in "\code\azores_Handel\AlturaPorts\NewFileLibs\FF_Aud ioproperty.cpp" ' line 33

Chris there is only one track to select, but I'll go try again.

I have no idea why there is a space in audioproperty above, illmuzik put it there thats not the way the messg reads.
7th Angel yes before sessions would open at other studios.
LDB its lookin like I may need that upgrade, but I would need someone on the phone to hold my hand through that shit , as I didn't install any of this stuff in the 1st place lol, we are talking nervous sweat hella worried.

[LDB]

here's the message I get when I select convert after bounce:

Could not complete the "Bounce to Disk..." command because: Assertion in "codeazores_HandelAlturaPortsNewFileLibsFF_Audiopro perty.cpp" ' line 33

Chris there is only one track to select, but I'll go try again.

I have no idea why there is a space in audioproperty above, illmuzik put it there thats not the way the messg reads.
7th Angel yes before sessions would open at other studios.
LDB its lookin like I may need that upgrade, but I would need someone on the phone to hold my hand through that shit , as I didn't install any of this stuff in the 1st place lol, we are talking nervous sweat hella worried.

ah ha ha ha ha ha....no problem man. After you exhaust all other means hit me up and I'll send u 7.4 by way of usendit with written instructions and my phone number.....lmao {old ass baby}

[Relic]

^^ Im gonna do that , in the very near future.

But just to make things curiouser I managed to bounce a diff file to wav..
Apparently my system doesnt like illmuzik radio...

[Kontents]

So it worked for some file type but not the Illmuzik Radio one?

[Relic]

yes.... weird.. But I have been having this problem sporadically...
I'm really leaning toward upgrading here..lol

[Relic]

The solution was to "save session copy as" in the same basic folder and the copy bounced.

TaDaaaaaaa!

And now you dont have to sweat like I had to!

[Relic]

well... Now Ive tried that solution with a recent bounce, and I still am getting a line 33 problem.

Im going to attempt the previous solutions again.

Any other solutions?

U may have to just reinstall Pro Tools and turn off things that are going on in the background when you're bouncing down. I use to have that problem with 6.4 sometimes. Anything interfering with the process i.e background stuff, can cause this. It's like when burning a cd, if your system hiccups the burn process won't complete.

nothing is going on in the background, whole pc is commited to just recording.

record to disk. print the mix into pt via aux into a stereo track (with any final fx on a master channel not on the recording track). then export it. i don't know the key command but the option is there and sill the best and safest method compared to bounce to disk in pt. if you have a program that can change bit rate and dither, export out at 24 if that's what your using if not export at 16 bits

havent tried this..

Really shouldnt hve to go thru all that, but its an idea..

? before this problem, did you ever check to see if your 'version' will open in another persons pt?

yes it has..

No you dont need new hardware. Try hitting select all and then doing a bounce. Or setting your selection markers to the song. Let me know what happens.

I have selcted all the tracks and tried bouncing, this is a good solution and is the one that is supposed to do it, but it no longer is.. I think that is what has me most frustrated and sweating.


Not really sure why my solution above worked for that instance and no longer does here...

[Chrono]

after all... if it is a computer-line-coding registry or whuthastuck situation.. you might just need to reformat!! backup an ZOOMmm

[Kontents]

Wow..this has been quiet an issue..

[Relic]

DigiDesign support says:


Could Not Complete Bounce To Disk...command because: Assertion in "\code\azores_Otis\AlturaPorts\NewFileLibs\FF\Audio \FF_AudioProperty.cpp", line 33 when attempting to Bounce To Disk in Pro Tools 6.4.

In one case, reducing the DAE Playback Buffer to 0 solved the problem. (Setups menu > Playback Engine)


http://archive.digidesign.com/support/

[7thangel]

you still haven't tried the export solution? it's not complex, convoluted or a lot of work (and prior to v7, some felt necessary due to losing automation or other glitches while performing 'bounce to disk')

pc: ctrl+shift+k

[Relic]

Im gonna try that too. I didnt try that yet, cuz I havent ever tried it before.

[7thangel]

it's like an offline bounce but there's no real bounce just a straight up export. try to export just one of your tracks (consolidate it if you have a bunch of edits) and do it to see if it will work (choose a place where to send it).

if it works, then just make your mixes utilizing the master and/or a aux buss in rec with it's input set to whatever you're sending the track outputs to (i.e. audio 1-2) use the master either for automated fade or for master buss/channel effects if you're they type to put something on the master (don't bother putting it on the aux/buss master record). export and done.

as far as dither, i'm not sure if you export out as 16 from a 24 bit audio file, that pt will apply dither, they have auto settings that can be enabled/disabled with choice of built-in dither algo's, but that's in 7, and like i said, i don't know if it would apply to export as well.

personally, this is the only method i use with pt, printing in pt allows me to analyze with my ears in the future within pt as well as analyze using visual spectrum and phase tools.

another advantage other than forgoing the possible wonkiness of pt's bounce and it bouncing in real time, is if i print stems along with the mix, i can come back and easily lower the vox stem if that's what someone asks for after they've got the mix, make a radio edit if needed (same for tv, instrumental, etc versions) or make changes i feel need to be made all with simple quick fader moves or muting and printing that mix without having to go back to the track and aux/buss.

[Relic]

^^ That is all very good info, Im gonna have to digest some of that, maybe even ask some more questions, however before I even got to what you were talking about the solution, at this point was:

reducing the DAE Playback Buffer to 2 (default) solved the problem. (Setups menu > Playback Engine)

I may play with what your talking abou ttho Angel as I haven't fooled around with those features before.

[7thangel]

good to hear that the prob was solved