• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

PC compatability with LogicPro?

So as I understand it at present, LogicPro will not work with Windows 10.

Is there recording software which is compatible for sharing files with LogicPro. I have used Reaper, but I have read reaper files cannot be imported into Logic Pro.

I ask because my bandmate has a Apple, I have a PC. We've used BandLab, bit it's a PIA.

As a related BL question, is there a Win10 interface that will work with BL? It doesn't seem to recognize my Alesis iO4 which needs Asio4All.

Thanks in advance.
 
As others have mentioned, the audio files can be easily imported, exported and shared between different users on different DAW software on different OS. WAV files being the most common.

You won't be able to share project metadata/settings - e.g, tempo, automation, levels, pans, mutes, track names, track order, and other track attributes. etc. from Logic into any other DAW besides Logic. And Logic is Mac only.

Even if you were running the same version of Logic on your own Mac, there would be certain things that won't get carried over automatically - e.g., plug-ins, loops, etc. If you don't have the same plug-ins licensed and installed, you won't be able to initialize them when you open someone else's project. Such as: MIDI drum tracks, guitar amp sim plug ins, other instruments on MIDI tracks (that aren't part of the base Logic install).

File management is another thing. Right out of the box, if the file paths are not exact, you'll have to go through the process of remapping the file paths. That could made easier if file paths were "well set up" at the other end....e.g., not in a path like: ".../Bob's Computer/Music Stuff/Tracks/Music/Logic/Demos/2021/March/<song name>/Take 001/...".

My collaborators and I have attempted to standardize on Ardour/Ubuntu Studio....I'd say that typically 75% of a typical project loads as expected but the remaining 25% doesn't (usually related to plug-ins and file paths). That means troubleshooting plug-in installs and/or remapping file paths manually. And then there's the audio interface hardware. Any changes in hardware usually have to managed handraulically. I've spent more time remapping file paths than I have recording. Also troubleshooting issues with FLAC files, but thats another story captured in another thread!

Expecting a completely seamless 1:1 interoperability - even between two computers of the same type - is not realistic unless you have an EXACT mirror of software, plug-ins hardware and file management set up. Unless you had exacting standards for multiple users in terms of hardware, OS, DAW, plug-ins, file management, etc., you're simply out of luck. Maybe if you are a Chris Lord-Alge, you could enforce those standards. but for us run-of-the mill duffers, not realistic. Completely seamless 1:1 interoperability using different DAW software on different OS - approaches the impossible.

That's why the audio stems and mixdowns are the most common way things are shared in various stages of production...as opposed to the project itself.
 
  • Like
Reactions: Hummergeist
Expecting a completely seamless 1:1 interoperability - even between two computers of the same type - is not realistic unless you have an EXACT mirror of software, plug-ins hardware and file management set up. Unless you had exacting standards for multiple users in terms of hardware, OS, DAW, plug-ins, file management, etc., you're simply out of luck. Maybe if you are a Chris Lord-Alge, you could enforce those standards. but for us run-of-the mill duffers, not realistic. Completely seamless 1:1 interoperability using different DAW software on different OS - approaches the impossible.
I've been in a room with two guys trying get their supposedly identical MacBooks to sync - only working after one of them updated only-just-behind OS.
 
I've been in a room with two guys trying get their supposedly identical MacBooks to sync - only working after one of them updated only-just-behind OS.

I’m a moron and I have my MacBook mirrored perfectly with our studio PC. Same plug-ins and sound sets of course. If I have a project that I’m carrying back and forth, I start the session/project on an external SSD and work with that drive until the project is finished. Then I transfer the files to an archive drive, either mine or the studio’s where they will live. It’s just keeping up with file management.
 
I’m a moron and I have my MacBook mirrored perfectly with our studio PC. Same plug-ins and sound sets of course. If I have a project that I’m carrying back and forth, I start the session/project on an external SSD and work with that drive until the project is finished. Then I transfer the files to an archive drive, either mine or the studio’s where they will live. It’s just keeping up with file management.

What DAW software are you using and how many other people are you sharing your projects with?
 
What DAW software are you using and how many other people are you sharing your projects with?

I use Studio One by Presonus and I’m not sharing or collaborating with other writers or players. I bring projects that I’m personally involved in (writing, playing, singing, etc) back and forth from the studio to my house when I feel like working at home. I have also sent stems to other players for them to play parts on and send back. Easy stuff.
 
I use Studio One by Presonus and I’m not sharing or collaborating with other writers or players. I bring projects that I’m personally involved in (writing, playing, singing, etc) back and forth from the studio to my house when I feel like working at home. I have also sent stems to other players for them to play parts on and send back. Easy stuff.

Ah, OK, so you have full control over structure and content of your projects. My problems stem from swapping projects with other collaborators who might have different implementations of the same DAW software, different plug-ins, different file structures. I’ve tried to introduce some structure/standardization but it’s always the case that I open up a project to learn a file or a plug-in can’t be found. That’s if we’re working in the same DAW software! Very difficult to achieve any kind of perfect interoperability between two or more collaborators unless someone is either funding the whole thing and/or taking steps to enforce standards.

One of my collaborators is an inveterate tinkerer. There was one time he sent me an entire project created in software that I’d never heard of to that point. And I was just supposed to lay down one bass track and maybe do some mixing.

hell, even when I swap projects between machines I sometimes get caught up in my own mess. Usually file management.
 
I have not found a virtual host that will allow you to install MacOS on a PC. Windows on a Mac, yes. Mac on Windows, no.

Also, when running an OS inside a VM, you never get direct access to the hardware (it's all virtual) so the latency from an audio interface is WAAY HUGE.

OK, so let's say there is a "Hack Intosh" PC that you can boot MacOS on (I've head of such things). Problem - you will be running on an unsupported platform, with who knows what kind of issues under the hood. Not a lot of fun unless you enjoy poking around in the basement of your computer system.

Better to just buy a Mac and get to the business of making music
 
  • Like
Reactions: filmtex