Samples reloading when saving

Hi,
Every time I save a song, Logic reloads samples I'm using.
This is happening with Intakt and Ultrabeat, but not with EXS24 and Kontakt.
It means saving can take up to several minutes.
It is happening with Logic Pro 7.1. I have never experienced this with previous versions of Logic.
Has anyone had any experience with Logic behaving this way?
I haven't been able to find anything about it in preferences...
Thanks!
Morten

Bump - still haven't found an explanation as to why Logic reloads samples.

Similar Messages

Images are down sampled only when saved

Hey is there a way to get full 2048 images into the photos app? I tried saving images in safari and chrome which are viewed at full resolution, but when I check the photos app I can clearly tell the quality is reduced when comparing to in browser.

If you know the size of the images, have the renderer return measuredWidth
and measuredHeight that reflects the size of the image (or approximate
size). There should be past discussions on this topic.

Ultrabeat loses track of samples when saved within a Project???

Why is it that when I save a project with all my custom samples loaded into the Ultrabeat, I have to manually re-find them once it comes time for me to open the saved project?
Example:
- I'm working on a project, many instances of the Ultrabeat, many wav samples loaded into a blank 'sample player' patch.
- I save the project, making sure that all samples are to be saved in their respective folders along with the project.
- I go and open the project folders, double checking that the samples are indeed saved. Yep - they are.
- I Send the project file and folder out to my laptop to work on it on the go.
- I Recheck the files.
- I load up the project file, all normal samples load, yet the Ultrabeat comes up with a search window and tells me to find EACH. INDIVIDUAL. HIT. Which are located DIRECTLY in the folder that Logic itself saved them in. No tampering. No modifications.
- Then I spend the next hour manually finding the samples out of the SAME folder...
You'd think that if I saved a project, along with all files associated with it, and Logic put them in a specific destination folder, that it MIGHT know where to go and find them once it comes time to reopen the project.
Maybe I'm doing something wrong? Any ideas?
If not, WAKE UP APPLE.

That's exactly what I do already, so there is no reason why it should be having a hard time finding the files.
And, as I mentioned earlier, I double check to make sure that the files were actually copied before I transfer the project and included project folders. Also, when it comes time for Ultrabeat to lose track of the samples, each and every one of them are in the exact same Ultrabeat Samples folder that was created by Logic itself.
Again, There is no reason why Logic shouldn't just be able to find the files that it itself put into a specific folder within the project file.

Adobe bridge crashes when saving illustrator files

Hi there,
We are developing custom connector using Adobe Drive SDK for our DAM system, the integration with CS was working fine, we recently updated Adobe Drive to 4.2, and we are encountering bridge crashes when saving illustrator file. It didn't happen with older version(4.0.2) of Adobe Drive, not sure why. I pin point the part that causing the issue: in our custom connector, we have READ_XMP_METADATA capability which we need to display the thumbnails and previews, and in the ftp sample connector, this capablity is not included originally, so the issue does not happen, but if I add this capabilty, the crash issue happens as well. If we exclude this capablity from our connector, this crash issue doesn't happen.
We noticed this only happens when saving illustrator file, not photoshop or indesign, and it seems that only in illustrator, when save, and the bridge has the current file folder showing, we are seeing there are twice folder refreshes, and usually it will crash after the second time. In photoshop and indesign, we don't see folder refreshes. If switch to other folder, the crash won't happen. We tested on both windows and Mac, on Mac, this seems happen less often. Another thing we noticed is in debug mode, or we have many debug logging turned on, the crash happens less often, if it is deployed with no debug logging, the crash happens almost everytime. So we are guessing it might be some synchronization problem.
Could you please advice what's the cause of this issue?
Thanks,
Katherine

Has it ever worked?
What kind of files are they and where do you save them?
Is a printer connected, set up and turned ON?
Have you already tried resetting the preferences?
Generally it's not a good idea to just save old files, because then some artwork may be automatically flattened. Illustrator will save the file to the old version file-format and if you used new features in-between, those cannot stay live in the old version file format.

CS3 hangs when saving as PDF

Having another issue today. When saving my file as Acrobat(PDF), the program just lock up. Only way out is to task manager and close down. Am running Vista Home Pro, Core2 Quad with 3gb memory. It had worked for about a week then all of a sudden, this issue. I have the complete CD3 master suite loaded and reloading/running the repair did not help. Anyone experience this or have an answer? Thanks in advance.

