Zynewave's Forum Page

@kyran wrote:

Your explanation made me think.

Jack has a transport control as well. If you set it to playback, the transport in podium starts functioning.

All the other apps I tried didn’t really need this. I don’t know why I didn’t try this before. I’m feeling kind of stupid here now. 😳

edit:
I tried beta 5 and it there is no change. Exactly the same behaviour as before, so you can put the check back in.

Hitting play in jack transport before you start working in podium fixes it though. I’ll put this in bold on my soon to be written FAQ 🙂

Great. I am not familiar with Jack, so I didn’t know that transport functionality was something that should be configured. I’ll revert my ASIO code back to the way it was before.

@kyran wrote:

I’ve saved it as a txt file here:

http://files.getdropbox.com/u/464948/PodiumReport.txt

Let me know if you need something else.

Thanks. From the report:

ASIO driver status:
– ASIO sample position gaps: 6503 (-512)

That’s the problem. 6503 buffers * 512 sample buffer size / 44100 ~= 75 seconds of non movement, which is the exact duration of the interval measured in the report.

I checked the wineasio 0.7.4 sourcecode that you linked to, and it appears to set a valid sample position, provided that the jack_transport_query() function works as expected. I see that the sourcecode is a little experimental around this call. There is an outcommented “// if (ts == JackTransportRolling)” line, which could indicate that it is not working. The wineasio changelog also mentions a fix for the jack transport in the 0.7.3 wineasio release.

If you have other hosts that work with wineasio, then it must be because they ignore the sample offset provided by the ASIO driver. I’m checking the value in Podium, because some drivers may use this offset to indicate if buffer over/underruns have occurred. I’m not fond of compromising this security check because of faulty drivers, but I’ve added some code that ignores the sample offset if it is zero. Please try the 2.19 beta3 or the 2.19 final release and let me know if this fixes the wineasio issue.

@moikkelis wrote:

So, it’s a line indicating the end of the arrangement?

Well, my english sucks, so decide to make little video. (it hosted by my own website, 100% safe. It is direct link, no audio in videos)

Thanks for the videos. That’s a very efficient way of illustrating feature requests and bugs. I like the idea with the vertical guide lines when dragging events. I’ll keep that in mind for a future update.

What program are you using for the screen capture?

@moikkelis wrote:

Can you take a look about this freeware

http://www.acusticaudio.net/modules.php?name=Products&file=nebula3free

(You need to download those librararies as well)

I rly like it, however its crash podium alot. Also it cause very very high cpu spikes. Keep hitting 100%. 😥

I downloaded Nebula3 and both libraries. I managed to get one crash, but only when using two instances of N3. Try and disable the “enable plugin multiprocessing” option in the Podium preferences, and see if this gets rid of the crashes. I only get CPU spikes when I change presets in the N3 editor. As far as I can tell, that’s because the plugin loads the samples from disk in the audio processing call, and thus blocking the Podium audio processing. Not much I can do about that.

Second thing, can you make this thing in podium. I think it would be “easy” to do..? That vertical line at the end. When you zooming far this would help alot putting clips right place.

It is very useful 😀

So, it’s a line indicating the end of the arrangement?

@moikkelis wrote:

However i have now problem. Sometimes if i move super fast notes on pianoroll its messing up pretty bad. Like 5 or more notes keep playing and it wont stop until i stop podium engine.

Any clue?

A common problem referred to as “hanging notes”. Make sure the notes you entered in the editor don’t overlap.

Edit; Oh boys.. i think i am very stupid person 😳 i look that manual couple times and i still dont get it. So i have to ask it.. How i can automate my jp’s knobs? Like filter cut off? Sorry for being so dumass 😳

If you have imported one of the “Generic xxx Instrument” definitions from the “import hardware definition” menu, then you should have a set of MIDI CC parameters in the parameter panel on the track where you assign the Roland device. You can consult the manual of the jp-8000 to find which CC number is used for controlling filter cut-off. Or you could just start recording, turn the cut-off dial on the synth, and Podium should then create a parameter track.