Transferring SD2 created in ProtoolsHD to DP5 causes crash?
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
- Posts: 40
- Joined: Tue Oct 19, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Leeds, UK
- Contact:
Transferring SD2 created in ProtoolsHD to DP5 causes crash?
Hi All.
I suddenly seem to have an issue with some SD2 files -exported from a Protools session- crashing DP on my Intel iMac as soon as I try to import them from a project.
I have been working this way for years between platforms and this is a new one this time.
I track on a 32 channel PT HD system, export, then make DP file, import then mix at home in the analogue domain via RME 800.
The curious thing is that I can build up the DP session, with the same files, and have it all running happily on my G4 powerbook out to interface and desk.
I cannot believe it is an intel/DP issue as I have done 6 major projects this way with no troubles at all since I switched to an Intel Mac.
any ideas please?
my specs are below.
many thanks
barks
I suddenly seem to have an issue with some SD2 files -exported from a Protools session- crashing DP on my Intel iMac as soon as I try to import them from a project.
I have been working this way for years between platforms and this is a new one this time.
I track on a 32 channel PT HD system, export, then make DP file, import then mix at home in the analogue domain via RME 800.
The curious thing is that I can build up the DP session, with the same files, and have it all running happily on my G4 powerbook out to interface and desk.
I cannot believe it is an intel/DP issue as I have done 6 major projects this way with no troubles at all since I switched to an Intel Mac.
any ideas please?
my specs are below.
many thanks
barks
Last edited by barks on Tue Sep 18, 2007 6:00 am, edited 1 time in total.
iMac 2GHz Intel Core 2 Duo 2gig ram, DP5.12 (err, back to 5.11 actually...), RME Fireface 800, ADA8000, RME ADI-2 Converter, Allen & Heath GS3 24 channel mixer, Genelec 1030, dbx Drawmer Focusrite Roland Lexicon TC outboard, studio sofa + kitty...
-
- Posts: 744
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Hollywood, CA.
I've had the same problem. I have a bunch of sessions that I created in 5.11, some with OMF audio coming from PT sessions. Almost every single one of them works fine in 5.11 but crashes 5.12. I've had to go through and check every audio file in Peak. Some of them have end of line errors, the ones from OMF do anyway, so I resaved them as wave and them reimported them into the sessions. That seemed to work for some of the errors. In the end I ended up taking all my audio files and batch converting them into wave and the reimporting them into the 5.12 sessions.
5.12 has some strange behavior with audio files. It seems to have issue with files coming from PT and also with AIFF files. It's been a major pain in the ass for me. I'm a stone throw away from drop kicking DP out the studio door. Now that Logic has a fresh GUI, I might very well do that.
5.12 has some strange behavior with audio files. It seems to have issue with files coming from PT and also with AIFF files. It's been a major pain in the ass for me. I'm a stone throw away from drop kicking DP out the studio door. Now that Logic has a fresh GUI, I might very well do that.
-
- Posts: 744
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Hollywood, CA.
Absolutely.pcm wrote:Wasn't the new file format of 5.12 supposed to be for better
compatibility with Pro Tools? This would be funny if not so tragic.
I think a move to .wav format is what is called for here.
Can you believe it? It's way worse for compatibility now. 5.12 won't work with OMF at all and even has serious audio file issues when bringing in older 5.11 sessions, or just importing certain audio files. It's like working in a mine field. Never know which audio file is going to blow the session up in your face.
For the life of me, I can't figure out why MOTU is still hanging on to SD2. It's no good for higher sample rates and no one else is using it anymore. Bwav would probably be the best, keeps the time stamping intact. And all the apple stuff uses AIFF.
-
- Posts: 40
- Joined: Tue Oct 19, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Leeds, UK
- Contact:
I managed to build the DP project on my G4 powerbook and import the files fine (DP5.12) . The iMac intel was not working.
My work around was to then merge each track to a new file, then I was able to build the project in DP5.12 and import the new files on the iMac.
Something seems to have happened with the original files being consolidated and exported in PT on the iMac, so could it be an intel issue too?
barks
My work around was to then merge each track to a new file, then I was able to build the project in DP5.12 and import the new files on the iMac.
Something seems to have happened with the original files being consolidated and exported in PT on the iMac, so could it be an intel issue too?
barks
iMac 2GHz Intel Core 2 Duo 2gig ram, DP5.12 (err, back to 5.11 actually...), RME Fireface 800, ADA8000, RME ADI-2 Converter, Allen & Heath GS3 24 channel mixer, Genelec 1030, dbx Drawmer Focusrite Roland Lexicon TC outboard, studio sofa + kitty...
-
- Posts: 103
- Joined: Sat Jun 04, 2005 10:01 pm
- Primary DAW OS: Unspecified
This is a bug for sure - I've had the same problem.
My solution was to export .aif files from PT and re-import them to DP.
If DP had created SD2 files, and Pro Tools had so much as referenced the files, not changed or created or consolidated or anything, those files became instant crash food for DP.
As far as I know that's still true - when I reported this to MOTU they made a few suggestions but were unable to duplicate the problem.
Oddly enough...
Their suggestions had to do with a new user account... Didn't help.
I just had to incorporate a double-import into my workflow.
This might very well be an Intel issue.
JW
My solution was to export .aif files from PT and re-import them to DP.
If DP had created SD2 files, and Pro Tools had so much as referenced the files, not changed or created or consolidated or anything, those files became instant crash food for DP.
As far as I know that's still true - when I reported this to MOTU they made a few suggestions but were unable to duplicate the problem.
Oddly enough...
Their suggestions had to do with a new user account... Didn't help.
I just had to incorporate a double-import into my workflow.
This might very well be an Intel issue.
JW
DP5.12/MacPro2.66/2GB RAM/10.4.9 Combo/Pro Tools HD2/Pro Tools 7.3.1/Stylus RMX/Vanilla Plug-ins
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
Did motu tell you to change the extension to SD2?
2009 Intel 12 core 3.46, 64GB, OSX.10.14.6, Mojave, DP11, MTPAV, Key-station 49,(2) RME FF800,
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
-
- Posts: 744
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Hollywood, CA.
Nope, my rig is G5, so it's not an intel issue.barks wrote:I managed to build the DP project on my G4 powerbook and import the files fine (DP5.12) . The iMac intel was not working.
My work around was to then merge each track to a new file, then I was able to build the project in DP5.12 and import the new files on the iMac.
Something seems to have happened with the original files being consolidated and exported in PT on the iMac, so could it be an intel issue too?
barks
-
- Posts: 744
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Hollywood, CA.
Yes, that's my understanding too. I think the issue with audio file names and coruption is universal to all the processor platforms. I'm still not clear on what exactly is causing it. The file names don't seem to be the issue for me. It's more a matter of coruption that ocurs during or after importing.Timeline wrote:The sd2 extension is also required for G5 operating DP 5.12
I'm about to OMF a session out of DP to PT for overdubing in another studio tonight. I geuss I'll see if it works going the other way or not.
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
I could never get OMF to work completely to Nuendo from DP either.
I just combined files load them and start over. These DAW's are all very different and they will never truly be compatible because the MFG's don't want them to be.
Remember the days when manufacturers would meet and set standards?
Now it seems they argue over whose right and wrong never really quite get to complete compatibility. It's time to set up a technical group or board to set the standards for them and make this happen.
I would start the board with Shooshie.
I just combined files load them and start over. These DAW's are all very different and they will never truly be compatible because the MFG's don't want them to be.
Remember the days when manufacturers would meet and set standards?
Now it seems they argue over whose right and wrong never really quite get to complete compatibility. It's time to set up a technical group or board to set the standards for them and make this happen.
I would start the board with Shooshie.
2009 Intel 12 core 3.46, 64GB, OSX.10.14.6, Mojave, DP11, MTPAV, Key-station 49,(2) RME FF800,
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2