@eight

It works for most people with exactly the same machine as you.

These were some other softwares installed on someone else's machine that perhaps could affect things. It would be great if you checked your system report for these:

Kernel Extensions
libusbdmxshield
MobileIOAudioDriver
OlympusDSCSCSIDriver
SophosFileProtection
SophosPortInterceptor
SophosWebProtection

Preference Panes
Java
LanRev Agent
YAMAHA-USBMIDIPatch
Squeezebox

Do you have any of these?

Best Wishes,
Mark

@tomthebom

on line14 change textureLod to texture2D.

@crystalhorizon

I have downloaded both and a third one.

Best Michel

@barneybroomer This is because SDI only works with SMPTE standard resolutions, not VESA ones (like 1024 768). Any convertor box that outputs SDI and lets you input any screen setting (not just size but also specific timed refresh rates) are scaling and retiming you image and in general messing with it. You can check out the SMPTE standards here:

https://en.wikipedia.org/wiki/...

https://en.wikipedia.org/wiki/...

@dbini The problems you experienced getting the SDI signal in can easily come from having either the wrong colour space inside your SDI signal or by using the wrong level 3G SDI, there are 2 common ones, SDI level A and level B, they dont mix, lots of gear can auto switch but a lot does not.

@DusX this http://vb-audio.pagesperso-ora...

@Fred
Interesting. Thanks

@gomer_pyle

Do you mean something like this...

You could try the 'pulse generator' with a 'sound frequency watcher' and calibrating as appropriate.

Using an audio input and "sound Frequency Watcher' to jitter a video in response to sound frequency. The Sound Frequency Watcher provides a frequency for the 'Pulse Generator'. The Pulse Generator triggers 'Random' node actors at various speeds dependent on the frequency of trigger inputs. The Random numbers are limited using the 'Limit-Scale Value' before input to a 'Pan/Spin/Zoom' node actor. A 'Warp' node actor is added for additional disruption before the video is routed to the output 'Projector'. Audio node actors interact with the OSX system using 'Soundflower' to route the audio into Isadora's 'Live Capture Settings'. It is in the Live Capture Settings that a checkbox allows 'Sound Frequency Analysis'. Checking Sound Frequency Analysis allows the Sound Frequency Watcher node actor to respond to the audio file in the patch. You need to work all the sound inputs out and remember the Sound Frequency Analysis check box.

cheers
bonemap

@barneybroomer

Yes it appears the software download link is no longer easily accessible through the internet. Here is a copy of the LCEdit software package 3.4.5 March 2012 - the last update I downloaded and the last update of the software by Lanbox as far as I know.

https://www.dropbox.com/sh/5sh...

cheers

bonemap

Just a little update:

As mentioned above, this is the mobo I think I will be using;

https://www.asus.com/uk/Mother...

It has it's own onboard graphics; HDMI, DP, DVI, etc but packs enough punch to be used with all the other components I need. 

@mwasser - thanks for the information - it looks like this might be a good option - i shall investigate your links and report back. i use SoundJack for realtime audio - its worth checking out if you want a low-latency, high quality audio stream to a specific IP.

John

Hi,

If you're trying to send OSC from Isadora, as you stated, I don't understand the example "code" you wrote.

Just get the IP adress of your device running Lemur, and the osc address Lemur is listening to, like "/textaddress".

Fill the following infos in the isadora OSC Transmit actor, and then you can send your text in the "value" field.

@DusX

Thanks. I don't recall what happens to live input video when using snapshots - perhaps it is unaffected? I think it is time to get the dancer in for some testing.

cheers
bonemap 

The input values are saved the same as all actors inputs in Isadora. I suspect you might be experiencing the fact that if you have a Set globals actor in multiple scenes, updating one will not update the others, and they will in fact Set the values when you enter that scene.

A great way around this behaviour (which can be useful at times) is to Put your Set actor inside an User Actor, and update it so that all instances of the User Actro update throughout your project. 
This is much like the practice of putting Projectors with mapping inside a User actor, so that updating the mapping once will update thoughout the project.

@DusX

There is a thought - i will have a look at the mapper although i have the assumption it will be difficult to integrate into separate scenes and transitions. - thanks for the insight Ryan.

cheers,

bonemap

@DusX

I finally just cut and pasted the elements into a new scene and they worked fine, so I'm wondering if there was something having to do with a competing set of fades I may have accidentally made between the scenes--one in the jump actor and one in the scene transition panel at the bottom of the frame. I'll pull in the Trigger Delay actors and make things simpler as well

Thanks!

@DusX any idea of an ETA? I'm building a big mapping project starting mid august that runs a month. It would be great to get ahead with some new features...

@Fred said:

@Skulpture D3 uses blue fish capture afaik

 Forgot about BlueFish; I think they do now use them yes. 

As Mark has mentioned, scaling before measuring is your best choice. 
I have found that scaling by an even factor seems to work best... so divide the width and height by, 2, 4, 8, or 16 etc... until its small enough to allow a good framerate.
You could also, try adding a 'multi blocker' before scaling, and limiting the frames thru.
A 'time' setting of 0.08 for the MultiBlocker will give a framerate of 12.5 fps thru  [ (1 / (25 / 2)) where 25 is your isadora target framerate ]
Half as many frames to process. This will help, but adds some latency.

@eratatat

Can't be sure without having the hardware. I know that often you must connect these cameras to independant USB hosts (many machines only have 1).
If you can connect to separate USB hosts that may help. (on my laptop, I have 1 usb host that connects all my USB ports, except for 1.. I have 1 that is a USB/Esata port and it has a different controller.)

Right, thanks a lot! I've redesigned the monitor set up slightly as I reached a dead end with what I was doing. CCTV camera signal and signal from computer is anyway different type. Did a workaround with putting all cameras on one monitor and now sending signal from my computer to the other ones.

@Fred I had a look at the roland v1hd, looks great, no budget for it I'm afraid.