Topic: newbie questions : tranzport + window7 x64 + CPU

Hi,

@eincande wrote:

– I must be a little “slow” but i cannot manage to control play/record etc from my tranzport “mackie compatible” control surface. The green midi indicator flashes all right, but nothing moves. I made the necessary settings but it just don’t do anything at all ? 🙁

Just checking: In the interfaces dialog, enable the MIDI input AND the MIDI output that the tranzport is connected to. Select the tranzport MIDI output in the list, and then select the “Detect Mackie…” option for that output. If the device is 100% MCU compatible, then that should do it. I don’t have a Tranzport so I can’t test if this device behaves differently.

– I have red that Podium works flawlessy on window 7 x64 with x32 vst plugs. is that confimed ? as cubase doesn’t even do it, i would find that pretty cool 🙂

Podium is currently only available as a 32bit application, so it will work only with 32bit plugins. Once I’ve made a x64 version of Podium, then that will only work with 64bit plugins. I’ll probably integrate support for the jBridge converter, which then will allow any Podium version to use any 32/64 bit plugin:
http://jstuff.wordpress.com/jbridge/

– In your opinions, how can you compare CPU load with Podium over Cubase 5 ?

I haven’t compared with Cubase 5, but the user feedback I’ve received says that Podium does ok in CPU comparizon tests.

@eincande wrote:

Can i provide you with info (log file ?) that would make you track down the tranzport issue ? maybe record a midi track with midi message correspondig to start/stop/Etc ?

the control is MCU compatible but i don’t know if it is 100%. but start stop should work at least 😉

I’ve looked at my source code for the MCU support, and I think I’m going to revise it very soon. The problem is that it currently requires the MCU device to respond to MIDI SysEx messages to identify the device. I think that is why it won’t work with a lot of the so-called “MCU-compatible” devices. I’ve received reports that Kore2 and Zoom R16 doesn’t work either. These devices probably only support the non-sysex messages that are used for button presses and fader movements etc. The SysEx messages are primarily for updating the MCU LCD display etc. With a bit of luck, I’ll have this working for Podium 2.28 or 2.29.

– about x64 : does podium user multicore ? i need to handle large project if a close future and i would like to get rid of cubase + i need to adress more ram (samples banks, like always :).

Podium supports multicore. To make use of RAM beyond the 3GB limit (which is the limit for 32bit applications), you can use the jBridge converter. I haven’t yet tried jBridge myself, but from what I’ve read then EACH plugin wrapped in the converter can use up to 3GB.

– Can you export all tracks to indiviual wav file ? (sending all session to protools) with or without effects ?

You can by using the bounce feature. If you have bounced all the individual tracks, then there already are bounced wave files in the project folder. You also have an export option in the bonce menu. In the bounce menu you can also specify whether it should bounce before or after effects.

The features in the 2.28 release was implemented based on user requests, so it was not on my original plan. This means that 2.28 and maybe even 2.29 won’t have the improvements to the Mackie support. Sorry about that.