Rendering to external HD - no output file error

[MLJONES]

Hi Please help - used Reaper on PC for years - love it - now I've moved over to the dark side and have a mac. I can't render to my external HD - error with output file - just freezes. It renders to my local drive but not my external - I have checked the path and all is ok!

Any thoughts please - thanks in advance.

OX S Yosemite 10.10.3

[EricM]

Can you copy anything to your external disc? If not, its probably formatted to NTFS
which Osx can only read by default.

e

[MLJONES]

Originally Posted by EricM

Can you copy anything to your external disc? If not, its probably formatted to NTFS
which Osx can only read by default.

e

Thanks for your reply

Hi, My external drive is new and formatted to Mac OS Extended (Journaled) def not PC NTSC

[vdubreeze]

Maybe you've already done this, but I would run Disk Utility on it anyway, and fix permissions on internal just to make sure. Yosemite was a problem for me with some random drives over 3T where permissions to access were wrong and a mystery. Ended up solving by reformatting via terminal.

As EricM says, does the drive function fine for every other kind of transfer? Any non standard symbols in the drive name?

[MLJONES]

Originally Posted by vdubreeze

Maybe you've already done this, but I would run Disk Utility on it anyway, and fix permissions on internal just to make sure. Yosemite was a problem for me with some random drives over 3T where permissions to access were wrong and a mystery. Ended up solving by reformatting via terminal.

As EricM says, does the drive function fine for every other kind of transfer? Any non standard symbols in the drive name?

Hi - thanks for your reply.

I have run the disk utility and all appears to be in order. I so used to PC and only just moved to MAC.

The path has no drive letter at the beginning just:

/Volumes/Cre8mediaLtdMaster/Cre8media/AUDIO/BTCC

The External drive is a Samsung 1TB and formated to Mac OS Extended (Journaled) from new

[citizenkeith]

Can you copy files to this external drive, or is the problem ONLY happening when rendering to it using Reaper?

[MLJONES]

Hi, yes, all other files are fine, no problem - just Reaper render freezes.

[vdubreeze]

What happens if you start a new project and try it?

How about if you create a project on the external? It would be very odd if Reaper could record to and play from with no issue but not render to it. If it couldn't run a project at all from the external it would mean something less mysterious : )

[Mink99]

Did you notice any obvious error messages in the osx-console ?

[serr]

Is your audio interface USB based? And is your external HDD also USB based?

Could be a USB bandwidth issue.

[bluetinstar]

I use 2 Samsung 1Tb external drives formatted to Mac OS Extended (Journaled) off a Novatech USB 2 Powered hub into a Mac Book Pro running OS 10.10.2 Yosemite. I have had no rendering issues with this set up.

I do however, create new Reaper projects on one of the external Samsung drives, and save all project data and subsequent renders to that drive. (The second Samsung drive is used for all my Spectrasonics and other VST sound libraries, some 400Gb at the moment)

Hope this helps,
Fred.

[MLJONES]

Dear All - thank you for your advice.

I will answer your questions below, and thanks again.

Yes I have tried starting a new project. I have also checked an double checked the paths in preferences.

My audio device is my MAC's internal playback and record and my your external HDD is 3.0 USB based?

I've also tried reaper 32bit

I can recored to and even load older projects to pay back from the external drive! - just can render - error message - the target drive/ path does not exist.

I can render directly to my mac's internal drive no problem at all.

Thank you for your patients, I would dearly like to see if or what I am doing wrong.

bluetinstar -when you say create new Reaper projects on the external Samsung drive ? how do I do that?

BW

Matt












Reaper Vr - 4.78/64
OX S Yosemite 10.10.3

[serr]

Alright, so your external HDD is named Cre8mediaLtdMaster. (And as you see, you can use actual names for drive volumes in OSX. You aren't restricted to single letters for volume names.)

Create new Reaper projects on the external simply means save the project file (.rpp) in a subfolder on the external.

I know you said you checked the file path you entered in the render window multiple times... but humor us with a screen shot of the render window open with said render file path entered.

[bluetinstar]

Originally Posted by serr

Alright, so your external HDD is named Cre8mediaLtdMaster. (And as you see, you can use actual names for drive volumes in OSX. You aren't restricted to single letters for volume names.)

Create new Reaper projects on the external simply means save the project file (.rpp) in a subfolder on the external.

I know you said you checked the file path you entered in the render window multiple times... but humor us with a screen shot of the render window open with said render file path entered.

Matt... As serr says... + 1

[Aymara]

I guess you have access rights for the folder on the external HDD?

Might the long volume name play a role? Never saw such a long volume name

[bjonko90@hotmail.com]

I am having the same problem with rendering a track. When I try to render the window says "the target/ drive path does not exist, is unavailable, or is not in use"

This is strange, because I am able to render other projects, but this particular project will not render

Any tips?

Barry

[MLJONES]

Ok ..... Dear All,

Thank you for your advice and patience... I've found the problem.

My external HD label had an invisible space at the end of its name! (my error when labelling it)

I kept removing the space in the path ie- /Volumes/Cre8mediaLtdMaster /Cre8media/AUDIO/BTCC

So I relabelled the drive (removing the space at the end of the name and all is fine!) Reaper renders like a dream!

You live and learn!

BW

Matt

[Aymara]

Originally Posted by MLJONES

You live and learn!

Hehe ... I thought, if the long label could have caused issues. I would have chosen a shorter name like CMmaster, which is more handy at the command line

[bluetinstar]

Good news... Glad you found the problem and got it sorted !

Fred