Looking for Access to iPad MWorks with Audio Support for macOS 16.2

Support
1

Hi Chris, we are looking to present some audio through iPad, but our iPad cannot upgrade to the latest macOS (17.xx) and thus can’t support the version of MWorks currently available in the App store. Our iPad is on macOS 16.2 and currently runs MWorks 0.11 - which does not support audio. Would it be possible to get access to an iPad version of MWorks > 0.12.1 that can run on macOS 16.2? If you could possibly share a nightly version of MWorks 0.13, I believe that would resolve our conflict.

2

Hi Liza,

Our iPad is on iPadOS 16.2 and currently runs MWorks 0.11 - which does not support audio.

MWorks 0.11 absolutely supports audio (as have all MWorks versions since the beginning of time). See the 0.11 docs for Sound Stimulus. MWorks 0.12 did introduce some significant improvements to MWorks’ audio support, but basic sound playback is definitely available in 0.11.

Would it be possible to get access to an iPad version of MWorks > 0.12.1 that can run on iPadOS 16.2? If you could possibly share a nightly version of MWorks 0.13, I believe that would resolve our conflict.

Sorry, but I don’t keep old nightly builds. (In fact, we weren’t even generating nightly builds for iPad until after the 0.13 release.)

Honestly, if your iPad is too old to run iPadOS 17, it is very old indeed. Based on this chart, you’re talking about a device from 2017 or earlier. 8+ years old is positively ancient for an iPad, and it probably isn’t going to run MWorks well in any case. I think your best bet would just be to get a newer device.

Cheers,
Chris

3

Hi Chris,

Thanks for your help! Based on your suggestion, I’ve tried to fix the 0.11 mWorks version, but I’m unsure what to use instead of sound_group which doesn’t work in this version.

Should I list all the sounds individually, or is there a better alternative?

sound_group audio {
    range_replicator (
    	from = 0
    	to = 369  
    	step = 1
    	variable = rr_index
    	) {
    	wav_file audio${rr_index} (
        	path = '/path to /audio${rr_index}.wav'
    	)
    }
}
4

Hi Shirin,

You can still use a range replicator to define the sounds. Just remove the enclosing sound_group:

range_replicator (
    from = 0
    to = 369  
    step = 1
    variable = rr_index
    ) {
    wav_file audio${rr_index} (
        path = '/path to /audio${rr_index}.wav'
    )
}

The difficulty is that you’ll need to reference each sound by its tag: audio0, audio1, etc. This is going to prevent you from, say, selecting a random index and playing the sound at that index, so it probably won’t work for you.

An ugly but viable workaround would be to convert your sounds into videos and then define each sound as a video stimulus inside a stimulus group. The actual video content could be minimal (e.g. a single pixel), and you could hide it by setting alpha_multiplier to zero. You should be able to use FFmpeg to create the videos (see this discussion).

Cheers,
Chris