Daisy-chaining within an LMS

I am trying to run a web based training I created with Captivate 2 in a Meridian Global LMS. I created the WBT in segments (daisy chaining them together so that the end of one jumps to the beginning of the next). When I upload and try to make the parts work together in the LMS only the first segment works. I am exporting the Captivate files as SCORM 1.2-compliant. Has anyone been successful in getting daisy-chaining of Captivate files to work in a SCORM-compliant LMS?

Daisy-chaining files in an LMS is bad practise and will almost certainly result in failure. I bet that you have each of the daisy-chained files set to report to SCORM as well so it would probably reset and restart SCORM communication every time it loads a file.
Instead you should create a multiple SCO SCORM manifest. Since you are using CP2 you can only do this manually by using a third party tool such as Reload. If you have the eLearning suite from Adobe they have a "SCORM packager" included that could do this for you.
/Michael
Visit my Captivate blog with tips & tricks, tutorials and Widgets.

Similar Messages

Yet another question on daisy chaining...

After having thoroughly sifted through prior discussion on the subject, as well as looked at the online tutorial (gooberguides) and other sources, I am compelled to come back and ask this question. This is Captivate 5.
Here is my scenario, and it seems to be quite simple. I have a large project, which I want to break up into smaller ones. This is so that users don't have to sit and wait for it to load from the LMS before they can start. I need to have SCORM reporting, so that users can leave and come back to where they were. I don't think I can resolve this using Multi-SCO Packager, as the resulting package doesn't appear as a single module, but as several modules within a single package. Aggregator wouldn't quite work, since it forces that TOC, which I don't want to have.
One more wrinkle in the whole thing is that I have my own TOC, which is on the first slide of Module no. 2, to which I have a link from most other (subsequent) modules.
I have successfully daisy-chained all of this using the online guide mentioned above. I used 'Open URL or file'. At first, I tried pointing to the SWF file for the next module, but when I deployed the final package, my browser (Firefox) wanted to download the next module, instead of playing it back in the browser window. Pointing to HTML file resolved that. My links back to the Module 2 (TOC) work fine. It took me a while to figure out why none of the linking wouldn't work at first. It only started working when I removed spaces from file names (this I couldn't find anywhere in documentation, and stumbled upon by myself).
My only problem (a deal breaker) is with SCORM tracking. When I publish with reporting turned on, the following happens: first module plays back throughout (all five slides). At the end, it loads the second module. However, when second module starts playing, it either freezes on load, or skips right past first 5 slides and starts playing from slide no. 6. This is telling me that the LMS is treating this as if the user has closed the session after reaching slide 5, then immediately re-opened it, so the LMS is sending him straight to slide 6, except this is now Module 2, and not Module 1. Meanwhile, user has never touched anything and has actually never left the session. Sure enough, if I leave the session at, for example, Module 2, slide 7, when I come back, LMS will be stuck trying to load Module 1, slide 7 (which doesn't exist; my Module 1 has only 5 slides).
So, apparently, simple daisy-chaining doesn't work well with SCORM reporting. Meanwhile, Aggregator (and Multi-SCO Packager) aren't doing it for me, as they force TOC to show individual modules.
Does anyone have any ideas how to work around these obstacles?

Copy the ENTIRE iTunes folder from the old computer to the new computer.
Open iTunes, everything in iTunes should be exactly as it was on the old computer.
Connect the device and sync.

Fw800 daisy chain problems - crashing MBP

I just had two massive crashes on a 6-month old MCP with new external FW800 drives daisy-chained. The first crash happened when I tried to hook and "old" (5 years) FW400 hard drive within the daisy-chain of newer FW800 hard drives. The second happened when all 3 of my new (8-months old) FW800 drives were connected: one of the drives just spun its wheels and never showed any data. After shutdown / reboot it's ok - but there are 1.3TB of info on it.
Questions: How many FW800 drives can you daisy-chain out of the one FW800 bus on a MacBook Pro?
Or is it a length of cable issue? Or is hooking up the older FW400 into the chain the problem?
I researched online and found multiple posts that said you can daisy-chain Sixty-Three hard drives. This sounds impossible and unbelievable given what I have just experience with THREE hard drives.

The problem is that this could be tough to troubleshoot if it is a power supply, as the offending drive will attempt to pull the juice it needs to keep running from the FireWire bus.

Daisy chain isp to MP then out ethernet 2 to wireless hub possible?

hello
I have a 2 x 2.66 GHz macPro and am running 10.5.7
I have 2 ethernet ports in the back of my unit.
and I would like to run the internet into port one.
then daisy chain port to to my wireless hub. (a D-link dl-524)
I know this is a little unorthodox
but there seems to be an odd transfer issue when I go the other way (from my d link to my mac first)
and I need a nice clean signal and thought this may be the best way to go.
so any advice on setting within my network prefs?
thanks

the way I have it now is I have the ethernet going directly into my MP
then what I want is to use my second ethernet port as an out to my d-link so I can
go wireless with the same connection.
I don't want to do it the other way as for some reason it "dirty's" up my signal when I go into
the D-link then into my MP
does that make sense?

Audio Distortion on FW400 Audio Interface Daisy Chained to FW800 Hard Drive

Hi everyone! I’m an experienced Mac user in need of help resolving FireWire device issues.
I received my 27” i7 iMac a couple of weeks ago running 10.6.2. After a long process of migrating over from my 9+ year old Dual 500 MHz G4 PowerMac tower, I was excited to set up two 1TB drives inside an OWC Mercury Elite Quad-Interface Dual HD enclosure via FW800. I then daisy chained my Focusrite Saffire 10 audio interface (FW400) to the HD enclosure via a FW800 to FW400 converter cable. To reiterate:
i7 iMac (FW800 port) --> OWC Mercury Pro Quad-Interface Dual HD Case with 2X 1TB drives (FW800) --> Focusrite Saffire 10 audio interface (FW400)
Although a lot of people may disagree, I wasn’t concerned about having my FW800 hard drives drop down to FW400 speeds because of the slower audio interface. I have read enough about the 1394 FW protocol and its ability to use something called beta clouds, allowing both FW400 and FW800 daisy chained devices to operate at their maximum speeds. So far, so good. The drives are reading/writing data fast.
As many studio audiophiles have said, you should separate your audio recordings and projects from your startup disk. I’ve done so. However, call me naïve, but I did not imagine that every time my external drives read or wrote data, my audio interface would go into a state of distortion (like raising the gain on a track as high as it can go). When the activity of the disk drops below a certain level, the audio interface usually switches back to clean pristine audio. I am experiencing this within a studio environment and with simple CoreAudio iTunes playback via my audio interface. How is this possible? Am I doing something wrong or is there a blatant limitation with the FW chipset Apple is using for their single bus in the new iMacs? If anyone can provide me with a solution or a convenient work around, I will be very grateful!

Thank you for the feedback, Rick. To shed some light on daisy chaining FW800 with FW400 devices, I provide the following quote from one FireWire technical article I came across on the web:
+"The concept of beta clouds allows FireWire to keep all devices on the bus to operating at their maximum speeds. Devices are cluster together on a logical level in a cloud. The cloud operates as a single block at 800 Mb/sec. The borders of these clouds are where legacy devices are connected, operating normally. Each device operates at its highest speed."+
In short, beta clouds allow both devices to operate at their highest speeds.
Both the audio interface and the external hard drive enclosure has its own, connected power source.
I wish I had the option to use USB2 with my audio interface, but it only has a FW400 connection.

I have a MBPro mid 2013 with 1 Thunderbolt port. Just bought a Mac monitor and want to daisy chain a PC monitor to it. Use a Mini DVI to VGA adapter from MBP to PC monitor. How do I daisy chain the 2 monitors?

I have a MBPro mid 2013 with 1 Thunderbolt port. Just bought a Mac monitor and want to daisy chain a PC monitor to it. Use a Mini DVI to VGA adapter from MBP to PC monitor. How do I daisy chain the 2 monitors?

Hall Palm Desert,
if your Mac monitor has Thunderbolt ports, and the PC monitor is on the end of the daisy chain, then you might be able to do it by connecting your PC monitor’s VGA cable to a Mini DisplayPort-to-VGA adapter (e.g. Apple, NewerTech), connecting that cable’s Mini DisplayPort end to one of the Mac monitor’s Thunderbolt ports, and then connecting a Thunderbolt cable between the other port on the Mac monitor and your MacBook Pro.

Camera not recognized unless daisy-chained with external HD

I just bought a LaCie 250GB external FW drive to use as a scatch disk for FCE. Now my camera (Sony DCR-HC30) is not recognized unless I plug it into the LaCie. I borrowed a second camera (Panasonic), swapped the FW cable while the camera and HD were plugged into separate FW ports, and the Panasonic was immediately connected in both iMovie (v4) and FCE. I've tried the suggested fixes (unplug, Garageband, swap ports, new cable...) and the problem remains. I upgraded memory, QT and applied several patches prior to attaching the HD. Any suggestions? Can I live with the daisy chain arrangement or will that cause problems importing to the external HD? (I've not tried to import any video yet). Thanks

