Page 1 of 1

Background audio for each scene

Posted: Thu Nov 20, 2014 12:45 pm
by Chu
So, I'm back in the muddy topic of background audio.

I'm trying to create a sort of Jukebox scenario. At the moment each scene contains a media element, each scene's element has identical names (bg_audio) and the skin calls this name.

It works fine in flash but (what a surprise) not well in HTML5.

Is there a final workflow for including 'audio track per scene' in HTML5 or should I rely on some other jukebox-like script?

Re: Background audio for each scene

Posted: Thu Nov 20, 2014 3:18 pm
by Hopki
Hi,
You are probably better to add each sound to each node using the static sound mode.
Then tag each pano.
Use a node marker for each pano and use actions:

active, play media, sound1,
deactivate, stop media, sound1

Then add another node marker to react to the tag for the next pano.

active, play media, sound2
deactivate, stop media, sound2

As you enter a node the node marker activates the sound, as you leave it stops it, but when enter the next node, its node marker plays its sound.

Note, make sure all sound loops are set to -1.
Regards,
Hopki

Re: Background audio for each scene

Posted: Mon Nov 24, 2014 9:13 pm
by Chu
Hopki wrote:Use a node marker for each pano
Thanks Hopki, I'm a little 'old school' and completely forgot about the node markers...

I'll give it a whirl
Cheers

Re: Background audio for each scene

Posted: Tue May 10, 2016 3:47 pm
by Chu
Hi Hopki,
I've been toying with this audio tour for some time now, with differing results dependent on browser and version of P2VR.
Currently I use v5 and it seems to work very similar to where I left it with v4.5

1. I add an audio media element (audio01) to the first node in the tour, so as to use it throughout the other nodes. This node is the only one with audio elements
I have added the alternative .ogg format too
I have added the alternative .ogg format too
2016-05-10 14_19_00-sickboy_tour-v2.p2vr - Pano2VR.png (8.8 KiB) Viewed 1138 times
2. I call this element with a 'Mouse Click' action in the skin, and refer to the $ud placeholder for the node
2016-05-10 14_20_13-Skin Editor.png
2016-05-10 14_20_13-Skin Editor.png (2.85 KiB) Viewed 1138 times
The audio element unique ID is drawn from the Description entry - i know about the typo in the Title entry
The audio element unique ID is drawn from the Description entry - i know about the typo in the Title entry
2016-05-10 14_19_43-sickboy_tour-v2.p2vr - Pano2VR.png (2.39 KiB) Viewed 1138 times
3. Expected behaviour in Firefox (desktop & mobile) yet no audio at all plays in portable Chrome or iOS Safari

4. iOS seems to 'preload' all of the audio (spinning wheel in task bar on iPhone between Wi-Fi & time), yet I haven't waited to find out if it downloads the ~100Mb audio file, it just doesn't stream.
NB: The whirring wheel of boredom
NB: The whirring wheel of boredom
Photo-2016-05-10-14-39-35_3439.PNG (71.58 KiB) Viewed 1138 times
I'm not sure how to inform the tour of ONE audio track on the above mentioned mobile browsers, have you got any information which would support the above workflow with v5?
Many thanks in advance Hopki, or any Gnome who can help

Re: Background audio for each scene

Posted: Wed May 11, 2016 1:51 pm
by Chu
Chu wrote:3. Expected behaviour in Firefox (desktop & mobile) yet no audio at all plays in portable Chrome or iOS Safari
Also - expected behaviour in Chrome Desktop

Re: Background audio for each scene

Posted: Wed May 11, 2016 3:27 pm
by Hopki
Hi Chu,
Just to let you know I had a meeting with the developers yesterday regarding sound.
The dev's have said they will look into this as it really does need a tidy up.
Regards,
Hopki

Re: Background audio for each scene

Posted: Wed May 11, 2016 3:36 pm
by Chu
Thanks for getting back to me Hopki, always keen to hear your wisdoms on any topic.
Hopki wrote:I had a meeting with the developers yesterday regarding sound
Now you're making me jealous. It is certainly an area which needs their attention.
More than happy to assist.

Does this mean there is no alternative but to resist the urge to make it iOS & mChrome friendly?