Anyone interested in doing a few odd-jobs?


#1

If anyone fancies earning a bit of pocket-money in return for some coding, there are a few self-contained little features which I’m struggling to find time to do myself… If you’ve got “m4d juce skillz” and some spare time, I can offer a (modest!) fee for the implementation of some of these things:

  • An openGL ES rendering engine for Android/iOS. This would basically be an openGL implementation of the LowLevelGraphicsContext class, and a type of Image::SharedImage that can hold a p-buffer. I know very little about openGL, and less about openGL ES, so it’d be a bit of a learning curve for me to do this myself… To be useful, it’d need to be able to produce an identical result to the software or CoreGraphics rendering engines, correctly performing anti-aliasing, complex clipping etc.

And some simpler items:

  • A CoreVideo video player, to replace the QuickTimeMovieComponent class.
  • A DirectShow video player to provide a Windows replacement for QuickTimeMovieComponent.
  • A CoreCodecAudioFormat class that can open and read (but not necessarily write) audio files using CoreCodec.
  • A DirectShowAudioFormat class… same as above, but for Windows.

If any of these sound interesting to you, please email me to discuss, and give me a quote!


#2
  • a VST3 Wrapper :wink:

#3

…actually, yes! Good suggestion!


#4

Don’t we then also need a VST3 host?


#5

A juce one? Eventually, but it’s not something I’m in any kind of a hurry to do.


#6

Don’t we then also need a VST3 host?[/quote]

Do you mean the ability to load VST3 as AudioPluginInstances ? If that’s the case, I second that !


#7

VST3++;


#8

Out of curiosity, do you think reimplementing Juce’s graphics to use OpenGL rather than CoreGraphics for instance will boost the graphics rendering performance of apps on iOS and android? I wrote an app for iOS that does a fair amount of high frame rate rendering, and I haven’t been 100% happy with its rendering performance. I had thought about reimplementing parts of the app using an OpenGL component or creating an OpenGL based LowLevelGraphicsContext for the app as a whole, but I wasn’t sure if CoreGraphics was using hardware acceleration already and whether this would actually give any measurable performance improvement…


#9

On iOS, CoreGraphics is probably pretty good already, so it might not make much difference (depending on what kind of thing you’re drawing). But on Android, the rendering would certainly be vastly better using openGL, not least because it’d cut out a huge number of very expensive JNI calls.


#10

On the iPad app I did, which has a fading slide show view, I had to go to OpenGL. Big, big difference.

I did a fairly nice trick by snapping the background of the component, and using that as the background in OpenGL - makes the seams of the OpenGLComponent invisible (hide component, draw and grab snapshot)

Bruce


#11

[quote]- A CoreVideo video player, to replace the QuickTimeMovieComponent class.

  • A CoreCodecAudioFormat class that can open and read (but not necessarily write) audio files using CoreCodec.[/quote]

What is CoreCodec? I’ve never heard of it mentioned in the Apple docs.
Additionally, CoreVideo only deals with uncompressed video frames, you will still need to use QuickTime to decode compressed video.

The AudioToolbox Framework apart of CoreAudio lets you decode/encode compressed Audio. It is available on iOS 2+ and will be available in Mac OS X 10.5+.
AVFoundation is a new Apple API meant to deal with decoding and displaying compressed video and audio. It is available on iOS 4+ and will be available in Mac OS X 10.7+.

It also may be worth noting that there are AAC and MP3 encoders and decoders available via Microsoft’s Media Foundation API. The downside is that these codecs are only available on Windows 7 and later.


#12

Yes, I’m getting all my apple API names confused… there are so many to remember! You know what I mean, anyway… the audio codec stuff that doesn’t use quicktime, whatever they call it these days!


#13

Hi,

I’m interested in doing DirectShow component…
I have base (working) code. It’s for 1.50 but it should work on current juce tip too.

Do you need it or it has already been done?

Bye


#14

Jules:
Nothing substantial found for a DirectShowAudioFormat class, but i found this code which works nice for MP3 decoding on Windows based on the the old ACM Decoding infastructure in Windows. It seems to work fine in Windows Vista 64bit.

Why not use this, if it just work, would be happy to have this as an Juce AudioFormat :slight_smile:

http://www.all4mp3.com/SoftwareTechTools.aspx Look at the second example ACM Decoder Sample Code (mp3 decoding)


#15

Thanks, I’ll take a look at that when I have a moment!


#16

As I suggested time ago, VST3 could be a good idea for Juce libraries. My vote for their implementation.


#17

hi Jules,

Can u post the completion of modules when it is done. we might be trying to implement when its already completed.

Regards,
Happy


#18

[quote]- A CoreCodecAudioFormat class that can open and read (but not necessarily write) audio files using CoreCodec.

  • A DirectShowAudioFormat class… same as above, but for Windows.[/quote]

open and read from which audio format?? JUCE already has audioformat to read and write to file.


#19

Please don’t start on anything without asking me! If you’re interested, contact me directly to discuss it.

well, for any format that the OS provides a codec for. Juce provides built-in support for a few open formats, but I haven’t added things like mp3, AAC etc, because of patent issues.


#20

hi Jules,

I m interested in creating DirectShowAudioFormat class. Can u please provide me the specification at sandy4coding@gmail.com

Regards,
Sandy.