Can I live with the daisy chain arrangement or will that cause problems importing to the external HD?
Yes and No, respectively.
(That's what I always did before getting an internal 200GB hard drive in my iMac.)

Daisy chain monitor from cinema display MacBook Air 5,2

I know the Mid-2012 MacBook Air is capable of 2 external displays as described here.
The monitor works when plugged directly into the MBA, but not when daisy chained from the back of the cinema display.
It's a dell monitor, and I'm using an Apple Thunderbolt-VGA adaptor.
Is there something I'm missing? Thanks!

As far as my question itself -- why does this happen? Has anybody had this issue on Lion and had it resolved on Mountain Lion?

Can I daisy chain 30" apple monitor to thunderbolt HD on macbook pro?

I have a 30" apple monitor plugged into this adapter: http://foliovision.com/2009/12/apple-dual-dvi-mini-displayport-adapter-mb571z that in turn is plugged into the thunderbolt port as well as one USB port on my 2011 macbook pro i7.
I want to buy a Lacie Big5 thunderbolt RAID system, but I only have one thunderbolt port. will i be able to daisy chain the monitor to the thunderbolt RAID?

I don't want to assume that it will work because it a little bit different on the Retina. All of the 2012 line of MacBook’s utilize the same thunderbolt controller which does support 2 displays and 4 10Gbit/s data (even the MacBook air 11" can support 2 external monitors and it's own display). But i think that the controller is hardwired for each port meaning each port only has 2 10Gbit/s data and 1 display. I haven't been able to confirm this because I don't have 2 thunderbolt displays and i was wondering if anyone has tried this. The reason why I ask is because I'm doing research on all of the new MacBook’s and their Thunderbolt controller.

