Weird question, I apologise in advance.
I'm using Twine 1.4.2 to create music lessons for students. (Remote learning and Covid. It's such a drag.) https://twinery.org/
I jiggered the music macros from here, https://www.glorioustrainwrecks.com/node/5061, to make the 'loopsound' macro into a thing where I could loop multiple .oggs on passages at 0 volume. Then I could use 'fadeinsound' and 'fadeoutsound' like faders on a mixer - so a passage could fade a stem in, or out. The tracks all looped simultaneously, so it was like one big piece of music, with stems being faded in or out - when you went to the next web page.
This worked for several years - on almost all browsers. It's broken recently. Not sure why. Something to do with how audio files are loaded and browsers changing up their conventions? This Twine code has preload written into it.
Anyway. I was thinking of trying to do rewrite myself, with the audio element. I do not have the chops.
This is where I'm at. So, on the first passage (like a web page), I've got ...
<audio preload>
<source src="c1.ogg" type="audio/ogg">
<source src="c2.ogg" type="audio/ogg">
<source src="c3.ogg" type="audio/ogg">
</audio>`<audio preload>
<audio preload>
<source src="f1.ogg" type="audio/ogg">
<source src="f2.ogg" type="audio/ogg">
<source src="f3.ogg" type="audio/ogg">
</audio>
The 3 cs are supposed to loop in line. And the 3 fs.
On the next passage I have ...
<audio loop autoplay id="c1">
<source src="c1.ogg" type="audio/ogg"></audio>
<audio loop autoplay id="c1">
<source src="c2.ogg" type="audio/ogg"></audio>
<audio loop autoplay id="c1">
<source src="c3.ogg" type="audio/ogg"></audio>
This works. All of these play in line. (Like, not out of time with each other.)
So ...
How do I get them to all loop at zero volume?
How would I then get them to fade in or out at current time - on a new page? (Like, without restarting the track.)
Any help appreciated! Hopefully that made sense. It's a weird, niche project, really.
Thanks!
Meg
Fixed it.
Sort of. In case anyone comes looking for anything this weird in the future.
Couldn't use the audio element at all because each passage is a separate page. Had to rearrange the order of the macros within Twine. I know what I did, but I have no idea how to explain it.
If someone really does come looking for this in the future (probably one of my students - hello), post and I'll try to explain.
PS. Full credit to L for the macro code. I just messed with it. (I just made the loops play at 0 volume and not restart after fadeout. https://www.glorioustrainwrecks.com/node/5061
Related
Using the server-side Node code from here, but for src="data:..." I use fileSystem.readFile(). For troubleshooting/testing, can also use the video in the link on that post. It doesn't actually matter what file I use; none work.
I recently started experimenting with HTML5 video. Everything works correctly on Chrome and Firefox, but Safari has been broken for a few days and I couldn't figure out why until I took some time to look closely at the tags.
I'm using this to stream content into the page in chunks:
<video width="800" height="600" autoplay controls>
<source src="/file.mp4" type="video/mp4;base64">
Not supported.
</video>
It wasn't until I tried this:
<video width="800" height="600" autoplay controls>
<source src="data:video/mp4;base64,(Data)">
</video>
That I noticed the problem. After all, how can you go wrong when embedding the entire file?
As it turns out, Safari automatically turns the second one into this:
<video width="800" height="600" autoplay controls>
<source src="data:video/mp4,video;base64,(Data)">
</video>
I decided to drop the video from my folder into Safari to see the markup it created, and I found something curious: src was in the <video> tag instead of in its own source tag.
For kicks I changed the src tag in the video tag to match the <source> tag and the issue persisted, but instead of a blank white box, it was a black box with a Play button with a diagonal line through it. This suggests that for some reason, Safari doesn't pay attention to <source> tags, while other browsers do.
This was a more concerning issue when I discovered even if the src of the <video> is broken (By having a broken src="data:..."), it still won't check to see if there's a compatible <source>. What's really interesting is that it was paying attention to <source> a few days ago.
Since the <video>'s src had the same issue (,video), I removed the ,video by editing in the dev console and it worked exactly as it should. I attempted to put data:base64;video/mp4, but the issue persisted.
A few other things I tried included removing video/mp4;base64, from the tag entirely, which broke it on all browsers. I put video/mp4;base64 into the type parameter both in the <video> and <source> tags, and it seems those are ignored when the src is data:.
Eventually I tried an image, since those are much shorter load times, and found the same issue: Safari automatically adds ,image to embedded images.
Linked images (<img src="/file.png">) work fine with type="image/png;base64" -- and don't add ,image, while linked videos (<video src="/file.mp4">) doesn't work (And adds ,video).
I thought perhaps this could have something to do with my system not taking byte range into account yet (Per this post)... though this same video, streamed with the exact same code, worked flawlessly the first day I tried it (Call it a week ago).
To make sure I wasn't just missing something, I re-enabled the old snippet (Had a backup) just to see if it'd work that way. No dice.
Although removing ,video and ,image manually works for data: sources, it doesn't work for file sources, as even editing it manually won't cause Safari to re-request the file (When you manually edit data:, you can visibly see it reload the player).
For kicks I tried a couple other thoughts: type="video,mp4" and mp4,video, and the equivalent for src="data:...", all of which also work fine on other browsers, but fail (With an added ,video to the end) on Safari.
For a brief recap:
Video, whether src="file" or src="data:..." becomes broken by Safari's automatic addition of ,video in either src="data:..." or src="file" type="...".
Images break if src="data:..." but not if src="file".
Manual removal of ,image or ,video from a src="data:..." works.
Manual removal of ,video from a src="file" doesn't work.
Video and image both worked fine ~ a week ago with the same (And similar) code.
Video and image currently work on Chrome and Firefox.
Anyone aware of what could cause ,image and ,video to show up, and/or how to prevent it?
Not looking for an external module to work around the problem. Wondering what's causing it and how to prevent it.
I have been asked to use aif audio files on a website. I am using jplayer.
Would there be a noticeable difference using .aif?
Which browsers support .aif?
Would you advise using .aif for the web?
Would it mean I would need 3 versions of each track to cover all Browsers/OS?
Like so:
<audio controls>
<source src="horse.ogg" type="audio/ogg">
<source src="horse.mp3" type="audio/mpeg">
<source src="horse.aif" type="audio/aif">
Your browser does not support the audio element.
</audio>
Thanks :)
The most widely supported format currently is mp3, aiff is supported but you'd need to test target browsers to determine which offer support.
You might also consider SoundJS, a library I helped develop that lets you play audio across a broad range of browsers and devices using a single code base.
Hope that helps.
Check your own browser.
I could not find a comprehensive list like you have asked for. So this is the second best.
I am trying to get mediaplayer.js to autoplay. Autoplay works perfect with the native audio tags but as soon as I implement the mediaelement java script the player works and looks great but will not autoplay anymore.
I've tried various javascript answers, none of which have worked and I have tried changing the autoplay="true" to auto or autoplay or... nothing works. I can't find anything about it on google either. There is a lot about wordpress but none of that seems to apply to non-wordpress scenarios.
The article "Autoplay MediaElementPlayer" said there was a solution but it failed to work for me.
This is my code:
<audio controls="controls" autoplay="true">
<source src="music/male.ogg" type="audio/ogg" /> <!--change song here for FF-->
<source src="music/male.m4a" type="audio/mpeg" /><!--change song here for webkit-->
</audio>
I've tried it in every browser too with no results: IE, Opera, FF, Chrome, Safari etc.
Everything works great except it will not autoplay anymore once the mediaelement javascript works. This is a simple feature of the audio tag. I've tried to implement autoplay in the provided demos and it will not work there either.
Any help would be great, thanks!
I know some might think autoplay is not good practice but my client wants it.
This works partially for me.
It's works for HTML5 but not for flash fallback.
vplayer = new MediaElementPlayer('video');
vplayer.play();
I'm trying to create a mobile ready audio player. However, I'm wondering if it's possible to "mask" the src so that a user couldn't view source and download the mp3. I'm definitely a n00b, so any simple direction would be extremely helpful (IE - use 'x' to do 'y'). I don't necessarily need code examples. Thanks!
Current:
<audio src="unreleased_track01mp3">
...
</audio>
What I'd like:
<audio src="01238134781239871">
...
</audio>
No.
You could attempt to stream the audio, but if you want to play a specific file, the user will always be able to download it if the user is able to listen to it.
I have no choice but to play wav files directly in the browser (serverside encoding to mp3 isn't an option, unfortunately.)
What's the best way to do this? I'd really like to take advantage of the HTML 5 audio tag but my target audience includes many, many teens using IE6. As far as I'm aware flash isn't an option, but speedy playback really is critical.
Thanks.
Nowadays, the best way is probably just to use the HTML5 <audio> tag. In the past, you might have done it like this:
Background:
<embed src="bgsound.wav" hidden="true" autostart="true" loop="1">
On Click:
Play Sound
It's been a few years since the last answer. Embed tag was good but I had an issue trying to trigger it to play in JavaScript. New audio tag works well is most browsers.
<audio src="cat9.wav" preload></audio>
You can trigger it manually with audioElement.play()
<audio controls="controls"><source src="http://blablabla.com/hghghgh/my%20file.wav" type="audio/x-wav" /></audio>
Due to unfixed bug (issue from 2012 year?) sometimes Chromium-like browsers cannot play .wav from redirected URLs because they "think" that file size is zero. But .mp3 is OK.
Opera 12.14 and Firefox play from < audio >
tag normally in the same case (redirected URL).
I tried JPlayer's 2.9.* lib in Drupal 7 with 3 players, but not successful (was black inactive rectangle 300*14 pixels for each player).