Now here's the problem: I only listen to a small part of audio on the base layer before I click on a layer and gradually move through all 5 layers. I then move on in the module. When I revisit the interactive slide, my seekbar is stopped where the audio on the base layer was stopped and displays the Play icon, yet the audio and video for the last-viewed layer is currently playing. Because the seekbar/timeline is showing the Play icon, I can't pause the audio on the layer. When I click the Play icon in an attempt to pause the audio on the layer, it actually creates a double audio - playing both the base layer and the continued audio of my layer (and now the seekbar starts to move as the base layer is played).
Hi Greg, yes your summation is correct. It's an interesting and frustrating issue for sure. I don't want to remove the seekbar (which would be a simple solution) because I want to allow the user to pause the audio as desired. Any help that you can provide would be greatly appreciated.
I came up with a workaround. Before I try to explain it, just have a look at the attached .story file, and see if that makes sense. Basically, you can manually program Storyline to display the correct timeline for an already-open layer when revisiting a slide.
Good idea Meryem! I've added a trigger to each layer to hide the layer when the user clicks Next. It works like a charm to avoid the double audio the first time a user returns to that slide. Of course, after reviewing the slide the user will probably use the menu to change slides and thus by not clicking Next, won't hide those layers. The double audio problem then returns if the user returns to that slide a 3rd time. However, that's probably a low, if not rare, occurrence.
You can eliminate the bug completely if you make the "Hide Layer" triggers activate when the timeline for the base layer starts (instead of when the user clicks the "Next" button). That way, no matter how the learner navigated away from the slide, the layers will hide when the learner revisits the slide.
Note that the "... when timeline begins" trigger does not care where on the timeline the seekbar is. When a slide is loaded, any "... when timeline begins" triggers attached to the base layer will attempt to activate.
Hi, I am not sure if my issue is exactly the same as the above, I have a base layer with audio and when entering this slide (and before playing the base layer) an slide layer is playing. First visit is working ok but on revisiting base layer and slide layer play at the same time.
Another issue, i would like to solve here, is that i want to prevent the user from clicking the next button for going to the next slide (and this way skipping the audio in the base layer) when the slide layer is playing.
The dropdown menu option to change my audio from stereo to dual mono has suddenly disappeared in FCP 10.5.4. In a previous thread it was suggested the problem is likely that it is a synch clip container. The suggestion was to go into the synch container and change the audio there.
Hello, quick question. The Tab S6 Lite is supposed to have dual audio Bluetooth right? From what I read it's available on all of the recent devices with Android 10 and Bluetooth 5.0. The Tab S6 has it as far as I know, and it's not on the list of the Lite's restricted features. So why don't I have the little checks in the 'Media' menu to activate two devices at the same time?
I am also looking for tablet with dual audio support to use specifically to play music via two different Bluetooth receivers in connected rooms. It works with my Samsung S20 but I am looking for a cheaper tablet alternative for this, I have tried a cheap Lenova tablet with BT 5.0 but that does not give the option for dual audio output. The Tab S6 Lite would be max I am willing to spend on this solution, but from Taupi's post it seems like S6 Lite might not support dual audio. Can anyone confirm please?
Yes, a dual(or more) Bluetooth audio output support is a definitely needed. It will be amazing to share audio with friends without being noisy for the surroundings, just like old times when 3.5mm splitters were available.
Dual audio was one of my favorite features on Samsung Galaxy devices. Nice to be able to share a podcast or movie audio with my girlfriend on flights/trains. Is it possible to roll this out via SW update? Or does it require additional Bluetooth antennas in the device?
Nothing should see through the matter that every little detail makes a Phone stand apart from others. Whole time I was thinking that my Phone (1) has Dual Bluetooth Audio support but after getting here I am now kind of embarrassed.
While doing my deep research on atx, to really understand how this technology works. I struggled to identificaing targets based on audio tones. Yes, I know that Pi machine has poor ability for recognition targets. But while motion mode provides dual tone audio feedback, I keep wondering about message that provides me. That scale of tones may varying from hi/low to low/hi and that is my question. If tone starts with very short low tone with long hi tone echo, what I can predict about target material? And otherwise. If target get you short hi tone followed by long low echo, may I assume that the long echo tone assigning the target to the scale of material corresponding to the tone? So if I get short low tone followed by long hi echo, target response should be somewhere close to low conductive material? Even if the complete audio response is low/hi indicating good conductor?
How the iron check actually works? Can I use it to helping identificaing targets, even if they are not iron. I have noticed that if I swing over for example pulltab in Iron check mode, it does not make any difference(off course it did not), but when the audio is non existent in Iron check, what that can tell me?
Before You ask why I decide for atx ( If you dont know Iam a begginer) I am also motorcycle enthusiastic and my condition for packing are limited, so this is numero uno for me, and offcourse the military housing just ring a bell for me.
A low/high signal only means "large/strong target" and high/low means "small/weak target". The tones correspond exactly with other dual tone PI detectors like all the Minelabs and the Infinium, as it is a byproduct of the dual channel ground balance system. The flip point between the two signals is determined by the current ground balance settings, but tends to end up somewhere in the region of a zinc penny when in bad ground. Just where depends on the exact ground and ground balance setting. In mild ground it could be far different. I need to experiment more with that, plus determine where the default setting is at.
The TDI and Fisher Impulse, as single channel models, have a simpler tone arrangement, either low, or high. However, the basics are the same. I wrote an extensive article on all this, referencing all my previous articles, for those that want to delve into how to use a ground balancing PI detector to discriminate items. The secret is knowing that is not about target composition so much as it is about target size and conductivity, with ferrous on both sides of the scale, small on one side, and large on the other. So small gold / low conductors and small ferrous read the same. Large ferrous and most coins / high conductors read the same.
Read the article I linked to above, and also the links it provides for details. Ultimately, the only way to learn is to use the detector while paying close attention to the tones, and using the iron check, and digging all targets found, for 50 - 100 hours of detecting.
perfect for the volcanic islands (you can go hunting for jewelry on the beaches at 1 meter deep, it's super discreet lol) and it is as powerful as a gpx 6000 (and even better on very polluted terrain)
I came across an artice about how is done Gbpi detector with no detection hole. There was written article about pairs of frequencies that reapet in order to exclude the detection hole. Each of these frequencies must be different from the other one, it make sense to me. But I want to ask you. It is the defference between them only in khz or is it something else?
795a8134c1