Thunderbolt daisy chain problem with display

Hi to everybody,
being a proud new user of a thunderbolt audio interface Apollo Quad since a couple of days i am struggling to set it up without trouble for my secondary display in my Thunderbolt daisy chain...
My setup and connections
MBP Late 2011 17" 16GB RAM running Mavericks and UAD SW 7.11, 1 Thunderbolt port
Promise Pegasus R4 Thunderbolt RAID drive
Apple TB display
Second 26" display connected via DVI/Mini display port adapter
Erverything worked like a charm prior to inserting the TB audio interface with a Thunderbolt 2 Card into the TB daisy chain. Order of TB connections: MPB -> Apple TB display -> TB Audio interface -> Ext. display via DVI to TB connector.
Since putting the audio interface (Apollo) in the TB chain Apollo itself, TB display and Pegasus RAID run fine - but the last display behind Apollo only shows "invalid mode" blinking on the display. I tried changing the order of the devices, no change.
Has anyone an idea what to do?? - I have not exceeded the max number of TB devices (6) allowed to run in sequence. I read here in the forum that an ext display behind Apollo should work and has proven to do so. It has the new option card for TB2 inserted... Does the left/right port matter, which is connected to the display?
Thanks in advance for any help to get that sorted out!! The last option would be to go remove the TB card and run the Apollo per firewire as I need the second screen.. not the most convincing solution for me though.
Regards
Uli

Hi Ilya,
I am curious why it only happens for one particular Process Chain. Normally displaying a log has nothing to do with the client settings of SCC4 and/or system settings of SE06. My only guess is that it might be created in this system directly and that the system wants to modify anything here.
I am quite sure that the system is "closed" and it's not a Development system, e.g. a Production System. Please confirm.
Anyway, I have one suggestion and that is to check the Object Changeability in the Transport Connection. Go to t/code RSA1, choose the Transport Connection view and click on the push button Object Changeability.
Here you can see a list of Object Types like RSPT (Process Chain Starter), RSPV (Process Variants), PSPC (Process Chain). If it is set to "Not Changeable", I suggest to change that in e.g. "Everything Changeable".
Please try that with the above mentioned Object Types for Process Chain related Object Types and see if you are able to display the log w/o the pop-up.
You can also refer to SAP Note 337950 - Queries (including objects) cannot be edited for more information.
Thanks,
Sander

Daisy-Chain Thunderbolt Monitors

