








Your rating: Now say why...



| Downloads:22,695 |
| Version Downloads:13,813 |
| Type:Multimedia & Design : Audio |
| License:Free |
| Date:10 Jul 2008 |
| Platform:PPC / Intel |
| Price:Free |
Overall (Version 2.x):![]() ![]() ![]() ![]() ![]() |
Features:![]() ![]() ![]() ![]() ![]() |
Ease of Use:![]() ![]() ![]() ![]() ![]() |
Value:![]() ![]() ![]() ![]() ![]() |
Stability:![]() ![]() ![]() ![]() ![]() |
I am very disappointed.
Do you know what the problem could be, and how can I make it work.
Many thanks
Paulamac
+45
Sorry for this, I'm trying to look forward.
Eric,
Polyrythmic
-6
This time a different message in Terminal:
powerbook:~ peterfackelmann$ /Users/peterfackelmann/Desktop/REC 211.app/Contents/MacOS/REC
JUCE v1.45
no interfaces folder, you are in serious trouble!
Regards
Peter
version 2.1.1 should work both on PPC and MacIntel.
Cheers,
Eric,
Polyrythmic
and many thanks for the report.
You're right, Rec 2.1 doesn't seem to work on PPC.
[tested on G4]
I'm trying to change this.
Cheers,
Eric,
Polyrythmic (7/1/2008, Version: 2.1)
-6
no interface
crashed
XC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0x80030000
tried in Terminal
powerbook:~ peterfackelmann$ sudo /Users/peterfackelmann/Desktop/REC.app/Contents/MacOS/REC
Password:
JUCE v1.45
Segmentation fault
(PPC G4 10.4.11)
Any proposal?
Thank you
Peter
and many thanks for the report.
You're right, Rec 2.1 doesn't seem to work on PPC.
[tested on G4]
I'm trying to change this.
Cheers,
Eric,
Polyrythmic
I work on a 1.67 GHz PPC G4 alu powerbook, 2 Gig, Mac Os X.4.8
Keep up the great work!
Cheers,
Rob
Well, what you describe is quite strange, and I can't reproduce this on my computer. What system are you running on?
the problem hasn't been reported yet for OS prior to 10.4.8. It concerns .dmg files compatibility (I'm running 10.3.9).
In December there was an important security alert concerning .dmg files. I suppose Apple has released security updates for these files too quickly.
Waiting for any valid solution, man can use your clever tip!
Oh yes, Citadel, now I remember.
Please don't write anything more about our private life... ;)
+51
Also, using a buffer~ to hold the recorded/loaded sound is both dangerous (crash = your audio recording gone) and it is not suitable for long recordings (takes a loooong time to load/save large audio files as the whole thing must be loaded into or transferred from RAM/VRAM).
I for one do wish MaxMSP had a direct-to-disk audio file editor like the one for buffers. Then you could do all sorts of great things like this with it.
+51