Moving projects from Mac to PC?
I've moved my Scope/SP from an Apple G4 to a PC and while everything works fine I can't open my old projects because the devices on the Mac are named xxxxxx/dev instead of xxxxx.dev. When I force the project to replace the devices, i get the error "value out of range".
Does anyone know how to work this out?
Does anyone know how to work this out?
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
'/' in the names? I haven't seen that (have been using Pulsar soft for 1.5 year on a Mac). The only solution that gets to my mind is to open all the projects back on your Mac and rename all those xxx/dev to xxx.dev. Actually I don't know if the names were proper in your Pulsar/Mac folder and they only appear with wrong suffixes in your SFP/PC/search window... Hmmm, strange. Can you please e-mail me one of those projects (that include standard devs rather than 3rd party)? I'll have a look on it...
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
I've opened a PC project on my mac succesfuly. If you haven't much time I'd suggest you moving the card back and try to see. In my Mac all the davs are named xxx.dev. There could be one thing though - I saw on my 'download page' at CW's different version of my 3rd party devices and there is a special for Scope 2.xx mac. Perhaps Scope/mac app have different suffixes? I still don't know (you didn't mention it) if they (the devs) have such strange names in your Scope folder on your Mac or the PC interprets '.' as '/'. ???????
<font size=-1>[ This Message was edited by: samplaire on 2002-11-11 17:19 ]</font>
<font size=-1>[ This Message was edited by: samplaire on 2002-11-11 17:19 ]</font>
From the look of it the Scope s/w folder structure looks exactly the same on Mac and PC, the same names, extensions etc.
But when I open a project that came from the Mac somehow the PC gets things mixed up with the devices looking for xxx/dev instead of xxx.dev for example. That's a pain but I can still force replace the devices manually. But then it wont load the settings of my project claiming "the value is out of range".
Most annoying indeed, but maybe I'm getting things wrong and any input would help since I'm porting all my work from Mac to PC...
But when I open a project that came from the Mac somehow the PC gets things mixed up with the devices looking for xxx/dev instead of xxx.dev for example. That's a pain but I can still force replace the devices manually. But then it wont load the settings of my project claiming "the value is out of range".
Most annoying indeed, but maybe I'm getting things wrong and any input would help since I'm porting all my work from Mac to PC...
It looks like the problem comes from the parameters, the way they are written in a MAC project seems different from the way it is on PC projects...
Transfering simple wav from mac to pc is already long and tedious, so imagine for entire scope projects.... looks like you are trying to achieve something difficult here.
Sorry, no idea on how to convert this or to solve the problem...
<font size=-1>[ This Message was edited by: spacef on 2002-11-15 04:21 ]</font>
<font size=-1>[ This Message was edited by: spacef on 2002-11-15 04:22 ]</font>
Transfering simple wav from mac to pc is already long and tedious, so imagine for entire scope projects.... looks like you are trying to achieve something difficult here.
Sorry, no idea on how to convert this or to solve the problem...
<font size=-1>[ This Message was edited by: spacef on 2002-11-15 04:21 ]</font>
<font size=-1>[ This Message was edited by: spacef on 2002-11-15 04:22 ]</font>
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
Hey Starco,
Language scripts could matter. Why? Sometimes after getting to PlanetZ with a Mac (but not mine!) I see question marks instead of apostrophs - switching the script solves the problem. I don't know if this could affect Scope Mac/PC but who knows???
I've got a suggestion for you - give your Mac project to any other PC/Pulsar/Scope user (I know there are many of PLZ people to help you
) to reproduce your problem. If it will not affect their system then maybe it's the simpliest way to transfer your projects via a different computer, save there and back to yours??? You know it's difficult to make a statement without even seeing the problem.
Have you tried to explain your problem to the CW support team?
Language scripts could matter. Why? Sometimes after getting to PlanetZ with a Mac (but not mine!) I see question marks instead of apostrophs - switching the script solves the problem. I don't know if this could affect Scope Mac/PC but who knows???
I've got a suggestion for you - give your Mac project to any other PC/Pulsar/Scope user (I know there are many of PLZ people to help you