I have been having a lot of issues since purchasing two new thunderbolt displays. I mounted both displays on my office wall via VESA brackets. I was super happy with how they looked and how they were able to Daisy-Chain together making them the most beautiful full function docking station for my MacBook Pro. I hooked up my mac via the single thunderbolt cable and power cord from monitor 1 and turned on my Mac. As expected the two monitors came to life in dazzling fashion giving me 54in of usable space. My issues began after I disconnected my Mac to go to a meeting. When I returned and reconnected the power and thunderbolt cords and after the usual blinking of the monitors only the Mac and monitor number 1 worked. Monitor 2 (the one daisy-chained to number 1) would not turn on, 27in of blackness. I tried reconnecting, changing the order of the displays, rebooting, and even re-imaging; nothing worked. I Googled it and found a lot of issues that people were having with displays and thunderbolt drives but none offered a solution that worked. after a lot of research I was able to piece together what was happening and a fix that actually worked. The issue is the Thunderbolt ports and they way peripherals get assigned. So the first time I connected the monitors they worked great but when I went to a meeting and connected to a projector or went home and connected to my single thunderbolt monitor there the ports would get reconfigured to run the single monitor or projector. Macs use SMC (System Management Controller) to control many low level functions like lights, fans, power button, and ports. http://support.apple.com/kb/HT3964 Following the SMC reset fixes the port assignment issue and allows the Mac to recognize the daisy-chained monitor or drive. One additional tip is to plug in the power and thunderbolt cable before resetting the SMC. it is a simple keyboard procedure that is easy and works every time. I hoping a firmware update of SMC will make this fix obsolete but until then at least my $2500 display investment is paying off in a lot of beautiful useable space.

Please do not double post - it does not help and things can get very confusing, so I've asked the hosts to remove the duplicate.
Good luck!

Thunderbolt Daisy Chain to a DisplayPort Monitor (Dell 2713HM)?

I have a Mac mini (2011) that supports my Dell monitor (2713HM 27'') at its maximum reslution of 2560x1440 only through a Thunderbolt to Mini-Displayport cable. As this Mac has only Thunderbolt as a fast connection for backup drives I have to add a Thunderbolt chain with the backup device in the middle and the Dell monitor at the end of the chain if I want bakcups faster than Firewire 800 or USB 2.0 (the other possible connections with this Mac). My first attempt with such a setup was the LaCie eSATA Hub. But this does not feed the display signals through, the monitor stays black. Checked in the store with a genuin Thunderbolt monitor from Apple the daisy chain worked.
Can my chain work at all? Is only the Lacie the wrong drive hub? Would it work with a Seagate Desktop Hub, for instance STAE122 or STAE 127?
Can I trick the Mac under Bootcamp as OS to use HDMI for the monitor? Dell officially says that the monitor can only accept 1900x1080 over HDMI, but some have fiddled wth different computers with custom settings that worked with some Monitors but mostly under Linux and to Dell 2711.

TechnoMax wrote:
for instance STAE122 or STAE 127?
FWIW, STAE129 is the current version TB adapter
that is self powered and has TB daisy chain port.
STAE122 and STAE127 are older versions and
not the current model, though there may be stock of
these around. As to whether this will solve your issue,
I don't know.
Can I trick the Mac under Bootcamp as OS to use HDMI for the monitor? Dell officially says that the monitor can only accept 1900x1080 over HDMI, but some have fiddled wth different computers with custom settings that worked with some Monitors but mostly under Linux and to Dell 2711.
The MacMini HDMI port is hardware limited to 1980x1200.

Has anyone been able to use an Apple Thunderbolt to FireWire to daisy chain a dozen or more FireWire drives?

Ever since I realized that I was not able to connect my FireWire daisy chain to my brand new Retina MBP there has been problems. Four months down the road, I am still unable to use my FireWire drives and have experienced terrible problems whenever I connect my FireWire daisy chain to this new Mac.
I have bought two of these adaptors from Apple now and both do the same thing. The daisy chain has been working perfectly for years with my older MBP and still does! There are no problems until I connect to the new Mac.
I have 15 various hard drives in NewerTech and DatOptics enclosures for over 22 TB. When connected to the new Mac, I would have multiple apps just hang, sometimes just Apple apps, sometimes 3rd party. I will not be able to force quit them and they will keep relauching as you can watch them in the Force Quit window. The Finder will hang and there is no relaunching it. I am having to do a force shutdown twice an hour which leaves no time for work!
After four months of this, now I am being told that Apple will buy back my Mac at full price. But I have basically lost the good part of four month’s worth of work because of constantly fighting the new Mac. This is cost me all my savings and I am about to lose a client. It certainly seems that releasing Thunderbolt1 was a huge, huge mistake.
Does anyone know of any large Fire Wire daisy chain working with Thunderbolt?
TIA,
R

