"Open in external sample editor" seems to be broken?

Hey all,
I'm hoping that someone can help me figure this out. I'm using Logic Pro X 10.0.7 in conjunction with Adobe Audition CS6. This problem seems to happen intermittently, and on some of my machines, but not others. I've also witnessed it on others' machines as well.
When I try to open a region of audio in the external sample editor (For which I've set up Adobe Audtion CS6 to do destructive edits), I can manage to get the file to open correctly in Audition. HOWEVER, when I make my edits in audition and try to SAVE the file in Audition to send it back to Logic Pro X, I get an error message that the file cannot be saved because it is "in use by another application". It's almost as if Logic doesn't release the file to the external sample editor in order for it to be overwritten, and updated.
When I switch back to Logic, after I get the error message, Logic "refreshes" the waveform information, but it's still unchanged, because the external sample editor can't save the changes that I've made to the region. Can anyone relate? Offer me useful tips on how to fix this? Is it a bad configuration on my end, or just a bug in Logic?
Thanks,
Steve

Ok so I think I might have figured this out on my own... Apparently, if you highlight a region, and the region is open in Logic's Editor window, while you're trying to edit the region with an external editor like Audition, it will throw the "file is in use by another application" error, when you try to save the changes you've made in the external editor. I found that if I close the "Editor" window in Logic, before trying to open the region in Audition, Audition is then able to save the changes to the file.
Derp.

Similar Messages

  • External sample editor

    how do I open an audio file from logic in an external sample editor? I know you can do it, but can't find in the manual how you do this or how to set what the default sample editor is when you open the file in the external editor
    Thanks

    There is a key command Search:
    "external"
    in the KC window. Assign it. 1st time you use it you will gett a prompt to select the app.
    Cheers,, J

  • External Sample Editor Broken

    "To transfer audio edited in the external sample editor back to Logic Pro
    Save the file in the external sample editor, then switch back to Logic Pro.
    The edited audio will be updated in the Audio Bin and Arrange area, if regions based on the audio file are in use. "
    This USED to be true but no longer
    I'm using Melodyne Single Track and instead of updating the relevant file in the arrange window I'm having to 'reimport' the tuned file.

    Ok so I think I might have figured this out on my own... Apparently, if you highlight a region, and the region is open in Logic's Editor window, while you're trying to edit the region with an external editor like Audition, it will throw the "file is in use by another application" error, when you try to save the changes you've made in the external editor. I found that if I close the "Editor" window in Logic, before trying to open the region in Audition, Audition is then able to save the changes to the file.
    Derp.

  • How to unset External Sample Editor?

    How do I unset External Sample Editor (and switch back to logics default sample editor)...?????

    Assign it in the preferences, set a location in your apps folder, STP is selecetd by default. Hit shift+w with an Audio region selected to open the audio in the assigned app.

  • Trying to get 'External Sample Editor' working.

    Hello,
    I cannot find anything in the manual about changing preferences as to what editor you are using. I found the key command and tried to get DP as my external but once I saw that wasn't going to work I couldn't find any possible way to change my choice of editor. There seems to be no preference or menu that would let you pick a new one. Is my only choice to complete trash prefs and rebuild everything? Not a huge ordeal but tedious none the less.
    Chris

    It's a lot easier than that.
    On my system there is an alias :
    ~/Library/Preferences/Logic/External Sample Editor
    You could try removing the file from it's location or going about the 'select new original method.

  • Open file in sample editor

    Hey forum,
    This is probably a super noob question, but I have a clip of a 7 bar guitar line that I want to open in the sample editor so I can reverse it. I know the default is to double-click it, but it has the arrow on the left side and when I double click it, it pulls down the only take that I did of that section (instead of opening in sample editor). I want to know how to do this for other clips with more than one take as well.
    So basically, how do I open a snippet in sample editor without double clicking on it?
    Thanks,
    Daniel

    Hey Jorge.
    Thanks for the suggestion. I've actually had to re-install the bug ridden 8.0.0 version to get it to work. Never thought i'd be saying that
    I haven't updated it yet as i need to get some work done before i waste another day trying to sort out mysterious errors.
    Thanks anyway
    Rowan

  • STPro as Logics sample editor.

    I like to use STPro as Logics sample editor in certain cases. However, one thing has me stumped.
    Does anyone know how to get STPro to show up the sample in beats, when I (launch external sample editor' in LogicPro?
    I have the preferences set to show 'Beats' in new documents, but it always defaults to min:secs....
    Anyone have any ideas...? I would love to be able to edit accurately in beat mode.

    The beat option only seems to be available from the multi-track vantage point. For instance you can't add a beat marker in the sample editor - the tool is greyed out - and if you've set some b-markers in the multi-track view, they're not visible any longer in the editor view. And yes, this drastically limits the usefulness of SoundTrack when setting up audio loops for example, and, of course, this is not discussed in the manual.

  • Sample Editor (More color please!)

    The 'Sample editor' window in Logic has arguably always been it's weak spot. Unfortunately in Logic 8, it seems to have taken a further step back visually, whilst functionally it's feature set has remained stagnant for some time.
    As a 'Pro' application, I would expect Logic's sample editor to compete with the likes of Peak, Recycle, Tools etc. All of these editors share great resolution, great visuals (some color!) and some excellent tools.
    I'm hoping future updates (?!!) will address this & the various other issues Logic 8 still has - voice your opinions if you feel the same way...

    I thought of an even more simple solution to avoid using Logic's sample editor (Logic programmers - hope you're listening!!) :
    If you were able to re-size an audio track in the arrange window to fit the whole screen, you would dispense of the need to open a separate sample editor window (or for that matter, a 3rd party Sample editor).
    You could even incorporate an additional menu into the arrange page for the destructive & non-destructive functions of the Sample editor (Time-Machine etc.)
    The waveforms are (apparently) sample accurate in the arrange window, so I see no reason why this couldn't work in practice. Certainly it would look better (more colourful), and also offer more continuity between the file, the arrangement, & the time-line...
    Jus' a thought!

  • Strangeness in Sample Editor / Arrange

    I have an audio file (aif) in my bin. I drag it to the arrange page. It plays fine. I can make edits, create regions, everything one could want. I double click on the region and the Sample Editor opens but with the wrong file - something I had open before. So ok, I figure I'm a reasonable guy, I can adjust, adapt, make changes - so I delete the wrong file from my bin and try again. I click on the aif in the arrange window - the correct file - and the Sample Editor opens and says - Nothing to Display.
    I tried moving it to a different track. Still no good. I'd sure like to normalize this file but it won't open in the Sample Editor.
    Any ideas, ye comrades of the logic discussion?
    Cheers,
    MJ

    Hate that bug! ...or should I say those bug variations:
    wrong region displayed
    "nothing to display" message
    wacky timeline displayed
    What works for me:
    1. Quickly toggle the sample editor in Arrange open/closed/open a few times.
    2. Quickly change screensets a few times.
    3. Open the region in the "big" sample editor (Window>Sample Editor) then switch back to the "small" one in Arrange. (Or stay in the big one if it fixed it)
    4. Open a new Arrange window (Window>Arrange) and close the old Arrange window then open the sample editor in your new Arrange window.
    Don't close the wacky Arrange window until you've opened a new one or Logic will think you want to quit.
    No rhyme or reason as to which method may work for any of the bug variations
    See if any of these help.

  • Sample Editor - "sample accuracy" is a matter of opinion...

    In trying to figure out exactly what was going on with start/anchor/end points in the Sample Editor, I discovered the basic relationship between the Sample Editor and Arrange window... thought this might be useful to others.
    Basically, it's a matter of opinion whether or not the Sample Editor truly lets you make sample-accurate edits. By itself, the Sample Editor does let you move the start/anchor/end points to any sample value, and Logic will save and remember these settings, accurate to the sample.
    But, you can't rely on those sample-accurate edits when you place the region in the Arrange window. Logic always "remembers" them, but the results in the Arrange window can get sloppy.
    Bottom line: Logic forces all region start and end boundaries to rounded tick values. So, if you go into the Sample Editor and adjust the start/anchor/end by samples, it's impossible for all of these edits to get consistently represented in the Arrange window. To get that, Logic would have to allow the region start and end to be between ticks, and it won't allow that--something has to give.
    Here's what actually happens: you set the anchor with sample accuracy in the Sample Editor, then you place the region in the Arrange to be at exactly bar 5 (5 1 1 1 1), for instance. You'd expect the anchor to be at exactly bar 5, but it isn't... it's close, but what Logic actually does is line up the region by the region start marker. The region start marker never moves relative to the region's audio: when you try to put the anchor at bar 5, Logic actually slides the region to the nearest tick value--the start marker goes precisely on a tick, and the anchor ends up slightly ahead or behind the bar 5 marker.
    Now, this behavior isn't so bad in most cases--can you really hear a few samples difference between exactly where you put the anchor, and exactly where it ends up ? Almost certainly not, although I know an obsessive-compulsive post editor who isn't going to be happy when I tell him this...
    But the dark side of this behavior occurs with the region end point. Again, Logic never moves the region start relative to the region's audio--it shifts around the anchor to make the region start fall on a rounded tick. But what about the region end ? Unfortunately, even though the Sample Editor will let you put the region end anywhere you want it, and it will save the region/file that way, that region end will get shifted around to fall on the nearest tick in the Arrange.
    So, you cut a sample precisely in the Sample Editor, make sure the start and end fall on zero crossings, then you place the anchor at a transient point and spot the region in the Arrange. What actually happens is that
    1) your start region edit gets preserved
    2) the anchor gets put somewhere fairly close to the actual spot point
    3) the region end gets rounded to the nearest tick
    #1 is great, #2 probably OK, but #3 can be a problem. Your region may sound great in the Sample Editor, but it may click on the back end in the Arrange... unless the region's start and end happen by luck to be exact tick multiples of each other, the region end will get moved by a few samples, which may cause a glitch in playback.
    My suggestions:
    1) Be aware that anchor's aren't placed with sample-accuracy. You probably will never care, but it's good to know.
    2) Leave a tick or two of silence at the end of a region. If you use a Sample Editor to trim the region end precisely to a zero crossing, you'll probably get bitten when you put this region in the Arrange. Either do a destructive fade in the Sample Editor, or use the fade tool in the Arrange. (DAWs are going to have to take a few more steps forward before we can stop being superstitious about fading the start and end of every single region, even when edits are at zero-crossings. If the work is important, crossfade everything!)
    3) Apple... PLEASE, PLEASE, PLEASE revamp the Arrange window to be sample-accurate. There are so many kludgy little issues that would go away if the base timescale could be samples. Not to mention that almost every other DAW has this...
    James
    [email protected]
    Dual 1.25 G4   Mac OS X (10.4.8)  

    iSchwartz,
    Serves me right for not doing a listening test.
    Turns out that you're entirely right about what actually gets played back. I did a few tests by aligning two regions, phase-canceling them, then moving around the start, end, and anchor points.
    Sure enough, what I HEARD corresponded exactly to what I saw in the Sample Editor.
    But the Arrangement doesn't show things that way--I was looking instead of listening, and in these cases, the Arrangement can show things that are contrary to what gets played back.
    When you move that end marker to the right in the last step of your test, I'll bet the Arrange window doesn't show the little glitch that you're now able to hear. And if you take an Arrangement region that ends with a little glitch, you can remove it by sliding the region end a sample to the left in the Sample Editor, but you'll still SEE the glitch in the Arrange window. Looks like the Arrangement plays back exactly what you've got in the Sample Editor, but it DISPLAYS things rounded to the nearest tick.
    And this gets more confusing when you move around the anchor point. Trim one of your clicks so the anchor and the region start are both precisely on the transient, and move that region to a bar marker. Then look at the Arrange window at maximum zoom--you'll see exactly what you'd expect.
    But... now... go back to the Sample Editor and try moving the anchor a few samples to the right. When you go back to the Arrange window, nothing has changed--the transient still looks like it's precisely on the bar marker, while the Sample Editor shows that it's not.
    And it gets weirder... go back to the Sample Editor, and move the region start a few samples to the left. Now, when you go back to the Arrange window, what you see is exactly the opposite of what you'd expect. You'd expect the anchor to have stayed put, and the region start should have moved. Instead, the region start is still at the bar marker, but the audio inside the region appears to have moved.
    This is why I was so confused about what was going on. You're completely right about the playback--I did some tests, and all this strange behavior I'm seeing in the Arrange window, none of it makes it to playback. When the Arrange window and Sample Editor disagree, the Sample Editor seems to be ALWAYS right.
    But when you start doing sample-accurate editing with the Sample Editor, the Arrange window no longer reflects reality--region start and end markers appear to be on at rounded ticks, even though they're not, and audio will appear to be displaced within regions, even though it's actually lined up perfectly by the anchor.
    Just goes back to point #3... it's kludgy crap in the Arrangement resulting from the tick timebase. Logic 8 ?
    James
    [email protected]
    Dual 1.25 G4   Mac OS X (10.4.8)  

  • Open in external editor -- original color space workaround

    I was frustrated--like other's whose posts I've read--by the fact that when opening files (tiff, jpeg, psd) in an external editor they are all converted to the Adobe 1998 rgb space.
    I am working around this comfortably and by using some Automator actions that I got from Ben Long's Complete Digital Photography site: http://www.completedigitalphotography.com/?p=414#more-414
    In my Pictures folder I have an Auto Processing subfolder with Photoshop droplets and lots of 'hot folders' tied to Applescript folder actions. I made two new folders: OPEN in Photoshop & IMPORT to Aperture
    The Open in Photoshop folder has attached from Automator the following actions from the default Finder suite: Open Finder Items and Move to Trash.
    The Open action is self explanitory, the next step of moving the recently opened file to the trash guarantees that I can't save to the source file. This forces Photoshop to do a Save As even if I hit command + S. The Save As prompts me for a location and I choose the Import to Aperture folder.
    The IMPORT to Aperture folder has attached the Import Photos action from Ben Long's Aperture suite. By selecting the Delete the Source Images After Importing Them option and the Show Action When Run option I get a prompt asking what project to add the new files to and the old files are deleted from my hot folder after the import.
    This isn't a perfect round trip solution because I still end up with two copies of the image in Aperture--even if I was just opening the source image to tweak an adjustment layer. I might create an Applescript that would prompt the user and delete the precvious copy of the image if desired.
    Like many of you I was feeling blue yesterday about rumors of changes in the Aperture team at Adobe. Blue not because I beleive Aperture's going away, instead because I expect if this rumor is true that we will see some delays in the short term while the new team gets up to speed.
    While I am waiting for that to happen I intend to use this discussion site to find creative workarounds for Aperture's current limitations and share them as widely as possible. Many of you are already doing the same.
    Thanks!

    Yes you could do that.
    I was part of the alpha/beta test group for Adobe CS2. Most of my work was with scripting and automation, especially for Bridge. I did have a very good dialog with Bruce Fraser, Seth Resnick and other testers whose opinions are as good as fact in my book.
    The consensus was that most digital cameras--certainly the pro models--had a color gamut substantially larger than Adobe RGB (1998). Note that ACR give the option of developing an image into sRGB, Adobe RGB, Color Match RGB, or Pro Photo RGB; 8-bit or 16-bit. That's the way I want it in Aperture.
    If you use the perceptial rendering intent (this is almost certainly what Aperture is using as its undisclosed default setting) then you will compress the wider gamut of the camera into the smaller Adobe RGB (1998) gamut. If in Photoshop you used the Convert to profile command and choose the perceptial rendering you would probably expand the color gamut back out a little bit. Why bother? Aperture really should have options for open in external editor like the very good export version settings.
    I have in my Aperture library a bunch of 16-bit grayscale scans and some CYMK files that seem to be working fine with the workflow above and Automator actions. (Lab files won't import.) I wouldn't want to go through the convert to Adobe RGB (1998) and reconvert to proper space with these files. My workflow is letting my store these files in Aperture and still edit in native color spaces in Photoshop with minimal effort for a round trip. I like it.
    P.S. I said in my original post that it would be easy to write an Applscript to delete the orignial file in Aperture when reimporting a slightly modified Photoshop version. It may be possible but its not easy in the current version which only has a bare skeleton of Applescript functionality.

  • "Open in external editor" difference in 1.5?

    In 1.1.2 I used to open a file in PS2, make adjustments, add layers, etc. and save back to Aperture. Occasionally, I would then straighten or crop in Aperture, and then re-open in PS2 for further edits at a later time. If I remember correctly, when I did this layers would still be preserved when I opened the file in PS2.
    However, when I go through the same steps in 1.5, the file is flattened when it is opened in PS2 that second time (after straightening or croppping or whatever in Aperture). Could someone check this on their system and let me know if they see the same behavior (I've been having strange issues with 1.5 that others don't seem to have, so I want to be sure it's not my computer).
    Also, is anyone out there still running 1.1.2 that could check the same thing? I may be losing my mind, but I'm almost certain that layers were preserved all the way through.
    Thanks,
    Chris

    Incorrect. They shouldn't flatten PSD files -- in fact with "open in external editor" they never have -- not even in the 1.0 release.
    The "flatten" issue was with 1.0 when you imported PSD files into Aperture... and this was because of Aperture's stated goal of "never touching a master file." This (somewhat annoying) behavior was changed in 1.1. But no version, to my knowledge, flattens PSDs that have been created in Photoshop with "open in external editor."
    I just tried this with 1.5, and I am able to see and edit the layers I created on a PSD file that I previously created via "edit in external editor" which was Photoshop. So that works fine in 1.5, as it did in 1.1.2 and previous version.
    However, I have noticed a couple weird things:
    1) It's creating a third version when I do this, from the original master
    2) Deleting any version created via this manner pops up a dialog "do you want to delete this master and all versions?" which is disconcerting as I just want to delete the extra version, not any versions. It works as expected, but the dialog could use some work I think.

  • No new version from Open With External Editor?

    Is there a way to not create a new version every time I use "Open with External Editor"?
    If I want to open an image in PS, just opening it creates a new version in Aperture, even if I don't make any adjustments to the image in PS.
    I've deselected "Create new versions when making adjustments" in the preferences.
    Thanks for anyone's insight!

    Not sure this will help, but I noticed this problem as well a while ago, but have since developed a work around...
    All my files start off as RAW. When I use "Open in External Editor", Aperture generates a new version with a bulls eye target (this is my C2 version). If manipulate this image in CS and save it when I close, it remains as a bullseye target (look at the lower right corner in full screen). If I reopen this specific image, no new file will be generated. If I manipulate it in Aperture, a new file will be generated (but without the bullseye target) and if I then use "Open in External Editor" another new file will be generated.
    I have never checked to see what happens with a primary PSD file imported. And I am sure the meaning the bullseye target is in the manual someplace.
    So my workflow is RAW file-->all my desired aperture adjustments-->open in external editor for final clean up and modification. I end up with my original RAW file (Aperture modified and restorable to original by removing all selections) and one CS2 file. If I want several version off of my first CS2 file, I duplicate version of the CS2 file, and the open the bullseyed version NOT the new duplicate version image.
    Hope this helps...i know is seems wierd, but it works
    steven

  • "Open with External Editor" command bug?

    Seems to be a bug with "open with external editor" command. If I try it just after Aperture has been opened, it usually works (sometimes not). And then after a couple of photos being edited in photoshop, it sometimes stops working. When I try it, it simply gives me SBBOD for a few seconds (which it does when it's working as well), and then nothing happens. No new master created in Aperture, and nothing in Photoshop. If I restart the program, it usually takes care of the problem, and it will work again for a bit. Sometimes restarting the program doesn't even work, and I have to reboot. Very strange.
    Any one else getting this? Any ideas?
    I'm using 1.1.1 and Photoshop CS2.
    powerbook G4 1.5 Ghz   Mac OS X (10.4.6)   2 GB RAM, ATI Radeon 9700 (64MB VRAM), 80 GB ATA HD (5400rpm)

    Anyone out there? No one else experiencig this "bug"?
    Help, please.

  • I tried transferring my iphoto library from my old macbook onto my new macbook pro (via external hard drive), but when i open the new iphoto, it seems to have transferred ALL images ever used on my old macbook. so i tried to just del

    i tried transferring my iphoto library from my old macbook onto my new macbook pro (via external hard drive), but when i open the new iphoto, it seems to have transferred ALL images ever used on my old macbook. so i tried to just delete all those images so i could try a different approach to transferring, but the new iphoto won't let me do anything and every time i try to delete anything it crashes (since the image amount is so high).  please help!!
    MacBook Pro, OS X Mountain Lion (10.8.2), iphoto '11, version 9.4.2

    To move an iPhoto Library to a new machine:
    Link the two Macs together: there are several ways to do this: Wireless Network,Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
    But however you do choose to link the two machines...
    Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
    Then launch iPhoto. That's it.
    This moves photos, events, albums, books, keywords, slideshows and everything else.

Maybe you are looking for