Have you tried to explain your problem to the CW support team?
Just to confirm that on my old g3 under os8.6 pulsar2.04 the devices are called
.dev and not /dev
I remember a little problem that i create one day changing the name of my hard disk.Pulsar did not recognize anymore the route with another hd name.I reput the first name and everything was ok after that.(just an info maybe not so usefull but who knows?).
.dev and not /dev
I remember a little problem that i create one day changing the name of my hard disk.Pulsar did not recognize anymore the route with another hd name.I reput the first name and everything was ok after that.(just an info maybe not so usefull but who knows?).
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
Hi Starco, nice fellowOn 2002-11-14 17:01, Starco wrote:
come on, guys... give me a better answer on this one. Any pros around here?

Me and Spacef have tried to reproduce your problem on our machines (my Mac and his PC) and unfortunatelly we did reproduce it. So we can conclude : there is an incompatibvility between the 2 platforms in sharing projects... Some may say it's a bug but I'm not into saying it. I even tried to open a project using HEX editor and found only bushes of letters... Perhaps black magic could help but it's rather not my domain, sorry.
P. S.
You didn't answer my question about informing CW about it. Are they aware of it? Do they see the problem? Do they do any remedy to it?
First of all thanks for your help and input.
I know it's been a little difficult to understand my problem unless one tries for himself but I'm glad that someone took the time to confirm my suspicion that Pulsar projects aren't cross platform, which is completely stupid since ALL devices and most of the application components are exactly the same.
Actually, it seems to me that Pulsar on the Mac employs a PC-shell somewhat similar to Virtual PC to run the program.
As a ProTools user for many years I've always enjoyed Creamwares modular approach and nearly open source environment which makes for more interesting and cheaper plug-ins than TDM, albeit at the sacrifice of some stability and arguebly also the quality of certain plug-in types such as reverbs etc.
But I'm still surprised that such a simple and easy thing to implement on Scope/SP as cross platform support isn't working when all the components are there.
I still hope I'm wrong, but I will now write to Creamware and ask them about this and if they confirm the problem they should write a little PC application that converts between the two formats.
So stay tuned on this channel....
I know it's been a little difficult to understand my problem unless one tries for himself but I'm glad that someone took the time to confirm my suspicion that Pulsar projects aren't cross platform, which is completely stupid since ALL devices and most of the application components are exactly the same.
Actually, it seems to me that Pulsar on the Mac employs a PC-shell somewhat similar to Virtual PC to run the program.
As a ProTools user for many years I've always enjoyed Creamwares modular approach and nearly open source environment which makes for more interesting and cheaper plug-ins than TDM, albeit at the sacrifice of some stability and arguebly also the quality of certain plug-in types such as reverbs etc.
But I'm still surprised that such a simple and easy thing to implement on Scope/SP as cross platform support isn't working when all the components are there.
I still hope I'm wrong, but I will now write to Creamware and ask them about this and if they confirm the problem they should write a little PC application that converts between the two formats.
So stay tuned on this channel....
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
I've been using PT for 5 years (on a Mac) and there was a similar situation abot 2-3 years ago - I had to move my session to a PC. Though the PC PT (and the manual, too) allowed me to import a Mac session - it didn't open due to SDII<->wav incompatibility... Now (in PT 5.3.1) it is possible (force PC compatibility option)On 2002-11-17 13:17, Starco wrote:
As a ProTools user for many years I've always enjoyed Creamwares modular approach and nearly open source environment which makes for more interesting and cheaper plug-ins than TDM, albeit at the sacrifice of some stability and arguebly also the quality of certain plug-in types such as reverbs etc.
But I'm still surprised that such a simple and easy thing to implement on Scope/SP as cross platform support isn't working when all the components are there.
1. I will!I still hope I'm wrong, but I will now write to Creamware and ask them about this and if they confirm the problem they should write a little PC application that converts between the two formats.
So stay tuned on this channel....
2. The tool you mentioned is a good idea.
3. Try to be polite and calm in the e-mail to CW to get an answer

_________________
Sir SamPlaire
<font size=-1>[ This Message was edited by: samplaire on 2002-11-17 18:00 ]</font>