Bounced files do NOT appear in finder immediately

Yes, it's an OS issue and, as reported above, has been with us for a long time. It's not only audio files, I have the same problem with video files and screen capture. It happens because the Desktop is not registering that a new file has appeared and nor does the file system tell the desktop that it needs to refresh. It's probably in this latter area that the problem is most acute. The OS ought to know which windows are open (including Desktop, which is a sort of meta-window) and cause them to refresh.

I have no sure fire way of getting around it but normally, if my file doesn't appear, I open up a Finder window, point it at the target folder (eg Desktop or Music > Logic > etc) and the file appears then. Creating a finder window appears to interrogate the disk correctly, whereas pre-existing FInder windows have to wait a looooong time to get notification that their folder contents have changed.

I'm not surprised if you didn't find a thread in the Logic section. There may be some in the OS sections of the Discussion Forums so don't feel too bad 😉

Pete

I don't think it's an OS issue, I think it's a Logic issue.

Let's take a quick example: I'm in Safari, I hit "save as" and save to the desktop. The saved web page file icon shows up on the desktop immediately. So there is no general "the finder doesn't realise a file is there and doesn't refresh" going on - if that was a simple fact, it would show this behaviour with saving files from any application.

And if I save a song file from Logic to the desktop, it also shows up straight away.

So there is something in writing the bounce file that is implemented differently from saving a song file, and potentially it's related to the filetype, as bounced WAV's do show up as expected, but AIFF's don't.

All this tells me it looks most likely to be a (longstanding) Logic bug, that perhaps only shows itself with certain OS combinations.

Hi Bee Jay,

But I've seen it with FCP, Compressor, Snapz Pro video capture and other software as well, that I can't bring to mind at the moment.

What I am pretty sure about is that I've seen it more often with software that takes a while to stream its data to the file (which might imply that there is a bug in the file close routine or that the app still have the file handle open when it ought to close it) and that might imply it a problem in the Pro Apps support routines (if they handle streaming to files, which I doubt) or some aspect of file management which, guessing that these things are all done through OS file management objects, would imply incorrect use of the object or a bug in the object itself.

I've certainly seen it elsewhere so it's wider than Logic. Have just tested a Snapz Pro video capture again and it's definitely there as well. I'd agree completely, though, that it's a combination problem. Doesn't always happen. I haven't rebooted this machine for three days. I suspect that, were I to do so the problem would go away. Ho hum...

Pete

But I've seen it with FCP, Compressor, Snapz Pro video capture and other software as well, that I can't bring to mind at the moment.

Ok - so if it's quite common, then indeed it could be a common implementation of file writing that's not quite working right (due to changes in the OS perhaps) or is particular system routines themselves that have this issue. Makes sense.

What I am pretty sure about is that I've seen it more often with software that takes a while to stream its data to the file (which might imply that there is a bug in the file close routine or that the app still have the file handle open when it ought to close it) and that might imply it a problem in the Pro Apps support routines (if they handle streaming to files, which I doubt) or some aspect of file management which, guessing that these things are all done through OS file management objects, would imply incorrect use of the object or a bug in the object itself.

Yes, agreed. A much more eloquently written version of my above paragraph 🙂

I've certainly seen it elsewhere so it's wider than Logic.

I'm not up on the OSX reporting things - are there OSX feedback places where you can report OS bugs? There's always the ADC bug tracker I guess...

If you have Transmit you can use this as a workaround for this problem, especially if you have a critical need to see your files immediately (for delivery to a client, etc...), as follows:

Open a new window in Transmit. On the left is "my stuff", to the right "their stuff". Navigate to the drive/folder in "my stuff" and hit CMD-R (refresh). This forces the updating of the file list and "missing" files will appear.

I've had situations where a Finder window for a drive/folder and Transmit were open simultaneously. The Finder window would not display recently created files, but the Transmit window (upon hitting CMD-R) would.

The files are there, it's just that the desktop doesn't redraw to show the file.

If you open a finder window on your desktop folder, you will see the bounce file there without problems - as indeed you will in any other program that displays a file list of the desktop folder....

Just to clarify, I'm not saying that the files aren't there. They are there, but they don't always show up, per what we're discussing. And as I described above, opening a finder window for the drive/folder where those files live (but are not visible) will not always display those files right away. That's the problem. But they will show up in a Transmit window. So... you can simultaneously have both the Finder window and Transmit window open, only that the Finder won't show the same files that you can see in Transmit. Hope that's clear.

Message was edited by: iSchwartz

And as I described above, opening a finder window for the drive/folder where those files live (but are not visible) will not always display those files right away

Oh really? I haven't seen that behaviour. I've certainly seen the desktop refresh issue, but those "unrefreshed" files are always visible in finder windows for me.

That definitely sounds like an OS (or perhaps a Finder) problem, if the directory is displaying from the cache and not seeing one of our phantom bounces...

I had something similar yesterday that might be related.

I was exporting some tracks from Logic and created a folder to contain them by clicking on the New Folder button in the All Tracks as Audio Files... dialog.

After exporting the tracks I tried to add them to the Audio Bin in a new project to check they were OK. The Open File dialog couldn't see the new folder that had been created from the Export dialog. It was there when I looked in the Finder and the files were inside, but not visible from within Logic.

I've just checked and Logic can now see the folder, so it was only temporary blindness.

Message was edited by: tankfield

I believe this is an OS issue.

Definitely an OS issue. It's been a problem for years.

If you bounce .WAV they appear
If you bounce .AIF they don't

So I always bounce .WAV