Logic pro 8 & windows (.iso) files

Hi everybody,
My name is Franck and I'm a Logic audio user since 1999.
I made a lot of backups from 1999 to 2005 of logic songs saved under Windows (98 & XP).
I was able to open and convert this files to the Mac Os format with logic express 7, but since I upgraded to Logic pro 8 it isn't possible anymore.
The soft says I have to install the 7 version, but when I try to install the 7 version I have a message "there is an earlyer version of this soft on your computer, do you want to replace it, and then only two buttons : "replace" or "Cancel"! I mean is it impossible to install the 7 version in "parralel" to the 8 version? Is there any plug in or add on who can convert this windows files with the 8 version? Is there any good reason for Logic 8 not opening this files anymore???
I really would like to use my logic backups when ever I want (or need like today!), without having to convert all of them. This is one of the reason I switched to mac os 5 years ago. Thanks for your help!

Finally I made a clone of my Imac on a external Hard drive with Carbon Copy Cloner (cause I didn't have another machine!). I installed LE7 over LP8 on the clone after restarting on it.I copied LE7 to my applications folder on my Imac.
It seems to be OK. I opened a windows file .iso with LE7 and saved it under a new name after conversion in 5 format. Than I was able to open it with LP8 on the same computer!
Better than nothing, I mean it would be much easyier if LP8 could open & convert directly this windows files. I can't understand why they removed this function in L8! Is that progress???

Similar Messages

Ich nutze Logic Pro um Midi-Files zu bearbeiten. Unbearbeitete Midi-Files werden von Qmidi mit deutschen Buchstaben ä, ö, ü, ß wiedergegeben. Sobald ich das midi-file mit logic-Pro bearbeitet habe werden die Buchstaben nicht korrekt wiedergegeben

Ich nutze Logic Pro um Midi-Files zu bearbeiten. Unbearbeitete Midi-Files werden von Qmidi mit deutschen Buchstaben ä, ö, ü, ß wiedergegeben. Sobald ich das midi-file mit logic-Pro bearbeitet habe werden die Buchstaben nicht korrekt wiedergegeben. Dies passiert auch, wenn ich keine Änderungen im Midi-File vorgenommen habe. Bei Qmidi kann ich die Schriftarten / Einstellung " Western ( ISO Latin 1 ) " eingeben und diese Buchstaben werden korrekt erkannt. Es muss daran liegen, was Logic Pro aus dem Midi-File macht.
vielen Dank für Eure Hilfe im voraus
I use Logic Pro to edit midi files. Unprocessed Midi-Files reproduced from the programm "Qmidi" with German letters ä, ö, ü ß. Once I have edited the midi-file with logic-Pro are not correctly play back the letters. This also happens when I have not made any changes in the midi file. In Qmidi I can the font / setting "Western (ISO Latin 1)" and enter these characters are correctly recognized. It must be because what makes Logic Pro from the midi file.
Thank you for your help in advance

That's clearly a bug. Please send this to Apple using their feedback form:
http://www.apple.com/feedback/logic-pro.html
Best,
DaCaptain

Recovering Logic Pro 8 Project files

I have been trying to recover my accidentally deleted Logic Pro 8 project files for over a week now I have been using Data Rescue II and File Salvage all I can find is my old Logic 7 Project files and some audio files. How do I find Logic Pro 8 project files?
I rang Apple today and the 'Expert' had no clue of the software I was using to recover deleted files or how to go about finding them, Please could anyone help. I have barely used the computer since as I don't want it to overwrite the trashed files.
I have realised that Logic no longer uses the .lso extension and is a bundled folder when I go show package contents there is a folder and within this folder there are two files when I search all of these file sin the data recovery software they only retrieve the files that have not been deleted which is not helpful.
Please help!

I was waiting for some ******* to respond to my post with a lecturing. Thanks for not disappointing me Christian.
I back up all 4 of my internal drives several times a day with SuperDuper. I also back up off site with Carbonite.com It's saved me from hard drive failure once. This is the first time in over a decade that I cannot find a file that I suspect I deleted by accident. That's a pretty good track record. I'm doing the best that I can with what I have.
Now here's a strategy for you to keep you "on the clever side" Christian: If you don't have a solution to a problem posted on here, don't bother posting your judgmental and arrogant ******** without knowing the entire situation of the person who's asking for help.

Logic Pro X: Audio file not found?

I have Logic Pro X, and this problem has never occurred before but...
I was mixing one of my songs and everything was perfect, then I made sure to save it.
As I reopened literally 10 seconds later (not sure why I even closed it) it was showing me a message that said "Audio file not found"
At least 12 audio files went missing out of nowhere. It's only the files recorded from Logic that are not found.
I tried to locate them through my Finder but I don't know where my audio files are stored onto my macbook, and it doesn't seem to be in an easily accessible place.
It's just weird because they were all fine just before I closed Logic, then they disappeared.
I checked the audio bin in Logic and they seem to be there but they seem corrupted.
If anyone can help, or at least show me where audio files are stored on your mac from recording through Logic, that may help.
Thank you.

To clarify:
Logic Pro X
I have also experienced this issue as a result of having recording delay set other than zero, and rectified it by returning to 0.
Otherwise,
[Command 8] or
Window > Open Project Audio, select audio files that appear flatline, click 'Audio File' menu at top left, click 'Refresh Overview(s)'.
No way I know of to auto-enable this.

Logic Pro 7 song files to Cubase (PC)

I just got Logic Pro 7. I had been recording with Garageband 3. Since I've purchased Logic Pro though, I've been importing all the files into Logic. Now here's my problem -
I need to send the tracks to an engineer in Las Vegas (I'm in St. Louis) so that our drummer (who is also in Vegas) can be tracked. The issue is that the engineer uses Cubase on a Windows PC. Please tell me there's a way to export the songs out of Logic without manually exporting each single track individually (which would take days)! I need for him to be able to open the songs in Cubase and edit or mix them as he goes.
He will do the final mix on that PC, so once he has the files in Cubase, they will likely stay there. Any help or suggestion is much appreciated!
peace,
rick
Power Mac G5 (Dual 2 Ghz), Power Mac G4, Powerbook G4 Mac OS X (10.4.5)

Ask the Video guy what format he wants-it'll probably be at 48k but it is of several different types.

How do I make a bootable cd from the windows .iso file

I am trying to install windows xp on my iMac. My univeristy gives me free copy of XP but I have to download the .iso file. I tried burning the .iso file to a cd but bootcamp says it can not recognize the cd for installation. How can a make a bootable copy of the windows xp .iso file so that I can install it on my iMac.

You used Disk Utility I take it?
http://en.wikipedia.org/wiki/ISO-9660
http://www.ezbsystems.com/ultraiso/
This is for creating a custom Vista SP1 EFI-enabled DVD:
http://www.jowie.com/post/2008/02/Select-CD-ROM-Boot-Type--prompt-while-trying-t o-boot-from-Vista-x64-DVD-burnt-from-iso-file.aspx

Logic pro 8 missing files

Hey all,
Seems like a lot of knowledge floating around these forums. How grateful I am to have access to such a great community! I have a quick question:
I just migrated from a macbook pro to an iMac. When setting up, using my external drive, my iMac attempted to migrate (hopefully I'm not using that term incorrectly) all my old apps over - including Logic 8. Problem is, some stuff is missing. So far, the only thing I've noticed (it's only been about a week, I haven't been using the program extensively) is that some instruments etc cannot be located. To try and solve this, I dragged and dropped all the jam packs I have from the external drive onto my hard disk, and even put them in Logic's folder. However, the program is still unable to locate these instruments, and even when the external drive is on, it doesn't load the instrument - it just indicates that the instrument is somewhere on the external drive.
I figured tomorrow I would just drag drop logic (my iMac has hardly much else on it) to the recycle bin and reinstall from scratch. However, I'm not sure if this is necessary. If I put the disks in, will it make duplicates (thereby wasting storage space) or would it selectively install whatever isn't already found on my iMac? I've seen an extensive list of files I would need to delete, and can do this (provided they all made it onto my iMac.
I was just wondering what would be the, obviously, quickest way to remedy these missing files. I'm still really inexperienced, as this is only my second mac computer, and the first one I've tried to bring old files/programs on to from my old computer.
Thanks for any suggestions!

Since you have the Logic Pro DVD's, I would just reinstall it on your iMac.However, if you want to see if there is another option that would work with Logic Pro, you might post your question in the Logic Pro dicussion here.

Recovering Deleted Logic Pro 8 Project files with .logic extension

I've been trying to recover a project file I accidentally deleted from Logic Pro 8 for a few days now. I'm using FileSalvage and all that comes up are the older Logic files with the .lso extension - some from as far back as 9 months ago. But no files with the .logic extension have appeared.
The file I'm looking for was dragged into my trash on November 2 from my media drive (internal HDD #2) and I have barely used that drive since because I don't want to fragment the deleted file.
I realize that the new .logic files are bundles and when I show package contents, there are 2 files that show up.
Any ideas on how I can recover this file?

I was waiting for some ******* to respond to my post with a lecturing. Thanks for not disappointing me Christian.
I back up all 4 of my internal drives several times a day with SuperDuper. I also back up off site with Carbonite.com It's saved me from hard drive failure once. This is the first time in over a decade that I cannot find a file that I suspect I deleted by accident. That's a pretty good track record. I'm doing the best that I can with what I have.
Now here's a strategy for you to keep you "on the clever side" Christian: If you don't have a solution to a problem posted on here, don't bother posting your judgmental and arrogant ******** without knowing the entire situation of the person who's asking for help.

How to install Logic Pro X additional files to a secondary hard drive?

Hi all, I have tried and failed to install additional Logic Pro X data to my second hard drive. The SSD that OS X runs through is almost full and I don't have enough space for the files to stay there.
I have tried to use the 'Symbolic Link' solution, but to no avail as it continues to install the software on my SSD! I can tell, because after installing the files I lose a big chunk of storage on the SSD.
Please help! Is there an alternate solution, am I doing it wrong?

Sorry! I did select Logic Pro... Wonder why that happened.... Thanks

Logic Pro missing audio files and instrument patches

Good morning
Last week I downloaded Logic Pro version 9.1.8 from the App store.
I have downloaded all the additional copntent listed
I am running a brand new IMAC with OSX10.8.2
The instrument choices and patches show up.....
However many of the audio files and instrument patches are missing.
Prerecorded songs can be loaded but...
When I open a logic song (recorded on my prior IMAC) and recorded within Logic Audio 9.0.0, I get consistent messages such as
EXS24 Instrument "Classical piano.exs" Audio file "BDorfer f O d#.aif not found.
This happens with most most of the patches.
Many thanks for your help

The only things missing from the App Store version compared to the Boxed set are the loops and samples that came as part of Soundtrack Pro and those are no longer available..
However, the sample you mentioned is actually part of the GarageBand Library.... Did you install GB too?
If you did so... then... three things..
First, try using FindAnyFile
http://apps.tempel.org/FindAnyFile/
(Download the version on that webpage and not the App Store version)
..and do a search for BDorfer.. (Just that and nothing else) and see if it finds your missing file.
If it doesn't find it.., install GB and try again... (You may need to rebuild Spotlight afterwards as described below)
If it does find it then..
Two.. rebuild GB's Loop index as this fixes all kinds of weird things in Logic... (and yes, i know its loops not samples but it's worth trying based on past experience fixing these kinds of issues)
http://support.apple.com/kb/HT2443?viewlocale=en_US&locale=en_US
and... if that doesn't work..
Three... Have you reindexed Spotlight?
http://osxdaily.com/2012/01/17/rebuild-spotlight-index/
Logic uses Spotlight to find everything it needs.. so that is worth a try too if everything else fails..

Logic Pro trouble shoot files provided by apple

I apologize in advance if someone has already posted this link but it is well worth taking a look at.
http://search.info.apple.com/?q=logicpro+&search=Search&lr=lang_en&search=Go&type=ktech+ORklearn

You may need to rebuild the loops index.
Open up Logic and display the Loops Browser
Open up FInder and locate the folder containing the loops as you describe
Drag the loops folders onto the Loops Browser
That will rebuild the index and all should be well.
Pete

Bootcamp (iMac 27-inch, Mid 2011) Windows 7 (32-bit) or Windows 8.1 via iso file?

Hey peeps,
I'm trying to bootcamp my iMac (27-inch, Mid 2011) from an iso file downloaded via Microsoft (DreamSparks).
The only versions of Windows DreamSparks offers are Windows 7 (32-Bit) and Windows 8.1, both of these are .iso files.
I've tried putting both versions onto both a USB and Rewritable DVD, but my iMac doesn't detect the install disk anywhere when running bootcamp.
Any idea how this could be fixed?
I read somewhere that my iMac doesn't support Windows 8+ and will only support 64-bit versions on Windows, any clarification on these two areas would be great.
Thanks for your time!
Charkizard

Your Dreamspark account should have an option for both Win 7 Pro 32 and 64 bit. If not, you can download the 64 bit ISO at http://msft.digitalrivercontent.net/win/X17-24281.iso The serial numbers provided by Dreamspark will work on both the 32 and 64 bit.
Once you have downloaded the ISO on your Mac you use Boot Camp Assistant to create a USB install disk that has both the installer and the bootcamp drivers. You will need an 8GB flash drive to do this.
Open up Boot camp assistant, there is an option to create a Windows install disk. When you use this option, it *** for the location of the Windows ISO file, once you select the ISO that you want to use just follow the prompts. Boot Camp Assistant will download the latest Boot camp Drivers, and then will create a USB drive with the Windows installer that includes all of the Apple Specific drivers needed by your iMac.
Just note that this process can take over an hour to finish. But once it does, you can then use Boot Camp Assistant to partition your iMacs drive and then install Windows using the Flash drive that you created.

Checksum for windows.ISO created by MS mediacreationtool.exe

Primary question - What is the sha1 {&/or Md5} checksum for the "windows.ISO" file downloaded when using the MS supplied "mediacreationtools.exe"? I specifically want the checksum for the ISO resulting from selecting
Language: English {UK} Edition: Windows 8.1 Architecture: 64-bit {x64}
Situation - I am wanting to do a clean install of win 8.1 {build9600} onto a laptop which has a barely usable build 9600 already installed, damaged recovery partitions, and no OEM recovery media.
I have downloaded and used the Microsoft supplied tool 'mediacreationtool.exe' which subsequently downloads a file called 'Windows.iso'. I wish to verify the integrity of that ISO file to ensure it arrived correctly. Obviously I want to do that
**before** I repartition the HD and attempt to re-install OS rather than simply cross my fingers and hope all goes well.
I have searched for a checksum or other method to ensure the ISO is 'good' yet could not find one.
I downloaded a second copy of the same type of ISO using the same method with the same tool. I had hoped for the same checksum on both ISOs as a means of verification.
If the 'media creation tool' uses an 'automatic' checksumming/correction as part of the download process to ensure the integrity of the downloaded ISO then it appears to be untrustworthy given that the two ISOs it gave me, which should have
been the same, unfortunately arrived with different checksums.
It is obviously ludicrous to continue downloading >3GB files until I find a pair whose checksum match. I am frustrated by this situation.
I presume Microsoftland employs at least a few brainiacs who are capable of understanding what checksums are and how they can be useful. Consequently I am astounded that MS does not publish the checksums for ISOs officially obtained from MS, using
an official MS tool. Can anyone shed some light on why this situation exists and offer a useful remedy?

Thankyou Shaon for your continued attention and help.
I had ignorantly presumed the MCTool was in effect a download manager which downloaded/checked the entire ISO rather than 'constructed' it. Your advice that it is not possible to gain a common checksum of any ISO created by the tool obviously answers
my primary question.
Yet the intent behind that initial question was to gain an understanding of how I can verify the integrity of the install media, downloaded using official MS method, which I intend to use as the basis for building the winOS. In this respect I am
hardly any closer to my goal of being able to verify/trust the media to perform a "clean install".
I mean "clean" in both senses of the word. The concept of SISO pre-dates Microsoft. The fact that the ISO doesn't contain enough s##t to stop it booting, or even setting up an OS, does not prove that the ISO or the OS constructed from
it does not in fact contain s##t which might unduly complicate processes down the line.
My enquiry is not merely an academic one.
I have been asked to fix an Acer laptop for a boy who for a few short months proudly enjoyed his new rig. The laptop came with win 8.0 pre-installed and all the devices worked as expected. He was a good boy and followed recommended procedure by
allowing automatic updates.
MS effectively coerced this kid into "upgrading" to build 9600 when they unexpectedly removed support for full updates on the breed of OS he was using. MS deceived him into readily accepting the installation of "windows 8.1 update
1" by strongly implying that it was, well... you can read, merely an "update" - not even big enough for an 8.2 moniker.
"Win 9" broke the kid's heart. He was suddenly the kid with the gimpy computer - no webcam, a wild trackpad and a schizophrenic network connection. Whilst still under warranty, Acer performed their magic and "clean installed"
build 9600, leaving the win8.0 recovery and original 'push button' partitions in place. This gave the boy an impressive 6 partitions but didn't actually fix any of his problems.
Acer then abandoned this kid by gutlessly feeding him 'professional scareware', blaming all his woes on malware. The frustrated boy, aided by well-meaning friends, over-reacted to this supposed threat and further trashed his system {as indication
- a year later I found it running two active AVs along with services for an extra two}.
Laughed at by his macbook using brother, the boy abandoned his MicroSelfish rig.
The pity about this whole saga is that even when half-broken Win 9 looks like it's actually a decent OS. If only it could simply be instructed to play nicely with devices.
I have found countless sad accounts of systems which, after 'updating' to build 9600, have exhibited strikingly similar problems to those which exist on the machine I am working with.
I find it interesting to note that there are comparatively few accounts of troubles after a "clean install". It isn't clear to me whether this is a result of people having abandoned their machines like the kid did or whether they simply
reverted back to builds 9200 or 9400 {"stuff the updates"}.
I suspect lots of people paid 'Danegeld' for either a new build 9600 install disk or a magic fix from a professional who had such a disk and performed a clean install.
I also suspect there were many who couldn't afford to pay and were subsequently {and ironically} encouraged by MS's actions to download the media from 'unofficial' sources. I now wonder if I should attempt to do the same - at least I could easily
verify the media with an officially published checksum and move on.
Microsoft eventually provided a tool which {it is claimed} can be used to facilitate a "clean install" of build 9600. I have used this official tool to download the setup media.
I do not have the option of reverting back to the originally installed {and no longer supported} 'build 9200'. Those partitions were damaged. The existing build 9600 was also badly damaged.
I have tested {OS independent} the major hardware components and am convinced the problems are all software related. I feel that doing a clean install of the OS and replacing a couple of wonky drivers would go a very long way towards resolving
all issues.
I anticipate that finding and testing the correct drivers may be a time consuming task yet the process should nonetheless be relatively straightforward.
I want to use "known good" media to establish a "known good" baseline for the OS before applying updates, drivers, and {lastly} other software. I am astounded that the seemingly simple task of verifying I am starting this process
with "known good" media with "known good" content has be so difficult.
I wonder why MS insists on a "near enough is good enough"/"suck it and see"/"cross your fingers"/"have some faith" approach by it's customers. Does MS management operate this way?
I am not encouraged by either the process or the behaviours of the MS supplied MCTool. The first ISO it 'constructed' for me will not even boot. I have twice burned it to dvd and tested. The MCTool gave me no indication whatsoever that it had failed
to construct the ISO correctly.
The second ISO it constructed for me does boot up and does install an OS. I have now used that install media multiple times to build the OS foundation. All installations have been unexpectedly problematic. To put this into context, I *did* expect
there to be problems with the operation of some devices.
When allowed, the OS self-activates using the BIOS-embedded key.
I have tried to inject 3rd party drivers before MS OOB ones. This did not fix any issues. It may simply be that I need to keep searching for the "correct" drivers {there appears to be a bewildering amount of choices}.
Looking through WUC I have gained the impression that MS has now taken the lead in providing hardware drivers {esp. when compared to the embarrassing filth which Acer calls "Support"}. So I decided to trust in the fully automated MS update
process to see if these updates can eventually lead to MS supplied drivers which *actually* work.
Frustratingly, most of the updates "failed". I have tried to apply these updates with and without Defender running. I have repeatedly used the MS 'fixit' tool which keeps telling me it has found and "fixed" problems. Very ugly.
I now wonder how I might, with a straight face, eventually advise the boy to keep his "win9" OS fully updated using the officially recommended method.
The machine is not ancient - manufactured in mid-2013.
Basic OOB MS drivers for webcam and touchpad work. Whilst I have not yet extensively searched for alternatives drivers for these devices, the OEM supplied drivers and software I have tried break them again. It may be that basic drivers will
be the best that computer geeks can offer the boy and that he will have to find other uses for his multi-finger gestures.
Regarding the frequent network dropouts I have searched for and {conservatively} applied a variety of "fixes" for alarmingly similar problems which I have found splashed all over the internet. I have used things like ipconfig/netsh commands,
changing DNS, switching off power management for the network devices, etc. None have lasting effect.
Throughout, I have tried to avoid introducing any major 3rd party software which might complicate investigations yet I was forced to install an alternate browser after IE {which I haven't used since IE3} absolutely refused to save web pages in
any format {incl. text}. Apart from suffering the same network connection issues, the alternate browser appears to work just fine.
This is 2015. "Win8.1 update 1" was introduced a reasonably long time ago. I am sick to death of having to do all this monkeying around to properly install MS's current OS and have it play nicely with the devices on the underlying machine.
I am especially peeved that I don't even know if any of the issues I face whilst trying to resolve the matter simply stem from flawed files on the install media. Even on the damaged OS I originally found on the machine IE and auto updates worked
fine.
This is fundamentally an issue of 'trust'.
At this stage of the game the peaceful win7 on my desktop machine will *never* be ugraded to another Microsoft OS. I would also throw this POS Acer/win9 away if I could also gutlessly ignore the boy who has already been shafted by big men in suits.
So I seek your further help, on behalf of the boy.
I do *not* here and now seek help with all the problems which exist on the machine. I particularly seek help regarding how to verify the integrity of the media used to install the OS.
I have no idea how the size of "install.esd" relates to determining the integrity of the hundreds of other files which also populate the ISO. Nonetheless I checked this within both ISOs I received {one now "known bad"} and both
matched yours for size. This method appears to prove nothing.
I don't seek clarity about the above process and will simply presume it was worth a try anyway. It did however lead me to another line of enquiry which may prove useful {Yet may prove to be wishful thinking founded on ignorance}.
Rather than comparing filesize, wouldn't it have been more exact to compare checksums for the file? Further, couldn't this entire issue of verification be solved by extracting all the files from their ISO container, checksumming the resulting individual
files, then comparing checksums?
{as a random example, I presume that "/boot/resources/bootres.dll" *is* v6.3.9600.16384 *is* "17.8KB" in size *is* datestamped "Thursday, 22 August 2013, 10:39:14 PM" *is* sha1 "3e8c4c5dcc9797f596dcca7334f405b217242190"
-- every day of the week, everywhere in the world., within any of the same 'type' of ISOs created by MCTool.}
Although the above method is more cumbersome than simply comparing the checksum for one file {ie the ISO} it would still be a relatively simple thing to do programmatically with regularly available tools - 7-zip/ISObuster etc to extract the
files, any of a number of tools/methods to gain an ordered list of checksums plus a tool capable of showing differences between two lists of checksums {eg. winmerge}.
By doing a simple comparison, any individual with an MS supplied ISO/disk could essentially verify the integrity of the contents {ie the parts if not the whole}. Obviously, this would involve having a reliable list to compare against.
I suppose MS could officially provide this data, even in a simple text file. Do you know if they have? {I can't see one within the ISO itself which would seem to be a logical place for it}.
If MS has not provided this data then perhaps the MS community could independently establish such lists. It wouldn't take very many comparisons before a reliable list could be published. Perhaps such lists already exist?
At a pinch, it seems to be that any two customers possessing what is ostensibly the same ISO to produced the same type of OS might alone be able to establish confidence in the *contents* of their ISOs if they compared the checksums of the extracted
files and they exactly matched.
Obviously, if the checksums of any of the compared files do not match then the data set is too small to establish which copy of a non-matching file, if either, is true.
Is the above reasoning and strategy sound?
Otherwise is there an alternative workaround?
Or are Microsoft customers best served by firing up a bittorrent program and trying their luck?

Best workflow for editing Logic Pro 8 regions/tracks in Soundtrack Pro?

I've searched for a solution for the below question in several forums and to no avail. Thanks in advance for any help!
What is the easiest workflow for editing Logic Pro 8 audio files with Soundtrack Pro 2? And I'm thinking of a process very similar to the Final Cut Pro timeline audio-to- Soundtrack Pro Audio File project workflow.
I'd imagine that a good amount of the time, I'd be editing regions rather than full audio files -- as in, once in a while, while mixing sessions that another engineer has tracked, I'll hear clicks and pops from pre-amps clipping; or I'll hear an air conditioner blower running or something.
Basically, I occasionally hear noise in the arrange window while mixing that I'd like to edit out with Soundtrack Pro, and I need to know the easiest way to send that audio clip to Soundtrack Pro and then back to Final Cut Pro.

Connecting your FS Mobile to powered speakers will not increase latency. Latency is simply the fixed amount of time it takes for your computer to process sounds. Once the sound is processed and available at the outputs of the FS Mobile, it can go anywhere; to a PA mixer, a separate monitor mixer, headphones, etc. One thing you will want to consider when playing live is to have a personal monitor very close to you and pretty loud. The reason being is that the physical distance between you and the main PA speakers will itself induce a type of latency since sound travels at about 1126 ft/sec or 1000 msec of delay for every 1126 feet. Adding this delay to your latency could make holding a groove or pitch for that matter nearly impossible. The delays add up pretty quickly. For example, if your speakers are say 50 feet away from you, you would likely have around 20 msec of delay right there. Add this to your system latency of 20 msec and your up to 40 msec which is like trying to play a rubber guitar underwater. Even if your PA speakers are closer, the delays add up quickly. So having that nice loud monitor right up next to you will insure that you only have to get the feel of your system latency.

Windows exe file

I bought windows through Microsoft online and I have received an exe file. I can't seem to open it on my iMac, I have downloaded the windows support files from boot camp but I still can't get anywhere. What do I need to do?
Thanks,

Use a Windows PC and use the exe file to download a Windows ISO file. You can also put it on a USB2 flash disk.
To install Windows on a Mac start at How to install Windows using Boot Camp - Apple Support.

Logic pro 8 & windows (.iso) files

Similar Messages

Maybe you are looking for