Yes, my first post is all about how darn iffy the adaptors are and I have two of them to return now.
I question your answer because I am betting that four drives that are in one enclosure NOT all RAIDed together as one drive, but as four separate drives that those four drive will count as four devices. The daisy chain that I had going had eight drives in TWO quad boxes, four drives in TWO dual drives and another drive in a single enclosure. A total of five “devices” if you will, but also a total of 13 drives that were usually in this daisy chain.
Both of the Apple branded Thunderbolt to FireWire adaptors chocked BIG TIME on this and it works no problem on my older MBP. You basically can not use a new Mac when you are connected to a daisy chain like this!
Just checked the Apple website and indeed, I can get a new MBP with FireWire 800, just not with the Retina display! I wish that I would have known this five months ago before this all started!

Daisy chain two display port monitors (Dell U2913WM) to new Mac mini Thunderbolt?

Everything I read said that I could hook up a display port monitor to a Thunderbolt port on the mac mini. I purchased two display port monitors (Dell U2913WM) that can be daisy chained, and hooked them up. All I get is mirroring. Does anyone know how to turn off mirroring with this setup? I did not get the "uncheck mirroring" option in preferences until I hooked up the second via the HDMI port instead of a daisy chain. The problem with that is, I cannot take advantage of the full resolution through the HDMI. It seems I have wasted my money on two monitors.
Looking for advice on:
1) How to daisy chain these two Dell monitors to the mac mini and turn off mirroring and use an extended desktop, or
2) How to take advantage of the full resolution through HDMI port?
Any help would be greatly appreciated.
Thanks!

So re-reading this thread, I now realize you did exactly what I wanted to do but your issue was having a cloned vs. extended desktop. Oops!
I believe your "nothing plugged in" issue is the cable. I'm not sure that TB cables are backwards compatible with DP - I think it's only the ports. Do you see multiple monitors in "System Preferences > Displays" if you hook the monitors up like you described in your OP?
My Dell U2713H arrived today and it works like a charm with the supplied Mini-DP to DP cable. The built-in display on my 13" mid 2009 MBP still works if not in clamshell mode, although I will mostly use mine in my HengeDock. In the OSD of the monitor, you can access "Display Settings > Display Info" and it will show you the DP capability. Mine is only DP 1.1a and I believe to run 2 of these at full resolution you will need the bandwidth in DP 1.2 which includes MST (daisy-chaining). This could be your problem.
Can you access the same menu in your OSD and report back what your DP compatability is?
Thanks!
mgb

Can I daisy chain a DisplayPort-only monitor through the 2nd TB connector on a WD 8TB My Book Thunderbolt Duo to a mid-2011 Mac Mini?

I'm very tempted by a refurb HP Smartbuy ZR2740w 27" WQHD display, but it doesn't have a HDMI port. It does have DisplayPort.
Since the mid-2011 Mac Mini I have has either HDMI or Thunderbolt to choose from, plus I've just bought an external TB storage system, I think I'd need to connect the monitor to the second TB port on the external TB storage and hope that the external storage would pass the DisplayPort signals along.
I've read that DisplayPort connections are compatible with TB ports on Macs, and that you can daisy chain TB devices.
I don't want to assume those statements hold when I'd need to connect the DisplayPort cable to the 2nd TB port on the external storage.
Anyone know if this will work?
Is it "supported"?
Thanks!
Andrew

23. How do I connect my Mini DisplayPort monitor or monitor using a Mini DisplayPort adapter to my Thunderbolt-equipped Mac when I have other Thunderbolt devices connected?
When connecting a Mini DisplayPort display or a display using a Mini DisplayPort adapter to a Thunderbolt peripheral (except as described in question 24), make sure the display is connected at the end of the Thunderbolt chain. You can use only one Mini DisplayPort device in the Thunderbolt chain.
Note: Systems with more than one Thunderbolt port, like an iMac, can have more than one Mini DisplayPort monitor or monitor connected with a Mini DisplayPort adapter connected as each Thunderbolt port can support one Mini DisplayPort display.
24. Can I connect my Mini DisplayPort monitor or monitor using a Mini DisplayPort adapter to my Apple Thunderbolt Display?
Mini DisplayPort Monitors or Monitors connecting with Mini DisplayPort adapters will not function when connected through a Thunderbolt Display. They must be connected directly to the Thunderbolt port on the computer or to a non-display device as indicated above.
from
http://support.apple.com/kb/HT5219#23

Daisy-chaining within an LMS

Similar Messages

Maybe you are looking for