![](https://en.delphipraxis.net/uploads/set_resources_2/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
![](https://en.delphipraxis.net/uploads/monthly_2018_10/H_member_385.png)
Hans♫
-
Content Count
130 -
Joined
-
Last visited
-
Days Won
3
Posts posted by Hans♫
-
-
It looks like the Oboe library is the way to go for low-level audio input/output on Android. But it's a C++ library, so it will require writing a wrapper to flatten it.
Do you know anyone using Oboe in Delphi, that might have written a full or partial wrapper?
PS. I am usually a little afraid to share my own wrappers on various platforms because they are usually only partially completed and I fear that I also have to provide support for it, and instruct how to use it 😉. However, anything you have would be a great help 🙂
-
I have usedSDKtransform
for years (executed through "SDK Transform Assistant") to implement the iOS and OSX frameworks that are not included with Delphi.However, an increasing number of classes fail to be converted and are not included in the output .pas header file. Right now I need to convert
AVAudioEngine
fromAVFoundation
in MacOS 11 (Big Sur), but SDKtransform fails with a lot of these lines added to the log:"WARN: cannot add ObjCInterface AVAudioEngine - base class unknown"
Could this be due to the way it is defined (as an interface)?
API_AVAILABLE(macos(10.10), ios(8.0), watchos(2.0), tvos(9.0)) @interface AVAudioEngine : NSObject { @private void *_impl; } - (instancetype)init; - (void)attachNode:(AVAudioNode *)node; - (void)detachNode:(AVAudioNode *)node; ... @property (readonly, nonatomic) BOOL isInManualRenderingMode API_AVAILABLE(macos(10.13), ios(11.0), watchos(4.0), tvos(11.0)); ... @end // AVAudioEngine
How do I autoconvert this type of header definitions?
PS. This is a copy of my post on StackOverflow.
-
10 hours ago, Nasreddine said:I'm also facing issues where the app works great on an intel machine but fails on an M1 one.
I have not seen any yet. Where do you experience problems?
10 hours ago, Nasreddine said:we have to wait at least 8 months for 10.5 to be able to target arm.
Maybe. There is a chance that you could implement debugging without offering arm as a target, but I suppose it would rely on the Rosetta 2 emulator, if that implements mapping of instructions and memory for debugging purpose. With the limited development ressources that Embarcadero can put into it, we are probably not seeing debugging support for the M1 until they make a full support of the M1 ARM target.
-
On 2/7/2021 at 2:42 AM, Nasreddine said:did you manage to solve it? I have M1 as well and with same error
No it still doesn't work, and I realize I forgot to create an issue about it. Now it is there:
https://quality.embarcadero.com/browse/RSP-32362-
2
-
-
I have no performance numbers, but it "feels" faster. Apps starts faster and feels more responsive, but maybe it is also related to being a new and fresh installation of MacOS, compared to a 3 years old Mac Mini with Intel.
-
I have a Mac Mini with M1 CPU. You can run PAServer on it and deploy Delphi MacOS apps on it, but you cannot debug. So as long as you choose "Run without debugging", then it works fine.
See also this post:
-
1
-
-
1 hour ago, Lajos Juhász said:According to the Roadmap (https://blogs.embarcadero.com/rad-studio-roadmap-november-2020/) in Delphi 10.5 H2 2021 you can expect a better support for the M1 CPU. In the roadmap it's under Platform Enhancements macOS ARM (Delphi).
The roadmap refers to ARM M1 as a target platform.
What I am referring to is to be able to debug the Intel target on an ARM M1 CPU.
I can deploy and run from Delphi on the M1 CPU, but I cannot debug.
It might not be possible to use the CPU view in Delphi, as it would have to work through the Rosetta 2 converter, but limited debug facilities would suffer, e.g. Breakpoints and variable inspection.
-
Now I had time to investigate it a bit further. Looks like debug mode does NOT work on the new M1 CPU.
I can run a MacOS application from Delphi on the M1 Mac, without debugging, but when I run in debug mode I get the error: "unable to create process 'debug kernel timeout'".
The same application runs fine in Debug mode when using an Intel Mac having the same versions of MacOS (Big Sur) and XCode.
Before I create an issue on on Quality Portal. Are there any suggestions for things I should try first? - or extra information I can retrieve and include in the issue?
-
It works with Delphi 🙂
Just received the Mac Mini with the new Apple M1 CPU. After a quick attempt to deploy our FMX app, I can confirm that PAServer runs and I can deploy and run our FMX app without problems.
"Rosetta 2" seems to do the job very well!
-
4
-
-
I have attached the FMX.InAppPurchase.Mac.pas that we use so it is easy to use for others. All you need is to add it to your project and also add a modified version of FMX.InAppPurchase.pas where you include the file (just search for FMX.InAppPurchase.IOS, and see how that file is added, and do the same with the FMX edition)
-
3
-
1
-
-
We use InApp purchase on MacOS and it works fine. Sorry for not updating this thread.
I worked with David directly to solve the problem in our code, but I think David has implemented his own solution in his Kastri framework:
-
You'll probably need to do a lot of tweaking and manual work to create an AU with Delphi. The recommendation from Apple is to inherit from the AU base classes:
"The quickest way, the one endorsed by Apple, and the one described in this document, is to subclass the appropriate C++ superclasses of the freely-downloadable Core Audio SDK."
When I have needed to access C++ objects in Delphi, I have flattened them, but I don't know if this can be done everywhere in this situation. Someone else can probably tell you more about how you can handle that.
-
1 hour ago, Kas Ob. said:Does creating and playing music using kitchen cookware count ?
Good sense of rhythm is always a plus 😉
-
EarMaster is a unique and highly praised app made in Delphi for Windows, MacOS and iOS.
We are looking for a unique profile, and therefore I also share the job internationally. For the right person, this will be a dream job that might make you consider to relocate to Denmark!
This job is at our office in Aarhus, Denmark, and remote work is not an option - don't waste your time to ask if we are sure, or if we have other jobs for remote workers 😉
The job add is in Danish, but it is not an absolute requirement that you speak Danish if you have strong English skills. The Google translated job add can be accessed here:
https://www.it-jobbank.dk/jobannonce/362739/musikalsk-lead-udvikler-til-verdenskendt-musikteori-app
You can find more information about the app at our
Website: https://www.earmaster.com
Youtube channel: https://www.youtube.com/user/eartraining
and for a more technical insight, here is the video we made 4 years ago when our iPad app became the Embarcadero "Cool App Winner":
-
6
-
-
I made Delphi headers for the Canon SDK about 20 years ago. It allowed me to connect to the camera, show live preview, zoom, take pictures and download the pictures into my software. Don't know if the headers are of any use with the current SDK, but if you want to try, you can get it. No support included 😉
-
5 hours ago, lefjucabro said:I had to get iOSapi.AudioUnit.pas, iOSapi.CoreAudioTypes.pas and iOSapi.CoreMidi.pas which are declared in iOSapi.AudioToolbox.pas.
Sorry I didn't see that. I have sent a PM with those headers too.
However, there are a lot of details to figure out before you can achieve what you want. Having the headers is just a small part of it. With a lot of Googling, reading and persistence - eventually you will get through 😉 Keep up the spirit!
-
2 hours ago, lefjucabro said:... (I really am a beginner). If you have a link to explain it or send me your file if it is ok for you.
If have sent a PM with the file, but you are far from done having this file. The best advice is to find code in Objective-C that does what you want, and then convert it to Delphi - which might include a few headaches.
-
All the AudioQueue... functions are in iOSapi.AudioToolbox. Do you know how to convert the SDK headers your self? - or else I can send you my version of the file.
-
We have developed a low-level audio input solution for Windows, MacOS and iOS. It allows us to process audio immediately when each buffer is filled and delivered to our code. I cannot share my code here, but here are some hints of the API functions we use on iOS:
AudioQueueNewInput
AudioQueueAllocateBuffer
AudioQueueEnqueueBuffer
AudioQueueStart
AudioQueueStop
-
2
-
-
I suppose the problem you have is the one described here:
-
1
-
-
11 minutes ago, MikeMon said:... and use an Xcode storyboard to provide the app’s launch screen.
Thanks, I got that email too, but obviously missed the part about the storyboard 🙂
-
2 hours ago, MikeMon said:How come there's nothing in forums about this? How are other Delphi users developing for iOS tackling this? The above solution doesn't feel right.
I don't know when (or if) Apple will make it a requirement to use the Storyboard, but so far you can still use the old way that Delphi supports right now. We are not using the storyboard solution in our app, and that is still accepted by Apple. Its only one week ago we uploaded the last update.
-
Is there a confusion between "App Store" and "Mac App Store" somewhere?
The error message contains both "Mobile" and "App Store", which refers to iOS, not MacOS.
Our App is on Mac App Store now, though we use our own shell scripts to sign and build the final application package.
-
On Firemonkey there is a problem loading fonts dynamically, so maybe its related to that?
FMX on mobile: Best practice to handle touch scroll of components?
in FMX
Posted
Having various components on a TListbox, scrolling does not work when i touch a component that has HitTest=True.
What is the best way to solve this?
I have comboboxes, radiobuttons, checkboxes, etc on Listboxitems to create a dynamic interface. So far I have only used native components on iOS (TMS iCL) where scrolling vs control interaction, is handled automatically by the OS in a very smooth way. Now we are preparing an Android version based on our FMX view, but on FMX it does not seem to work out of the box. If HitTest is true for a component, then scrolling does not work, and if HitTest is false for a component, then it does not respond, but scrolling works.
I found this nice solution made by David Nottage, but it requires to create a descending class of each component used:
https://stackoverflow.com/questions/57452568/prevent-firing-events-while-scrolling-tvertscrollbox