Hi all,

So, here's the software:

• Windows 7
• Pure Data-extended 0.41.4
• Nuendo 5.5
• LoopBe 1

Here's my goal:

• Use 4 toggles in Pd to solo 4 individual audio tracks in Nuendo

Progress so far:

• Successfully setup "Generic remote" in Nuendo. It recieves MIDI messages from my Arturia MIDI keyboard. When I press the keyboard notes:
  "C" (address 12), Audio track 1 is soloed
  "D" (address 14), Audio track 2 is soloed
  "E" (address 16), Audio track 3 is soloed
  "F" (address 17), Audio track 4 is soloed
  This is all working nicely over my RME babyface MIDI port.

• I now need to replace this MIDI keyboard (hardware) with 4 toggle buttons in Pd (software). I have LoopBe1 installed as my internal MIDI connection, and I can select this as the output port in Pd and as the input port on Nuendo.

Problem:

• Despite the correct MIDI ports being selected in both Pd and Nuendo, when I try to send MIDI messages from Pd.. absolutely nothing happens in Nuendo. I've tried using [ctlout] and [noteout] with no luck.

• I think the problem is either incorrect use of [ctlout] or [noteout]. Or the LoopBe1 virtual MIDI connection is not working (or a combination of both).

I hope I explained clearly enough! Any feedback would be much appreciated.
(And I have already trawled the internet for relevant forums/discussion, and so far I've found no solution from these).

Please check out my screen shots of Nuendo setup and Pure Data setup.
Any questions, please ask!
Thank you.

http://www.pdpatchrepo.info/hurleur/pd_MIDI_test.png

Hi all,
I'm pretty experienced with PD, though only just started to use the GEM side of things.

Here's what I have:
Layered geomtrical shapes (sphere, some cones and circles), which together resemble a dummy head. This is all working nicely, with the sphere at the top of the hierarchy. This means rotating the sphere rotates everything else. All well and good.

Separately, I've also successfully got my internal webcam linked to the GEM window, using the very simple:
|gemhead|
|
|pix_video|
|
|pix_texture|
|
|rectangle|

Here's what I'd like:
Layer the two together (geometry and internal webcam), with the option of mixing them such that you can see both of them.
I believe the geometry stuff needs manipulating before being inserted into pix_mix, but I have no idea despite a fair few hours and google searching.

Does anyone have ideas on how to mix pix_video with geometry, using the pix_mix object?

Many thanks for your time,
Oggy

Hi all,
Sorry if this is the wrong section to post, but it seemed the most appropriate place.

I'm not sure if there's a solution to this (very simple) problem, but wanted to check.
So I understand how to open a subpatch via pd message:
|; (
|pd-nameofsubpatch vis $1(

At the moment, I control the argument $1 using a radio button, which outputs either a 0 or 1. This works nicely as an Open/Close object for the subpatch.

What would be useful for me is to receive the current Open/Close status of a subpatch. For example, imagine the subpatch is already open, however the subpatch window is large and takes up the full screen. It's therefore less convenient to move the subpatch to be able to click on the aforementioned radio button and close it.
It's much more convenient to simply click the red cross on the subpatch window - however this does not then make the corresponding change to the radio button (so it still says "Open" even though the user closed the subpatch).

So is there a way to receive information on the Open/Close status of a specific subpatch? If I can receive this info, it's obviously then trivial to alter the state of the radio button.

Thanks in advance for your time.
Oli

Hi,

This is my first post so would be good to hear what you think.
Improvements/adjustments are welcome.

Not intended/expected to replace iTunes or anything, but I designed it as a means to test multiple loudspeaker setups...

• The patch plays the audio files in a pre-determined order
• Custom routing is available (i.e. you can route each audio file to a different output)
• The idea is that you hit play, and audio file plays.
  For example, Track 1 plays: "Surround Left speaker", Track 2 plays: "Surround Right speaker" etc... Assuming you have routed it correctly, each track is played out through the correct speaker.
  Custom routing is not required, of course. The patch works just fine for a single dac~ output.

I have used many comments inside each sub patch to help explain what is happening, however any questions are welcome and thoughts for improvements etc...

Enjoy!

http://www.pdpatchrepo.info/hurleur/pdTunes.pd

Hi,

This is my first post so would be good to hear what you think.
Improvements/adjustments are welcome.

Not intended/expected to replace iTunes or anything, but I designed it as a means to test multiple loudspeaker setups...

• The patch plays the audio files in a pre-determined order
• Custom routing is available (i.e. you can route each audio file to a different output)
• The idea is that you hit play, and audio file plays.
  For example, Track 1 plays: "Surround Left speaker", Track 2 plays: "Surround Right speaker" etc... Assuming you have routed it correctly, each track is played out through the correct speaker.
  Custom routing is not required, of course. The patch works just fine for a single dac~ output.

I have used many comments inside each sub patch to help explain what is happening, however any questions are welcome and thoughts for improvements etc...

Enjoy!

http://www.pdpatchrepo.info/hurleur/pdTunes.pd

Ok, thanks for info shawnb.
I decided to ignore MIDIOX, for the simple reason that I have everything working as intended with LoopBe (though I should note I'm now using LoopBe30, not LoopBe1).

Furhtermore, my DAW is a 64bit Nuendo 5.5

Cheers

Problem solved!

I won't bother explaining as it seems no one else is having the same problem (plus it would take a fair amount of time).
But, please write here if this problem applies to you and I will be happy to show how to solve it.

Thanks for the input so far.

Some progress made:

• The LoopBe connection is definitely working
• I created 4 MIDI tracks in Nuendo, set the input port to "LoopBe":
  MIDI 01 has Channel 1 as input
  MIDI 02 has Channel 2 as input
  MIDI 03 has Channel 3 as input
  MIDI 04 has Channel 4 as input
• I then used [noteout] in Pd to send messages to these MIDI tracks, with LoopBe set as the MIDI output port.

Problems:

• The MIDI messages are definitely received by the MIDI tracks in Nuendo.
• However, when I send a MIDI message, this is received by ALL MIDI tracks in Nuendo.
• For example, I send the list [12 127 1 ( to [noteout] and MIDI tracks 1, 2, 3 and 4 ALL show input. I would expect only MIDI track 1 to receive input.
• If I then change the list to [12 127 2 ( , the same thing happens. So, how do I send MIDI messages to be channel specific? According to the help file of [noteout], this should be the last argument of the list... i.e. [12 127 $3 ( should send a MIDI message with the following properties:
  Note number = 12 (this is a "C" note on a MIDi keyboard)
  Velocity = 127
  Channel number = $3

So, either my use of [noteout] is incorrect, or the Nuendo MIDI track input setup is wrong. I can't see the mistake in either case.

Any experience or ideas would be much appreciated.
In the meantime, I will keep searching for the problem.

Many thanks!
oggy

Gromit,
I already checked it out, but unfortunately MIDI-OX only works upto Windows XP... not for Windows 7.
At least, that's what their website says...

thanks for the reply susz0n..
I'm actually not new to Pd - I've got a lot of experience with it (including MIDI). However, no experience with internal MIDI routing.
I'm currently in the process of re-installing Pd to the latest version and I will test the MIDI connection (like you said) tomorrow morning. Then I'll report back here with the result.

Cheers!

here's the Nuendo screen shot.

http://www.pdpatchrepo.info/hurleur/Nuendo_MIDI_setup.png

@Joe: thanks for your response. The additional bang inside the subpatch is an option I hadn't thought of.. I guess if I coloured it red and placed it in the top right corner it would be quite convenient.

@maelstrom: Thanks.. I'll look into this tomorrow.

Cheers,
Oli