I'll assume you're working on a Windows system.
It's there, just off-screen.
Have you ever had a second monitor installed or worked at a different screen resolution?
Unfortunately, the PDF options dialog cannot be repositioned using normal methods (see http://forums.adobe.com/message/2465666#2465666). Position information is buried deep in the Windows registry, so resetting prefs (and, possibly, even reinstalling Illustrator) won't help.
Can you temporarily switch to a higher resolution or attach a second monitor? Once you have the dialog visible, you can pull it into your primary monitor area. It should then stay there after you restore your setup.
Creating a new Windows user account and logging in as a new user might also solve the problem.

Are these unnecessary files/folders? (When saving a premiere project)

Using Premiere Pro CS3 on Windows 7.
When saving a project, I'm always left with the actual file ( a .prproj file) and then some folders which also contain files. The folders created are called "Media Cache Files" "Adobe Premiere Pro Preview Files" "Adobe Premiere Pro Auto-Save" and "Encoded Files". Now I know the original .prproj file is NEEDED, but what about the excess stuff? I need to free up some space on my comp but don't want to ruin the project in case I need to edit it in the future. Thank you!

Well, I have multiple projects and it's unlikely I will have to recreate all of them, and very unlikely I'll have to recreate all of them at the SAME time. So can I (temporarily at least, since they'll be recreated) delete those folders? Will there be any down side besides having to wait for them to load again once I reload the project? Does this go for all 4 folders I mentioned or just some...?

Changing file type when saving doesn't work

How can I fix the problem where, if I change file type when saving, eg from tiff to jpg, the 'jpg' suffix is not appended in the save window? It remains as tiff. This has only started happening recently.

I have a G5 iSight running OSX 10.4.11 with all the latest upgrades. The problem is about a week old.
Yesterday I did a clean install of everything (not because of this problem) which I'm sure would have cleared the problem. But I was playing around with importing all my old PS and InDesign settings via copying the old preference files (and others), and the tiff/jpeg problem has reappeared. Seems to me like one of the files I copied, contains the problem. I suspect the only way out of this is to reload PS. But I was hoping it might be as simple as deleting a certain preference file.

Crash when saving photo when contact edit screen open - anyone else?

On two separate iPhones I have experienced a crash when saving a photo taken from "inside" the contacts edit screen. In both cases the photo app would capture the image and attempt to save. The screen goes black for about 5 seconds then returns to the home screen. The photo is not in the camera roll and the image container on the contact editor screen is empty.
iPhone G3, 16GB, v2.2 <--both phones tested
Sequence: Open Contacts, locate existing entry, tap "edit", tap "add photo", tap "take photo", shoot picture, tap "set photo", system shows "saving photo" pinwheel, then screen goes black.
Doesn't happen every time. One instance corrupted the mail application and applied a false name in the "from" field for many of my emails. Remedy: Reload v2.2 software and restore from backup.
Anyone else see this behavior?

I have had this same problem. As best I can recall, I have the problem every time. I've certainly updated software, reset software and reinstalled 2.2 for my phone, for other reasons. And, I've gotten another friend to duplicate the problem. My workaround is to save the contact info and then take the picture from the camera and then reopen and edit the contact and add the picture. It's just that, sometimes, I make a leap of faith and try to take a save a picture from within the contacts. It's a teeny, minor embarassment when I then have to ask a person for their info again, as the contact crashes before it's been saved.
Mostly, I'd enjoy the elegance of being able to add contacts and their photo at the same time. I know that's what is intended by Apple.
I don't intend to newly install 2.2 software, etc. with my iPhone to try and solve this problem. Just seems like a waste of time at the moment. I just want to state that it's a problem and it would be meaningful for Apple to correct this in 3.0
Life with the iPhone hasn't been perfect, but it has been awesome!
Graham

Colour shift in save for web when saving on PC and then viewing on Mac

Hey peeps, I am aware of this colour shift when saving images for web. I have a designer resizing, cropping photos, and then saving on PC. He uses PC and when he sends the photos over to me on my Mac there is a big colour shift (photos are much lighte
Could anyone please explain exactly what he needs to do in order for these photos to look the same as the originals on my computer, basically no lightness shift? Any help would be much appreciated.
Thanks
Adam

Because the WWW is based on untagged (2.2 gamma) sRGB - your genius is probably sending you untagged sRGB if they were Saved for the Web (that's how I prepare my Web color).
Your Mac display should be profiled to 2.2 gamma (you are likely at the old default 1.8 gamma now if you're seeing a lightness shift on untagged sRGB)...if you want "your color" back in Photoshop, you will need to (re)Assign the sRGB profile...

The niFPui.mxx plug-in caused an exception in the CmxAggregateItemUI::InvokeCommand function in the NIMax process. When saving *.iak file in MAX4.6

The niFPui.mxx plug-in caused an exception in the CmxAggregateItemUI::InvokeCommand function in the NIMax process. When saving *.iak file in MAX4.6
Hi There,
The subject header just about says it all. This is the first action I took with MAX - it is a fresh install. The file I wanted to save was still written and the FP seems to be working ok. However, I need to know what happened.
I can't post the whole log file due to the amount of characters allowed on this post. I can cut and paste sections if there is a specific part of the file you need. Below is the first section and last section.
Context where exception was caught:
Func:
CmxAggregateItemUI::InvokeCommand Args: plugin=niFPui.mxx Item=0107EAB1
cmdID.cmdId={4A36174B-EC0C-4D73-A23D-F15D164542DE} cmdID.index=0
Application   : C:\Program Files\National Instruments\MAX\NIMax.exe
User Name     : slaney
OS Version    : 5.1.2600 (Service Pack 3)
Exception Code: C000001E
Exception Addr: 457BC448
Return Address: 457BC448
Function Name : nNIFPServer::tFpLinearScaleRange::`vftable'
Module Name   : FieldPoint71
Parameters    : F001008E 7800FDDD C5100DFC EC0107EA
Source File   : (not available)
Return Address: 481000C3
Function Name : (not available)
Module Name   : (not available)
Parameters    : 00000000 00000000 00000000 00000000
Source File   : (not available)

Hi,
I did a research on your error message and it seems this problem was introduced with MAX 4.6. This version switched to a new error reporting mechanism and reports even errors that are which are not critical to your task.
These errors typically show up as "unexpected" and if your error falls into this category have a look to this KB for further assistance.
If it doesn't fall into this category, your could try to go back to the MAX 4.5 or 4.4.. Of course you would need to reinstall some components and might not be able to use newer drivers at all.
Let me know.
DirkW

Page shows different data when saved after few minutes

Hi,
I have a peculiar problem to describe.
I have a page which contains af:table inside af:panelCollection layout. I use a af:commandLink to drilldown to another page using setCurrentRowWithKey method.
I am able to drill down to the correct data in another page which contains data that is editable. Once after editing the page when i click save button, i am able to save the data. This is working fine.
But the problem is, once i drilled down to this edit page and edit some fields and save it after few minutes, say 5 minutes later, it is not saved. Also, the page is refreshed to bring some random record.
Can anyone let me know why is this happening and how to resolve it?
Thanks

Hi Timo,
Which jdev version?I am using jdev 11.1.1.3.0.
Is it possible that the data has changed (e.g. by an other user) after you drilled to the one record you want to change?There is a possibility that the data can be changed by other user as well. But, for the time being we have implemented for the single user environment.
When you click save after some time, do you get any error (on the screen or in the logs)?Yes. On the screen, it is displayed as "oracle.jbo.JboException: Document type mismatch (source INVOICE, type Sales)". It is a validation exception thrown at viewRowImpl level by me. But it validates the data perfectly when saved immediately after editing
Which session timeout do you have configured in your web.xml?Session-timeout is given as 240
Have you tried your use case with the HR schema?Yes. when i reproduce the situation in HR schema, it is getting saved perfectly
Regards

Print program is not getting triggered when saving the application

Hi all,
My requirement is when i save the invoice using VF01 the print program should get triggered.
The print program is not getting triggered when saving the application even when i have configured the outtype and have attached the print program.
The setting "send immediately (when saving application)" is also checked.
I need to configure it for VF01 transaction.
The error message displayed was " please maintain output device in master data".
Regards,
Umesh

Hi Umesh
Please check if you have missed any of the following:
1. Defining Access Sequence(can use existing).
2. Defining Output Condition Type(can use existing). - Assigning the Driver Program and Form in processing routine.
3. Output Determination Procedure
4. Assign Output Procedure to Billing Types
Kind Regards
Eswar

Downloads Folder No Longer Jumps Up When Saving Attachments

When saving attachments in Mail, my downloads folder on the Doc used to jump up a couple of times when I hit "save" from within an email that I received to signify that I just saved it into that folder.
However, for no rhyme or reason, the downloads folder no longer jumps up when I save attachments. The attachment still save in to that folder but I miss the pop-up action telling me that it did.
I searched the net and posts and found nothing on this quark. This is driving me nutz!
Please help!

Check in System Preferences>Dock and check off Animate opening applications and see if that doesn't do it. Not sure if that is why but it is worth a shot.

Errors when saving to SMB mounts (a thorough examination)

Several of the users I support have reported the following issue when trying to save files to the network from Photoshop. I have found several threads about this on both the Adobe forums and the Mac forums. However, in most of the threads the information provided is incomplete or does not control for enough variables. And the result is that Adobe seems to blame Apple, and Apple seems to blame Adobe. So blame aside, here is information that I hope helps Adobe solve the issue at hand.
When saving to a mounted SMB point, users report one of two errors:
Could not save <filename> because of a program error
Could not save <filename> because write access was not granted
I can replicate the issue on:
Lion 10.7.X with Photoshop CS 5
Lion 10.7.X with Photoshop CS 5.1
Snow Leopard 10.6.X with Photoshop CS 5
Snow Leopard 10.6.X with Photoshop CS 5.1
Details:
We have only seen this error in Photoshop. << Adobe has seen the same problems in several other applications >>
I have not tested out whether the issue applies to any other products in the CS suite.
At first I thought the issue might have to do with permissions, but it does not. I have reapplied permissions and the issue persists. And it affects all users, including Domain Admins, such as me, who have no R/W restrictions at any level.
The issue only occurs when Finder is in a view that shows a thumbnail/preview of the image.
Switching Finder to list mode resolves the error in all scenarios
So far I can replicate this with any file on any mount on any of our servers
It only occurs on mounted network points (ie - if I move the files locally, no errors are encountered)
For the following tests, presume the following:
Source folder: smb://example/source/folder
Target folder: smb://example/source/folder
Target sub-folder: smb://example/source/folder/sub
Here are the steps I tested:
Opened the file problem_file.psd.
A warning pops up prompting me to resolve a font vector issue, I chose "Update"
Note: that this error does not pop up for every file, just the original file I worked with, but this warning has nothing to do with the errors being received
Moved a layer so that there would be a change to save
Clicked save
Received the error: "Could not save <filename> because of a program error" << probably related to the known MacOS bug on SMB, or a known Finder/thumbnailing bug >>
The original file, problem_file.psd, is *DELETED* (very problematic) << Known MacOS bug in SMB service, Apple is working on it >>
Then I tested with multiple variations of the following to conrol for things such as layers or font issues:
To eliminate the source file being the issue, I used a .png file that I had created locally with the OS-X screen shot keyboard command. This eliminated layers and fonts as issues.
In step 2 I chose to not update the font vector issue
In step 4 I tried saving as different file types (.jpg, .png, .gif)
Prior to step 6 I flattend the image to eliminate fonts and layers. This eliminated layers and fonts as issues.
Prior to step 6 I flattened the image, duplicate the image, closed the original (without saving), and attempted to save the new duplicate. This eliminated layers and fonts as issues.
Each variation still resulted in "Could not save <filename> because of a program error" and resulted in the deletion of the source file.
Next I controlled for saving image previews:
Photoshop -> Preferences -> File Handling
Under File Saving Options -> Image Previews, I set it to "Never Save" previews
Now when I repeated the tests from aobve, I receved the error "Could not save <filename> because write access was not granted".
Next I controlled for .DS_store files:
Disabled .DS_Store file creation on remotely mounted points.
Deleted the .DS_Store file for the source folder
Verified that .ds_store files were not being created on remotely mounted points
Ran the tests above, and the issue persisted: "Could not save <filename> because write access was not granted"
Now I decided to test sub-folders:
Created a target sub-folder.
Repeated the test above, and its variations, but saving the problem_file.psd to the target sub-folder.
Still received one of the two errors, depending on the variation, but the source file is no longer deleted. This make sense because saving in another directory is really a "save as", and one would not expect safe saving (talked about more later) to affect source files in this scenario.
Sort of a Solution:
Open the file from Finder
Depending on the Finder view, Finder shows a thumnail of the image
Go back to Finder and select a different file
Make changes to the file
Save the file
No error is received
This is when I discovered that the error only occurs when Finder is in a view that shows a thumbnail/preview of the image. Further testing of Finder show that in Cover Flow the error only occurs for the selected image. For example:
Cover flow shows thumbnails/previews of files: A, B, C, D, E
Open A
In Cover Flow select file B
The thumnails of of files A, B, C, D, E are still visible
Make a change to the open file
Save the change
No error is received
This shows that Finder is treating the thumbnails/previews of unselected files different than selected files.
An Interesting Twist:
If from the last scenario with Cover Flow...
Open file A
Go back to Finder and select a different file
Then make a change and attempt to save to the target sub-folder
Receive the error "Could not save <filename>" because of a program error.
Discussion:
Photoshop does something called safe saving.
Photoshop saves the current document to a temporary file with a unique name
Photoshop deletes the original file << this is incorrect >>
Photoshop moves the temporary file to a file with the name of the original file that was deleted in step 2 << incorrect: the temp file replaces the original with an OS call to a function that is supposed to be an atomic operation >>
However, you can see that "safe saving" is misnamed, because while the original is deleted, Photoshop does not appear to be correctly ensuring that permissions exist to allow the temporary file to be ranemd or that the temporary file was renamed without error. Photoshop is either:
Not checking for the error << yes, it is >>
Checking for the permissions and not catching the error << incorrect >>
Checking for the permissions and giving an error to generic to discern the exact problem from. << also incorrect >>
Somewhere there is a conflict (perhaps a race condition) between:
Photoshop creating the temporary file
The server applying permission to the newly created temporary file
OS-X reporting the file has been created
Photoshop deleting the original file
Photoshop saving the new file
Finder updating the thumbnail of the file
As I've shown here, the problem doesn't seem to reside fully with Apple or fully with Adobe. Hopefully this post provides enough information for some clever engineer to create a fix.
My information about safe saving is from an Adobe mod on a previous thread regarding this issue << and copied incorrectly, plus added bad assumptions>>. He detailed the process and also explained that Photoshop uses OS APIs to create and delete the files during safe saving. If his details are accurate, it seems that a temporary fix would at least change the safe saving process to the following:
Photoshop saves the current document to a temporary file with a unique name
Photoshop moves the original file to a temporary backup file (original-file-name.original-extension.bak)
Photoshop moves the temporary file to a file with the name of the original file moved in step 3
Photoshop checks to make sure that the temporary file has been succesfully renamed
If the temporary file has successfully been renamed, it deletes the backup file from step 2 OR if the temporary file has failed to be renamed, the backup is returned to its original file name
The appropriate error message, if any, is displayed
A Few Sources:
http://adobe.hosted.jivesoftware.com/message/4016324
http://forums.adobe.com/thread/732422
https://discussions.apple.com/thread/3380971?start=0&tstart=0

You got several details wrong.
And it sounds like you are describing 2 known MacOS bugs:
1) The OS fails when creating or swapping files on SMB servers, and this happens more often on files that have a resource fork.
2) The Finder/QuickLook/Thumbnailing holds a file busy when it should not, causing program errors or file is busy errors.
We did as much as we could to work around these issues in Photoshop CS6 - after spending a lot of time debugging the OS issues and working with Apple.
Apple is still working on proper fixes within the OS.

Stop Safari pages from reloading when selected.

Safari in iPad is driving me crazy. Unlike tabs in Safari for Mac, the pages on the iPad seem to be hardwired to reload when you select them (I usually have several pages open and need to switch back and forth between them). And that means lots of wasted time waiting for pages to reload and many times the new page refreshes with different content so I've lost the exact page I was on. Is there a way to stop Safari from auto-reloading pages when they are selected? I'd prefer to have to manually initiate refreshes.

Your advice didn't work for me. Safari was the only app I had running, and I only had two tabs. I was attempting to post in school discussion forum. I opened a new tab, and found the link I wanted to reference. When I returned to the discussion board tab, the page reloaded and I lost everything I had typed thus far.
I have a 16GB iPad 2 with 12GB free. Only one app running and two tabs open and yet it still did this.
Any thoughts on why that might be?

Samples reloading when saving

Similar Messages

Maybe you are looking for