SYNTH ZONE
Visit The Bar For Casual Discussion
Page 2 of 3 < 1 2 3 >
Topic Options
#25515 - 01/02/01 12:37 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
dnarkosis Offline
Member

Registered: 01/01/01
Posts: 217
Loc: usa
I hate to rain on your parade, but my XP60 does not exhibit this anomaly, i.e., it does not double any controller data on any channel or track (including aftertouch), nor have I ever experienced timing glitches or problems, and many of my sequences are nothing if not dense. Sorry.

Yes, I'm familiar with the sequencer, microscope mode, etc.; I've been using these sequencers since 1993 (also have a JV1000). I can't get my XP60 to duplicate the controller doubling.

I'm certainly not saying your units don't act the way you describe; I'm just saying mine have not exhibited any of these problems (I also had the XP50 before the XP60).

Top
#25516 - 01/02/01 12:49 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
epu Offline
Member

Registered: 02/20/00
Posts: 466
That's really weird DN. It happened on both of my units including the JV2080 and these units were made within years of each other and have no relation (other than the series).

Are you sure you're checking this right? I've had some other XP/JV owners try this around the way and they got the same results. Maybe this is a US problem only?

Also I thknk the EFX problem is null because even when I bypass the FX processors, I still get the timing problem, it completely disappears when I erase CH16 controller data however.

The Infamous EPU.

Top
#25517 - 01/02/01 01:46 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
dnarkosis Offline
Member

Registered: 01/01/01
Posts: 217
Loc: usa
"Are you sure you're checking this right?"

Well, I know I've never had timing problems, so that's not a matter of checking. I do stagger some events by 1, 2, 3, etc. ticks/clocks if a passage is particularly dense, but I've never done it because I've been prompted by timing delays. I just do it; always have (even on the JV1000, which has some massively dense sequences).

As for the controller doubling, I just went in and recorded about six measures on track one, channel one, just random doodling, pressing down for aftertouch, using pitchbend and modulation, leaning into aftertouch again to get plenty of events. Checked in the microscope: nothing but channel 1 data, everything I had played; nothing from channel 16.

"Maybe this is a US problem only?"

I'm in the US.

So now what? That's why I said that this thread has always puzzled me.

Top
#25518 - 01/02/01 02:08 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
epu Offline
Member

Registered: 02/20/00
Posts: 466
Hey DN. I understand where you are coming from. What I now have o figure out is when this happens. I recorded a couple of tracks weeks ago. When I went in and looked at all of my tracks, they all had doubled controller information.

Today I recorded a couple of tracks and saw no doubled information. Now I'm confused. Maybe this thing happens on certain occasions? Maybe after a sequence of events? I'm really psyched!

I know this happened on my XP50 and has happened a lot on the XP60. I have to look out.

The Infamous EPU.

Top
#25519 - 01/02/01 02:27 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
dnarkosis Offline
Member

Registered: 01/01/01
Posts: 217
Loc: usa
I have no clue; because it is intermittent, though, some parameter *has* to be engaging when it happens. Try going into System and turning your control channel (which I believe defaults to 16) "off", then see what happens. I'll futz around ("futz"?) with my control channel settings and see if it has any effect.

Top
#25520 - 01/03/01 02:37 AM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
Bungle Offline
Member

Registered: 11/23/00
Posts: 54
Loc: Den Haag, The Netherlands
okay, I checked the doubling on an XP30 using Cakewalk 8. Absolutely NO info on channel 16. So perhaps the problem is corrected in the xp30. However, the first thing, as Dnarkosis said, this problem reminded me of was the controller channel parameter. I have noticed the parameter being switched back to it's original value (16) automatically. Very strange.... so maybe these problems are interrelated.
maybe it's a sequencer problem. Perhaps your sequencer is independantly doubling the info because both sequencer and JV/XP unit are trying to direct the info to a channel.

furthermore I experience very frequent timing problems especially when two or more program changes are sent on different channels and when there are lots of controller data events like pitch bends sent.

Top
#25521 - 01/03/01 06:12 AM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
epu Offline
Member

Registered: 02/20/00
Posts: 466
Rememeber when using Cakewalk that you have to check every track for channel 16 info, especially since it won't show up on channel or rtack 16 since all tracks can contain any channel.

I don't know what's up, but I'm pretty sure that it's got to be something like this. I've never had any problems with timing on my XP60 and that was my original point, so I never understood this arguement about MIDI timing, am I one of the few that never experienced it?

The Channel 16 thing was to provide a solution to some accidental MIDI slop that may occur giving the impression of bad timing, but it isn't. And last night I recorded a track 1 and there was channel 16 info on track 1 in the micro window, and this time the control channel parameter was set to OFF.

Maybe it's the Y3K bug - Lol!!

The Infamous EPU.

[This message has been edited by epu (edited 01-03-2001).]

Top
#25522 - 01/03/01 11:52 AM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
fvicente Offline
Member

Registered: 01/25/99
Posts: 149
Loc: Port Moody, BC, Canada
The MIDI timing issue was definitely there (at least on the JV2080). I owned a JV-2080 for a year. Shortly after getting it home, I noticed it and it would drive me bonkers at times.

Over time, I got used to it and took steps to compensate for it so it would be noticeable in my tracks. At the time, I sold another module to get it so it's not like I could return it to the store (or I would have). I now have the XV-5080 and it is better timing wise. There are some OS issues still on it but it is definitely better in terms of MIDI timing.

Fernando

Top
#25523 - 01/03/01 03:48 PM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
Totty Offline
Member

Registered: 08/19/99
Posts: 35
Loc: Farncombe
Thanks Fernando,

I'm glad someone else out there agrees! The 2080 was a pain in the ass. At the time I loved it and hated it at the same time. Im very pleased with the 5080 though-despite the sample load and save stuff having a few problems, but Im not using that part of it-yet.....

Top
#25524 - 01/04/01 02:10 AM Re: The JV2080, JV1080, XP50, XP60 & XP80 Bug - Here's how to correct MIDI timing.
Stephane Offline
Junior Member

Registered: 10/19/99
Posts: 3
I can't understand how a JV-2080 can suffer from the problem described by EPU, namely doubling the MIDI information on channel 16 (in particular for aftertouch). The 2080 is a module: it doesn't produce aftertouch at its MIDI out (but is able to receive aftertouch info at its MIDI in). If EPU noticed some weired MIDI information at the "output" of a JV-2080, it might be because this information was already present in the input MIDI stream...

Top
Page 2 of 3 < 1 2 3 >

Moderator:  Admin 



Help keep Synth Zone Online